From: | Peter Eisentraut <e99re41(at)DoCS(dot)UU(dot)SE> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Changes in 7.0 |
Date: | 2000-02-24 13:04:52 |
Message-ID: | Pine.GSO.4.02A.10002241400260.17421-100000@Hummer.DoCS.UU.SE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 23 Feb 2000, Bruce Momjian wrote:
> Here is my list of 7.0 changes. Please let me know of any changes I
> should make to it.
> 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? With everyone requesting longjmp's
at the last minute, I had to disable ^C during COPY.
--
Peter Eisentraut Sernanders vaeg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-02-24 13:08:42 | Re: [BUGS] First experiences with Postgresql 7.0 |
Previous Message | Peter Eisentraut | 2000-02-24 12:51:40 | Re: GNU make (Re: [HACKERS] Re: [PATCHES] Patch for more readable parse error messages) |