Date: Fri, 1 Apr 2022 07:34:33 +0200 (CEST)
From: Fabien COELHO <coelho@cri.ensmp.fr>
To: Tatsuo Ishii <ishii@sraoss.co.jp>
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: <20220401.095700.2266633058878785752.t-ishii@sranhm.sra.co.jp>
Message-ID: <alpine.DEB.2.22.394.2204010731390.1603090@pseudo>
References: <202203280757.3tu4ovs3petm@alvherre.pgsql>
 <701162.1648474392@sss.pgh.pa.us>
 <20220401.095700.2266633058878785752.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-53089504-1648791278=:1603090"
Archived-At: 
 <https://www.postgresql.org/message-id/alpine.DEB.2.22.394.2204010731390.1603090%40pseudo>
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-53089504-1648791278=:1603090
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8BIT


> 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.
--2056645051-53089504-1648791278=:1603090--