Re: Add \syncpipeline command to pgbench - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Add \syncpipeline command to pgbench
Date
Msg-id Za4IObZkDjrO4TcS@paquier.xyz
Whole thread Raw
In response to Re: Add \syncpipeline command to pgbench  (Anthonin Bonnefoy <anthonin.bonnefoy@datadoghq.com>)
Responses Re: Add \syncpipeline command to pgbench
List pgsql-hackers
On Fri, Jan 19, 2024 at 08:55:31AM +0100, Anthonin Bonnefoy wrote:
> I've updated the doc to group the commands. It does look better and
> more consistent with similar command groups like \if.

I was playing with a few meta command scenarios while looking at this
patch, and this sequence generates an error that should never happen:
$ cat /tmp/test.sql
\startpipeline
\syncpipeline
$ pgbench -n -f /tmp/test.sql -M extended
[...]
pgbench: error: unexpected transaction status 1
pgbench: error: client 0 aborted while receiving the transaction status

It looks to me that we need to be much smarter than that for the error
handling we'd need when a sync request is optionally sent when a
transaction stops at the end of pgbench.  Could you look at it?
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: jian he
Date:
Subject: Re: remaining sql/json patches
Next
From: Peter Smith
Date:
Subject: Re: Moving forward with TDE [PATCH v3]