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

From Jeff Davis
Subject Re: MaxOffsetNumber for Table AMs
Date
Msg-id 171f92ddd77306614e03954cd6c5cabff75afd48.camel@j-davis.com
Whole thread Raw
In response to Re: MaxOffsetNumber for Table AMs  (Hannu Krosing <hannuk@google.com>)
Responses Re: MaxOffsetNumber for Table AMs
Re: MaxOffsetNumber for Table AMs
List pgsql-hackers
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.

Regards,
    Jeff Davis






pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: v14 mechanical code beautification patches
Next
From: "tsunakawa.takay@fujitsu.com"
Date:
Subject: RE: [bug?] Missed parallel safety checks, and wrong parallel safety