| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: optimize file transfer in pg_upgrade |
| Date: | 2025-03-06 02:34:37 |
| Message-ID: | Z8kJveW4yBOI7Jtx@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Mar 05, 2025 at 03:40:52PM -0500, Greg Sabino Mullane wrote:
> I've seen various failures, but they always get caught quite early.
> Certainly early enough to easily abort, fix perms/mounts/etc., then retry.
> I think your instinct is correct that this reversion is more trouble than
> its worth. I don't think the pg_upgrade docs mention taking a backup, but
> that's always step 0 in my playbook, and that's the rollback plan in the
> unlikely event of failure.
Thank you, Greg and Robert, for sharing your thoughts. With that, here's
what I'm considering to be a reasonably complete patch set for this
feature. This leaves about a month for rigorous testing and editing, so
I'm hopeful it'll be ready v18.
--
nathan
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0001-initdb-Add-no-sync-data-files.patch | text/plain | 13.0 KB |
| v4-0002-pg_dump-Add-sequence-data.patch | text/plain | 5.0 KB |
| v4-0003-pg_upgrade-Add-swap-for-faster-file-transfer.patch | text/plain | 28.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-03-06 02:43:57 | Re: Update Unicode data to Unicode 16.0.0 |
| Previous Message | Nathan Bossart | 2025-03-06 02:19:36 | Re: Statistics Import and Export |