2011/9/29 Ondrej Ivanič <ondrej.ivanic@xxxxxxxxx>: > Hi, > > On 30 September 2011 01:08, Kevin Grittner <Kevin.Grittner@xxxxxxxxxxxx> wrote: >>> Is there a suggested number of child tables for table >>> partitioning, >> >> Generally, don't go over about 100 partitions per table. > > Having 365 partitions per table is fine... yeah -- the system was certainly designed to support 'dozens to hundreds', but 'hundreds of thousands' is simply not realistic. any measurable benefit gained from partitioning is going to be var exceeded by the database having to track so many tables. btw, partitioning for purposes of performance is a dubious strategy unless you can leverage non-uniform access patterns of the data or do other tricks that allow simplification of structures (like removing 'company_id' from all tables and indexes because it's implied by the partition itself). merlin -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
