Re: Avoid mix char with bool type in comparisons - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Avoid mix char with bool type in comparisons
Date
Msg-id CA+TgmoahJ=qpauaktUzSBR=9+V-Wh=K=d+RNL_hF4ujj9=evEg@mail.gmail.com
Whole thread Raw
In response to Re: Avoid mix char with bool type in comparisons  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Avoid mix char with bool type in comparisons  (Ranier Vilela <ranier.vf@gmail.com>)
List pgsql-hackers
On Fri, Oct 7, 2022 at 11:40 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> FWIW, I did take a look at this code, and I don't see any bug.
> The entryRes[] array entries are indeed GinTernaryValue, but it's
> obvious by inspection that matchPartialInPendingList only returns
> true or false, therefore collectMatchesForHeapRow also only deals
> in true or false, never maybe.  I do not think changing
> matchPartialInPendingList to return ternary would be an improvement,
> because then it'd be less obvious that it doesn't deal in maybe.

I mean if the code isn't buggy, I'm glad, but I think there should
have been more substantial grounds for getting you to spend time
looking at it. It's not asking too much for people to produce a
non-zero amount of evidence that the thing they are worried about is
actually a problem.

-- 
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Avoid mix char with bool type in comparisons
Next
From: Robert Haas
Date:
Subject: Re: Simplify event trigger support checking functions