Re: Hooks for session start and end, take two - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: Hooks for session start and end, take two
Date
Msg-id CAFcNs+p=7dbu6DPXG9SvDMA0ffoQVLLVVY3pAsiJCijhh9O_bw@mail.gmail.com
Whole thread Raw
In response to Re: Hooks for session start and end, take two  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Hooks for session start and end, take two
List 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 by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: Connections hang indefinitely while taking a gin index's LWLockbuffer_content lock(PG10.7)
Next
From: Greg Stark
Date:
Subject: Partitioning versus autovacuum