Re: Best practice when reindexing in production - Mailing list pgsql-performance

From Jeff Janes
Subject Re: Best practice when reindexing in production
Date
Msg-id CAMkU=1wZ72UCDqeVVY_EhMLxh0riOSa1OO8-XUOetoK6A71cdQ@mail.gmail.com
Whole thread Raw
In response to Best practice when reindexing in production  (Niels Kristian Schjødt <nielskristian@autouncle.com>)
List pgsql-performance
On Wednesday, May 29, 2013, Niels Kristian Schjødt wrote:
Hi,

I have a database with quite some data (millions of rows), that is heavily updated all the time. Once a day I would like to reindex my database (and maybe re cluster it - don't know if that's worth it yet?). I need the database to be usable while doing this (both read and write). I see that there is no way to REINDEX CONCURRENTLY - So what approach would you suggest that I take on this?

I think the "best practice" is...not to do it in the first place.

There are some cases where it probably makes sense to reindex on a regular schedule.  But unless you can specifically identify why you have one of those cases, then you probably don't have one.  

Cheers,

Jeff

pgsql-performance by date:

Previous
From: Josh Berkus
Date:
Subject: Re: Performance bug in prepared statement binding in 9.2?
Next
From: Robert DiFalco
Date:
Subject: SQL performance