Re: Unexpected table size usage for small composite arrays

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Erik Sjoblom <sjoblom65(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Unexpected table size usage for small composite arrays
Date: 2024-10-22 23:49:28
Message-ID: CAKFQuwY47deTv+txZvETGmtsdHUUDQ0aD3y3W1OMLDPrTcGTvA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Oct 22, 2024 at 4:42 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Tue, Oct 22, 2024 at 4:40 PM Erik Sjoblom <sjoblom65(at)gmail(dot)com> wrote:
>
>> I hear what you are saying Tom and what I have read says that it would
>> take 24 + 12 x N bytes for the array.
>>
>
> Whatever you are reading, or your interpretation of it, is flawed.
>

Since you are posting to -hackers anyway (not that figuring this out from
the user-facing documentation seems easy if possible at all...) here is
what Tom is referring to.

https://github.com/postgres/postgres/blob/a0bff38d133ac95fb56bbd868a128bba95ec46c9/src/include/access/htup_details.h#L54

David J.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2024-10-22 23:54:34 Re: Parallel heap vacuum
Previous Message David G. Johnston 2024-10-22 23:42:56 Re: Unexpected table size usage for small composite arrays