Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wDGwu-002nkb-0D for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Apr 2026 07:15:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1wDGwt-004ZQz-0D for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Apr 2026 07:15:39 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1wDGws-004ZQr-26 for pgsql-hackers@lists.postgresql.org; Thu, 16 Apr 2026 07:15:38 +0000 Received: from mail.postgrespro.ru ([93.174.132.70]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1wDGwp-00000001HD1-3NgK for pgsql-hackers@lists.postgresql.org; Thu, 16 Apr 2026 07:15:37 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1776323732; bh=YHI6iohrPKbdqZA2/lLlVbvh27TvDqw4L6jQdAHkxKY=; h=Message-ID:Date:User-Agent:Subject:To:References:Cc:From: In-Reply-To:From; b=Xaclh0f3sIL0C5YjWj/N5+sr/I6pyTxtEVzzxxVEyU5pncanCcu+efoYAH3HNG3Ad CPf62pZ16r/rnm6wC+fhN073E9z2FLYPpMMGuaPPauzcaHtxR2BEA2uWc7/JEOlOUL 4F+bIpIrIZwudDJFluqk5d7MHGjpg/i5IJ5sdEhfQj5eGesNM8DqeVAMeSmi8KMB+n 0L/xO4IeDHwW4+8RKWTvppg0SY/Bvzq9uzqe3SHJLkOGw6VP7MvkMooEw8y/xqem8l KLSJNZhxa/xnS0MS6QFwLNFAaNO1nC+F26XV2w7t62+46aWedemuz3J56SC1lscJY4 6Prf2ektwOXQw== Received: from [10.8.4.218] (unknown [95.170.154.43]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: d.bondar@postgrespro.ru) by mail.postgrespro.ru (Postfix/465) with ESMTPSA id 28420611DB; Thu, 16 Apr 2026 10:15:32 +0300 (MSK) Content-Type: multipart/alternative; boundary="------------Yvk5tnn1mJy3EPkLGhL7A9Iw" Message-ID: <980f17ee-1a2b-4feb-9286-01690eb3be20@postgrespro.ru> Date: Thu, 16 Apr 2026 14:15:31 +0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: Pgbench: remove synchronous prepare To: lakshmi References: <2da56b59-acb6-4ee3-af6b-6e800115dc7f@postgrespro.ru> Content-Language: en-US Cc: pgsql-hackers@lists.postgresql.org From: Dmitrii Bondar In-Reply-To: X-KSMG-AntiPhishing: NotDetected, bases: 2026/04/16 06:25:00 X-KSMG-AntiSpam-Interceptor-Info: not scanned X-KSMG-AntiSpam-Status: not scanned, disabled by settings X-KSMG-AntiVirus: Kaspersky Secure Mail Gateway, version 3.0.0.9059, bases: 2026/04/15 22:51:00 #28402805 X-KSMG-AntiVirus-Status: NotDetected, skipped X-KSMG-LinksScanning: not scanned, disabled by settings X-KSMG-Message-Action: skipped X-KSMG-Rule-ID: 1 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------Yvk5tnn1mJy3EPkLGhL7A9Iw Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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 > 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 > > --------------Yvk5tnn1mJy3EPkLGhL7A9Iw Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit

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


--------------Yvk5tnn1mJy3EPkLGhL7A9Iw--