Re: doc fix for pg_stat_activity.backend_type

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: jcnaylor(at)gmail(dot)com, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: doc fix for pg_stat_activity.backend_type
Date: 2018-11-13 04:05:30
Message-ID: CAA4eK1KT=rBGQi1X9kxwBLbfytiXYZZe3neyuPo_bvkP1wo=Lw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 13, 2018 at 5:38 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Mon, Nov 12, 2018 at 09:42:45PM +0700, John Naylor wrote:
> > Looks like it. A quick search revealed "parallel worker" and "logical
> > replication worker". src/test/modules/ also show "test_shm_mq" and
> > "worker_spi", but it seems those don't need to be publicly documented.
> > If that sounds right I'll update the patch to include the first two.
>
> Just wondering: do we actually need to include in the docs this list at
> all? This is a recipe to forget its update each time a new backend type
> is added.
>

Sure, but how will we justify documenting (autovacuum launcher and
autovacuum worker) and not (logical replication launcher and logical
replication worker)? I think we can document the type of workers that
are part of core-server functionality. We can make some generic
statement on the workers that can be launched by extensions.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2018-11-13 05:48:11 Re: Resetting PGPROC atomics in ProcessInit()
Previous Message Amit Langote 2018-11-13 04:04:47 Re: move PartitionBoundInfo creation code