Re: MaxOffsetNumber for Table AMs

On Wed, May 5, 2021 at 10:53 PM Jeff Davis <pgsql@j-davis.com> wrote:
> On Thu, 2021-05-06 at 03:26 +0200, Hannu Krosing wrote:
> > How hard would it be to declare TID as current ItemPointerData with
> > some values prohibited (NULL, SpecTokenOffsetNumber = 0xfffe,
> > MovedPartitionsOffsetNumber = 0xfffd, presumably also 0xffff ?).
>
> I don't think there's consensus in this thread that we want to do that,
> but I'd be fine with it.
>
> It's possible but not trivial. tidbitmap.c would be the biggest
> challenge, I think.

I think that would be fine, too. I don't think it's the ideal
situation, but it seems like a clear improvement over what we have
now. We might want to reserve a few values for future projects that
might need distinguished values like SpecTokenOffsetNumber or
MovedPartitionsOffsetNumber, though, so we don't completely box
ourselves into a corner.

-- 
Robert Haas
EDB: http://www.enterprisedb.com