| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, bruce(at)momjian(dot)us |
| Subject: | Re: optimize file transfer in pg_upgrade |
| Date: | 2025-03-18 17:37:02 |
| Message-ID: | tlkgkf3woe4ye2l4m4dnwui4wmqtajotozw5r3fhefyuv6hwrl@34xroqbvddpj |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2025-03-18 12:29:02 -0500, Nathan Bossart wrote:
> Here is a first sketch at a test that cycles through all the transfer modes
> and makes sure they succeed or fail with an error along the lines of "not
> supported on this platform." Each test verifies that some very simple
> objects make it to the new version, which we could of course expand on.
> Would something like this suffice?
I'd add a few more complications:
- Create and test a relation that was rewritten, to ensure we test the
relfilenode != oid case and one that isn't rewritten.
- Perhaps create a tablespace?
- Do we need a new old cluster for each of the modes? That seems like wasted
time? I guess it's required for --link...
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2025-03-18 17:39:12 | Re: md.c vs elog.c vs smgrreleaseall() in barrier |
| Previous Message | Nathan Bossart | 2025-03-18 17:29:02 | Re: optimize file transfer in pg_upgrade |