From: | Arthur Pemberton <pemboa(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Cannot upgrade from 9.3 to 9.4 using pg_upgrade |
Date: | 2016-01-05 05:39:47 |
Message-ID: | CABD0o2Tu1bRC+iBPvfjQgMmBzMGK9t38Kajn1LWdMRR1oHtSqg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Maybe there was a verbose settings that would have given me that, but what
I pasted was literally all the output I got. In the end, I did a pg_dumpapp
On Mon, Jan 4, 2016 at 8:40 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 01/04/2016 02:37 PM, Arthur Pemberton wrote:
>
>> Nothing useful. I'm just going to give up and use pg_dump to a new
>> machine. Hopefully that allows me to bypass this issue.
>>
>
> Did that help?
>
> To help someone else troubleshoot this, did the error you get occur after
> the pg_upgrade line:
>
> Restoring global objects in the new cluster
>
> or
>
> Restoring database schemas in the new cluster
>
> or even better yet could you post the section of the log above the error?
>
>
>> On Mon, Jan 4, 2016 at 4:58 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
>> <mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
>>
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Kretschmer | 2016-01-05 06:28:56 | Re: Streaming replication stacked. |
Previous Message | Jeff Janes | 2016-01-05 05:39:42 | planner does not detect same-as-default collation. |