From: | "anarazel(at)anarazel(dot)de" <andres(at)anarazel(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,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:31:51 |
Message-ID: | cbaae57b-116e-49eb-aabc-ea4a2d200cff@email.android.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> schrieb:
>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.
You need to look at inisready in 9.2 since thats used for about to be dropped indexes. No?
Andres
---
Please excuse brevity and formatting - I am writing this on my mobile phone.
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-03-28 21:35:08 | Re: Ignore invalid indexes in pg_dump. |
Previous Message | Tom Lane | 2013-03-28 21:27:28 | Re: Ignore invalid indexes in pg_dump. |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-03-28 21:35:08 | Re: Ignore invalid indexes in pg_dump. |
Previous Message | Tom Lane | 2013-03-28 21:27:28 | Re: Ignore invalid indexes in pg_dump. |