Re: pg_upgrade --copy-file-range

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_upgrade --copy-file-range
Date: 2023-12-24 02:57:19
Message-ID: ZYeeD4mIcT_y5APF@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Dec 23, 2023 at 09:52:59AM +1300, Thomas Munro wrote:
> As it happens I was just thinking about this particular patch because
> I suddenly had a strong urge to teach pg_combinebackup to use
> copy_file_range. I wonder if you had the same idea...

Yeah, +1. That would make copy_file_blocks() more efficient where the
code is copying 50 blocks in batches because it needs to reassign
checksums to the blocks copied.
--
Michael

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ivan Kush 2023-12-24 11:27:47 Re: Autonomous transactions 2023, WIP
Previous Message Michael Paquier 2023-12-24 02:30:21 Re: pgsql: Prevent tuples to be marked as dead in subtransactions on standb