From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Dave Johansen <davejohansen@gmail.com>
To: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Best way to handle "read only" paritions
Date: Fri, 29 Apr 2016 22:15:00 -0400
Message-ID: <57241524.2040304@2ndquadrant.com> (raw)
In-Reply-To: <CAAcYxUcZRzfq3RPXEkuRFgqduiRaFA2RgTaHkPBTizZZhmZRwA@mail.gmail.com>
References: <CAAcYxUcZRzfq3RPXEkuRFgqduiRaFA2RgTaHkPBTizZZhmZRwA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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
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: peter.eisentraut@2ndquadrant.com, davejohansen@gmail.com
Subject: Re: Best way to handle "read only" paritions
In-Reply-To: <57241524.2040304@2ndquadrant.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