| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Bugs in CREATE/DROP INDEX CONCURRENTLY |
| Date: | 2012-11-29 19:43:59 |
| Message-ID: | 20121129194359.GA29711@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2012-11-29 11:53:50 -0500, Tom Lane wrote:
> 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.
Looks good me.
> I think this much of the patch needs to go into all supported branches.
Looks like that to me, yes.
Thanks for all that work!
Andres
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2012-11-29 20:03:48 | Re: Enabling frontend-only xlog "desc" routines |
| Previous Message | Andres Freund | 2012-11-29 19:25:59 | Re: foreign key locks - EvalPlanQual interactions |