Re: Avoid mix char with bool type in comparisons

From: Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Avoid mix char with bool type in comparisons
Date: 2022-10-07 00:35:25
Message-ID: CAEudQArAKDpCth4dv2+ykSaiNGpusDZru3Xoza2UG2H2KT8Tuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Em qui., 6 de out. de 2022 às 21:21, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> escreveu:

> Ranier Vilela <ranier(dot)vf(at)gmail(dot)com> writes:
> > My main concerns is this point:
> > /* If already matched on earlier page, do no extra work */
> > - if (key->entryRes[j])
> > + if (key->entryRes[j] == GIN_TRUE)
> > continue;
>
> > If GIN_MAYBE cases are erroneously ignored.
>
> So, if that's a bug, you should be able to produce a test case?
>
No Tom, unfortunately I don't have the knowledge to create a test with
GIN_MAYBE values.

With the patch, all current tests pass.
Either there are no bugs, or there are no tests that detect this specific
case.
And I agree with you, without a test showing the bug,
there's not much chance of the patch progressing.

Unless someone with more knowledge can say that the patch improves
robustness.

regards,
Ranie Vilela

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2022-10-07 00:50:11 Re: Reducing the chunk header sizes on all memory context types
Previous Message Masahiko Sawada 2022-10-07 00:33:57 Re: Issue with pg_stat_subscription_stats