Re: 64 bit transaction id

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: Павел Ерёмин <shnoor111gmail(at)yandex(dot)ru>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: 64 bit transaction id
Date: 2019-11-04 18:44:53
Message-ID: 20191104184453.v3hblaesodocz53z@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-11-04 18:53:00 Re: Missed check for too-many-children in bgworker spawning
Previous Message Tomas Vondra 2019-11-04 18:39:18 Re: 64 bit transaction id