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

From Andres Freund
Subject Re: 64 bit transaction id
Date
Msg-id 20191104180409.ygj3tkmx4ospcpi2@alap3.anarazel.de
Whole thread Raw
In response to Re: 64 bit transaction id  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: 64 bit transaction id  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
List pgsql-hackers
Hi,

(I've not read the rest of this thread yet)

On 2019-11-04 16:07:23 +0100, Tomas Vondra wrote:
> On Mon, Nov 04, 2019 at 04:39:44PM +0300, Павел Ерёмин wrote:
> >   And yet, if I try to implement a similar mechanism, if successful, will my
> >   revision be considered?
> >    
> 
> Why wouldn't it be considered? If you submit a patch that demonstrably
> improves the behavior (in this case reduces per-tuple overhead without
> causing significant issues elsewhere), we'd be crazy not to consider it.

And "without causing significant issues elsewhere" unfortunately
includes continuing to allow pg_upgrade to work.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [PATCH] contrib/seg: Fix PG_GETARG_SEG_P definition
Next
From: Andres Freund
Date:
Subject: Re: Excessive disk usage in WindowAgg