From: Noah Misch <noah@leadboat.com>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Fix a pg_dump scenario for platforms where SEEK_CUR != 1.
Date: Tue, 03 Jun 2025 18:19:37 +0000
Message-ID: <E1uMWEb-0002G2-2c@gemulon.postgresql.org> (raw)
Fix a pg_dump scenario for platforms where SEEK_CUR != 1.
POSIX allows such platforms. Given the lack of complaints, we may not
currently test on such a platform. This is new in v18 (commit
7d5c83b4e90c7156655f98b7312a30ae5eeb4d27), so no back-patch.
Branch
------
master
Details
-------
https://git.postgresql.org/pg/commitdiff/0e164eb9f43626dc9e31f4bae26eeb3e8422584a
Modified Files
--------------
src/bin/pg_dump/pg_backup_archiver.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
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: noah@leadboat.com, pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix a pg_dump scenario for platforms where SEEK_CUR != 1.
In-Reply-To: <E1uMWEb-0002G2-2c@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