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

From: Ryan Murphy <ryanfmurphy(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(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 19:37:14
Message-ID: CAHeEsBe8pY0Mu4CrSwOu23bHds-pJZfcxuFQC1Cx8jJ2Eea3dQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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.
>
>
Thanks! Maybe I'll do some benchmarks.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2017-02-15 19:38:28 Re: Should we cacheline align PGXACT?
Previous Message Robert Haas 2017-02-15 19:36:44 Re: Parallel Index-only scan