| From: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com> |
|---|---|
| To: | Rural Hunter <ruralhunter(at)gmail(dot)com> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Query Plan Performance on Partitioned Table |
| Date: | 2015-08-11 14:42:15 |
| Message-ID: | CAK-MWwSwUA9Fehg_BpuG344RQfdS=nVLkFTP+ed3PRtPZX1WeQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Check constraints:
> "article_729_cid_check" CHECK (cid = 729)
>
Used partition schema looks very simple and straightforward, and should
have no issues with 80 partitions.
Are you sure that you have only 80 partitions but not (lets say) 800?
Are every other partition of the article table use the same general idea of
partition check (cid=something)?
Maxim Boguk
Senior Postgresql DBA
http://www.postgresql-consulting.ru/ <http://www.postgresql-consulting.com/>
Phone RU: +7 910 405 4718
Phone AU: +61 45 218 5678
LinkedIn: http://www.linkedin.com/pub/maksym-boguk/80/b99/b1b
Skype: maxim.boguk
Jabber: maxim(dot)boguk(at)gmail(dot)com
МойКруг: http://mboguk.moikrug.ru/
"People problems are solved with people.
If people cannot solve the problem, try technology.
People will then wish they'd listened at the first stage."
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rural Hunter | 2015-08-11 14:51:04 | Re: Query Plan Performance on Partitioned Table |
| Previous Message | Rural Hunter | 2015-08-11 14:01:42 | Re: Query Plan Performance on Partitioned Table |