Re: [HACKERS] Does having a NULL column automatically exclude thetable from the tupleDesc cache? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] Does having a NULL column automatically exclude thetable from the tupleDesc cache?
Date
Msg-id 20170215181048.nc7e5yoeieusts3d@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] Does having a NULL column automatically exclude thetable from the tupleDesc cache?  (Ryan Murphy <ryanfmurphy@gmail.com>)
Responses Re: [HACKERS] Does having a NULL column automatically exclude thetable from the tupleDesc cache?
List pgsql-hackers
Ryan Murphy wrote:

> My question kind of remains though - does that mean that having any nulls
> in the tuple loses the ability to use the tupleDesc cache? and how much of
> a performance impact is this?  I'm sure there's a good reason why you can't
> really use the cache if you have a null column, just was curious of the
> implications.

attcacheoff can only be set positive for fields preceding any varlena
(typlen<0, but including the first such) or nullable values.  I don't
know how much faster it is with the cache; you can measure it if your
curiosity is strong enough -- just set the first column to nullable.

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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [HACKERS] Reporting xmin from VACUUMs
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Parallel Index Scans