Re: Suggestion to add --continue-client-on-abort option to pgbench - Mailing list pgsql-hackers

From Chao Li
Subject Re: Suggestion to add --continue-client-on-abort option to pgbench
Date
Msg-id DD5572D9-7271-4DB6-890D-E2CED3FFE6CA@gmail.com
Whole thread Raw
In response to Re: Suggestion to add --continue-client-on-abort option to pgbench  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Suggestion to add --continue-client-on-abort option to pgbench
List pgsql-hackers

> On Nov 13, 2025, at 17:40, Yugo Nagata <nagata@sraoss.co.jp> wrote:
>
> The following script:
>
> \startpipeline
> <queries list 1>
> \syncpipeline
> <queries list 2>
> \endpipeline
>
> can be considered equivalent to:
>
> BEGIN;
> <queries list 1>
> END;
> BEGIN;
> <queries list 2>
> END;

This looks like that every \sysnpipeline will start a new transaction, is that true?

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/







pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Idea to enhance pgbench by more modes to generate data (multi-TXNs, UNNEST, COPY BINARY)
Next
From: Amit Kapila
Date:
Subject: Re: Issue with logical replication slot during switchover