Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qydME-009pGE-9k for pgsql-admin@arkaria.postgresql.org; Thu, 02 Nov 2023 19:27:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1qydMC-00ExOH-Rc for pgsql-admin@arkaria.postgresql.org; Thu, 02 Nov 2023 19:27:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qydMC-00ExO8-FN for pgsql-admin@lists.postgresql.org; Thu, 02 Nov 2023 19:27:56 +0000 Received: from mail-yb1-xb2f.google.com ([2607:f8b0:4864:20::b2f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qydM8-004NCR-11 for pgsql-admin@lists.postgresql.org; Thu, 02 Nov 2023 19:27:55 +0000 Received: by mail-yb1-xb2f.google.com with SMTP id 3f1490d57ef6-da0cfcb9f40so1296746276.2 for ; Thu, 02 Nov 2023 12:27:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1698953270; x=1699558070; darn=lists.postgresql.org; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=+Kvj7YOQ6PSLzfcZqXzf6TdioUhzKjeOt7sUq/Gf26k=; b=BMA8EKSLHbQg4ZvdKQYSJ4tCFqBeAnf3kMFP2GJ50zcm7UQQgB4zjdrvBhk6wllcAe AdTXsQCip0RETvAEJpn0LWvTYjnDzaVMVCdDUxD6czsZFKxIg/yArm4PgvfVj805aIJN n8y54Hrdzj2kbDOKoG7CCJAMdCLA0ly+9YmqsFviHjHaLxGpuF4NAzVj6kaEfTAs3CwU FruXqJxYHOVwWqL8UeusO/aDBY0bhFMWkCHt8j9Sh36SsVpX5cZ1yeezMz8Somu95cGP lPNtqlopAnvQLUKvO63s3pdyw37FY4ETsQLxXLskbDTJPNArZaognU7n8yNs+8zZZDVj oISA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1698953270; x=1699558070; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=+Kvj7YOQ6PSLzfcZqXzf6TdioUhzKjeOt7sUq/Gf26k=; b=E8lvAzWCxZdWNQbozs2lYMkjK33Hp7dzRS2vNE4EnCaxT2BTr8KVyQlDL+oyK7OyOs RO+kLBcDnRsTkyUsSfgPfJMmObi9AbWPCb07ssGhg+BFUkoO/7wmer/anGh+B4BTRIoW hFYmGUhfJKJBkdwgnoqS1Y0bWhwgt2iJMdCL8P3K/65b3IBAsfzR2Ko5PwLR5VXS1I3l wAT/R4YmqBTXfR4/VyWg4pt9I2AJGC5XdW3XyNdV2c7rtGN93uAGlDxJO0xRcCj0CoKf +sPP0X4bXAPMDaITDiALoN16XxHUxvjli90KnUUfafWsSYhE/GRsZoFxTdnShapdZu9D U4jA== X-Gm-Message-State: AOJu0YxnqybhCXuienSVptGVPRoBBSf2dDsHG830EJwdbLW9vF5rdFfY p+AKjQKcwLh5z4sxSWMEj1aeorMle7Y= X-Google-Smtp-Source: AGHT+IHwK1y2z5tI6G+I7R1qdXqWP+TlpOVfn1NaoqM8S6ZE1F0bGZBvyONtPeNFkAWq4M2/WKeG9g== X-Received: by 2002:a5b:44:0:b0:da0:54f7:69bd with SMTP id e4-20020a5b0044000000b00da054f769bdmr17512563ybp.22.1698953269577; Thu, 02 Nov 2023 12:27:49 -0700 (PDT) Received: from ?IPV6:2600:1700:bd2c:b810::44? ([2600:1700:bd2c:b810::44]) by smtp.googlemail.com with ESMTPSA id e9-20020a258909000000b00d89679f6d22sm71184ybl.64.2023.11.02.12.27.49 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 02 Nov 2023 12:27:49 -0700 (PDT) Content-Type: multipart/alternative; boundary="------------0wfnuj6LUuhNSWTMh3gYaqAI" Message-ID: <16b8d553-b18c-40ee-8cbc-7eed208c1474@gmail.com> Date: Thu, 2 Nov 2023 14:27:48 -0500 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: How to _not_ save startup options in postmaster.opts? Content-Language: en-US To: Pgsql-admin References: <89ffab7a-0dfe-42e5-ae9d-e2fff60c9762@gmail.com> From: Ron In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------0wfnuj6LUuhNSWTMh3gYaqAI Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 11/2/23 12:24, David G. Johnston wrote: > > Alas, those config values are remembered in postmaster.opts.  But I > don't want that. > > > I don’t know where this file is even documented ATM but my understanding > is it just shows you the values used during the last startup.  It doesn’t > remember anything in any real sense because it isn’t used by the system to > determine what those parameter values should be during startup. https://pgpedia.info/p/postmaster.opts.html "*|postmaster.opts|*is a file in the data directory written after startup which contains the options used to start the postmaster process. The contents of|postmaster.opts|are used to ensure the postmaster process can be restarted with the same options with which it was originally started." I've confirmed this behavior, which I why I wrote the email. > > Use the -c functionality for your manual maintenance boots and just let > the normal startup mechanism do whatever it does when you re-engage it. > > David J. > -- Born in Arizona, moved to Babylonia. --------------0wfnuj6LUuhNSWTMh3gYaqAI Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit On 11/2/23 12:24, David G. Johnston wrote:

Alas, those config values are remembered in postmaster.opts.  But I don't want that.

I don’t know where this file is even documented ATM but my understanding is it just shows you the values used during the last startup.  It doesn’t remember anything in any real sense because it isn’t used by the system to determine what those parameter values should be during startup.

https://pgpedia.info/p/postmaster.opts.html

"postmaster.opts is a file in the data directory written after startup which contains the options used to start the postmaster process. The contents of postmaster.opts are used to ensure the postmaster process can be restarted with the same options with which it was originally started."

I've confirmed this behavior, which I why I wrote the email.


Use the -c functionality for your manual maintenance boots and just let the normal startup mechanism do whatever it does when you re-engage it.

David J.


--
Born in Arizona, moved to Babylonia.
--------------0wfnuj6LUuhNSWTMh3gYaqAI--