From: Tom Lane <tgl@sss.pgh.pa.us>
To: cookt@blackduck.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19017: pg_upgrade from 17.5 to 18.0beta2 fails with a complaint about max_slot_wal_keep_size
Date: Mon, 11 Aug 2025 14:24:18 -0400
Message-ID: <3169484.1754936658@sss.pgh.pa.us> (raw)
In-Reply-To: <19017-e5fc45491b9b91a0@postgresql.org>
References: <19017-e5fc45491b9b91a0@postgresql.org>
PG Bug reporting form <noreply@postgresql.org> writes:
> waiting for server to start....2025-08-11 11:31:36.664 EDT [619244] LOG:
> invalid value for parameter "max_slot_wal_keep_size": 8192
> 2025-08-11 11:31:36.664 EDT [619244] DETAIL: "max_slot_wal_keep_size" must
> be set to -1 during binary upgrade mode.
Already reported, and should be fixed in beta3, but thanks for the
report!
regards, tom lane
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, cookt@blackduck.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19017: pg_upgrade from 17.5 to 18.0beta2 fails with a complaint about max_slot_wal_keep_size
In-Reply-To: <3169484.1754936658@sss.pgh.pa.us>
* 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