Re: MaxOffsetNumber for Table AMs - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: MaxOffsetNumber for Table AMs
Date
Msg-id CAH2-Wz=2CvJ_z6vzY=W+HjX9QGGj8jKXQBKFpi6xMXReJutX6Q@mail.gmail.com
Whole thread Raw
In response to Re: MaxOffsetNumber for Table AMs  (Andres Freund <andres@anarazel.de>)
Responses Re: MaxOffsetNumber for Table AMs
List pgsql-hackers
On Wed, May 5, 2021 at 11:25 AM Andres Freund <andres@anarazel.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



pgsql-hackers by date:

Previous
From: "Joel Jacobson"
Date:
Subject: Re: COPY table_name (single_column) FROM 'iso-8859-1.txt' DELIMITER E'\n'
Next
From: Tom Lane
Date:
Subject: Re: Re: COPY table_name (single_column) FROM 'iso-8859-1.txt' DELIMITER E'\n'