Quick Links

pgsql: Check HAVE_COPY_FILE_RANGE before calling copy_file_range

From:	Tomas Vondra <tomas(dot)vondra(at)postgresql(dot)org>
To:	pgsql-committers(at)lists(dot)postgresql(dot)org
Subject:	pgsql: Check HAVE_COPY_FILE_RANGE before calling copy_file_range
Date:	2024-04-05 17:38:44
Message-ID:	E1rsnWW-000fQ0-DC@gemulon.postgresql.org
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-committers

Check HAVE_COPY_FILE_RANGE before calling copy_file_range

Fix a mistake in ac8110155132 - write_reconstructed_file() called
copy_file_range() without properly checking HAVE_COPY_FILE_RANGE.

Reported by several macOS machines. Also reported by cfbot, but I missed
that issue before commit.

Branch
------
master

Modified Files
--------------
src/bin/pg_combinebackup/reconstruct.c | 4 ++++
1 file changed, 4 insertions(+)

	From	Date	Subject
Next Message	Robert Haas	2024-04-05 17:50:41	pgsql: Fix incorrect calculation in BlockRefTableEntryGetBlocks.
Previous Message	Tomas Vondra	2024-04-05 17:25:34	pgsql: Allow using copy_file_range in write_reconstructed_file