Re: NOTIFY does not work as expected

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Andrey <parihaaraka(at)gmail(dot)com>
Cc: Pg Bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: NOTIFY does not work as expected
Date: 2018-07-03 00:37:21
Message-ID: CAMkU=1ytid9NHkLpOyu9bgLb47L34WX+KQnfU8KmQGAOAFJ_Zg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jul 2, 2018 at 4:33 PM, Andrey <parihaaraka(at)gmail(dot)com> wrote:

> PostgreSQL 9.6.9, 10.4 (broken):
> A: listen test;
> A: select pg_sleep(5);
> 1
> 2
> B: notify test, 'test1';
> 3
> 4
> 5
> A: done
> 6
> 7
> 8
> 9
> B: notify test, 'test2';
> A:
> * notification received:
> server process id: 2837
> channel: test
> payload: test
> * notification received:
> server process id: 2837
> channel: test
> payload: test2
>
> PostgreSQL 9.6.2 and earlier (workds as expected)
> A: listen test;
> A: select pg_sleep(5);
> 1
> 2
> B: notify test, 'test1';
> 3
> 4
> 5
> A: done
> A:
> * notification received:
> server process id: 2837
> channel: test
> payload: test
> 6
> 7
> 8
> 9
> B: notify test, 'test2';
> A:
> * notification received:
> server process id: 2837
> channel: test
> payload: test2
>

I don't think this is a bug. I don't see that the docs promise one
behavior over the other, so it is really a dealer's choice. Also, I can't
reliably reproduce the reported 9.6.2 behavior on my own 9.6.2 server.

Cheers,

Jeff

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrey 2018-07-03 04:54:02 Re: NOTIFY does not work as expected
Previous Message Andrey 2018-07-02 20:33:49 NOTIFY does not work as expected