Re: GinPageIs* don't actually return a boolean - Mailing list pgsql-hackers

From Yury Zhuravlev
Subject Re: GinPageIs* don't actually return a boolean
Date
Msg-id c3f0eca7-9303-4a7d-9150-257dcc5d520d@postgrespro.ru
Whole thread Raw
In response to Re: GinPageIs* don't actually return a boolean  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: GinPageIs* don't actually return a boolean
Re: GinPageIs* don't actually return a boolean
List pgsql-hackers
Robert Haas wrote:
> On Wed, Mar 2, 2016 at 9:48 PM, Peter Eisentraut <peter_e@gmx.net> wrote:
>> On 2/11/16 9:30 PM, Michael Paquier wrote: ...
>
> We need to decide what to do about this.  I disagree with Peter: I
> think that regardless of stdbool, what we've got right now is sloppy
> coding - bad style if nothing else.  Furthermore, I think that while C
> lets you use any non-zero value to represent true, our bool type is
> supposed to contain only one of those two values.  Therefore, I think
> we should commit the full patch, back-patch it as far as somebody has
> the energy for, and move on.  But regardless, this patch can't keep
> sitting in the CommitFest - we either have to take it or reject it,
> and soon.
>

I know that we are trying to do the right thing. But right now there is an
error only in ginStepRight. Maybe now the fix this place, and we will think
about "bool" then? The patch is attached (small and simple).

Thanks.


--
Yury Zhuravlev
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
Attachment

pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: Odd system-column handling in postgres_fdw join pushdown patch
Next
From: Stas Kelvich
Date:
Subject: Re: fd.c: flush data problems on osx