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

From Andres Freund
Subject Re: pg_upgrade problem with invalid indexes
Date
Msg-id 20121207184914.GF8476@awork2.anarazel.de
Whole thread Raw
In response to Re: pg_upgrade problem with invalid indexes  (Josh Berkus <josh@agliodbs.com>)
Responses Re: pg_upgrade problem with invalid indexes  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pg_upgrade problem with invalid indexes  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 2012-12-07 10:44:53 -0800, Josh Berkus wrote:
>
> > I wonder though if we shouldn't ignore !indislive indexes in pg_dump
> > (and the respective bw-compat hack).

Obviously I wanted to ask whether we *should* ignore them in the future.

> Quite likely we shouldn't.  However, that is why it wasn't considered a
> problem.

!indislive indexes are created during DROP INDEX CONCURRENTLY. Thats a
different case than CREATE INDEX CONCURRENTLY. Accessing their
definition is actually problematic because i can vanish while youre
examing it which could cause errors both in the backend and in pg_dump.

Greetings,

Andres Freund

--Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: pg_upgrade problem with invalid indexes
Next
From: Tom Lane
Date:
Subject: Re: pg_upgrade problem with invalid indexes