| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Terminating a backend |
| Date: | 2008-03-10 19:13:35 |
| Message-ID: | 20164.1205176415@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> I am suggesting we add a new fuction pg_terminate_backend() that does
> everything just like cancel, but also sets a global variable that we
> check in the loop where we look for the next command and if it is set,
> we exit the backend.
And if you never *get* to that loop, what have you accomplished?
Keep in mind that 99% of the excuse for people to want to use SIGTERM is
that the backend isn't responding to SIGINT. If you've fixed things so
that SIGTERM cannot get them out of any situation that SIGINT doesn't
get them out of, I don't think it's a step forward.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-03-10 19:18:19 | Re: Terminating a backend |
| Previous Message | Peter Eisentraut | 2008-03-10 18:32:32 | Re: Detecting large-file support in configure |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2008-03-10 19:18:19 | Re: Terminating a backend |
| Previous Message | Bruce Momjian | 2008-03-10 18:22:20 | Re: Terminating a backend |