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

From Peter Geoghegan
Subject Re: MaxOffsetNumber for Table AMs
Date
Msg-id CAH2-Wz=cPMa6bnzkEuniCpskrPUNH-VbM-DNBtHOa2+7XghS8Q@mail.gmail.com
Whole thread Raw
In response to Re: MaxOffsetNumber for Table AMs  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: MaxOffsetNumber for Table AMs
List pgsql-hackers
On Wed, May 5, 2021 at 10:33 AM Robert Haas <robertmhaas@gmail.com> wrote:
> I don't know what to say here. I think it's unrealistic to believe
> that a very new API that has only 1 in-core user is going to be fully
> stable, or that we can know how it might evolve. I can understand why
> you and probably other people want that, but if somebody figures out a
> way to make some part of core significantly better and it requires
> changing that API, they're going to change the API, not give up on the
> idea.

I strongly agree. More generally, we need to decide what downsides
we're willing to live with.

What we have right now has little chance of failing. It also has
little chance of succeeding (except for something like zheap, which
can presumably get by with the heapam's idea of TID).

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Isaac Morland
Date:
Subject: Re: COPY table_name (single_column) FROM 'iso-8859-1.txt' DELIMITER E'\n'
Next
From: Robert Haas
Date:
Subject: Re: MaxOffsetNumber for Table AMs