Re: Bug #436: backend closed the channel unexpectedly - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Bug #436: backend closed the channel unexpectedly
Date
Msg-id 26333.999615436@sss.pgh.pa.us
Whole thread Raw
In response to Bug #436: backend closed the channel unexpectedly  (pgsql-bugs@postgresql.org)
List pgsql-bugs
pgsql-bugs@postgresql.org writes:
> Using Postgresql 7.1.3 on Redhat 7.1 and 6.2, currently we have 2
> projects running. a few days the databases do work perfectly - then we
> get error message following.

> Warning: PostgreSQL query failed: FATAL 1: This connection has been
> terminated by the administrator.

This message indicates that the backend got a SIGTERM signal from
someplace.  If the postmaster got a SIGINT signal it would turn around
and SIGTERM all the backends, but there's no other mechanism in Postgres
that would cause this to happen.

Is the postmaster still alive after the backends shut down, or does it
quit too?  What shows up in the postmaster's stderr log?  (If you're
sending stderr to /dev/null, now is a good time to stop doing so.)

            regards, tom lane

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: Build problem with CVS version
Next
From: Tom Lane
Date:
Subject: Re: postgresql v7.1.3 bug report