Re: [HACKERS] Press Release Draft - 2016-02-09 Cumulative Update - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] Press Release Draft - 2016-02-09 Cumulative Update
Date
Msg-id 20170207234003.67rpuqda4gorso44@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] Press Release Draft - 2016-02-09 Cumulative Update  ("Jonathan S. Katz" <jkatz@postgresql.org>)
Responses Re: [HACKERS] Press Release Draft - 2016-02-09 Cumulative Update  ("Jonathan S. Katz" <jkatz@postgresql.org>)
List pgsql-hackers
Jonathan S. Katz wrote:
> 
> > On Feb 7, 2017, at 4:07 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
> > 
> > Jonathan S. Katz wrote:
> > 
> >> Thanks for the clarification.  I have updated the recipe along with Emre’s comments here:
> >> 
> >> [updated text not included in the email]
> > 
> > I still don't think the recipe is a very good one because it leaves you
> > with a window where the affected columns are not indexed at all.
> 
> Okay, so I propose two options:
> 
>     1.  Does anyone have a recipe they recommend that might be better? OR

Do the CREATE INDEX CONCURRENTLY first, then DROP INDEX CONCURRENTLY the
old index, then rename the new index to the old name.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: [HACKERS] Caching index AM working data across aminsert calls
Next
From: Robert Haas
Date:
Subject: Re: [HACKERS] Caching index AM working data across aminsert calls