Re: Querying w/ join slow for large/many child tables
| От | Ron |
|---|---|
| Тема | Re: Querying w/ join slow for large/many child tables |
| Дата | |
| Msg-id | 91a008bf-180b-f60b-b8e1-39c32537baee@gmail.com обсуждение исходный текст |
| Ответ на | Querying w/ join slow for large/many child tables (Wells Oliver <wells.oliver@gmail.com>) |
| Список | pgsql-general |
On 1/29/19 8:49 PM, Wells Oliver wrote:
A partititioned table?
If it's a partitioned table, then yes, putting the appropriate indexes on each child table as well as the empty parent table is what we do.
I have a primary parent table with a child table per week of the year for each week back through 2015. There are a lot of child tables. Each week's child table has maybe 80-110m rows.
A partititioned table?
When I join to the parent table on a column, it's very slow, but when I manually specify the specific week's child table, it's quite fast, e.g.Slow:select * from foojoin schema.mytable on foo.col = mytable.colvs. fast:select * from foojoin schema.mytable_2015_wk33 as mytable on foo.col = mytable.colWhat's the resolution to make querying the table faster in terms of it finding the appropriate child table? Is it putting an index on `col` on each child table? Some other thing?
If it's a partitioned table, then yes, putting the appropriate indexes on each child table as well as the empty parent table is what we do.
--
Angular momentum makes the world go 'round.
Angular momentum makes the world go 'round.
В списке pgsql-general по дате отправления: