Re: Dealing with SeqScans when Time-based Partitions Cut Over
| От | Greg Sabino Mullane |
|---|---|
| Тема | Re: Dealing with SeqScans when Time-based Partitions Cut Over |
| Дата | |
| Msg-id | CAKAnmmL3_WPtWRrCy1t3zJOcDConYA__so4FZj_Bzzza-inJjw@mail.gmail.com обсуждение исходный текст |
| Ответ на | Dealing with SeqScans when Time-based Partitions Cut Over (Matthew Planchard <msplanchard@gmail.com>) |
| Ответы |
Re: Dealing with SeqScans when Time-based Partitions Cut Over
|
| Список | pgsql-general |
If this is still an issue after you check David's theory about premature analyzing, another approach is to pre-populate and pre-analyze future tables. Something like this:
* disable autovac on the future table
* detach the table from the main partition
* insert a few hundred thousand rows into it, then run analyze on it
* can pull rows from a current table, or just use random data on a key column- whatever is enough to generate "good" stats
* delete the rows - the stats will remain
* reattach the table
* enable autovac if you like; I would not
Cheers,
Greg
--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support
В списке pgsql-general по дате отправления: