Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Ye4ds-0006NO-BM for pgsql-admin@arkaria.postgresql.org; Fri, 03 Apr 2015 16:40:24 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Ye4dr-0004of-Ms for pgsql-admin@arkaria.postgresql.org; Fri, 03 Apr 2015 16:40:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1Ye4dr-0004oZ-1d for pgsql-admin@postgresql.org; Fri, 03 Apr 2015 16:40:23 +0000 Received: from cerberus.pinpointresearch.com ([66.7.238.130] helo=polaris.pinpointresearch.com) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Ye4dm-00071x-Jm for pgsql-admin@postgresql.org; Fri, 03 Apr 2015 16:40:21 +0000 Received: from [192.168.1.179] (betelgeuse.pinpointresearch.com [192.168.1.179]) by polaris.pinpointresearch.com (Postfix) with ESMTP id 741A8E00EC83; Fri, 3 Apr 2015 09:40:16 -0700 (PDT) Message-ID: <551EC270.5000604@pinpointresearch.com> Date: Fri, 03 Apr 2015 09:40:16 -0700 From: Steve Crawford User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: John Scalia , "pgsql-admin@postgresql.org" Subject: Re: vacuum and table locking References: <551EB8D4.7050406@gmail.com> <551EC12E.2030400@pinpointresearch.com> In-Reply-To: <551EC12E.2030400@pinpointresearch.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org 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