Re: [HACKERS] pgsql: Avoid coercing a whole-row variable that is already coerced

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: [HACKERS] pgsql: Avoid coercing a whole-row variable that is already coerced
Дата
Msg-id 29947.1507913791@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: [HACKERS] pgsql: Avoid coercing a whole-row variable that is already coerced  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: [HACKERS] pgsql: Avoid coercing a whole-row variable that isalready coerced  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Fri, Oct 13, 2017 at 5:57 AM, Amit Khandekar <amitdkhan.pg@gmail.com> wrote:
>> One thing we can do is : instead of calling
>> map_variable_attnos_mutator(), convert the var inside the if block for
>> "if (IsA(node, ConvertRowtypeExpr))". Please check the attached patch.
>> There, I have avoided coerced_var context variable.

> Tom, is this more like what you have in mind?

It's better ... but after reading the patched code, a lot of my remaining
beef is with the lack of clarity of the comments.  You need ESP to
understand what the function is trying to accomplish and what the
constraints are.  I'll take a whack at improving that and push.
        regards, tom lane


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Geoghegan
Дата:
Сообщение: Re: [HACKERS] [COMMITTERS] pgsql: Fix traversal of half-frozen update chains
Следующее
От: Adam Brusselback
Дата:
Сообщение: Re: [HACKERS] Discussion on missing optimizations