|
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----- 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 IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses. |
