Re: undead index

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jens Wilke <jens(dot)wilke(at)affinitas(dot)de>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: undead index
Date: 2011-05-06 15:50:22
Message-ID: 12234.1304697022@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Jens Wilke <jens(dot)wilke(at)affinitas(dot)de> writes:
> Thanks Tom, yes, the index is named
> Indexes:
> "concurrently" btree (ulq_guid)
> In the 8.4 cluster and 9.0.4's pg_dumpall dumps it as

> CREATE INDEX concurrently ON foo USING btree (ulq_guid);

> That's it.

Oh, fun. We knew that not reserving that keyword was going to cause
some problems.

> But shouldn't pg_upgrade be able to handle this?

It's not pg_upgrade's fault; it's pg_dump that's failing to reproduce
the state of the source database.

I'm inclined to think that maybe we should hack pg_dump to forcibly
quote "concurrently" in this context, even though it doesn't do so
anywhere else since the word isn't reserved.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Iain Barnett 2011-05-06 15:51:21 Re: Locale and UTF8 for template1 in 8.4.4
Previous Message Jens Wilke 2011-05-06 15:37:42 Re: undead index