Re: fixing typo in comment for restriction_is_or_clause - Mailing list pgsql-hackers

From John Naylor
Subject Re: fixing typo in comment for restriction_is_or_clause
Date
Msg-id CAFBsxsGKV_M52XrtT3xhXnvstU61M6wb5GrWbzMt2Zj09FPJmA@mail.gmail.com
Whole thread Raw
In response to fixing typo in comment for restriction_is_or_clause  (Zhihong Yu <zyu@yugabyte.com>)
Responses Re: fixing typo in comment for restriction_is_or_clause  (Richard Guo <guofenglinux@gmail.com>)
List pgsql-hackers

On Tue, Oct 25, 2022 at 12:19 AM Zhihong Yu <zyu@yugabyte.com> wrote:
>
> Hi,
> When I was looking at src/backend/optimizer/util/restrictinfo.c, I found a typo in one of the comments.

Using "t" as an abbreviation for "true" was probably intentional, so not a typo. There is no doubt what the behavior is.

> I also took the chance to simplify the code a little bit.

It's perfectly clear and simple now, even if it doesn't win at "code golf".

--
John Naylor
EDB: http://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Julien Rouhaud
Date:
Subject: Re: [PATCHES] Post-special page storage TDE support
Next
From: Richard Guo
Date:
Subject: Re: Question about savepoint level?