Re: elog(FATAL) vs shared memory - Mailing list pgsql-hackers

From Tom Lane
Subject Re: elog(FATAL) vs shared memory
Date
Msg-id 14772.1175879965@sss.pgh.pa.us
Whole thread Raw
In response to Re: elog(FATAL) vs shared memory  (Stuart Bishop <stuart.bishop@canonical.com>)
Responses Re: elog(FATAL) vs shared memory  (Mark Shuttleworth <mark@ubuntu.com>)
Re: elog(FATAL) vs shared memory  (Stuart Bishop <stuart.bishop@canonical.com>)
List pgsql-hackers
Stuart Bishop <stuart.bishop@canonical.com> writes:
> After a test is run, the test harness kills any outstanding connections so
> we can drop the test database. Without this, a failing test could leave open
> connections dangling causing the drop database to block.

Just to make it perfectly clear: we don't consider SIGTERMing individual
backends to be a supported operation (maybe someday, but not today).
That's why you had to resort to plpythonu to do this.  I hope you don't
have anything analogous in your production databases ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Auto Partitioning
Next
From: Andrew Dunstan
Date:
Subject: Re: What X86/X64 OS's do we need coverage for?