| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: pg_upgrade problem with invalid indexes |
| Date: | 2012-12-07 18:59:41 |
| Message-ID: | 27926.1354906781@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Fri, Dec 7, 2012 at 07:49:14PM +0100, Andres Freund wrote:
>> !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.
> Is that something pg_upgrade need to worry about too? Is
> pg_index.indisvalid the only thing pg_upgrade need to check?
indisvalid should be sufficient. If you try to test more than that
you're going to make the code more version-specific, without actually
buying much.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-12-07 19:07:18 | Re: pg_upgrade problem with invalid indexes |
| Previous Message | Bruce Momjian | 2012-12-07 18:57:35 | Re: pg_upgrade problem with invalid indexes |