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 1jlfjn-0000wp-1u for pgsql-admin@arkaria.postgresql.org; Wed, 17 Jun 2020 21:36:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jlfjj-0001bc-BK for pgsql-admin@arkaria.postgresql.org; Wed, 17 Jun 2020 21:36:47 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jlfji-0001bV-Mp for pgsql-admin@lists.postgresql.org; Wed, 17 Jun 2020 21:36:47 +0000 Received: from resqmta-po-01v.sys.comcast.net ([2001:558:fe16:19:96:114:154:160]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jlfjf-0007Vg-T1 for pgsql-admin@lists.postgresql.org; Wed, 17 Jun 2020 21:36:45 +0000 Received: from resomta-po-03v.sys.comcast.net ([96.114.154.227]) by resqmta-po-01v.sys.comcast.net with ESMTP id leWCjYpOn3uNglfjejn6aj; Wed, 17 Jun 2020 21:36:42 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1592429802; bh=rM28YeLUY4a0FG50u6RnTxDPqIKvTmAxMDE0KGk0zX0=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=hv0IPk6+q6WOETPSgIzHkO1h9KfUprtG5vW07wFWVJakuipsYJH3rIFR4+pY6wmNM bQilpqTHb3Yf+pex1h5qo1K11cldxWBYays2yND72HRbcflJ3DCPkinprtS/+ysYqF QewMrSl+wclq+hdT1s4puuROlTgjn5uMR+Z7hjJPCdSrpL2OwcdCpxriDTvgR3M/Hr wCG7vU75Lq54pn6uLMkeV5AKbRX3o+826xtMvrg6gtwITpaq1R5FZV9Mh8NFBk5C4L +uXccMniMAWpW33VY7CGXy3WwqSpvMwKTfP/BY6e+3a5vRnuo7IF3pjqliha3m0b6k iky5V/hwy+bcw== Received: from jsievers.comcast.net ([12.187.116.132]) by resomta-po-03v.sys.comcast.net with ESMTPA id lfjUjFRcTyQZplfjVjxm9Z; Wed, 17 Jun 2020 21:36:40 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgeduhedrudejfedgtdduucetufdoteggodetrfdotffvucfrrhhofhhilhgvmecuvehomhgtrghsthdqtfgvshhipdfqfgfvpdfpqffurfetoffkrfenuceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmnecujfgurhephffvufhfffgjkfgfgggtgfesthhqredttderjeenucfhrhhomheplfgvrhhrhicuufhivghvvghrshcuoehgshhivghvvghrshduleestghomhgtrghsthdrnhgvtheqnecuggftrfgrthhtvghrnhepvefhlefgueduveduteevgfdtkeehgefgheegteehkeekhfdvgedvheeuhedvkeevnecukfhppeduvddrudekjedrudduiedrudefvdenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopehjshhivghvvghrshdrtghomhgtrghsthdrnhgvthdpihhnvghtpeduvddrudekjedrudduiedrudefvddpmhgrihhlfhhrohhmpehgshhivghvvghrshduleestghomhgtrghsthdrnhgvthdprhgtphhtthhopehrrghmphhrrghtrghptddttddtsehgmhgrihhlrdgtohhmpdhrtghpthhtohepphhgshhqlhdqrggumhhinheslhhishhtshdrphhoshhtghhrvghsqhhlrdhorhhg X-Xfinity-VMeta: sc=-100.00;st=legit Received: from jsievers.enova.com (localhost [127.0.0.1]) by jsievers.comcast.net (Postfix) with ESMTP id D466626005A; Wed, 17 Jun 2020 16:36:31 -0500 (CDT) From: Jerry Sievers To: ram pratap maurya Cc: pgsql-admin@lists.postgresql.org Subject: Re: old and new pg_controldata WAL segment sizes are invalid or do not match References: Date: Wed, 17 Jun 2020 16:36:31 -0500 In-Reply-To: (ram pratap maurya's message of "Thu, 18 Jun 2020 02:35:17 +0530") Message-ID: <87y2olwf1c.fsf@jsievers.enova.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk ram pratap maurya writes: > Hello taem, > > i am faction=C2=A0issue during upgrade postgres11 to 12. can you please > suggest how to resolve this issue. > > .........................................................................= ................................................. > bash-4.1$ /usr/pgsql-12/bin/pg_upgrade --old-datadir /var/lib/pgsql/ > 11/data/ --new-datadir /var/lib/pgsql/12/data/ --old-bindir /usr/ > pgsql-11/bin/ --new-bindir /usr/pgsql-12/bin/ --check > Performing Consistency Checks > ----------------------------- > Checking cluster versions =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 ok > > old and new pg_controldata WAL segment sizes are invalid or do not > match > Failure, exiting Did you initdb the v12 cluster with a non-default WAL size? Suggest you run pg_controldata for both old/new clusters and see what it says, which the pg_upgrade error message is telling you to do. HTH > > > regards, > ram Pratap > > --=20 Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net