From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: UNLISTEN bug |
Date: | 2010-09-22 17:04:50 |
Message-ID: | 201009221704.o8MH4og09531@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Jeff Davis wrote:
> In honor of the very first bug report I sent to postgresql more than 10
> years ago regarding UNLISTEN[1], I have decided to submit another
> UNLISTEN bug (against HEAD):
>
> Session1:
>
> LISTEN foo;
> BEGIN;
> UNLISTEN foo;
>
> Session2:
>
> NOTIFY foo;
>
> Session1:
>
> SELECT 1;
> COMMIT;
> SELECT 1;
>
> I seem to recall testing out similar situations during my review of this
> patch, but I think the code has changed since that time.
So the problem report is? I tested it and the problem is that the final
SELECT 1 hung. Is that the problem?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-09-22 17:06:35 | Re: UNLISTEN bug |
Previous Message | Tom Lane | 2010-09-22 17:03:06 | Re: BUG #5669: server process was terminated by exception 0xC0000005 |