Re: [HACKERS] pg_stat_wal_write statistics view
От | vinayak |
---|---|
Тема | Re: [HACKERS] pg_stat_wal_write statistics view |
Дата | |
Msg-id | 6f60e4ca-0a94-4d5c-8b99-3d37ff9ce9d3@lab.ntt.co.jp обсуждение исходный текст |
Ответ на | Re: [HACKERS] pg_stat_wal_write statistics view (Haribabu Kommi <kommi.haribabu@gmail.com>) |
Ответы |
Re: pg_stat_wal_write statistics view
|
Список | pgsql-hackers |
On 2017/03/16 14:46, Haribabu Kommi wrote:
Understood. Thanks.On Thu, Mar 16, 2017 at 4:15 PM, vinayak <Pokale_Vinayak_q3@lab.ntt.co.jp> wrote:On 2017/03/16 10:34, Haribabu Kommi wrote:The patch looks good to me.Updated patch attached.Thanks for the review.How about rename the view as "pg_stat_walwriter"?With the use of name "walwriter" instead of "walwrites", theuser may confuse that this view is used for displayingwalwriter processes statistics. But actually it is showingthe WAL writes activity in the instance. Because of thisreason, I went with the name of "walwrites".
Ok.The columns of view :
backend_writes -> backend_wal_writes
writes-> background_wal_writes
write_blocks-> wal_write_blocks
write_time->wal_write_time
sync_time->wal_sync_time
As the view name already contains WAL, I am not surewhether is it required to include WAL in every column?I am fine to change if others have the same opinion ofadding WAL to column names.
Regards,
Vinayak Pokale
NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: