From: Niels Kristian Schjødt <nielskristian@autouncle.com>
To: pgsql-performance@postgresql.org list <pgsql-performance@postgresql.org>
Subject: Best practice when reindexing in production
Date: Wed, 29 May 2013 14:24:14 +0200
Message-ID: <5359686B-FAE8-4056-AF13-F9FD6919FE82@autouncle.com> (raw)
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
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?
Regards Niels Kristian
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: nielskristian@autouncle.com
Subject: Re: Best practice when reindexing in production
In-Reply-To: <5359686B-FAE8-4056-AF13-F9FD6919FE82@autouncle.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox