Re: Best way to handle "read only" paritions

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Apr 29, 2016 at 7:15 PM, Peter Eisentraut <peter.eisentraut@xxxxxxxxxxxxxxx> wrote:
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.

Would setting the fill factor on the indexes before the CLUSTER do anything?

[Index of Archives]     [KVM ARM]     [KVM ia64]     [KVM ppc]     [Virtualization Tools]     [Spice Development]     [Libvirt]     [Libvirt Users]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite Questions]     [Linux Kernel]     [Linux SCSI]     [XFree86]

  Powered by Linux