From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
---|---|
To: | Willy-Bas Loos <willybas(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:40:17 |
Message-ID: | CANu8FixDOAJZWXupdAJh0aCmtmRKEK9eB85GQUXTGjbbv3YUyg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Jul 15, 2016 at 10:34 AM, Willy-Bas Loos <willybas(at)gmail(dot)com> wrote:
>
>
> On Fri, Jul 15, 2016 at 4:31 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
> wrote:
>
>> Remember you can reconstitute a plain format dump from a custom format
>> dump by doing:
>>
>> pg_restore ... -f plain_sql.txt custom_dump.out
>>
>> Not sure what errors you are talking about?
>>
>>
> Nice one!
> errors in my previous answer directed at melvin
>
> --
> Willy-Bas Loos
>
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.
--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
From | Date | Subject | |
---|---|---|---|
Next Message | Willy-Bas Loos | 2016-07-15 14:55:05 | Re: migrating data from an old postgres version |
Previous Message | Willy-Bas Loos | 2016-07-15 14:34:08 | Re: migrating data from an old postgres version |