From: Bruce Momjian <bruce@momjian.us>
To: Jeff Janes <jeff.janes@gmail.com>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: ram.maurya@lavainternational.in, pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Subject: Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match
Date: Thu, 18 Jun 2020 10:30:03 -0400
Message-ID: <20200618143003.GE7349@momjian.us> (raw)
In-Reply-To: <CAMkU=1zRirCC-kZTZb0hBq+jqy7vjk8+ehbrZpjr5LATKFChKQ@mail.gmail.com>
References: <16497-38bb1f1bcec44964@postgresql.org>
<20200618080509.GH118592@paquier.xyz>
<CAMkU=1zRirCC-kZTZb0hBq+jqy7vjk8+ehbrZpjr5LATKFChKQ@mail.gmail.com>
On Thu, Jun 18, 2020 at 10:18:21AM -0400, Jeff Janes wrote:
> On Thu, Jun 18, 2020 at 4:05 AM Michael Paquier <michael@paquier.xyz> wrote:
>
> On Wed, Jun 17, 2020 at 09:00:23PM +0000, PG Bug reporting form wrote:
> > I am facing error during upgrade from postgresql -11 to 12.
> > can you please suggest what is solution.
>
> As the error message is telling, you need to make the WAL segment
> sizes of the old and new clusters match. This can be defined at
> server initialization time using initdb with a default of 16MB, so
> that's not a bug from us, but something you need to take care of
> within your upgrade process.
>
>
> Since wal-segsize is changeable with pg_resetwal since v11, and pg_upgrade is
> already calling pg_resetwal, shouldn't pg_upgrade ideally just deal with this
> situation automatically by allowing the upgrade to also change this value,
> rather than forcing the user to make them match manually?
Uh, well, pg_upgrade is very conservative and fails if anything looks
odd, like different WAL sizes. Since pg_upgrade doesn't even copy the
WAL from the old server, I am not sure why we require the WAL segment
size to match, but it might be so we can run pg_upgrade on replicas.
The bottom line is that pg_upgrade is complex enough, and having it try
to do more is not a wise approach.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: bruce@momjian.us, jeff.janes@gmail.com, michael@paquier.xyz, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16497: old and new pg_controldata WAL segment sizes are invalid or do not match
In-Reply-To: <20200618143003.GE7349@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox