Re: Legacy GiST invalid tuples - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Legacy GiST invalid tuples
Date
Msg-id 20180704210858.m3m4lxixqaun34ll@alap3.anarazel.de
Whole thread Raw
In response to Re: Legacy GiST invalid tuples  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Legacy GiST invalid tuples  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: Legacy GiST invalid tuples  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2018-07-04 17:02:01 -0400, Alvaro Herrera wrote:
> On 2018-Jul-04, Andres Freund wrote:
> 
> > > I think the soonest this can work is to add the column in pg12 so that
> > > it can be used to upgrade to pg13.
> > 
> > I don't think we can easily require that everyone pg_upgrading to v13+
> > upgrades to v12 first?
> 
> We've never done that, I don't know if we can get away with it.
> Upgrades with pg_upgrade are not cheap enough for that, methinks.
> Maybe I'm wrong, but people complain even at a *single* pg_upgrade --
> seems everybody wants in-place upgrades nowadays ...

Right. That's why I was wondering about making the "last full scan"
feature backpatchable...

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Legacy GiST invalid tuples
Next
From: Tom Lane
Date:
Subject: Re: Unexpected behavior of DROP VIEW/TABLE IF EXISTS