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

In response to

• Re: pg_upgrade problem with invalid indexes at 2012-12-07 18:44:53 from Josh Berkus

Responses

• Re: pg_upgrade problem with invalid indexes at 2012-12-07 18:54:44 from Tom Lane
• Re: pg_upgrade problem with invalid indexes at 2012-12-07 18:57:35 from Bruce Momjian

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2012-12-07 18:54:44
	Subject: Re: pg_upgrade problem with invalid indexes
Previous:	From: Josh Berkus	Date: 2012-12-07 18:44:53
	Subject: Re: pg_upgrade problem with invalid indexes