From: Alan Hodgson <ahodgson@simkin.ca>
To: pgsql-performance@postgresql.org
Subject: Re: Best practice when reindexing in production
Date: Wed, 29 May 2013 10:47:04 -0700
Message-ID: <1514687.3ZLd7LDGHi@skynet.simkin.ca> (raw)
In-Reply-To: <1369848321.28819.31.camel@risotto.smithersbet.com>
References: <5359686B-FAE8-4056-AF13-F9FD6919FE82@autouncle.com>
<51A63717.7070301@krogh.cc>
<1369848321.28819.31.camel@risotto.smithersbet.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On Wednesday, May 29, 2013 06:25:21 PM Daniele Varrazzo wrote:
> My solution has been to become pg_repack maintainer. YMMV. Just don't
> expect vacuum to reduce the indexes size: it doesn't.
It's not supposed to. It is supposed to keep them from indefinitely growing,
though, which it does reasonably well at.
--
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: ahodgson@simkin.ca
Subject: Re: Best practice when reindexing in production
In-Reply-To: <1514687.3ZLd7LDGHi@skynet.simkin.ca>
* 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