| From: | Daniel Farina <daniel(at)heroku(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pg_terminate_backend for same-role |
| Date: | 2012-03-20 08:38:52 |
| Message-ID: | CAAZKuFZ1_6p_zE2esf12-jkT++TZFiauDkCs7448EtrxMVrGuw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Mar 15, 2012 at 9:39 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Fri, Mar 16, 2012 at 8:14 AM, Daniel Farina <daniel(at)heroku(dot)com> wrote:
>> Parallel to pg_cancel_backend, it'd be nice to allow the user to just
>> outright kill a backend that they own (politely, with a SIGTERM),
>> aborting any transactions in progress, including the idle transaction,
>> and closing the socket.
>
> +1
Here's a patch implementing the simple version, with no more guards
against signal racing than have been seen previously. The more
elaborate variants to close those races is being discussed in a
parallel thread, but I thought I'd get this simple version out there.
--
fdr
| Attachment | Content-Type | Size |
|---|---|---|
| Extend-same-role-backend-management-to-pg_terminate_backend.patch | text/x-patch | 2.7 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hitoshi Harada | 2012-03-20 08:44:18 | CREATE DOMAIN json vs built-in json |
| Previous Message | Daniel Farina | 2012-03-20 08:35:58 | Re: Cross-backend signals and administration (Was: Re: pg_terminate_backend for same-role) |