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

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: cookt@blackduck.com

Cc: pgsql-bugs@lists.postgresql.org

Date: 2025-08-11T18:24:18Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Restrict psql meta-commands in plain-text dumps.
- 67a2fbb8f9e9 18.0 cited

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