Re: migrating data from an old postgres version

From: Willy-Bas Loos <willybas(at)gmail(dot)com>
To: Melvin Davidson <melvin6925(at)gmail(dot)com>
Cc: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: migrating data from an old postgres version
Date: 2016-07-15 14:55:05
Message-ID: CAHnozTjmZRp+T1r-UZ0yeKQOkdxUHE2QP=MatQvtdBr7GVi1cQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jul 15, 2016 at 4:40 PM, Melvin Davidson <melvin6925(at)gmail(dot)com>
wrote:

> Look, if you dump in plain SQL, it is standard to both old and new
> versions of PostgreSQL. That is the recommended method to upgrade.
> Yes, errors like "row_security" can/will happen, but you can edit and
> comment them oout or just ignore.
>
> ALL THE SQL is the same. So CREATE, COPY, etc. will all work.
> I have previously sent you the url that shows you pg_dump and pg_dump are
> what is needed.
>
> But if you don't believe me, I will comment no further.
>
> Hi, i've learned to dump the database with the pg_dump version of the
target platform.
That way you get 0 errors.
There can be inconsistencies in the database if you do it the way you
suggest (like sequences missing and the like), BUT that is the best plan
for my current situation.
I will use the "​--quote-all-identifiers" option.

(the manual says:"It is recommended that you use the pg_dump and pg_dumpall
programs from the newer version of PostgreSQL")

Thank you,

--
Willy-Bas Loos

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2016-07-15 15:01:39 Re: Cascade streaming replication + wal_files - Pgsql 9.2
Previous Message Melvin Davidson 2016-07-15 14:40:17 Re: migrating data from an old postgres version