pg_upgrade supported versions policy

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org
Subject: pg_upgrade supported versions policy
Date: 2018-11-21 23:47:22
Message-ID: 20181121234722.nk3hb7hcmssioeia@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

I feel like we ought to trim the support for a few old versions from
pg_upgrade. In my particular case I don't really think it's reasonable
to test < 9.0 versions for pg_largeobject_metadata migrations. But I
think we should create a policy that's the default, leaving individual
cases aside.

I can see a few possible policies:

1) Support upgrading from the set of releases that were supported when
the pg_upgrade target version was released. While some will argue that
this is fairly short, people above it can still upgrade ~10 years
worth of versions with a single intermediary upgrade.
2) Same, but +2 releases or such.
3) Support until it gets too uncomfortable.
4) Support all versions remotely feasible (i.e. don't drop versions that
still can be compiled)

I personally think 1 is preferrable and 2 is acceptable.

Greetings,

Andres Freund

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2018-11-22 00:12:14 reg* checks in pg_upgrade are out of date
Previous Message David Rowley 2018-11-21 22:24:50 Re: Speeding up INSERTs and UPDATEs to partitioned tables