Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jmFLW-0006wJ-Qk for pgsql-bugs@arkaria.postgresql.org; Fri, 19 Jun 2020 11:38:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jmFKz-0007FC-VY for pgsql-bugs@arkaria.postgresql.org; Fri, 19 Jun 2020 11:37:37 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jmFKz-0007Eb-PZ for pgsql-bugs@lists.postgresql.org; Fri, 19 Jun 2020 11:37:37 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jmFKs-0003I9-Jk for pgsql-bugs@lists.postgresql.org; Fri, 19 Jun 2020 11:37:37 +0000 Received: from bruce by momjian.us with local (Exim 4.92) (envelope-from ) id 1jmFKl-0005mS-1Q; Fri, 19 Jun 2020 07:37:23 -0400 Date: Fri, 19 Jun 2020 07:37:23 -0400 From: Bruce Momjian To: Ram Pratap Maurya Cc: Stephen Frost , Michael Paquier , Jeff Janes , Tom Lane , pgsql-bugs Subject: Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match Message-ID: <20200619113723.GA19125@momjian.us> References: <20200618152911.GF7349@momjian.us> <20200618154152.GB6680@tamriel.snowman.net> <20200618154854.GG7349@momjian.us> <20200618155537.GC6680@tamriel.snowman.net> <20200618163615.GI7349@momjian.us> <20200618174241.GD6680@tamriel.snowman.net> <20200618180058.GK7349@momjian.us> <20200618181114.GG6680@tamriel.snowman.net> <20200618182943.GL7349@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Jun 19, 2020 at 05:20:21AM +0000, Ram Pratap Maurya wrote: > Dear All, > > any impact of server. If we Can reset manually postgres old version (11) WAL segment size . You can change the wal segment size _after_ running pg_upgrade, but for the upgrade, they have to match. Use an initdb flag so they do. -- Bruce Momjian https://momjian.us EnterpriseDB https://enterprisedb.com The usefulness of a cup is in its emptiness, Bruce Lee