Justin Pryzby writes:
> On Tue, May 29, 2018 at 02:00:20PM -0400, Tom Lane wrote:
>> Yeah, that :-(. pg_dump's approach to cross-version catalog differences
>> can only cope with differences between major versions. So if it sees
>> a server that calls itself 11-something it's going to think
On Tue, May 29, 2018 at 02:00:20PM -0400, Tom Lane wrote:
> Justin Pryzby writes:
> > I've used pg_upgrade like this before, but maybe from a different (recent)
> > 11dev HEAD; I found: "pg_upgrade supports upgrades from 8.4.X and later to
> > the
> > current major release of PostgreSQL,
Justin Pryzby writes:
> I've used pg_upgrade like this before, but maybe from a different (recent)
> 11dev HEAD; I found: "pg_upgrade supports upgrades from 8.4.X and later to the
> current major release of PostgreSQL, including snapshot and beta releases."
> (But maybe upgrades FROM beta
I've used pg_upgrade like this before, but maybe from a different (recent)
11dev HEAD; I found: "pg_upgrade supports upgrades from 8.4.X and later to the
current major release of PostgreSQL, including snapshot and beta releases."
(But maybe upgrades FROM beta releases aren't supported in the
