Re: pg_upgrade supported versions policy - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_upgrade supported versions policy
Date
Msg-id 2e529d92-d204-8d21-5b86-0ff6cdfc9d80@2ndquadrant.com
Whole thread Raw
In response to pg_upgrade supported versions policy  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On 22/11/2018 00:47, Andres Freund wrote:
> 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 would prefer #3.  That's basically how we handle pg_dump, psql, etc.
normally.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Pavel Stehule
Date:
Subject: Re: ToDo: show size of partitioned table
Next
From: Peter Eisentraut
Date:
Subject: Re: New function pg_stat_statements_reset_query() to reset statisticsof a specific query