From: Tomas Vondra <tomas.vondra@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Check HAVE_COPY_FILE_RANGE before calling copy_file_range
Date: Fri, 05 Apr 2024 17:38:44 +0000
Message-ID: <E1rsnWW-000fQ0-DC@gemulon.postgresql.org> (raw)
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(+)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-committers@postgresql.org
Cc: tomas.vondra@postgresql.org, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Check HAVE_COPY_FILE_RANGE before calling copy_file_range
In-Reply-To: <E1rsnWW-000fQ0-DC@gemulon.postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox