| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | "Lu, Dan" <Dan(dot)Lu(at)sig(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Upgrade check failed from 11.5 to 12.1 |
| Date: | 2020-12-19 15:28:07 |
| Message-ID: | 43b12147-5346-796d-09d9-f08cedaa1c1f@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-12-19 15:32:03 | Re: FATAL: could not load library "/usr/pgsql-13/lib/libpqwalreceiver.so" during replication |
| Previous Message | Rambabu V | 2020-12-19 10:54:44 | FATAL: could not load library "/usr/pgsql-13/lib/libpqwalreceiver.so" during replication |