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

From Jeff Davis
Subject Re: MaxOffsetNumber for Table AMs
Date
Msg-id 63ff8eb7ecf64fa25000903a95d92775d8a57b34.camel@j-davis.com
Whole thread Raw
In response to Re: MaxOffsetNumber for Table AMs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: MaxOffsetNumber for Table AMs
List pgsql-hackers
On Fri, 2021-04-30 at 12:35 -0400, Tom Lane wrote:
> ISTM that would be up to the index AM.  We'd need some interlocks on
> which index AMs could be used with which table AMs in any case, I
> think.

I'm not sure why? It seems like we should be able to come up with
something that's generic enough.

> I think the hard part may really be in places like tidbitmap.c, which
> one would wish to be AM-independent, but right now it's quite
> specific
> to heap-style TIDs.  Maybe we can think of a way to parameterize it.

For my particular AM, being able to have a parameterized granularity
might be nice, but not required.

Regards,
    Jeff Davis





pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: MaxOffsetNumber for Table AMs
Next
From: Robert Haas
Date:
Subject: Re: MaxOffsetNumber for Table AMs