Re: How to release locks

From: Jim Nasby <decibel(at)decibel(dot)org>
To: Andrus <eetasoft(at)online(dot)ee>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: How to release locks
Date: 2006-03-23 17:37:03
Message-ID: 36226A35-78A8-41B8-A662-E8635CFB58FB@decibel.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


On Mar 22, 2006, at 7:14 PM, Andrus wrote:

>> Do you mean that the statement hadn't been fully transmitted yet?
>
> Yes. Sending 2 MB takes most of time so client is terminated in
> this stage.
>
>> If so, the backend would have just been waiting for the rest of the
>> statement to arrive. Perhaps you're looking at some sort of
>> network bug
>> that caused the backend not to be told that the connection was lost.
>
> If so why pgAdmin Cancel command does not terminate the process ?
> If process
> is waiting for data,
> Cancel signal sent through pgAdmin should terminate process
> immediately.

If pgAdmin's cancel is just dropping the connection, the server might
take some time to notice it, especially if it's in the process of
running a query and doesn't have reason to talk to pgAdmin.
--
Jim C. Nasby, Database Architect decibel(at)decibel(dot)org
Give your computer some brain candy! www.distributed.net Team #1828

Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jim Nasby 2006-03-23 17:41:07 Re: how to update structural & data changes between PostgreSQL
Previous Message Michael Schmidt 2006-03-23 17:07:25 Re: partial resultset in java