Re: Major performance problem after upgrade from 8.3 to 8.4
От | Pavel Stehule |
---|---|
Тема | Re: Major performance problem after upgrade from 8.3 to 8.4 |
Дата | |
Msg-id | AANLkTik14X_MYoZA5CHNGC8M7Rc0zXrRhoGw6FrfUPXm@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Major performance problem after upgrade from 8.3 to 8.4 (Gerhard Wiesinger <lists@wiesinger.com>) |
Ответы |
Re: Major performance problem after upgrade from 8.3 to
8.4
|
Список | pgsql-performance |
2010/8/30 Gerhard Wiesinger <lists@wiesinger.com>: > On Mon, 30 Aug 2010, Pavel Stehule wrote: > >> Hello >> >> 2010/8/30 Andreas Kretschmer <akretschmer@spamfence.net>: >>> >>> Gerhard Wiesinger <lists@wiesinger.com> wrote: >>> >>>> I know that the data model is key/value pairs but it worked well in 8.3. >>>> I need this flexibility. >>>> >>>> Any ideas? >>> >>> If i understand the query correctly it's a pivot-table, right? >>> >> >> no - it's just EAV table on very large data :( > > Yes, it is an EAV table, but with query space comparable low (Max. 1 day out > of years, typically 5mins out of years). > it is irelevant - there are repeated seq scans - so you need a partitioning or classic table - maybe materialized views can help Pavel > Thnx. > > Ciao, > Gerhard > > -- > http://www.wiesinger.com/ > >
В списке pgsql-performance по дате отправления: