From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | Niels Kristian Schjødt <nielskristian(at)autouncle(dot)com> |
Cc: | "pgsql-performance(at)postgresql(dot)org list" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Best practice when reindexing in production |
Date: | 2013-06-01 02:38:19 |
Message-ID: | CAMkU=1wZ72UCDqeVVY_EhMLxh0riOSa1OO8-XUOetoK6A71cdQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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
From | Date | Subject | |
---|---|---|---|
Next Message | Robert DiFalco | 2013-06-02 19:39:02 | SQL performance |
Previous Message | Josh Berkus | 2013-05-31 18:54:15 | Re: Performance bug in prepared statement binding in 9.2? |