Re: pg_upgrade problem with invalid indexes - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: pg_upgrade problem with invalid indexes
Date
Msg-id 20121207030811.GC31540@momjian.us
Whole thread Raw
In response to Re: pg_upgrade problem with invalid indexes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_upgrade problem with invalid indexes  (Stephen Frost <sfrost@snowman.net>)
List pgsql-hackers
On Thu, Dec  6, 2012 at 10:06:13PM -0500, Tom Lane wrote:
> Stephen Frost <sfrost@snowman.net> writes:
> > * Andrew Dunstan (andrew@dunslane.net) wrote:
> >> Making the user fix it seems much more sensible to me. Otherwise I
> >> suspect we'll find users who get strangely surprised when they can
> >> no longer find any trace of an expected index in their upgraded
> >> database.
> 
> > Or preserve it as-is.
> 
> To do that, we would have to add an option to CREATE INDEX to create it
> in an invalid state.  Which is stupid...

I think we would have have pg_dump --binary-upgrade issue an UPDATE to
the system catalogs to mark it as invalid.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com
 + It's impossible for everything to be true. +



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Commits 8de72b and 5457a1 (COPY FREEZE)
Next
From: "David Rowley"
Date:
Subject: Re: Functional dependency in GROUP BY through JOINs