From: | Jerry Sievers <gsievers19(at)comcast(dot)net> |
---|---|
To: | ram pratap maurya <rampratap0000(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: old and new pg_controldata WAL segment sizes are invalid or do not match |
Date: | 2020-06-17 21:36:31 |
Message-ID: | 87y2olwf1c.fsf@jsievers.enova.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
ram pratap maurya <rampratap0000(at)gmail(dot)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(dot)consulting(at)comcast(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Förster | 2020-06-18 09:45:47 | Re: old and new pg_controldata WAL segment sizes are invalid or do not match |
Previous Message | ram pratap maurya | 2020-06-17 21:05:17 | old and new pg_controldata WAL segment sizes are invalid or do not match |