Re: Does having a NULL column automatically exclude the table from the tupleDesc cache?

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Ryan Murphy <ryanfmurphy(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Does having a NULL column automatically exclude the table from the tupleDesc cache?
Date: 2017-02-15 18:10:48
Message-ID: 20170215181048.nc7e5yoeieusts3d@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-02-15 18:39:43 Re: Parallel Index Scans
Previous Message Alvaro Herrera 2017-02-15 18:05:06 Re: Reporting xmin from VACUUMs