Re: Estimates on partial index
От | Jim Nasby |
---|---|
Тема | Re: Estimates on partial index |
Дата | |
Msg-id | 4c143963-7fc1-b1b8-e605-35b695969830@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: Estimates on partial index (Jeff Janes <jeff.janes@gmail.com>) |
Ответы |
Re: Estimates on partial index
|
Список | pgsql-performance |
On 8/18/16 3:06 PM, Jeff Janes wrote: > If you can come up with a data generator which creates data that > others can use to reproduce this situation, we can then investigate it > in more detail. BTW, the easy fix to this is most likely to create an index on due_date WHERE is_current. Or perhaps partition the table so non-current rows don't live with current ones. I'm not a fan of mixing history tracking in with the main table, because it leads to problems like this. -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532) mobile: 512-569-9461
В списке pgsql-performance по дате отправления: