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

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Fix a pg_dump scenario for platforms where SEEK_CUR != 1.
Date: 2025-06-03 18:53:44
Message-ID: aD9EuG2IGEEC5oTu@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

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

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2025-06-03 19:43:32 pgsql: Fix incorrect format placeholders
Previous Message Noah Misch 2025-06-03 18:19:37 pgsql: Fix a pg_dump scenario for platforms where SEEK_CUR != 1.