Re: elog(FATAL) vs shared memory
| От | Tom Lane |
|---|---|
| Тема | Re: elog(FATAL) vs shared memory |
| Дата | |
| Msg-id | 14772.1175879965@sss.pgh.pa.us обсуждение |
| Ответ на | Re: elog(FATAL) vs shared memory (Stuart Bishop <stuart.bishop@canonical.com>) |
| Ответы |
Re: elog(FATAL) vs shared memory
Re: elog(FATAL) vs shared memory |
| Список | 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 по дате отправления: