Re: Partitioned table performance
От | Josh Berkus |
---|---|
Тема | Re: Partitioned table performance |
Дата | |
Msg-id | 200412151025.02262.josh@agliodbs.com обсуждение исходный текст |
Ответ на | Re: Partitioned table performance ("Stacy White" <harsh@computer.org>) |
Ответы |
Re: Partitioned table performance
|
Список | pgsql-performance |
Stacy, > Thanks again for the reply. So it sounds like the answer to my original > question is that it's expected that the pseudo-partitioning would introduce > a fairly significant amount of overhead. Correct? Correct. For that matter, Oracle table partitioning introduces significant overhead, from what I've seen. I don't think there's a way not to. Generally, I counsel people that they only want to consider pseudo-partitioning if they have one axis on the table which is used in 90% or more of the queries against that table. What would improve the situation significantly, and the utility of pseudo-partitioning, is the ability to have a single index span multiple partitions. This would allow you to have a segmented index for the partitioned axis, yet still use an unsegmented index for the other columns. However, there's a *lot* of work to do to make that happen. -- --Josh Josh Berkus Aglio Database Solutions San Francisco
В списке pgsql-performance по дате отправления: