From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Christophe Pettus <xof(at)thebuild(dot)com> |
Cc: | tony(at)exquisiteimages(dot)com, pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_dump of database with numerous objects |
Date: | 2020-05-31 21:02:08 |
Message-ID: | f735afa0-a02e-74b8-67ca-0b046938066e@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
>
> --
> -- Christophe Pettus
> xof(at)thebuild(dot)com
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Andrus | 2020-05-31 21:03:30 | Re: How to start slave after pg_basebackup. Why min_wal_size and wal_keep_segments are duplicated |
Previous Message | Andrus | 2020-05-31 20:56:05 | Re: How to start slave after pg_basebackup. Why min_wal_size and wal_keep_segments are duplicated |