Tom Lane wrote:
>Dru <andru@treshna.com> writes:
>
>
>>I am running of postgresql database servers with generally 30-50 users
>>at a time per server. I have noticed one thing for web based databases
>>that they fail to initialse a pg_connection connection every now and
>>again and return no error message at all.
>>
>>
>
>That's fairly hard to believe. I don't know of any failure paths that
>won't log some traceable result *somewhere* --- if nothing gets returned
>to the client, try looking in syslog or stderr output (you're not
>sending postmaster stderr to /dev/null I hope), or at worst look for a
>core dump file.
>
> regards, tom lane
>
>
I've spent ages going though logs and turning debugging to max. There is no
error message returned at all. The connection handle is returned as NULL.
This is in the php functions though so their pg_last_error() function may
not be catching all error messages but it seems it should pass on every
error. It is just really weird. The weirder thing i find is the fact it is
doing this a lot more often while backups are running than when they arn't
running. 80% of the time when it is reported by users a backup is running
at the same time.
