Re: pg_stat_wal_write statistics view

From: vinayak <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>
To: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>
Cc: Julien Rouhaud <julien(dot)rouhaud(at)dalibo(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat_wal_write statistics view
Date: 2017-03-16 05:54:04
Message-ID: 6f60e4ca-0a94-4d5c-8b99-3d37ff9ce9d3@lab.ntt.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 2017/03/16 14:46, Haribabu Kommi wrote:
>
>
> On Thu, Mar 16, 2017 at 4:15 PM, vinayak
> <Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp
> <mailto:Pokale_Vinayak_q3(at)lab(dot)ntt(dot)co(dot)jp>> wrote:
>
> On 2017/03/16 10:34, Haribabu Kommi wrote:
>>
>> Updated patch attached.
> The patch looks good to me.
>
> Thanks for the review.
>
> How about rename the view as "pg_stat_walwriter"?
>
>
> With the use of name "walwriter" instead of "walwrites", the
> user may confuse that this view is used for displaying
> walwriter processes statistics. But actually it is showing
> the WAL writes activity in the instance. Because of this
> reason, I went with the name of "walwrites".
Understood. Thanks.
>
> 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 sure
> whether is it required to include WAL in every column?
> I am fine to change if others have the same opinion of
> adding WAL to column names.
>
Ok.

Regards,
Vinayak Pokale
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2017-03-16 06:31:45 Re: new set of psql patches for loading (saving) data from (to) text, binary files
Previous Message Haribabu Kommi 2017-03-16 05:46:02 Re: pg_stat_wal_write statistics view