From: Dmitrii Bondar <d.bondar@postgrespro.ru>
To: lakshmi <lakshmigcdac@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Pgbench: remove synchronous prepare
Date: Thu, 16 Apr 2026 14:15:31 +0700
Message-ID: <980f17ee-1a2b-4feb-9286-01690eb3be20@postgrespro.ru> (raw)
In-Reply-To: <CAEvyyTgTR6yRuevy+PQQndfQBRh1nhtK8zs=EkQD-yeadbwT_Q@mail.gmail.com>
References: <2da56b59-acb6-4ee3-af6b-6e800115dc7f@postgrespro.ru>
<d8b4e3b2-a21f-4989-9663-3689f0d4232b@postgrespro.ru>
<cdb264ce-acb5-4a20-bd69-5eb924bef253@postgrespro.ru>
<CAEvyyTgTR6yRuevy+PQQndfQBRh1nhtK8zs=EkQD-yeadbwT_Q@mail.gmail.com>
Hi!
Thank you for reviewing my patch! Should I consider your review complete
and move the patch to ‘ready for committer’?
On 4/6/26 1:54 PM, lakshmi wrote:
>
>
> On Mon, Mar 23, 2026 at 11:45 AM Dmitrii Bondar
> <d.bondar@postgrespro.ru> wrote:
>
> Rebase.
>
> Hi Dmitrii,
>
> I tested the latest patch with PgBouncer in session pooling mode
> (pool size 20, 21 clients).
>
> Before applying the patch, pgbench got stuck under this setup and
> eventually hit a query_wait_timeout error.
>
> After applying the patch, pgbench runs smoothly even when clients
> are queued. I can see continuous progress output and normal
> throughput (~60k TPS), with no errors or stalls.
>
> The change works well in my testing.
>
> Thanks for the patch!
>
> Regards,
> Lakshmi G
>
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: d.bondar@postgrespro.ru, lakshmigcdac@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Pgbench: remove synchronous prepare
In-Reply-To: <980f17ee-1a2b-4feb-9286-01690eb3be20@postgrespro.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox