pgsql: Check HAVE_COPY_FILE_RANGE before calling copy_file_range - Mailing list pgsql-committers

From Tomas Vondra
Subject pgsql: Check HAVE_COPY_FILE_RANGE before calling copy_file_range
Date
Msg-id E1rsnWW-000fQ0-DC@gemulon.postgresql.org
Whole thread Raw
List 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

Details
-------
https://git.postgresql.org/pg/commitdiff/079d94ab3412fdeda637a24b17bde53c576b0007

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


pgsql-committers by date:

Previous
From: Tomas Vondra
Date:
Subject: pgsql: Allow using copy_file_range in write_reconstructed_file
Next
From: Robert Haas
Date:
Subject: pgsql: Fix incorrect calculation in BlockRefTableEntryGetBlocks.