From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Legacy GiST invalid tuples |
Date: | 2018-07-04 21:02:01 |
Message-ID: | 20180704210201.fd3kwph3de4vnuia@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 ...
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-07-04 21:08:58 | Re: Legacy GiST invalid tuples |
Previous Message | Tom Lane | 2018-07-04 21:00:56 | Re: Should contrib modules install .h files? |