Re: Ignore invalid indexes in pg_dump - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Ignore invalid indexes in pg_dump
Date
Msg-id CA+U5nMLe+qMQDx-=Ef4WS68QW7RGK4Sokk1jFNzLV6rPaU0XJg@mail.gmail.com
Whole thread Raw
In response to Ignore invalid indexes in pg_dump  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Ignore invalid indexes in pg_dump  (Josh Kupershmidt <schmiddy@gmail.com>)
List pgsql-hackers
On 20 March 2013 02:51, Michael Paquier <michael.paquier@gmail.com> wrote:

> If failures happen with CREATE INDEX CONCURRENTLY, the system will be let
> with invalid indexes. I don't think that the user would like to see invalid
> indexes of
> an existing system being recreated as valid after a restore.
> So why not removing from a dump invalid indexes with something like the
> patch
> attached?
> This should perhaps be applied in pg_dump for versions down to 8.2 where
> CREATE
> INDEX CONCURRENTLY has been implemented?

Invalid also means currently-in-progress, so it would be better to keep them in.

> I noticed some recent discussions about that:
> http://www.postgresql.org/message-id/20121207141236.GB4699@alvh.no-ip.org
> In this case the problem has been fixed in pg_upgrade directly.

That is valid because the index build is clearly not in progress.

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



pgsql-hackers by date:

Previous
From: Daniel Farina
Date:
Subject: Re: postgres_fdw vs data formatting GUCs (was Re: [v9.3] writable foreign tables)
Next
From: Ants Aasma
Date:
Subject: Re: Enabling Checksums