On Wed, Jul 06, 2005 at 03:10:40PM -0400, Tom Lane wrote:
> > felix@crowfix.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?
select it.id, it.it_class_id, it.it_code_version_id,
it.it_data_version, it.note, it_class.class, it_class.id,
it_code_version.version, it_code_version.id, it_class.id,
it_code_version.id from it join it_class on (it_class.id =
it.it_class_id) join it_code_version on (it_code_version.id =
it.it_code_version_id) where class = ? AND version = ? AND
it_data_version > ?
> Bruce Momjian <pgman@candle.pha.pa.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?
Haven't had any others open, it's a dev system. But I'll try leaving
a psql session open. Right now it's gotten itself into the mood of
always working, so it might have to wait a while.
Could a corrupt db cause these mood swings? And if so, would that
persist even across dropdb / creatdb?
--
... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.
Felix Finch: scarecrow repairman & rocket surgeon / felix@crowfix.com
GPG = E987 4493 C860 246C 3B1E 6477 7838 76E9 182E 8151 ITAR license #4933
I've found a solution to Fermat's Last Theorem but I see I've run out of room o