Subject: Re: Best way to handle "read only" paritions
To: Dave Johansen <davejohansen@gmail.com>,
 pgsql-admin <pgsql-admin@postgresql.org>
References: 
 <CAAcYxUcZRzfq3RPXEkuRFgqduiRaFA2RgTaHkPBTizZZhmZRwA@mail.gmail.com>
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Organization: 2ndQuadrant
Message-ID: <57241524.2040304@2ndquadrant.com>
Date: Fri, 29 Apr 2016 22:15:00 -0400
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101
 Icedove/38.6.0
MIME-Version: 1.0
In-Reply-To: 
 <CAAcYxUcZRzfq3RPXEkuRFgqduiRaFA2RgTaHkPBTizZZhmZRwA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On 04/29/2016 12:46 PM, Dave Johansen wrote:
> We're using a time-based partitioning scheme for our data and so
> partitions become "read only" once the time covered by it has passed.
> We've been CLUSTERing those partitions but here's some questions I have:
> Should we set the fill factor of the indexes from the default of 90 to 100?
> Should we do anything with xids and freeze age?

If you are already spending the effort to cluster the completed
partitions manually, you might as well also VACUUM FREEZE them manually.
 Otherwise, this will happen eventually via autovacuum, so you shouldn't
need to worry about it unless you have particular problems with vacuum
keeping up or finishing.

Setting the index fill factor is a reasonable thought, but if you're
never going to change the old partitions again, the new fill factor will
never be applied.  But it might still be worthwhile if you expect
occasional changes on old partitions.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin