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

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

On Tue, Jun 03, 2025 at 06:19:37PM +0000, Noah Misch wrote:
> 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.

Whoops, that was a typo.  Thanks for fixing it.

-- 
nathan