Re: 64 bit transaction id - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: 64 bit transaction id
Date
Msg-id 20191104194455.rcmdbytofjejhq3m@development
Whole thread Raw
In response to Re: 64 bit transaction id  (Andres Freund <andres@anarazel.de>)
Responses Re: 64 bit transaction id
List pgsql-hackers
On Mon, Nov 04, 2019 at 10:44:53AM -0800, Andres Freund wrote:
>Hi,
>
>On 2019-11-04 19:39:18 +0100, Tomas Vondra wrote:
>> On Mon, Nov 04, 2019 at 10:04:09AM -0800, Andres Freund wrote:
>> > And "without causing significant issues elsewhere" unfortunately
>> > includes continuing to allow pg_upgrade to work.
>
>> Yeah. I suppose we could have a different AM implementing this, but
>> maybe that's not possible ...
>
>Entirely possible. But the amount of code duplication / unnecessary
>branching and the user confusion from two very similar AMs, would have
>to be weighed against the benefits.
>

Agreed. I think code complexity is part of the trade-off. IMO it's fine
to hack existing heap AM initially, and only explore the separate AM if
that turns out to be promising.

regards

-- 
Tomas Vondra                  http://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services 



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: v12 and pg_restore -f-
Next
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index.