Re: fixing typo in comment for restriction_is_or_clause

From: Japin Li <japinli(at)hotmail(dot)com>
To: Zhihong Yu <zyu(at)yugabyte(dot)com>
Cc: Richard Guo <guofenglinux(at)gmail(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 03:46:10
Message-ID: MEYP282MB166954D2DF97D3796B81DB07B6319@MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


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.

--
Regrads,
Japin Li.
ChengDu WenWu Information Technology Co.,Ltd.

Attachment Content-Type Size
v3-is-or.patch text/x-diff 2.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2022-10-25 03:57:36 Re: fix stats_fetch_consistency value in postgresql.conf.sample
Previous Message Peter Smith 2022-10-25 03:43:43 Re: GUC values - recommended way to declare the C variables?