Search Postgresql Archives

Re: R: Slow queries on very big (and partitioned) table

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

 



> We thought to implement one partition for day.

That would be 365 partitions in a year.

In our experience INSERTS suffers the most in a partitioned table because triggers are the only way to route the row to the proper child (inherited) table.

Question: How is your insert pattern? Do you insert always current date. In that case you can write the trigger code to have current date at the top so that the insert trigger finds the matching date as early as possible.

Selects, updates and deletes are reasonably better.

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




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux