| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Magnus Hagander <mha(at)sollentuna(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] Function to kill backend |
| Date: | 2004-07-25 20:23:36 |
| Message-ID: | 410416C8.8010804@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
>>Would you use a kill operation in the way you describe above
>>if you knew
>>that it had, say, a 1% chance of causing a database-wide PANIC
>>each time
>>you used it?
Seems there's the need for some connection killing functionality. If
it's not present, the whole cluster needs to be shut down, which makes
it unavailable with 100 % chance.
If there's a .00001 % chance it *corrupts* the cluster, the function is
not acceptable. But iff it's a good chance to keep the cluster running,
it's worth having it (and should be used sensibly).
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2004-07-25 20:58:01 | [subxacts] Savepoint syntax |
| Previous Message | Dave Page | 2004-07-25 18:03:32 | Re: [HACKERS] Function to kill backend |