Re: UNLISTEN bug

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;
> >
> > 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?

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.  :-(

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +