| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
| Cc: | Magnus Hagander <mha(at)sollentuna(dot)net>, 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-26 03:52:38 |
| Message-ID: | 18470.1090813958@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
Andreas Pflug <pgadmin(at)pse-consulting(dot)de> writes:
> If there's a .00001 % chance it *corrupts* the cluster, the function is
> not acceptable.
See my response to Dave Page just now. Not only wouldn't I give you
those odds today, but I don't think we could ever get to the point of
saying that session kill is that reliable, at least not from our
ordinary methods of field testing. It'd require significant focused
code review and testing to acquire such confidence, and continuing
effort to make sure we didn't break it again in the future.
If we had infinite manpower I'd be happy to delegate a developer or
three to stay on top of this particular issue. But we don't :-(
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-07-26 04:36:13 | Re: [HACKERS] Function to kill backend |
| Previous Message | Tom Lane | 2004-07-26 03:46:28 | Re: [HACKERS] Function to kill backend |