| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alfred Perlstein <bright(at)wintelcom(dot)net> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: 7.0.2 dies when connection dropped mid-transaction |
| Date: | 2000-11-10 01:18:59 |
| Message-ID: | 2685.973819139@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Alfred Perlstein <bright(at)wintelcom(dot)net> writes:
> I have a program that does a:
> DECLARE getsitescursor CURSOR FOR select...
> I ^C'd it and it didn't properly shut down the channel to
> postgresql and I got this crash:
> ...
> These sources are the current CVS sources with the exception of
> some removed files by Marc.
I tried this on my copy of 7.0.3:
test7=# begin; declare c cursor for select * from foo;
BEGIN
SELECT
test7=# fetch 1 from c;
f1
----
1
(1 row)
[kill -9 on the psql process from another window]
test7=# Killed
The postmaster log shows
pq_recvbuf: unexpected EOF on client connection
and no sign of a crash. So there's more to this than just killing
a client that has a cursor. Can you provide a more complete example?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kevin O'Gorman | 2000-11-10 01:24:25 | Tip of current tree: Seg fault in query |
| Previous Message | Alfred Perlstein | 2000-11-10 01:17:35 | Re: 7.0.2 dies when connection dropped mid-transaction |