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:

pgsql: Fix incorrect format placeholders

Fix incorrect format placeholders Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/58fbfde152b28ca119fef4168550a1a4fef61560 Modified Files -- src/backend/storage/buffer/bufmgr.c | 2 +- src/backend/storage/buffer/localbuf.c | 2 +- src/backend/utils/adt/p

pgsql: psql: Abort connection when using \syncpipeline after COPY TO/FR

psql: Abort connection when using \syncpipeline after COPY TO/FROM When the backend reads COPY data, it ignores all sync messages, as per c01641f8aed0. With psql pipelines, it is possible to manually send sync messages with \sendpipeline which leaves the frontend in an unrecoverable state as the

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

On Tue, Jun 03, 2025 at 06:19:37PM +, 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 > 7d5c83b4e90c7156655f98b7312a30ae5eeb