Thanks Adrian.
This is what I am seeing.
postgresdbad:dpoc:pgdbadevbal800:> pg_controldata -D /hostname/pg/dev12upg/data | grep -i "Bytes per WAL segment"
Bytes per WAL segment: 131072
postgresdbad:dpoc:pgdbadevbal800:> pg_controldata -D /hostname/pg/dpoc/data | grep -i "Bytes per WAL segment"
Bytes per WAL segment: 16777216
-----Original Message-----
From: Adrian Klaver <adrian.klaver@aklaver.com>
Sent: Saturday, December 19, 2020 10:28 AM
To: Lu, Dan <Dan.Lu@sig.com>; Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-general@postgresql.org
Subject: Re: Upgrade check failed from 11.5 to 12.1
On 12/18/20 2:56 PM, Lu, Dan wrote:
> Thanks for catching that. Typo on my end.
>
> Now I am getting this.
>
> Performing Consistency Checks on Old Live Server
> ------------------------------------------------
> Checking cluster versions ok
>
> old and new pg_controldata WAL segment sizes are invalid or do not
> match Failure, exiting
>
> I found the setting in the current version of the instance via "show all" as "wal_segment_size | 16MB". I guess my new instance should be "16MB" as well when running this "initdb --wal-segsize=16 -D /hostname/pg/NewInstance/data"?
>
Well the default is 16MB so you should not have to set it.
What does:
pg_controldata -D <11.5 data dir>
pg_controldata -D <12.1 data dir>
show for the setting Bytes per WAL segment: ?
--
Adrian Klaver
adrian.klaver@aklaver.com
