| From: | Job <Job(at)colliniconsulting(dot)it> |
|---|---|
| To: | 'Stephen Frost' <sfrost(at)snowman(dot)net>, Job <Job(at)colliniconsulting(dot)it> |
| Cc: | Jaime Soler <jaime(dot)soler(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | R: R: Slow queries on very big (and partitioned) table |
| Date: | 2017-02-21 21:54:29 |
| Message-ID: | 88EF58F000EC4B4684700C2AA3A73D7A08054EACC765@W2008DC01.ColliniConsulting.lan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi Stephen,
Thank you for your excellent opinion!
>If this is really what you're mostly doing, having constraint exclusion and an index on 'profile' would probably be enough, if you insist on continuing to have the table partitioned by day (which I continue to argue is a bad idea-
>based on the number of total rows you mentioned and the number of partitions, you have partitions with less than 20M rows each and that's really small, month-based partitions with a BRIN would probably work better). If you get to
>the point of having years worth of daily partitions, you'd going to see increases in planning time.
Based on our simulation, we can raise until 5Gb of datas for a single day, with some millions of rows.
We thought to implement one partition for day.
Do you think it should be fine?
Thank you!
/F
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rakesh Kumar | 2017-02-21 21:58:36 | Re: R: Slow queries on very big (and partitioned) table |
| Previous Message | Job | 2017-02-21 21:49:36 | R: Search on very big (partitioned) table |