> On Feb 7, 2017, at 6:40 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > > Jonathan S. Katz wrote: >> >>> On Feb 7, 2017, at 4:07 PM, Alvaro Herrera <alvhe...@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.
Cool. Updated: https://git.postgresql.org/gitweb/?p=press.git;a=blob;f=update_releases/current/20170209updaterelease.txt;h=56551b56eb1f70e734c5762abf5ddf6bd6965fdb;hb=c1b7f9c0cfd0ff106409d14a36c3122a8ee460d0 <https://git.postgresql.org/gitweb/?p=press.git;a=blob;f=update_releases/current/20170209updaterelease.txt;h=56551b56eb1f70e734c5762abf5ddf6bd6965fdb;hb=c1b7f9c0cfd0ff106409d14a36c3122a8ee460d0> I added a note to alert people to disk space usage utilizing this method. Thanks for the help! Jonathan.
