From: | Ken Tanzer <ken(dot)tanzer(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PG-General Mailing List <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: 9.6 parameters messing up my 9.2 pg_dump/pg_restore |
Date: | 2017-06-29 07:05:33 |
Message-ID: | CAD3a31VRtpdpagowOBmcGrDoOkTyRRqiSpAQwJ9aat6pJAi+kQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thanks for the responses. For me, using the 9.2 binary was the winner.
Shoulda thought of that!
On Wed, Jun 28, 2017 at 1:30 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Generally speaking, it helps a lot if you don't insist on restoring the
> output in a single transaction. In this case, that would allow the
> restore to ignore the new parameters and move on.
>
> regards, tom lane
>
Well sure, I can see it increases your chances of getting _something_
restored. But there's also a lot to be said for ensuring that _all_ your
data restored, and did so correctly, no?
Cheers,
Ken
--
AGENCY Software
A Free Software data system
By and for non-profits
*http://agency-software.org/ <http://agency-software.org/>*
*https://agency-software.org/demo/client
<https://agency-software.org/demo/client>*
ken(dot)tanzer(at)agency-software(dot)org
(253) 245-3801
Subscribe to the mailing list
<agency-general-request(at)lists(dot)sourceforge(dot)net?body=subscribe> to
learn more about AGENCY or
follow the discussion.
From | Date | Subject | |
---|---|---|---|
Next Message | Timokhin Maxim | 2017-06-29 09:28:59 | duplicate key value violates unique constraint and duplicated records |
Previous Message | Alain Toussaint | 2017-06-29 05:45:53 | Re: Insertion of large xml files into PostgreSQL 10beta1 |