| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | Arthur Pemberton <pemboa(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Cannot upgrade from 9.3 to 9.4 using pg_upgrade |
| Date: | 2016-01-05 07:07:05 |
| Message-ID: | CAB7nPqQUxu2cNV3Wsci8PwfJHfTHTxBJeeRixiQ=fc=21jMaJQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Jan 5, 2016 at 6:58 AM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
> On 01/04/2016 12:53 PM, Arthur Pemberton wrote:
>>
>> Yes, I have tried it without --jobs, just to simplify.
>>
>
> That would have been too easy. Not sure what is going on.
>
> So are there any other errors, warnings, etc between?:
>
> Checking cluster versions ok
>
> and
>
> SQL command failed
Yeah, that's basically the same temporary relation created through the
same connection. That's likely an effect of --jobs though I cannot see
directly how get_db_and_rel_infos would get called twice for the same
connection.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2016-01-05 07:59:45 | Re: A unique pairs version of UNNEST() ? |
| Previous Message | Thomas Munro | 2016-01-05 06:57:36 | Re: planner does not detect same-as-default collation. |