Re: Fast default stuff versus pg_upgrade
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "David G. Johnston" <david.g.johnston@gmail.com>
Cc: Andres Freund <andres@anarazel.de>, Andrew Dunstan <andrew@dunslane.net>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2018-06-19T17:59:16Z
Lists: pgsql-hackers
"David G. Johnston" <david.g.johnston@gmail.com> writes: > On Tue, Jun 19, 2018 at 9:37 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> The problem here is that that function does not exist in 11beta1. >> Since adding the "incoming" function is certainly going to require >> initdb, we have to be able to dump from the server as it now stands, >> or we'll be cutting existing beta testers adrift. > I was under the impression that we don't promise to support a "v10 -> beta > -> rc -> final" upgrade path; instead, once final is released people would > be expected to upgrade "v10 -> v11". Well, we don't *promise* beta testers that their beta databases will be usable into production, but ever since pg_upgrade became available we've tried to make it possible to pg_upgrade to the next beta or production release. I do not offhand recall any previous case where we failed to do so. regards, tom lane
Commits
-
Allow for pg_upgrade of attributes with missing values
- 2448adf29c54 11.0 landed