From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Paul Jungwirth <pj(at)illuminatedcomputing(dot)com> |
Subject: | Re: useless RangeIOData->typiofunc |
Date: | 2020-03-05 14:18:59 |
Message-ID: | 20200305141859.GA6736@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2020-Mar-04, Tom Lane wrote:
> Hm, I'm not sure that really lessens the cognitive load any, but
> if you do commit this please fix the dangling reference you left
> in the nearby comment:
>
> {
> TypeCacheEntry *typcache; /* range type's typcache entry */
> - Oid typiofunc; /* element type's I/O function */
> Oid typioparam; /* element type's I/O parameter */
> FmgrInfo proc; /* lookup result for typiofunc */
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> } RangeIOData;
Thanks -- ISTM it makes more sense to put the FmgrInfo before the
typioparam too:
typedef struct RangeIOData
{
TypeCacheEntry *typcache; /* range type's typcache entry */
FmgrInfo proc; /* element type's I/O function */
Oid typioparam; /* element type's I/O parameter */
} RangeIOData;
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Attachment | Content-Type | Size |
---|---|---|
range-typiofunc-cleanup-2.patch | text/x-diff | 1.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | tushar | 2020-03-05 14:19:37 | Re: [Proposal] Global temporary tables |
Previous Message | Asif Rehman | 2020-03-05 14:10:49 | Re: proposal: schema variables |