Tom Lane wrote:
> Laurent Birtz <laurent.birtz@kryptiva.com> writes:
>
>> From the observed sequence of events, it would appear that the event
>> thread inserts a tuple in the pg_listener table BEFORE the command thread
>> actually commits the transaction. However, when this transaction commits,
>> Postgres does not actually find the event thread's tuple in this table.
>>
>
> I'm wondering exactly when you commit the LISTEN? The command thread
> can't see the pg_listener tuple until it's committed ...
>
I'm executing the LISTEN statement outside a transaction block.
I presume Postgres implicitly adds the BEGIN and COMMIT
statements in that case?
Just to be clear, the SELECT statement that retrieve new events is
also executed outside a transaction block.
Thanks for the help,
Laurent Birtz
