Search Postgresql Archives

Re: Optimal database table optimization method

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

 




I have no idea how good pg is with select queries over 365 partitions (1 year).

no need to use a partition per day, I'm pretty sure he won't mind having a few extra days or weeks. I'd go by month, and drop a whole month at a time, that way there's only 12-13 partitions.

and doing this, there's no need for a date index if he's never searching by date, just an index on the primary key. yes, the selects will have to search all 12-13 tables, but SELECT ... WHERE pk=?; are very fast searches, so doing this on 12 tables is pretty painless.





--
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