| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, Magnus Hagander <mha(at)sollentuna(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Function to kill backend |
| Date: | 2004-04-06 19:34:57 |
| Message-ID: | 660.1081280097@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> If there is a problem, maybe we can fix it, or perhap have the kill
> function use SIGINT, then wait for the query to cancel, then SIGTERM.
Well, if someone could prove that the SIGTERM path is equivalent to
a transaction-aborting error followed by normal client disconnect,
I'd feel a lot better about its reliability. We know those two code
paths work well.
Right now I do not think they are equivalent, but maybe they could be
made so.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-04-06 19:36:35 | Re: Function to kill backend |
| Previous Message | Chris Browne | 2004-04-06 19:34:08 | The Tomb of the Unknown Type? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-04-06 19:37:37 | Re: Function to kill backend |
| Previous Message | Andrew Dunstan | 2004-04-06 18:39:01 | Re: [HACKERS] logging statement levels |