From: | Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | michael(dot)paquier(at)gmail(dot)com |
Cc: | pgsql-hackers(at)postgresql(dot)org, robertmhaas(at)gmail(dot)com |
Subject: | Re: Header and comments describing routines in incorrect shape in visibilitymap.c |
Date: | 2016-07-07 07:57:29 |
Message-ID: | 20160707.165729.251012514.horiguchi.kyotaro@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At Thu, 7 Jul 2016 16:48:00 +0900, Michael Paquier <michael(dot)paquier(at)gmail(dot)com> wrote in <CAB7nPqQO0AaCwhKsyTChxu8h9-KE0_H6qMaWrg4t9aDhq0yyhw(at)mail(dot)gmail(dot)com>
> On Thu, Jul 7, 2016 at 4:41 PM, Kyotaro HORIGUCHI
> <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> wrote:
> > So, the 'pinned' is not necessary here or should be added also to
> > _clear. I think the former is preferable since it is already
> > written in the comments for the functions and seems to be a bit
> > too detailed to be put here.
> >
> > - * visibilitymap_set - set a bit in a previously pinned page
> > + * visibilitymap_set - set bits in the visibility map
>
> As far as I know, it is possible to set one or two bits,
That's right.
> so I would
> think that using parenthesis makes more sense. Same when pinning a
> page, the caller may want to just set one of the two bits available.
> That's the choice I am trying to outline here.
I'm not strongly opposed to the paretheses. That's fine with me.
regards,
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Netanel Katzburg | 2016-07-07 08:01:37 | Disable WAL completely - Performance and Persistency research |
Previous Message | Fujii Masao | 2016-07-07 07:53:19 | EXPLAIN ANALYZE for parallel query doesn't report the SortMethod information. |