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 1ulXC5-002Hew-Ha for pgsql-bugs@arkaria.postgresql.org; Mon, 11 Aug 2025 18:24:25 +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 1ulXC3-002xUQ-Ut for pgsql-bugs@arkaria.postgresql.org; Mon, 11 Aug 2025 18:24:24 +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 1ulXC3-002xUH-Mc for pgsql-bugs@lists.postgresql.org; Mon, 11 Aug 2025 18:24:23 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1ulXC1-000495-28 for pgsql-bugs@lists.postgresql.org; Mon, 11 Aug 2025 18:24:23 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 57BIOIPN3169485; Mon, 11 Aug 2025 14:24:18 -0400 From: Tom Lane 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 In-reply-to: <19017-e5fc45491b9b91a0@postgresql.org> References: <19017-e5fc45491b9b91a0@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Mon, 11 Aug 2025 17:45:27 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3169483.1754936658.1@sss.pgh.pa.us> Date: Mon, 11 Aug 2025 14:24:18 -0400 Message-ID: <3169484.1754936658@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form 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