| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | talk to ben <blo(dot)talkto(at)gmail(dot)com> |
| Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, "Bossart, Nathan" <bossartn(at)amazon(dot)com>, David Steele <david(at)pgmasters(dot)net>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Michael Paquier <michael(at)paquier(dot)xyz>, Magnus Hagander <magnus(at)hagander(dot)net>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: archive modules |
| Date: | 2022-07-07 15:11:57 |
| Message-ID: | 20220707151157.cakxxwwadchkov35@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2022-Jul-07, talk to ben wrote:
> The modified archive module parameters are visible in pg_file_settings.
> They don't show up in \dconfig+, which I understand given the query used by
> the meta command, but I find a little confusing from an end user POV.
Well, this does sound unsatisfactory. I suppose one answer would be to
load the module in all backends, in case the user wants to look at the
value. But that would be wasteful. Maybe we should have a warning
about it in the docs -- tell people to LOAD the library if they want to
examine the configuration?
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-07-07 15:25:19 | Re: Use outerPlanState macro instead of referring to leffttree |
| Previous Message | Fujii Masao | 2022-07-07 14:58:05 | Re: Backup command and functions can cause assertion failure and segmentation fault |