Re: GUC flags

From: Justin Pryzby <pryzby(at)telsasoft(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: GUC flags
Date: 2021-12-02 05:17:34
Message-ID: 20211202051734.GN17618@telsasoft.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Dec 02, 2021 at 02:11:38PM +0900, Michael Paquier wrote:
> On Wed, Dec 01, 2021 at 09:34:39PM -0600, Justin Pryzby wrote:
> >> @@ -2762,7 +2763,8 @@ static struct config_int ConfigureNamesInt[] =
> >> {"pre_auth_delay", PGC_SIGHUP, DEVELOPER_OPTIONS,
> >> - gettext_noop("Waits N seconds on connection startup before authentication."),
> >> + gettext_noop("Sets the amount of time to wait on connection "
> >> + "startup before authentication."),
> >> gettext_noop("This allows attaching a debugger to the process."),
> >
> > I wonder if these should say "Sets the amount of time to wait [before]
> > authentication during connection startup"
>
> Hmm. I don't see much a difference between both of wordings in this
> context.

I find it easier to read "wait before authentication ..." than "wait ... before
authentication".

> > BTW the EXPLAIN flag for enable_incremental_sort could be backpatched to v13.
>
> This could cause small diffs in EXPLAIN outputs, which could be
> surprising. This is not worth taking any risks.

Only if one specifies explain(SETTINGS).
It's fine either way ;)

--
Justin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2021-12-02 05:27:41 Re: pg_get_publication_tables() output duplicate relid
Previous Message Michael Paquier 2021-12-02 05:11:38 Re: GUC flags