Re: fixing typo in comment for restriction_is_or_clause

From: Richard Guo <guofenglinux(at)gmail(dot)com>
To: Japin Li <japinli(at)hotmail(dot)com>
Cc: Zhihong Yu <zyu(at)yugabyte(dot)com>, John Naylor <john(dot)naylor(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: fixing typo in comment for restriction_is_or_clause
Date: 2022-10-25 04:01:50
Message-ID: CAMbWs48z_VvzFRT=ZJj9MvMVeqTPdjpfcBrPJrYOBr0QD2rbTQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 25, 2022 at 11:46 AM Japin Li <japinli(at)hotmail(dot)com> wrote:

>
> On Tue, 25 Oct 2022 at 11:07, Zhihong Yu <zyu(at)yugabyte(dot)com> wrote:
> > Please take a look at patch v2.
>
> Maybe we should define those functions in headers. See patch v3.

Yes, putting them in .h file is better to me. For the v3 patch, we can
do the same one-line trick for restriction_is_securely_promotable.

Thanks
Richard

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2022-10-25 04:11:55 Re: Understanding, testing and improving our Windows filesystem code
Previous Message Peter Smith 2022-10-25 03:57:36 Re: fix stats_fetch_consistency value in postgresql.conf.sample