pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: 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 09:58:57 -0500
Message-ID: <20210717145856.GB19498@telsasoft.com> (raw)
In-Reply-To: <202107171445.v4okkq2xyytm@alvherre.pgsql>
References: <CALj2ACUtWWWLKAU_R3pryw7JvF1kS+EnBZq1XYSVsJ7ehKkRCQ@mail.gmail.com>
	<202107171445.v4okkq2xyytm@alvherre.pgsql>

On Sat, Jul 17, 2021 at 10:45:52AM -0400, Alvaro Herrera wrote:
> On 2021-Jul-17, Bharath Rupireddy wrote:
> 
> > On Thu, Jul 15, 2021 at 8:17 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
> > >
> > > On Fri, Jul 09, 2021 at 09:24:19PM +0530, Bharath Rupireddy wrote:
> > > > I've always had a hard time distinguishing various types of
> > > > processes/terms used in postgres. I look at the source code every time
> > > > to understand them, yet I don't feel satisfied with my understanding.
> > > > I request any hacker (having a better idea than me) to help me with
> > > > what each different process does and how they are different from each
> > > > other? Of course, I'm clear with normal backends (user sessions), bg
> > > > workers, but the others need a bit more understanding.
> > >
> > > It sounds like something that should be in the glossary, which currently refers
> > > to but doesn't define "auxiliary processes".
> > 
> > Thanks. I strongly feel that it should be documented somewhere. I will
> > be happy if someone with a clear idea about these various processes
> > does it.
> 
> 	Auxiliary process
> 
> 	Process of an <glossterm linkend="glossary-instance">instance</glossterm> in

I think "of an instance" is a distraction here, even if technically accurate.

> 	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.

Thanks,
-- 
Justin





view thread (14+ messages)  latest in thread

Message-ID: <20210717145856.GB19498@telsasoft.com>
Permalink:  ../20210717145856.GB19498@telsasoft.com/
Also on:    postgresql.org/message-id/20210717145856.GB19498@telsasoft.com

 · 

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-hackers@postgresql.org
  Cc: 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: <20210717145856.GB19498@telsasoft.com>

* 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