Re: MaxOffsetNumber for Table AMs

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Jeff Davis <pgsql(at)j-davis(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-03 16:59:45
Message-ID: CAH2-WznVFOQESbnB5RVgczJcEntnzzRavcTRM4AvvWtKGCTSVg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 3, 2021 at 9:45 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> But if you're saying those identifiers have to be fixed-width and 48
> (or even 64) bits, I disagree that we wish to have such a requirement
> in perpetuity.

Once you require that TID-like identifiers must point to particular
versions (as opposed to particular logical rows), you also virtually
require that the identifiers must always be integer-like (though not
necessarily block-based and not necessarily 6 bytes). You've
practically ensured that clustered index tables (and indirect indexes)
will never be possible by accepting this. Those designs are the only
real reason to have truly variable-length TID-like identifiers IMV (as
opposed to 2 or perhaps even 3 standard TID widths).

You don't accept any of that, though. Fair enough. I predict that
avoiding making a hard choice will make Jeff's work here a lot harder,
though.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2021-05-03 17:22:00 Re: MaxOffsetNumber for Table AMs
Previous Message Martín Marqués 2021-05-03 16:48:21 Update maintenance_work_mem/autovacuum_work_mem to reflect the 1GB limitation with VACUUM