Content-Type: multipart/alternative;
 boundary="------------qShAIasuOv19lwzgjMcQtjWZ"
Message-ID: <89ffab7a-0dfe-42e5-ae9d-e2fff60c9762@gmail.com>
Date: Thu, 2 Nov 2023 12:01:00 -0500
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: Pgsql-admin <pgsql-admin@lists.postgresql.org>
Content-Language: en-US
From: Ron <ronljohnsonjr@gmail.com>
Subject: How to _not_ save startup options in postmaster.opts?
Archived-At: 
 <https://www.postgresql.org/message-id/89ffab7a-0dfe-42e5-ae9d-e2fff60c9762%40gmail.com>
Precedence: bulk

This is a multi-part message in MIME format.
--------------qShAIasuOv19lwzgjMcQtjWZ
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

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.
--------------qShAIasuOv19lwzgjMcQtjWZ
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    Pg 14, if it matters.<br>
    <br>
    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).<br>
    <br>
    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?<br>
    <br>
    Alas, those config values are remembered in postmaster.opts.  But I
    don't want that.<br>
    <br>
    Thus: is there a way to tell pg to <i>not</i> put those options in
    postmaster.opts?<br>
    <br>
    Or is this my only option before restarting for production:<br>
    <font face="monospace">which postgres &gt; $PGDATA/postmaster.opts<br>
    </font><br>
    <div class="moz-signature">-- <br>
      Born in Arizona, moved to Babylonia.</div>
  </body>
</html>

--------------qShAIasuOv19lwzgjMcQtjWZ--