Postgres Pro
Downloads
Home   >   mailing lists

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

From Robert Haas
Subject Re: [HACKERS] pgsql: Avoid coercing a whole-row variable that is already coerced
Date
Msg-id CA+TgmoYj8ynJOqnDT6ECC2uK7MT-zjj=_x8q_EJ2VnR1QG57aQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] pgsql: Avoid coercing a whole-row variable that is already coerced  (Amit Khandekar <amitdkhan.pg@gmail.com>)
Responses Re: [HACKERS] pgsql: Avoid coercing a whole-row variable that is already coerced
List pgsql-hackers
Tree view 
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?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
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: Alexander Korotkov
Date:
Subject: Re: [HACKERS] Predicate Locks for writes?
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Aggregate transition state merging vs. hypothetical set functions