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

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(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 02:32:13
Message-ID: 20160727023213.GF27321@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jul 26, 2016 at 09:52:37PM -0400, Tom Lane wrote:
> 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.

Ah, OK, makes sense.

--
Bruce Momjian <bruce(at)momjian(dot)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 +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Andrew Gierth 2016-07-27 03:59:50 Re: BUG #7808: unnest doesn't handle nulls in array of composite typescorrectly
Previous Message Tom Lane 2016-07-27 01:52:37 Re: BUG #14226: pg_upgrade for 8.4 to 9.4 failed