Re: Add "io worker" as backend_type to the pg_stat_activity documentation

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