Re: [HACKERS] pg_upgrade to clusters with a different WAL segment size - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: [HACKERS] pg_upgrade to clusters with a different WAL segment size
Date
Msg-id CAB7nPqT6RObVs_xD_oJOM_pQDoVPKkV7woEvWqDm9TAa=xe2jQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] pg_upgrade to clusters with a different WAL segmentsize  (Andres Freund <andres@anarazel.de>)
Responses Re: [HACKERS] pg_upgrade to clusters with a different WAL segmentsize  (Andres Freund <andres@anarazel.de>)
List 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


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Migration to PGLister - After
Next
From: Andres Freund
Date:
Subject: Re: [HACKERS] pg_upgrade to clusters with a different WAL segmentsize