Re: pgsql: Report progress of startup operations that take a long time. - Mailing list pgsql-committers

From Alvaro Herrera
Subject Re: pgsql: Report progress of startup operations that take a long time.
Date
Msg-id 202111051432.x7qdfd4umrvz@alvherre.pgsql
Whole thread Raw
In response to Re: pgsql: Report progress of startup operations that take a long time.  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-committers
On 2021-Oct-29, Robert Haas wrote:

> On Fri, Oct 29, 2021 at 5:23 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
> > I noticed that the docs for this don't mention the default value and how
> > can it be changed.  I propose something like the attached, where I also
> > change the order of things so that the example is in a separate
> > paragraph and the reference blurb is all together.
> 
> OK. I don't mind that. I wasn't sure if it was our practice to mention
> the default value in all cases. Maybe I should have checked more
> carefully.

Thanks.  I only noticed because I got curious about what the default
was :-)

> > I was also going to complain that this failed to keep the alphabetical
> > order of the entries, but there was quite a mess already before this
> > patch, so I'd rather not get into that.
> 
> Well, I suppose that's up to you. :-)

I'll leave that for some other day :-)

-- 
Álvaro Herrera           39°49'30"S 73°17'W  —  https://www.EnterpriseDB.com/
"This is what I like so much about PostgreSQL.  Most of the surprises
are of the "oh wow!  That's cool" Not the "oh shit!" kind.  :)"
Scott Marlowe, http://archives.postgresql.org/pgsql-admin/2008-10/msg00152.php



pgsql-committers by date:

Previous
From: Alvaro Herrera
Date:
Subject: pgsql: Document default and changeability of log_startup_progress_inter
Next
From: Alvaro Herrera
Date:
Subject: pgsql: Pipeline mode disallows multicommand strings