[COMMITTERS] pgsql: Avoid coercing a whole-row variable that is already coerced. - Mailing list pgsql-committers

From Robert Haas
Subject [COMMITTERS] pgsql: Avoid coercing a whole-row variable that is already coerced.
Date
Msg-id E1e2kqF-0001aB-8g@gemulon.postgresql.org
Whole thread Raw
Responses Re: [COMMITTERS] pgsql: Avoid coercing a whole-row variable that is already coerced.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
Avoid coercing a whole-row variable that is already coerced.

Marginal efficiency and beautification hack.  I'm not sure whether
this case ever arises currently, but the pending patch for update
tuple routing will cause it to arise.

Amit Khandekar

Discussion: http://postgr.es/m/CAJ3gD9cazfppe7-wwUbabPcQ4_0SubkiPFD1+0r5_DkVNWo5yg@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/1c497fa72df7593d8976653538da3d0ab033207f

Modified Files
--------------
src/backend/rewrite/rewriteManip.c | 53 ++++++++++++++++++++++++++++++--------
1 file changed, 42 insertions(+), 11 deletions(-)


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

pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: [COMMITTERS] pgsql: Use ResultRelInfo ** rather than ResultRelInfo * for tuplerouti
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: Avoid coercing a whole-row variable that is already coerced.