From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | Christophe Pettus <xof(at)thebuild(dot)com>, tony(at)exquisiteimages(dot)com, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_dump of database with numerous objects |
Date: | 2020-06-13 17:57:39 |
Message-ID: | 20200613175739.GB20552@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, May 31, 2020 at 02:02:08PM -0700, Adrian Klaver wrote:
> On 5/31/20 1:38 PM, Christophe Pettus wrote:
> >
> >
> > > On May 31, 2020, at 13:37, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> > >
> > > Just a reminder that the OP's original issue was with using pg_upgrade.
> >
> > True, although IIRC pg_ugprade uses pg_dump under the hood to do the schema migration.
>
> Again true, but pg_upgrade will not work older to newer:
>
> /usr/local/pgsql11/bin/pg_upgrade --check -U postgres -d
> /usr/local/pgsql11/data -D /usr/local/pgsql12_up/data -b
> /usr/local/pgsql11/bin -B /usr/local/pgsql12/bin
>
> Performing Consistency Checks
> -----------------------------
> Checking cluster versions
> This utility can only upgrade to PostgreSQL version 11.
> Failure, exiting
This is saying you can only use pg_upgrade 11.X to upgrade _to_ Postgres
11.X. If you want to upgrade to 12, you have to use pg_upgrade from 12.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-06-13 17:58:59 | Re: Fwd: not able to give usage access to public schema |
Previous Message | Bruce Momjian | 2020-06-13 17:55:11 | Re: pg_dump of database with numerous objects |