Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors

Поиск
Список
Период
Сортировка
От Fabien COELHO
Тема Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors
Дата
Msg-id alpine.DEB.2.22.394.2204010731390.1603090@pseudo
обсуждение исходный текст
Ответ на Re: [HACKERS] WIP aPatch: Pgbench Serialization and deadlock errors  (Tatsuo Ishii <ishii@sraoss.co.jp>)
Список 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 по дате отправления: