Re: Suggestion to add --continue-client-on-abort option to pgbench

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Rintaro Ikeda <ikedarintarof(at)oss(dot)nttdata(dot)com>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>, "slpmcf(at)gmail(dot)com" <slpmcf(at)gmail(dot)com>, "boekewurm+postgres(at)gmail(dot)com" <boekewurm+postgres(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>
Subject: Re: Suggestion to add --continue-client-on-abort option to pgbench
Date: 2025-11-13 10:17:37
Message-ID: DD5572D9-7271-4DB6-890D-E2CED3FFE6CA@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Nov 13, 2025, at 17:40, Yugo Nagata <nagata(at)sraoss(dot)co(dot)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/

In response to

Responses

Browse pgsql-hackers by date

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