From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Ignore invalid indexes in pg_dump. |
Date: | 2013-03-28 21:27:28 |
Message-ID: | 24486.1364506048@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Should I just patch pg_upgrade to remove the "indisvalid", skip
> "indisvalid" indexes, and backpatch it? Users should be using the
> version of pg_upgrade to match new pg_dump. Is there any case where
> they don't match? Do I still need to check for "indisready"?
Yeah, if you can just ignore !indisvalid indexes that should work fine.
I see no need to look at indisready if you're doing that.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | anarazel@anarazel.de | 2013-03-28 21:31:51 | Re: Ignore invalid indexes in pg_dump. |
Previous Message | Bruce Momjian | 2013-03-28 21:01:04 | Re: Ignore invalid indexes in pg_dump. |
From | Date | Subject | |
---|---|---|---|
Next Message | anarazel@anarazel.de | 2013-03-28 21:31:51 | Re: Ignore invalid indexes in pg_dump. |
Previous Message | Bruce Momjian | 2013-03-28 21:17:43 | Re: pg_upgrade segfaults when given an invalid PGSERVICE value |