Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps
 (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1m4mge-0006GL-4u
	for pgsql-hackers@arkaria.postgresql.org; Sat, 17 Jul 2021 15:57:08 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.92)
	(envelope-from <pgsql-hackers-owner+archive@lists.postgresql.org>)
	id 1m4mgd-0003ZW-01
	for pgsql-hackers@arkaria.postgresql.org; Sat, 17 Jul 2021 15:57:07 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1m4mgc-0003ZO-OM
	for pgsql-hackers@lists.postgresql.org; Sat, 17 Jul 2021 15:57:06 +0000
Received: from sss.pgh.pa.us ([66.207.139.130])
	by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1m4mga-0006qV-M9
	for pgsql-hackers@lists.postgresql.org; Sat, 17 Jul 2021 15:57:05 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 16HFv0Om070160;
	Sat, 17 Jul 2021 11:57:00 -0400
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
        Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>,
        pgsql-hackers@lists.postgresql.org
Subject: Re: What are exactly bootstrap processes, auxiliary processes,
 standalone backends, normal backends(user sessions)?
In-reply-to: <20210717145856.GB19498@telsasoft.com>
References: 
 <CALj2ACUtWWWLKAU_R3pryw7JvF1kS+EnBZq1XYSVsJ7ehKkRCQ@mail.gmail.com>
 <202107171445.v4okkq2xyytm@alvherre.pgsql>
 <20210717145856.GB19498@telsasoft.com>
Comments: In-reply-to Justin Pryzby <pryzby@telsasoft.com>
	message dated "Sat, 17 Jul 2021 09:58:57 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <70158.1626537420.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 17 Jul 2021 11:57:00 -0400
Message-ID: <70159.1626537420@sss.pgh.pa.us>
List-Id: <pgsql-hackers.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-hackers@lists.postgresql.org>
List-Owner: <mailto:pgsql-hackers-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-hackers>
Archived-At: 
 <https://www.postgresql.org/message-id/70159.1626537420%40sss.pgh.pa.us>
Precedence: bulk

Justin Pryzby <pryzby@telsasoft.com> writes:
> On Sat, Jul 17, 2021 at 10:45:52AM -0400, Alvaro Herrera wrote:
>> Process of an <glossterm linkend=3D"glossary-instance">instance</glosst=
erm> in
>> charge of some specific, hardcoded background task.  Examples are

> And I think "hardcoded" doesn't mean anything beyond what "specific" mea=
ns.

> Maybe you'd say: .. process which handles a specific, central task for t=
he
> cluster instance.

Meh.  "Specific" and "background" both seem to be useful terms here.
I do not think "central" is a useful adjective.

			regards, tom lane