Re: Cancelling Requests Frontend/Backend Protocol TCP/IP - Mailing list pgsql-general

From Tom Lane
Subject Re: Cancelling Requests Frontend/Backend Protocol TCP/IP
Date
Msg-id 24308.1257172680@sss.pgh.pa.us
Whole thread Raw
In response to Re: Cancelling Requests Frontend/Backend Protocol TCP/IP  (Craig Ringer <craig@postnewspapers.com.au>)
Responses Re: Cancelling Requests Frontend/Backend Protocol TCP/IP
Re: Cancelling Requests Frontend/Backend Protocol TCP/IP
List pgsql-general
Craig Ringer <craig@postnewspapers.com.au> writes:
> On 2/11/2009 5:15 PM, Raimon Fernandez wrote:
>> If for example I send  a SELECT * from myTable, it has 20000 rows, and
>> postgre starts sending the rows, how I can cancel this operation ?

> Assuming you're asking "is there any way to cancel a running query using
> the postgresql tcp/ip protocol" then, as you've noted, you can cancel
> the request until you start getting data.

> After that, you can still cancel the query by establishing another
> connection to the server and calling pg_cancel_backend( ) at the SQL
> level. This does, unfortunately, involve the overhead of setting up and
> tearing down a connection and the associated backend.

The above distinction is nonsense.  Query cancel works the same way
whether you have started receiving data or not --- it will open a
transient connection in any case.  Otherwise there would be race
condition problems if the backend is just about to start sending data.

            regards, tom lane

pgsql-general by date:

Previous
From: Grzegorz Jaśkiewicz
Date:
Subject: Re: [PERFORM] Problem with database performance, Debian 4gb ram ?
Next
From: Tom Lane
Date:
Subject: Re: Error on compile for Windows