| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Josh Kupershmidt <schmiddy(at)gmail(dot)com>, Sergey Konoplev <gray(dot)ru(at)gmail(dot)com>, Steph L <engel306sl(at)yahoo(dot)fr>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: How to disconnect a single user in Postgresql 8.2.5 from a database |
| Date: | 2010-04-20 14:58:10 |
| Message-ID: | 28207.1271775490@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> On Tue, Apr 20, 2010 at 7:31 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
>>> So, pg_cancel_backend(pid) is the 8.3 version, that may or may not
>>> always work then, right?
>>
>> No, I didn't say that.
> Well, my experience with it has been that it's similar and it doesn't
> always work.
pg_cancel_backend might or might not always succeed in canceling a
query, if that's what you mean. What I'm worried about with SIGTERM'ing
an individual backend is negative side-effects, like hanging the entire
database. Before 8.4 there was never any attempt to ensure that that
would work nicely, and if memory serves we did find some problems when
we tested it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2010-04-20 15:25:07 | Re: drop database / create database / data still here ? |
| Previous Message | Scott Marlowe | 2010-04-20 14:55:49 | Re: How to disconnect a single user in Postgresql 8.2.5 from a database |