Re: archive modules

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: talk to ben <blo(dot)talkto(at)gmail(dot)com>
Cc: 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-06 16:41:05
Message-ID: 20220706164105.GA2135371@nathanxps13
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jul 06, 2022 at 06:21:24PM +0200, talk to ben wrote:
> I am not sure why, but I can't find "basic_archive.archive_directory" in
> pg_settings the same way I would find for example :
> "pg_stat_statements.max".
>
> [local]:5656 benoit(at)postgres=# SELECT count(*) FROM pg_settings WHERE name
> = 'basic_archive.archive_directory';
> count
> -------
> 0
> (1 row)
>
> show can find it if I use the complete name but tab completion can't find
> the guc:
>
> [local]:5656 benoit(at)postgres=# show basic_archive.archive_directory;
> basic_archive.archive_directory
> ---------------------------------
> /home/benoit/tmp/tmp/archives
> (1 row)

I think the reason is that only the archiver process loads the library, so
the GUC isn't registered at startup like you'd normally see with
shared_preload_libraries. IIUC the server will still create a placeholder
GUC during startup for custom parameters, which is why it shows up for SHOW
commands.

--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2022-07-06 16:51:10 Re: O(n) tasks cause lengthy startups and checkpoints
Previous Message Andres Freund 2022-07-06 16:28:26 Re: Issue with pg_stat_subscription_stats