Re: fixing typo in comment for restriction_is_or_clause
От
Richard Guo
Тема
Re: fixing typo in comment for restriction_is_or_clause
Дата
Msg-id
CAMbWs4-RXhgz0i4O1z62gt+bTLTM5vXYyYhgnius0j_txLH7hg@mail.gmail.com
Ответ на
Re: fixing typo in comment for restriction_is_or_clause (Alvaro Herrera)
Список
Дерево обсуждения
fixing typo in comment for restriction_is_or_clause Zhihong Yu <zyu@yugabyte.com>
Re: fixing typo in comment for restriction_is_or_clause John Naylor <john.naylor@enterprisedb.com>
Re: fixing typo in comment for restriction_is_or_clause Richard Guo <guofenglinux@gmail.com>
Re: fixing typo in comment for restriction_is_or_clause Alvaro Herrera <alvherre@alvh.no-ip.org>
Re: fixing typo in comment for restriction_is_or_clause Richard Guo <guofenglinux@gmail.com>
Re: fixing typo in comment for restriction_is_or_clause John Naylor <john.naylor@enterprisedb.com>
Re: fixing typo in comment for restriction_is_or_clause Richard Guo <guofenglinux@gmail.com>
Re: fixing typo in comment for restriction_is_or_clause Japin Li <japinli@hotmail.com>
Re: fixing typo in comment for restriction_is_or_clause Zhihong Yu <zyu@yugabyte.com>
Re: fixing typo in comment for restriction_is_or_clause Japin Li <japinli@hotmail.com>
Re: fixing typo in comment for restriction_is_or_clause Richard Guo <guofenglinux@gmail.com>
Re: fixing typo in comment for restriction_is_or_clause Japin Li <japinli@hotmail.com>
On Tue, Oct 25, 2022 at 3:37 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
On 2022-Oct-25, Richard Guo wrote:
> Agree with your point. Do you think we can further make the one-line
> function a macro or an inline function in the .h file?
We can, but should we?
> I think this function is called quite frequently during planning, so
> maybe doing that would bring a little bit of efficiency.
You'd need to measure it and show some gains.
Yeah, that is what has to be done to make it happen.
Thanks
Richard
Thanks
Richard
В списке pgsql-hackers по дате отправления
От: Alvaro Herrera
Дата:
