Re: fixing typo in comment for restriction_is_or_clause

From: John Naylor <john(dot)naylor(at)enterprisedb(dot)com>
To: Zhihong Yu <zyu(at)yugabyte(dot)com>
Cc: PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: fixing typo in comment for restriction_is_or_clause
Date: 2022-10-25 02:05:10
Message-ID: CAFBsxsGKV_M52XrtT3xhXnvstU61M6wb5GrWbzMt2Zj09FPJmA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 25, 2022 at 12:19 AM Zhihong Yu <zyu(at)yugabyte(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2022-10-25 02:13:44 Re: Question about savepoint level?
Previous Message Julien Rouhaud 2022-10-25 01:55:59 Re: [PATCHES] Post-special page storage TDE support