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

From Robert Haas
Subject Re: [HACKERS] pgsql: Avoid coercing a whole-row variable that isalready coerced
Date
Msg-id CA+TgmoaL8MJ0UkxfEBK0_sCWsv2J_omYbmbtUEQgVhiWBOGMYg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] pgsql: Avoid coercing a whole-row variable that is already coerced  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Oct 13, 2017 at 12:56 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> 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.

OK, thanks.   The good thing is, now that we know you have ESP, you
can use it with the Ouija board Andres used to decide whether to apply
sizeof to the variable or the type.  That's got to be a win.

-- 
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: Robert Haas
Date:
Subject: Re: [HACKERS] Improve catcache/syscache performance.
Next
From: "Joshua D. Drake"
Date:
Subject: Re: [HACKERS] Determine state of cluster (HA)