| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Rıdvan Korkmaz <serkan(dot)ridvan(dot)korkmaz(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: pg_file_settings |
| Date: | 2023-12-26 19:22:53 |
| Message-ID: | 2091031.1703618573@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
=?UTF-8?Q?R=C4=B1dvan_Korkmaz?= <serkan(dot)ridvan(dot)korkmaz(at)gmail(dot)com> writes:
> In order to summarize things in first mail, from the documentation, we
> expect to see relevant errors in the "error" column of pg_file_setitings
> view for an invalid value of parameter.
Thanks for the report. It mostly does work, but not for
'log_connections', and it turns out also not for other PGC_BACKEND
GUCs (of which there are only half a dozen, probably explaining how
this didn't get noticed). I posted a proposed fix at [1].
regards, tom lane
[1] https://www.postgresql.org/message-id/2089235.1703617353%40sss.pgh.pa.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | M Sarwar | 2023-12-26 22:47:07 | Re: Login script |
| Previous Message | Rıdvan Korkmaz | 2023-12-26 18:12:24 | Re: pg_file_settings |