| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | "Bossart, Nathan" <bossartn(at)amazon(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] pg_upgrade to clusters with a different WAL segment size |
| Date: | 2017-11-13 22:26:22 |
| Message-ID: | CAB7nPqT6RObVs_xD_oJOM_pQDoVPKkV7woEvWqDm9TAa=xe2jQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Nov 14, 2017 at 6:11 AM, Andres Freund <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2017-11-13 22:32:38 | Re: [HACKERS] pg_upgrade to clusters with a different WAL segment size |
| Previous Message | Tom Lane | 2017-11-13 22:09:42 | Re: Migration to PGLister - After |