From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | felix(at)crowfix(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: 7.3.2 closing connections, sometimes |
Date: | 2005-07-06 19:10:40 |
Message-ID: | 29527.1120677040@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> felix(at)crowfix(dot)com wrote:
>> This is a SOAP server, Apache with mod_perl, connecting to Postgres
>> via DBI/DBD::Pg. Sometimes it gets in a mood, for want of a better
>> term, where a specific SQL statement fails with the good ole message
>> "server closed the connection unexpectedly". It will fail like this
The specific statement being what exactly?
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> This message is from the backend exiting abruptly. Is isn't an "ERROR"
> as we define it for logging purposes. That's why there is nothing in
> the logs.
Nonetheless I'd expect there to be at least a postmaster complaint about
a crashed backend --- assuming that that's what's going on. Do the
other active connections get forcibly closed when this happens?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tino Wildenhain | 2005-07-06 19:13:58 | Re: Scripting Functions to Separate Files |
Previous Message | Tom Lane | 2005-07-06 19:04:44 | Re: Transaction id wraparound questions |