From: | vignesh C <vignesh21(at)gmail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
Cc: | Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Data type correction in pgstat_report_replslot function parameters |
Date: | 2021-04-03 01:38:57 |
Message-ID: | CALDaNm3834hp5QZPxGLvuJM02jhRzqbMD5Lpt-HKg3m3o2yEHw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Apr 2, 2021 at 1:59 PM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
>
>
>
> On 2021/04/02 11:20, vignesh C wrote:
> > On Thu, Apr 1, 2021 at 11:18 PM Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:
> >>
> >>
> >>
> >> On 2021/04/02 2:18, Jeevan Ladhe wrote:
> >>>
> >>>
> >>> On Thu, Apr 1, 2021 at 10:20 PM vignesh C <vignesh21(at)gmail(dot)com <mailto:vignesh21(at)gmail(dot)com>> wrote:
> >>>
> >>> Hi,
> >>>
> >>> While I was reviewing replication slot statistics code, I found one
> >>> issue in the data type used for pgstat_report_replslot function
> >>> parameters. We pass int64 variables to the function but the function
> >>> prototype uses int type. I I felt the function parameters should be
> >>> int64. Attached patch fixes the same.
> >>
> >> Isn't it better to use PgStat_Counter instead of int64?
> >>
> >
> > Thanks for your comment, the updated patch contains the changes for it.
>
> Thanks for updating the patch! Pushed.
Thanks for pushing.
Regards,
Vignesh
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-04-03 02:05:02 | Re: SP-GiST confusion: indexed column's type vs. index column type |
Previous Message | Tatsuo Ishii | 2021-04-03 01:34:42 | Re: Using COPY FREEZE in pgbench |