Re: Query Plan Performance on Partitioned Table

Поиск
Список
Период
Сортировка
От Pietro Pugni
Тема Re: Query Plan Performance on Partitioned Table
Дата
Msg-id CABnidNRnSmWw75ZhK+X5nysMq3wq9RsgRYRHPc_w+oSm-tCzQg@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Query Plan Performance on Partitioned Table  (Rural Hunter <ruralhunter@gmail.com>)
Ответы Re: Query Plan Performance on Partitioned Table
Список pgsql-performance

Hi Rural Hunter,
Try to create an index on cid attribute.
How many rows has article_729?

Pietro Pugni

Il 11/ago/2015 16:51, "Rural Hunter" <ruralhunter@gmail.com> ha scritto:
yes i'm very sure. from what i observed, it has something to do with the concurrent query planing. if i disconnect other connections, the plan is very quick.

2015-08-11 22:42 GMT+08:00 Maxim Boguk <maxim.boguk@gmail.com>:


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/

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.boguk@gmail.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."



В списке pgsql-performance по дате отправления:

Предыдущее
От: Rural Hunter
Дата:
Сообщение: Re: Query Plan Performance on Partitioned Table
Следующее
От: Rural Hunter
Дата:
Сообщение: Re: Query Plan Performance on Partitioned Table