| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | legrand legrand <legrand_legrand(at)hotmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Hooks for session start and end, take two |
| Date: | 2019-09-27 04:54:26 |
| Message-ID: | 20190927045426.GE8485@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Sep 26, 2019 at 09:57:57AM -0700, legrand legrand wrote:
> Does that mean that all processes seen in pg_stat_activity like
> - autovacuum launcher
> - logical replication launcher
> - background writer
> - checkpointer
> - walwriter
> ...
> - Parallel worker
> are available with that hook (it seems not) ?
All processes using PostgresMain() for their startup take this code
path like WAL senders and normal backend sessions, but not things
going through StartChildProcess() (WAL receiver, bgwriter, etc.) or
other processes like autovacuum processes which use a different start
code path.
> The patch refers to a 2017 copyright, that's all I found yet ;o)
Fixed, thanks!
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2019-09-27 04:59:24 | Re: Add comments for a postgres program in bootstrap mode |
| Previous Message | Masahiko Sawada | 2019-09-27 04:51:25 | Re: pg_wal/RECOVERYHISTORY file remains after archive recovery |