| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stuart Bishop <stuart(dot)bishop(at)canonical(dot)com> |
| Cc: | Mark Shuttleworth <mark(at)ubuntu(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-06 17:19:25 |
| Message-ID: | 14772.1175879965@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2007-04-06 18:27:15 | Re: What X86/X64 OS's do we need coverage for? |
| Previous Message | Joshua D. Drake | 2007-04-06 17:12:59 | Re: Auto Partitioning |