| From: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr> |
|---|---|
| To: | Tatsuo Ishii <ishii(at)sraoss(dot)co(dot)jp> |
| Cc: | tgl(at)sss(dot)pgh(dot)pa(dot)us, alvherre(at)alvh(dot)no-ip(dot)org, nagata(at)sraoss(dot)co(dot)jp, thomas(dot)munro(at)gmail(dot)com, m(dot)polyakova(at)postgrespro(dot)ru, pgsql-hackers(at)postgresql(dot)org, teodor(at)sigaev(dot)ru |
| Subject: | Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors |
| Date: | 2022-04-01 05:34:33 |
| Message-ID: | alpine.DEB.2.22.394.2204010731390.1603090@pseudo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2022-04-01 05:38:51 | Re: Preventing indirection for IndexPageGetOpaque for known-size page special areas |
| Previous Message | Amit Kapila | 2022-04-01 05:24:06 | Re: unnecessary (same) restart_lsn handing in LogicalIncreaseRestartDecodingForSlot |