From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
Cc: tgl@sss.pgh.pa.us
Cc: alvherre@alvh.no-ip.org
Cc: nagata@sraoss.co.jp
Cc: thomas.munro@gmail.com
Cc: m.polyakova@postgrespro.ru
Cc: pgsql-hackers@postgresql.org
Cc: teodor@sigaev.ru
Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Date: Fri, 1 Apr 2022 07:34:33 +0200 (CEST)
Message-ID: <alpine.DEB.2.22.394.2204010731390.1603090@pseudo> (raw)
In-Reply-To: <20220401.095700.2266633058878785752.t-ishii@sranhm.sra.co.jp>
References: <202203280757.3tu4ovs3petm@alvherre.pgsql>
<701162.1648474392@sss.pgh.pa.us>
<20220401.095700.2266633058878785752.t-ishii@sranhm.sra.co.jp>
> Or those three columns always, sum_lag sum_lag_2, min_lag max_lag,
> skipped, retried retries?
>
> Anyway now that current CF is closing, it will not be possible to
> change those logging design soon. Or can we change the logging design
> even after CF is closed?
My 0.02€: I'm not sure how the official guidelines are to be interpreted
in that case, but if the design is to be changed, ISTM that it is better
to do it before a release instead of letting the release out with one
format and changing it in the next release?
--
Fabien.
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: coelho@cri.ensmp.fr, ishii@sraoss.co.jp, tgl@sss.pgh.pa.us, alvherre@alvh.no-ip.org, nagata@sraoss.co.jp, thomas.munro@gmail.com, m.polyakova@postgrespro.ru, teodor@sigaev.ru
Subject: Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
In-Reply-To: <alpine.DEB.2.22.394.2204010731390.1603090@pseudo>
* 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