| From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Support for REINDEX CONCURRENTLY |
| Date: | 2013-06-17 20:00:05 |
| Message-ID: | 20130617200005.GA30159@awork2.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2013-06-17 12:52:36 -0700, Josh Berkus wrote:
>
> > Well, it can do lots stuff that DROP/CREATE CONCURRENTLY can't:
> > * reindex primary keys
> > * reindex keys referenced by foreign keys
> > * reindex exclusion constraints
> > * reindex toast tables
> > * do all that for a whole database
> > so I don't think that comparison is fair. Having it would have made
> > several previous point releases far less painful (e.g. 9.1.6/9.2.1).
>
> FWIW, I have a client who needs this implementation enough that we're
> backporting it to 9.1 for them.
Wait. What? Unless you break catalog compatibility that's not safely
possible using this implementation.
Greetings,
Andres Freund
PS: Josh, minor thing, but could you please not trim the CC list, at
least when I am on it?
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-06-17 20:12:48 | Re: [RFC] Minmax indexes |
| Previous Message | Kevin Grittner | 2013-06-17 19:53:45 | Re: Batch API for After Triggers |