Re: Hooks for session start and end, take two

From: Fabrízio de Royes Mello <fabriziomello(at)gmail(dot)com>
To: legrand legrand <legrand_legrand(at)hotmail(dot)com>
Cc: Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hooks for session start and end, take two
Date: 2019-09-28 13:43:36
Message-ID: CAFcNs+qt6n7j-Qbes7Na_nwyytLkp91cK-jV=bo8EYsdnh9cug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 27, 2019 at 4:26 PM legrand legrand <legrand_legrand(at)hotmail(dot)com>
wrote:
>
> OK I confirm:
> - "client backend" appears at session start and end hook,
> - "autovacuum worker" and "pg_background" only appears at session end hook
> (backend_start can be retreived from pg_stat_activity),
> - "parallel workers" are not visible at all
> (because extension cannot assign XIDs during a parallel operation)
>
> All seems fine to me.
>

Hi all,

First of all thanks Michael for bringing this to life again.

I poked a little with the patch and everything is ok. Your check for normal
backend on test_session_hooks is much simpler than I did before:

+ /* just consider normal backends */
+ if (MyBackendId == InvalidBackendId)
+ return;

But one thing came to my mind, why not in this first version we hook just
normal backends?

Regards,

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2019-09-28 14:54:10 Re: Standby accepts recovery_target_timeline setting?
Previous Message Antonin Houska 2019-09-28 13:00:35 Re: Attempt to consolidate reading of XLOG page