Re: Header and comments describing routines in incorrect shape in visibilitymap.c

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Header and comments describing routines in incorrect shape in visibilitymap.c
Date: 2016-07-13 21:02:55
Message-ID: CAB7nPqRff531cT0ZtdQr-FDCTTHheUQnr54kiMHgyfBWR9qPzg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 14, 2016 at 4:29 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Jul 8, 2016 at 7:14 AM, Michael Paquier
> <michael(dot)paquier(at)gmail(dot)com> wrote:
>>> OK, that removes comment duplication. Also, what about replacing
>>> "bit(s)" by "one or more bits" in the comment terms where adapted?
>>> That's bikeshedding, but that's what this patch is about.
>>
>> Translating my thoughts into code, I get the attached.
>
> Seems reasonable, but is the last hunk a whitespace-only change?

Yes, sorry for that.
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-07-13 21:04:25 Re: rethinking dense_alloc (HashJoin) as a memory context
Previous Message David G. Johnston 2016-07-13 20:57:24 Re: unexpected psql "feature"