| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bugs in CREATE/DROP INDEX CONCURRENTLY |
| Date: | 2012-11-29 16:53:50 |
| Message-ID: | 25441.1354208030@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
And here is a version for 9.1. This omits the code changes directly
relevant to DROP INDEX CONCURRENTLY, but includes the changes to avoid
transactional updates of the pg_index row during CREATE CONCURRENTLY,
as well as the changes to prevent use of not-valid or not-ready indexes
in places where it matters. I also chose to keep on using the
IndexIsValid and IndexIsReady macros, so as to avoid unnecessary
divergences of the branches.
I think this much of the patch needs to go into all supported branches.
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| index-flags-fix-91.patch | text/x-patch | 30.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2012-11-29 17:59:19 | Re: Further pg_upgrade analysis for many tables |
| Previous Message | Tom Lane | 2012-11-29 16:31:30 | Overlength socket paths (was Re: [COMMITTERS] pgsql: Refactor flex and bison make rules) |