Re: BUG #19017: pg_upgrade from 17.5 to 18.0beta2 fails with a complaint about max_slot_wal_keep_size

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: cookt(at)blackduck(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19017: pg_upgrade from 17.5 to 18.0beta2 fails with a complaint about max_slot_wal_keep_size
Date: 2025-08-11 18:24:18
Message-ID: 3169484.1754936658@sss.pgh.pa.us
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2025-08-11 18:44:40 Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Previous Message PG Bug reporting form 2025-08-11 17:45:27 BUG #19017: pg_upgrade from 17.5 to 18.0beta2 fails with a complaint about max_slot_wal_keep_size