Re: [HACKERS] pg_upgrade to clusters with a different WAL segment size
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Andres Freund <andres@anarazel.de>
Cc: "Bossart, Nathan" <bossartn@amazon.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2017-11-13T22:26:22Z
Lists: pgsql-hackers
On Tue, Nov 14, 2017 at 6:11 AM, Andres Freund <andres@anarazel.de> wrote: > Hm. I'm not really on-board with doing this in pg_upgrade. A more > logical place seems to be pg_resetwal or something - there's no need to > force a pg_upgrade cycle (which is pretty expensive on clusters with a > significant number of objects) for somebody that wants to change the > segment size of a cluster without changing the major version. > pg_resetwal or a new tool seems like a more appropriate places for this. pg_upgrade makes use of pg_resetwal, so I am assuming that what Nathan means is actually what you mean, so as pg_upgrade gains as well an option with the segment size which will wrap the pg_resetwal's call. -- Michael
Commits
-
pg_resetwal: Prevent division-by-zero errors
- f1a074b146c9 11.0 landed
-
Make WAL segment size configurable at initdb time.
- fc49e24fa69a 11.0 cited