Re: Hooks for session start and end, take two

Поиск
Список
Период
Сортировка
От Fabrízio de Royes Mello
Тема Re: Hooks for session start and end, take two
Дата
Msg-id CAFcNs+p=7dbu6DPXG9SvDMA0ffoQVLLVVY3pAsiJCijhh9O_bw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Hooks for session start and end, take two  (Michael Paquier <michael@paquier.xyz>)
Ответы Re: Hooks for session start and end, take two  (Michael Paquier <michael@paquier.xyz>)
Список pgsql-hackers

On Sun, Sep 29, 2019 at 10:29 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> This code path can only be taken by normal backends, so that would
> apply, still I don't actually see why we should limit us here on the
> backend side.  If for a reason or another those two code paths begin
> to be taken by a backend with InvalidBackendId, then users of the
> session start/end hook will need to think how to handle it if they
> didn't from the start, which sounds like a good thing to me.
>

Makes sense to me. I become a reviewer and run all tests (make check && make check-world) and everything is ok. Changed status to "ready for commiter".

Regards,

--
   Fabrízio de Royes Mello         Timbira - http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

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

Предыдущее
От: Alexander Korotkov
Дата:
Сообщение: Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock(PG10.7)
Следующее
От: Greg Stark
Дата:
Сообщение: Partitioning versus autovacuum