| From: | Tobias Brox <tobixen(at)gmail(dot)com> |
|---|---|
| To: | Віталій Тимчишин <tivv00(at)gmail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org, Mladen Gogala <mladen(dot)gogala(at)vmsinfo(dot)com> |
| Subject: | Re: Why we don't want hints Was: Slow count(*) again... |
| Date: | 2011-02-11 09:29:06 |
| Message-ID: | AANLkTim+D5W3OyFWmXi0BA9xvP5yb5+Aja+Yfq0yOUFZ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
2011/2/11 Віталій Тимчишин <tivv00(at)gmail(dot)com>:
> If the list is hard-coded, you can create partial index on
> account_transaction(account_id, created desc) where trans_type_id in ( ...
> long, hard-coded list ...)
My idea as well, though it looks ugly and it would be a maintenance
head-ache (upgrading the index as new transaction types are added
would mean "costly" write locks on the table, and we can't rely on
manual processes to get it right ... we might need to set up scripts
to either upgrade the index or alert us if the index needs upgrading).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2011-02-11 09:38:32 | Re: ALTER EXTENSION UPGRADE, v3 |
| Previous Message | Dimitri Fontaine | 2011-02-11 09:24:15 | Re: ALTER EXTENSION UPGRADE, v3 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vitalii Tymchyshyn | 2011-02-11 09:44:05 | Re: Why we don't want hints Was: Slow count(*) again... |
| Previous Message | Віталій Тимчишин | 2011-02-11 08:19:01 | Re: Why we don't want hints Was: Slow count(*) again... |