Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: old and new pg_controldata WAL segment sizes are invalid or do
 not match
From: =?utf-8?Q?Paul_F=C3=B6rster?= <paul.foerster@gmail.com>
In-Reply-To: 
 <CAAiDzSeEEfhxjfT-v+DDySHnfB7N9y_QezQizuRV8RKQ0LDGSg@mail.gmail.com>
Date: Thu, 18 Jun 2020 11:45:47 +0200
Cc: pgsql-admin@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <AB36E2E4-BBD3-4288-9AC9-E80C1E5869DD@gmail.com>
References: 
 <CAAiDzSeEEfhxjfT-v+DDySHnfB7N9y_QezQizuRV8RKQ0LDGSg@mail.gmail.com>
To: ram pratap maurya <rampratap0000@gmail.com>
Precedence: bulk

Hi ram,

> On 17. Jun, 2020, at 23:05, ram pratap maurya =
<rampratap0000@gmail.com> wrote:
> old and new pg_controldata WAL segment sizes are invalid or do not =
match
> Failure, exiting

delete the *new* PostgreSQL cluster (it should be empty anyway) and =
reinitialize it setting the wal-segsize to the same as the old cluster:

$ initdb --wal-segsize=3D<size> ...

(see https://www.postgresql.org/docs/current/app-initdb.html)

Then perform the upgrade as you tried before.

After that, you can, if you want, reset the size to a new one using =
pg_resetwal. But make sure you first do a really clean backup!

$ pg_resetwal --wal-segsize=3D<new_size> ...
(see https://www.postgresql.org/docs/current/app-pgresetwal.html)

But know what you're doing! Try on a test database first to see how it =
works.

Cheers,
Paul=