Re: elog(FATAL) vs shared memory

From: Mark Shuttleworth <mark(at)ubuntu(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stuart Bishop <stuart(dot)bishop(at)canonical(dot)com>, pgsql-hackers(at)postgresql(dot)org, Martin Pitt <martin(dot)pitt(at)ubuntu(dot)com>
Subject: Re: elog(FATAL) vs shared memory
Date: 2007-04-07 07:37:07
Message-ID: 46174A23.7010404@ubuntu.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Stuart Bishop <stuart(dot)bishop(at)canonical(dot)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 ...
>
Ah, that could explain it. With the recent patches it seems to be
working OK, but I guess we should find a more standard way to rejig the
db during the test runs.

Mark

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2007-04-07 08:50:39 Re: Eliminating unnecessary left joins
Previous Message Bruce Momjian 2007-04-07 04:23:53 Re: UTF8MatchText