Re: [HACKERS] Changes in 7.0 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] Changes in 7.0
Date
Msg-id 21685.951406923@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] Changes in 7.0  (Peter Eisentraut <e99re41@DoCS.UU.SE>)
Responses Re: [HACKERS] Changes in 7.0  (Peter Eisentraut <e99re41@DoCS.UU.SE>)
List pgsql-hackers
Peter Eisentraut <e99re41@DoCS.UU.SE> writes:
>> Allow ^C to cancel COPY command (Massimo)

> That's cool, but if you look closely, psql doesn't do that (anymore). :(
> Is it safe to send PQcancelRequest in a copy state and then just forget
> about it? What's the correct behaviour?

For a COPY OUT (from the backend), the correct behavior is same as for
non-copy state: fire off the cancel request and then forget about it.
If the backend decides to honor the request then it will terminate the
copy in the usual way.  For a COPY IN, it's up to you to stop sending
data...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] Out of memory problem (forwarded bug report)
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] Re: [BUGS] First experiences with Postgresql 7.0