| From: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "leiyanliang(at)highgo(dot)com" <leiyanliang(at)highgo(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17077: about three parameters in postgresql 13.3 |
| Date: | 2021-07-17 14:50:39 |
| Message-ID: | CALj2ACWNacYVcZx4evp+KzQWXsXcWzRE9eewjpAJxNB+xCsKWA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Sat, Jul 17, 2021 at 7:50 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> "leiyanliang(at)highgo(dot)com" <leiyanliang(at)highgo(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-07-17 15:04:14 | Re: BUG #17077: about three parameters in postgresql 13.3 |
| Previous Message | Alvaro Herrera | 2021-07-17 14:28:09 | Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size |