Re: Add Pipelining support in psql

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: "a(dot)kozhemyakin" <a(dot)kozhemyakin(at)postgrespro(dot)ru>
Cc: Daniel Verite <daniel(at)manitou-mail(dot)org>, Anthonin Bonnefoy <anthonin(dot)bonnefoy(at)datadoghq(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Add Pipelining support in psql
Date: 2025-04-16 16:18:01
Message-ID: Z__YOQJqBJYhezm2@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Apr 16, 2025 at 09:31:59PM +0700, a.kozhemyakin wrote:
> After commit 2cce0fe on master
>
> ERROR:  unexpected message type 0x50 during COPY from stdin
> CONTEXT:  COPY psql_pipeline, line 1
> Pipeline aborted, command did not run
> psql: common.c:1510: discardAbortedPipelineResults: Assertion `res == ((void
> *)0) || result_status == PGRES_PIPELINE_ABORTED' failed.
> Aborted (core dumped)

Reproduced here, thanks for the report. I'll look at that at the
beginning of next week, adding an open item for now.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2025-04-16 16:22:42 Re: A modest proposal: make parser/rewriter/planner inputs read-only
Previous Message Andrew Dunstan 2025-04-16 16:17:53 Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore