From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: MaxOffsetNumber for Table AMs |
Date: | 2021-05-05 18:40:14 |
Message-ID: | CAH2-Wz=2CvJ_z6vzY=W+HjX9QGGj8jKXQBKFpi6xMXReJutX6Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, May 5, 2021 at 11:25 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> Agreed. And we can increase the fit a good bit without needing invasive
> all-over changes. With those changes often even helping heap.
>
> E.g. tidbitmap.c's harcoded use of MaxHeapTuplesPerPage is a problem
> even for heap - we waste a lot of space that's not commonly used. A
> better datastructure (radix tree like I'd say, but several tree shaped
> approaches seem possible).
Agreed -- even if we only cared about heapam we still ought to do
something about tidbitmap.c's use of MaxHeapTuplesPerPage.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-05-05 18:45:41 | Re: Re: COPY table_name (single_column) FROM 'unknown.txt' DELIMITER E'\n' |
Previous Message | Joel Jacobson | 2021-05-05 18:38:51 | Re: COPY table_name (single_column) FROM 'unknown.txt' DELIMITER E'\n' |