From: Jerry Sievers <gsievers19@comcast.net>
To: ram pratap maurya <rampratap0000@gmail.com>
Cc: pgsql-admin@lists.postgresql.org
Subject: Re: old and new pg_controldata WAL segment sizes are invalid or do not match
Date: Wed, 17 Jun 2020 16:36:31 -0500
Message-ID: <87y2olwf1c.fsf@jsievers.enova.com> (raw)
In-Reply-To: <CAAiDzSeEEfhxjfT-v+DDySHnfB7N9y_QezQizuRV8RKQ0LDGSg@mail.gmail.com>
References: <CAAiDzSeEEfhxjfT-v+DDySHnfB7N9y_QezQizuRV8RKQ0LDGSg@mail.gmail.com>
ram pratap maurya <rampratap0000@gmail.com> writes:
> Hello taem,
>
> i am faction issue 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 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
>
>
--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres.consulting@comcast.net
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-admin@postgresql.org
Cc: gsievers19@comcast.net, rampratap0000@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: old and new pg_controldata WAL segment sizes are invalid or do not match
In-Reply-To: <87y2olwf1c.fsf@jsievers.enova.com>
* 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