Postgres Pro
Downloads
Home   >   mailing lists

pgsql: Fix a pg_dump scenario for platforms where SEEK_CUR != 1. - Mailing list pgsql-committers

From Noah Misch
Subject pgsql: Fix a pg_dump scenario for platforms where SEEK_CUR != 1.
Date
Msg-id E1uMWEb-0002G2-2c@gemulon.postgresql.org
Whole thread Raw
Responses Re: pgsql: Fix a pg_dump scenario for platforms where SEEK_CUR != 1.
List pgsql-committers
Tree view 
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(-)

pgsql-committers by date:

Previous
From: Fujii Masao
Date:
Subject: pgsql: Rename log_lock_failure GUC to log_lock_failures for consistency
Next
From: Nathan Bossart
Date:
Subject: Re: pgsql: Fix a pg_dump scenario for platforms where SEEK_CUR != 1.