pgsql: Fix a pg_dump scenario for platforms where SEEK_CUR != 1.

From: Noah Misch <noah(at)leadboat(dot)com>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Fix a pg_dump scenario for platforms where SEEK_CUR != 1.
Date: 2025-06-03 18:19:37
Message-ID: E1uMWEb-0002G2-2c@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Nathan Bossart 2025-06-03 18:53:44 Re: pgsql: Fix a pg_dump scenario for platforms where SEEK_CUR != 1.
Previous Message Etsuro Fujita 2025-06-03 10:45:34 Re: pgsql: postgres_fdw: Inherit the local transaction's access/deferrable