table partitioning: effects of many sub-tables (was COPY too slow...)

Поиск
Список
Период
Сортировка
От Rick Schumeyer
Тема table partitioning: effects of many sub-tables (was COPY too slow...)
Дата
Msg-id 000101c5fadb$470c7df0$0200a8c0@dell8200
обсуждение исходный текст
Список pgsql-performance

Based on a suggestion on the postgis list, I partitioned my 80 million (for now) record table into

subtables of about 230k records (the amount of data collected in five minutes).  At the moment

I have 350 subtables.

 

Everything seems to be great…COPY time is ok, building a geometric index on “only” 230k records

is ok, query performance is ok.

 

I’m a little concerned about having so many subtables.  350 tables is not bad, but what happens if

the number of subtables grows into the thousands?  Is there a practical limit to the effectiveness

partitioning?

 

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

Предыдущее
От: Richard Huxton
Дата:
Сообщение: Re: Join the same row
Следующее
От: Stephan Vollmer
Дата:
Сообщение: First query is slow, subsequent queries fast