Re: debugging pg_connect
| From: | John DeSoi | Date: | Sun, 29 Apr 2007 15:06:18 +0000 |
| Subject: | Re: debugging pg_connect | ||
| References: | 1 | Groups: | php.db |
| Request: | Send a blank email to php-db+get-43508@lists.php.net to get a copy of this message | ||
I suspect that PostgreSQL would log anything related to a network connection problem if the error logging level was set correctly.
If you don't see any of those perhaps it is a networking issue. You might need to try an ethernet capture tool like Wireshark or perhaps something like tcpflow.
John
On Apr 26, 2007, at 4:26 AM, pobox@verysmall.org wrote:
Hello, since we upgraded to the latest php and PostgreSQL - we started to get frequent pg_connect() errors. What is sure is that they are not caused by insufficient connections - PostgreSQL reports 100 connections available and less than 10 used when the pg_connect fails. pg_last_error() and the other error handling functions operate on connection. So they do not seem useful when pg_connect() fails. In the PostgreSQL documentation I could find out how to log successful connections, but not how to login failed connections. Could somebody advice me on possible ways to test?John DeSoi, Ph.D. http://pgedit.com/ Power Tools for PostgreSQL