| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Hannu Krosing <hannuk(at)google(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, 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-06 02:53:21 |
| Message-ID: | 171f92ddd77306614e03954cd6c5cabff75afd48.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | tsunakawa.takay@fujitsu.com | 2021-05-06 02:54:10 | RE: [bug?] Missed parallel safety checks, and wrong parallel safety |
| Previous Message | Tom Lane | 2021-05-06 02:45:01 | Re: v14 mechanical code beautification patches |