Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifiesafter CommitTransactionCommand

Поиск
Список
Период
Сортировка
От David G. Johnston
Тема Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifiesafter CommitTransactionCommand
Дата
Msg-id CAKFQuwZg50MEY3N9co-9toSy5MvwWQSKvqyUut=RuYgukCMCWA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifiesafter CommitTransactionCommand  (RekGRpth <rekgrpth@gmail.com>)
Ответы Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifies after CommitTransactionCommand  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-bugs
Дерево обсуждения

пт, 14 февр. 2020 г. в 20:36, Tom Lane <tgl@sss.pgh.pa.us>:
RekGRpth <rekgrpth@gmail.com> writes:
> No, it wasn't. I listen in another connection and receive both
> notifications but only after 10 seconds!

Doesn't sound like a bug to me.  The sending backend will only
send out notifications when it goes idle

 Does a non-interactive psql session ever go idle mid-script?

On Friday, February 14, 2020, RekGRpth <rekgrpth@gmail.com> wrote:
Ok, thanks. But I expect to receive notification at every transaction commit!
with bst

This seems reasonable on its face and I don’t see any documentation regarding this aspect of timing.  All the docs says is listen/notify only take effect after the transaction they are in commits.  Absent further info one can reasonably assume that they take effect immediately after commit and not at the first idle moment subsequent to the commit.

David J.

В списке pgsql-bugs по дате отправления:

Предыдущее
От: RekGRpth
Дата:
Сообщение: Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifiesafter CommitTransactionCommand
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #16258: exec_simple_query does not call ProcessCompletedNotifies after CommitTransactionCommand