Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors - Mailing list pgsql-hackers

From Fabien COELHO
Subject Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Date
Msg-id alpine.DEB.2.22.394.2204010731390.1603090@pseudo
Whole thread Raw
In response to Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors  (Tatsuo Ishii <ishii@sraoss.co.jp>)
List pgsql-hackers

> 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.

pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: unnecessary (same) restart_lsn handing in LogicalIncreaseRestartDecodingForSlot
Next
From: Michael Paquier
Date:
Subject: Re: Preventing indirection for IndexPageGetOpaque for known-size page special areas