Re: pgsql: Track block level checksum failures in pg_stat_database

Поиск
Список
Период
Сортировка
От Julien Rouhaud
Тема Re: pgsql: Track block level checksum failures in pg_stat_database
Дата
Msg-id CAOBaU_ZqYVg5_o4CTz3PTbqmwBdf8PfXeoohibrbwcxS+GW=mw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: pgsql: Track block level checksum failures in pg_stat_database  (Magnus Hagander <magnus@hagander.net>)
Ответы Re: pgsql: Track block level checksum failures in pg_stat_database  (Magnus Hagander <magnus@hagander.net>)
Список pgsql-committers
On Wed, May 1, 2019 at 12:04 PM Magnus Hagander <magnus@hagander.net> wrote:
>
> Looks good to me in general
>
> I don't see the reasoning behind changing the name from msg_autovacuum to msg_autovacuum_start anywhere, perhaps I
misseda part of the discussion? Was that a change intended to be part of it?
 

That wasn't discussed, I should have mentioned it sorry.  I just
changed it for consistency while at it, as it seemed a little bit
ambiguous or error prone:

PgStat_MsgAutovacStart -> msg_autovacuum
PgStat_MsgVacuum -> msg_vacuum

As the member of the union weren't used anywhere, I thought it's ok to
rename it now they're used.  I'm not strongly attached to this change,
so feel free to discard it.



В списке pgsql-committers по дате отправления:

Предыдущее
От: Magnus Hagander
Дата:
Сообщение: Re: pgsql: Track block level checksum failures in pg_stat_database
Следующее
От: Magnus Hagander
Дата:
Сообщение: Re: pgsql: Track block level checksum failures in pg_stat_database