From: Nathan Bossart <nathandbossart@gmail.com>
To: Noah Misch <noah@leadboat.com>
Cc: pgsql-committers@lists.postgresql.org
Subject: Re: pgsql: Fix a pg_dump scenario for platforms where SEEK_CUR != 1.
Date: Tue, 3 Jun 2025 13:53:44 -0500
Message-ID: <aD9EuG2IGEEC5oTu@nathan> (raw)
In-Reply-To: <E1uMWEb-0002G2-2c@gemulon.postgresql.org>
References: <E1uMWEb-0002G2-2c@gemulon.postgresql.org>
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
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: nathandbossart@gmail.com, 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: <aD9EuG2IGEEC5oTu@nathan>
* 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