From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: What are exactly bootstrap processes, auxiliary processes, standalone backends, normal backends(user sessions)?
Date: Sat, 17 Jul 2021 11:57:00 -0400
Message-ID: <70159.1626537420@sss.pgh.pa.us> (raw)
In-Reply-To: <20210717145856.GB19498@telsasoft.com>
References: <CALj2ACUtWWWLKAU_R3pryw7JvF1kS+EnBZq1XYSVsJ7ehKkRCQ@mail.gmail.com>
<202107171445.v4okkq2xyytm@alvherre.pgsql>
<20210717145856.GB19498@telsasoft.com>
Justin Pryzby <pryzby@telsasoft.com> writes:
> On Sat, Jul 17, 2021 at 10:45:52AM -0400, Alvaro Herrera wrote:
>> Process of an <glossterm linkend="glossary-instance">instance</glossterm> in
>> charge of some specific, hardcoded background task. Examples are
> And I think "hardcoded" doesn't mean anything beyond what "specific" means.
> Maybe you'd say: .. process which handles a specific, central task for the
> 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
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-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, pryzby@telsasoft.com, alvherre@alvh.no-ip.org, 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: <70159.1626537420@sss.pgh.pa.us>
* 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