Jeff Davis writes:
> The bug is pretty simple: ProcessIncomingNotify() is called in a tight
> loop in EnableNotifyInterrupt() while notifyInterruptOccurred is true.
> EnableNotifyInterrupt() is assuming that ProcessIncomingNotify() will
> unset it, but it has an early return that's triggered by my
On Wed, 2010-09-22 at 13:06 -0400, Bruce Momjian wrote:
> To confirm, it was majorly hung. Cancel and kill did not work, pg_ctl
> -m fast did not work either. I had to kill -3. Bad. :-(
Yes, that was the problem. I believe the fix is simple, however.
If there had to be a problem with in 9.0.0
Bruce Momjian wrote:
> 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;
>
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;
>
> Se
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
