From: Steve Crawford <scrawford@pinpointresearch.com>
To: John Scalia <jayknowsunix@gmail.com>
To: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: vacuum and table locking
Date: Fri, 03 Apr 2015 09:40:16 -0700
Message-ID: <551EC270.5000604@pinpointresearch.com> (raw)
In-Reply-To: <551EC12E.2030400@pinpointresearch.com>
References: <551EB8D4.7050406@gmail.com>
<551EC12E.2030400@pinpointresearch.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
On 04/03/2015 09:34 AM, Steve Crawford wrote:
>
> Check out the pg_reorg extension. This extension does create a new
> table on the fly while tracking updates. It then applies any updates
> that have occurred while creating the new copy and finally swaps the
> new version in place of the old. It creates I/O but doesn't require
> the long-duration locks of the other methods.
Actually I should have also said check out pg_repack, the fork of
pg_reorg. In either case also do some reading on potential pitfalls:
http://adpgtech.blogspot.com/2014/10/pgrepack-pitfalls.html
Cheers,
Steve
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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-admin@postgresql.org
Cc: scrawford@pinpointresearch.com, jayknowsunix@gmail.com
Subject: Re: vacuum and table locking
In-Reply-To: <551EC270.5000604@pinpointresearch.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