Re: Partial index creation always scans the entire table
От | Laurenz Albe |
---|---|
Тема | Re: Partial index creation always scans the entire table |
Дата | |
Msg-id | 43b329d274c3535c75d2fbd6912b5ae8e3e51582.camel@cybertec.at обсуждение исходный текст |
Ответ на | Partial index creation always scans the entire table (MingJu Wu <mingjuwu0505@gmail.com>) |
Ответы |
Re: Partial index creation always scans the entire table
Re: Partial index creation always scans the entire table |
Список | pgsql-performance |
On Sat, 2020-02-15 at 19:04 +0800, MingJu Wu wrote: > When creating partial indexes, can postgres utilize another index for figuring which rows > should be included in the partial index, without performing a full table scan? No; it has to be a full sequential scan. > My scenario is that I have a table with 50M rows that are categorized into 10K categories. > I need to create a partial index for each category. I have created a index on the category > column, hoping that postgres can use this information when creating the partial indexes. > However, postgres always performs full table scan. There is your problem. You don't need a partial index per category, you need a single index that *contains* the category. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com
В списке pgsql-performance по дате отправления: