Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed
Date
Msg-id 20160727023213.GF27321@momjian.us
Whole thread Raw
In response to Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
On Tue, Jul 26, 2016 at 09:52:37PM -0400, Tom Lane wrote:
> Bruce Momjian <bruce@momjian.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.

Ah, OK, makes sense.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+                     Ancient Roman grave inscription +

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed
Next
From: Andrew Gierth
Date:
Subject: Re: BUG #7808: unnest doesn't handle nulls in array of composite typescorrectly