Best way to handle "read only" paritions - Mailing list pgsql-admin

From Dave Johansen
Subject Best way to handle "read only" paritions
Date
Msg-id CAAcYxUcZRzfq3RPXEkuRFgqduiRaFA2RgTaHkPBTizZZhmZRwA@mail.gmail.com
Whole thread Raw
Responses Re: Best way to handle "read only" paritions
List pgsql-admin
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?
Anything else?
Thanks,
Dave

pgsql-admin by date:

Previous
From: Dave Johansen
Date:
Subject: Re: Deadlock when inserting from multiple processes
Next
From: Peter Eisentraut
Date:
Subject: Re: Best way to handle "read only" paritions