pgsql: Avoid coercing a whole-row variable that is already coerced.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Avoid coercing a whole-row variable that is already coerced.
Date: 2017-10-12 21:16:31
Message-ID: E1e2kqF-0001aB-8g@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2017-10-12 21:42:01 Re: pgsql: Avoid coercing a whole-row variable that is already coerced.
Previous Message Robert Haas 2017-10-12 20:51:01 pgsql: Use ResultRelInfo ** rather than ResultRelInfo * for tuple routi