pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Michael Paquier <michael@paquier.xyz>
To: Laurenz Albe <laurenz.albe@cybertec.at>
Cc: Fujii Masao <masao.fujii@gmail.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: Add "io worker" as backend_type to the pg_stat_activity documentation
Date: Wed, 22 Jul 2026 07:18:33 +0900
Message-ID: <al_wOWrsHfB65Zbk@paquier.xyz> (raw)
In-Reply-To: <4aff5b0f5a1bf3b487d06daec5ed5a287afa7a22.camel@cybertec.at>
References: <5e94c0196084f648ae6a00107125494f5804318a.camel@cybertec.at>
	<al8noIYGjD_Lyyi8@paquier.xyz>
	<eb735d8aedf16ab2121af6f9b65b3274927afd2d.camel@cybertec.at>
	<CAHGQGwEDY0GkP4Tapn+qtaxB6aNtjPzqozRL8_Hf1Sg3B+H+8w@mail.gmail.com>
	<4aff5b0f5a1bf3b487d06daec5ed5a287afa7a22.camel@cybertec.at>

On Tue, Jul 21, 2026 at 09:04:15PM +0200, Laurenz Albe wrote:
> You are right.  Here is patch v3 with a completed list; I hope I didn't
> forget anything.

I am counting 23 entries.  I don't see anything forgotten on top of my
mind, and we are indeed missing a lot of new entries..  I feel that
like everybody who has added a new worker in the backend has forgotten
to update this list. 

While on it, I also feel like we may have some holes with
log_min_messages and the new process_type.  At least a bunch of them
are missing..  I'll ping that fact on a new thread.  No need to worry
about that here.

> +         <para>
> +          <literal>autovacuum worker</literal>: A background process running
> +          <command>VACUUM</command> or <command>ANALYZE</command> on a single
> +          table.
> +         </para>

Also active when autovacuum = on?

> +         <para>
> +          <literal>walreceiver</literal>: The background process that receives
> +          WAL records from a WAL sender, active in streaming replication
> +          standby mode.
> +         </para>

We can only have one of these.

> +        </listitem>
> +        <listitem>
> +         <para>
> +          <literal>walsender</literal>: A background process that sends WAL
> +          records to receivers (during streaming replication) or decodes WAL
> +          and sends the decoded information (during logical replication).
> +         </para>
> +        </listitem>

No mention of the max_wal_senders dependency?  Perhaps not worth
mentioning, still..
--
Michael

Attachments:

  [application/pgp-signature] signature.asc (832B, ../al_wOWrsHfB65Zbk@paquier.xyz/2-signature.asc)
  download

view thread (12+ messages)  latest in thread

Message-ID: <al_wOWrsHfB65Zbk@paquier.xyz>
Permalink:  ../al_wOWrsHfB65Zbk@paquier.xyz/
Also on:    postgresql.org/message-id/al_wOWrsHfB65Zbk@paquier.xyz

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: michael@paquier.xyz, laurenz.albe@cybertec.at, masao.fujii@gmail.com, pgsql-docs@lists.postgresql.org
  Subject: Re: Add "io worker" as backend_type to the pg_stat_activity documentation
  In-Reply-To: <al_wOWrsHfB65Zbk@paquier.xyz>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox