On Tue, Jan 4, 2011 at 2:47 PM, Bryce Nesbitt wrote:
> Michael Glaesemann wrote:
>> Likely you're looking for pg_terminate_backend().
>> Michael Glaesemann
>> grzm seespotcode net
>>
>
> Hmm, yes. Though it seems to not be in the documentation, or, for that
> matter, the current code:
8.4+
--
On Jan 4, 2011, at 17:29, Bryce Nesbitt wrote:
> Should I expect pg_cancel_backend() to work in a case like this? If not does
> this sound like a reportable bug?
pg_cancel_backend() cancels the running query for that backend. In the case of
, there is no running query for that backend.
Likel
Michael Glaesemann wrote:
On Jan 4, 2011, at 17:29, Bryce Nesbitt wrote:
Should I expect pg_cancel_backend() to work in a case like this? If not does
this sound like a reportable bug?
pg_cancel_backend() cancels the running query for that backend. In the case
of, there is no runnin
Dear helpful postgres people;
I've got a database deadlock. The initiating process was " in
transaction" with PID 2219.
Use of pg_cancel_backend() returns true, but does not actually kill the
process.
When this happens I kill the PID at the Unix level, which feels sort of
stupid, like drivi
