Re: pgbench logging broken by time logic changes
От | Andrew Dunstan |
---|---|
Тема | Re: pgbench logging broken by time logic changes |
Дата | |
Msg-id | a3be3485-3a5c-7654-78f6-817749e720b3@dunslane.net обсуждение исходный текст |
Ответ на | Re: pgbench logging broken by time logic changes (Fabien COELHO <coelho@cri.ensmp.fr>) |
Ответы |
Re: pgbench logging broken by time logic changes
|
Список | pgsql-hackers |
On 6/20/21 5:02 AM, Fabien COELHO wrote: > >> Upon reflection, that amounts to the same thing really, so yeah, >> scratch that plan. I'll defer until after that (and then I'll be >> leaning more towards the revert option). > > Sigh. I do not understand anything about the decision processus. Yes, sometimes it passeth all understanding. There will certainly be a BETA3, and in every recent year except last year there has been a BETA4. If this were core server code threatening data integrity I would be inclined to be more strict, but after all pg_bench is a utility program, and I think we can allow a little more latitude. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: