From: Ron <ronljohnsonjr@gmail.com>
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Subject: How to _not_ save startup options in postmaster.opts?
Date: Thu, 2 Nov 2023 12:01:00 -0500
Message-ID: <89ffab7a-0dfe-42e5-ae9d-e2fff60c9762@gmail.com> (raw)
Pg 14, if it matters.
When doing maintenance (including a giant pg_restore), sometime one wants to
run with different configuration values (like archivemode=off,
wal_level=minimal, autovacuum=off, etc).
I could edit postgresql.conf -- or have two of them: one normal, and one for
doing maintenance -- but if I'm going to restart anyway, why not just pass
those parameters directly to the postmaster?
Alas, those config values are remembered in postmaster.opts. But I don't
want that.
Thus: is there a way to tell pg to /not/ put those options in postmaster.opts?
Or is this my only option before restarting for production:
which postgres > $PGDATA/postmaster.opts
--
Born in Arizona, moved to Babylonia.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: How to _not_ save startup options in postmaster.opts?
In-Reply-To: <89ffab7a-0dfe-42e5-ae9d-e2fff60c9762@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox