Re: BRIN range operator class - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: BRIN range operator class
Date
Msg-id 20150505190823.GN2523@alvh.no-ip.org
Whole thread Raw
In response to Re: BRIN range operator class  (Emre Hasegeli <emre@hasegeli.com>)
Responses Re: BRIN range operator class  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Looking at patch 04, it seems to me that it would be better to have
the OpcInfo struct carry the typecache struct rather than the type OID,
so that we can avoid repeated typecache lookups in brin_deform_tuple;
something like

/* struct returned by "OpcInfo" amproc */
typedef struct BrinOpcInfo
{/* Number of columns stored in an index column of this opclass */uint16        oi_nstored;
/* Opaque pointer for the opclass' private use */void       *oi_opaque;
/* Typecache entries of the stored columns */TypeCacheEntry oi_typcache[FLEXIBLE_ARRAY_MEMBER];
} BrinOpcInfo;

Looking into it now.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: add -s to vacuumdb
Next
From: Peter Eisentraut
Date:
Subject: Re: Auditing extension for PostgreSQL (Take 2)