Re: NOTIFY in multi-statement PQexec() not sent outside of transaction

Wrapping the notify in a transaction does not fix it. Shouldn't the notify
be available as soon as the containing transaction is committed?

cur.execute(("begin; notify __test; commit; "
"begin; select pg_advisory_lock(7777); "
"select pg_advisory_unlock(7777); commit"))

On Mon, Apr 20, 2020 at 1:26 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Monday, April 20, 2020, John Muehlhausen <jgm(at)jgm(dot)org> wrote:
>
>>
>> # docs seem to indicate that an implied transaction
>> # will not exist if there is an explicit begin/commit?
>> cur.execute(("notify __test; "
>> "begin; select pg_advisory_lock(7777); "
>> "select pg_advisory_unlock(7777); commit"))
>>
>>
> A more comprehensive reading of the docs finds:
>
> “ If the BEGIN follows some statements that were executed as an implicit
> transaction block, those statements are not immediately committed; in
> effect, they are retroactively included into the new regular transaction
> block. “.
>
> David J.
>
>