Horton

Re: BUG #17077: about three parameters in postgresql 13.3

Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>

View thread View on postgr.es
From: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: "leiyanliang@highgo.com" <leiyanliang@highgo.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>
Date: 2021-07-17T14:50:39Z
Lists: pgsql-bugs 
On Sat, Jul 17, 2021 at 7:50 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
> "leiyanliang@highgo.com" <leiyanliang@highgo.com> writes:
> > I want to know: this bug report is a problem or not ?
>
> The code is operating as designed.  It does seem odd that there's no
> mention of these variables in the documentation, though.

I think the point that the 3 GUCs have no explanation in the docs but
still show up in the pg_settings was discussed at [1]. There, we
wanted to add GUC_NO_SHOW_ALL for 3 of them. I still would prefer it
because the 3 GUCs will only be used internally(?).

[1] - https://www.postgresql.org/message-id/237342.1620491116%40sss.pgh.pa.us

Regards,
Bharath Rupireddy.

Commits

  1. Doc: document the current-transaction-modes GUCs.