Postgres Pro
Downloads
Home   >   mailing lists

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

From Richard Guo
Subject Re: fixing typo in comment for restriction_is_or_clause
Date
Msg-id CAMbWs48z_VvzFRT=ZJj9MvMVeqTPdjpfcBrPJrYOBr0QD2rbTQ@mail.gmail.com
Whole thread Raw
In response to Re: fixing typo in comment for restriction_is_or_clause  (Japin Li <japinli@hotmail.com>)
List pgsql-hackers
Tree view

On Tue, Oct 25, 2022 at 11:46 AM Japin Li <japinli@hotmail.com> wrote:

On Tue, 25 Oct 2022 at 11:07, Zhihong Yu <zyu@yugabyte.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

pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: fix stats_fetch_consistency value in postgresql.conf.sample
Next
From: Thomas Munro
Date:
Subject: Re: Understanding, testing and improving our Windows filesystem code