Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1navT2-00072R-7z for pgsql-hackers@arkaria.postgresql.org; Sun, 03 Apr 2022 08:20:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1navSz-0002gM-Cr for pgsql-hackers@arkaria.postgresql.org; Sun, 03 Apr 2022 08:20:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1navSz-0002gD-3m for pgsql-hackers@lists.postgresql.org; Sun, 03 Apr 2022 08:20:09 +0000 Received: from sfr-1.cri.mines-paristech.fr ([77.158.180.225] helo=smtp.cri.ensmp.fr) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1navSx-0007lY-63 for pgsql-hackers@postgresql.org; Sun, 03 Apr 2022 08:20:08 +0000 Received: from pseudo (185.141.6.84.rev.sfr.net [84.6.141.185]) by smtp.cri.ensmp.fr (Postfix) with ESMTPSA id 98BF7C0133; Sun, 3 Apr 2022 10:23:30 +0200 (CEST) Date: Sun, 3 Apr 2022 10:20:05 +0200 (CEST) From: Fabien COELHO X-X-Sender: fabien@pseudo To: Tatsuo Ishii cc: tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org, nagata@sraoss.co.jp, thomas.munro@gmail.com, m.polyakova@postgrespro.ru, pgsql-hackers@postgresql.org, teodor@sigaev.ru Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors In-Reply-To: <20220403.152819.1855287099476193181.t-ishii@sranhm.sra.co.jp> Message-ID: References: <202203280757.3tu4ovs3petm@alvherre.pgsql> <701162.1648474392@sss.pgh.pa.us> <20220401.095700.2266633058878785752.t-ishii@sranhm.sra.co.jp> <20220403.152819.1855287099476193181.t-ishii@sranhm.sra.co.jp> User-Agent: Alpine 2.22 (DEB 394 2020-01-19) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="2056645051-1990285720-1648974005=:2117840" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --2056645051-1990285720-1648974005=:2117840 Content-Type: text/plain; format=flowed; charset=ISO-8859-15 Content-Transfer-Encoding: 8BIT >> Or those three columns always, sum_lag sum_lag_2, min_lag max_lag, >> skipped, retried retries? > > What about this? (a log line is not actually folded) > interval_start num_transactions sum_latency sum_latency_2 min_latency max_latency > failures serialization_failures deadlock_failures retried retries [ sum_lag sum_lag_2 min_lag max_lag [ skipped ] ] My 0.02¤: I agree that it would be better to have a more deterministic aggregated log format. ISTM that it should skip failures and lags if no fancy options has been selected, i.e.: [ fails ... retries [ sum_lag ... [ skipped ] ] ? Alterlatively, as the failure stuff is added to the format, maybe it could be at the end: [ sum_lag ... [ skipped [ fails ... retries ] ] ] ? > failures: > always 0 (if --max-tries is 1, the default) > sum of serialization_failures and deadlock_failures (if --max-tries is not 1) > > serialization_failures and deadlock_failures: > always 0 (if --max-tries is 1, the default) > 0 or more (if --max-tries is not 1) > > retried and retries: > always 0 (if --max-tries is 1, the default) > 0 or more (if --max-tries is not 1) > > Best reagards, > -- > Tatsuo Ishii > SRA OSS, Inc. Japan > English: http://www.sraoss.co.jp/index_en.php > Japanese:http://www.sraoss.co.jp > -- Fabien. --2056645051-1990285720-1648974005=:2117840--