Re: Add comments for a postgres program in bootstrap mode - Mailing list pgsql-hackers

From Amit Langote
Subject Re: Add comments for a postgres program in bootstrap mode
Date
Msg-id CA+HiwqEDZet3dguM8Dmc75iTu318Kv0WhRSu5rp_RdPWF=cvAQ@mail.gmail.com
Whole thread Raw
In response to Re: Add comments for a postgres program in bootstrap mode  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Fri, Sep 27, 2019 at 1:03 PM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Fri, Sep 27, 2019 at 12:29:08PM +0900, Youki Shiraishi wrote:
> > I also vote to get rid of such ambiguous stuff.
> > As you can see by grepping, "bootstrap-mode backend" (and something
> > like that) is also called in the sources as:
> >
> > - bootstrap backend
> > - (basic) bootstrap process
> > - backend running in bootstrap mode
> > - postgres (backend) program in bootstrap mode
> > - bootstrapper
> >
> > I think "bootstrap backend" is a strong candidate for an alternative
> > of "bootstrapper" because it is used in the official documentation of
> > initdb.
>
> It seems to me that "backend running in bootstrap mode" would be the
> most consistent way to define that state in a backend process:
> $ git grep -i "bootstrap mode backend" | wc -l
> 0
> $ git grep -i "bootstrap-mode" | wc -l
> 0
> $ git grep -i "bootstrap mode" | wc -l
> 68
> $ git grep -i "bootstrap process" | wc -l
> 9
>
> "bootstrapper" sounds weird.  My 2c.

Alright, count me in on the "bootstrap mode backend" side too. :)

Thanks,
Amit



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Add comments for a postgres program in bootstrap mode
Next
From: Amit Kapila
Date:
Subject: Re: dropdb --force