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

From Tom Lane
Subject Re: [HACKERS] pgsql: Avoid coercing a whole-row variable that is already coerced
Date
Msg-id 29947.1507913791@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] pgsql: Avoid coercing a whole-row variable that is already coerced  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: [HACKERS] pgsql: Avoid coercing a whole-row variable that isalready coerced
List 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 by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] [COMMITTERS] pgsql: Fix traversal of half-frozen update chains
Next
From: Adam Brusselback
Date:
Subject: Re: [HACKERS] Discussion on missing optimizations