Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: nqtien310(at)gmail(dot)com, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed
Date: 2016-07-27 01:52:37
Message-ID: 4847.1469584357@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Mon, Jul 4, 2016 at 12:09:32PM -0400, Tom Lane wrote:
>> Drop or rename your index named "concurrently".
>>
>> (PG 9.0 and up seem to quote that index name safely, but 8.4 doesn't,
>> and it's long out of support.)

> That is odd because pg_upgrade uses the _new_ 9.4 pg_dump to dump the
> old cluster.

Yeah, but pg_dump depends on the backend to do some of the work,
and 8.4 doesn't have quote-all-identifiers support.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2016-07-27 02:32:13 Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed
Previous Message Tom Lane 2016-07-27 01:37:37 Re: BUG #7808: unnest doesn't handle nulls in array of composite typescorrectly