From: Gerhard Wiesinger <lists@wiesinger.com>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: Andreas Kretschmer <akretschmer@spamfence.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Major performance problem after upgrade from 8.3 to 8.4
Date: Mon, 30 Aug 2010 18:11:36 +0200 (CEST)
Message-ID: <alpine.LFD.2.01.1008301808330.31277@bbs.intern> (raw)
In-Reply-To: <AANLkTik14X_MYoZA5CHNGC8M7Rc0zXrRhoGw6FrfUPXm@mail.gmail.com>
References: <alpine.LFD.2.01.1008300802300.4121@bbs.intern>
<20100830072230.GA28373@tux>
<AANLkTi=Te9ToTG-bqVy+fHQ0wM1YWv0nhBqqYiTk2ePg@mail.gmail.com>
<alpine.LFD.2.01.1008300956320.19598@bbs.intern>
<AANLkTik14X_MYoZA5CHNGC8M7Rc0zXrRhoGw6FrfUPXm@mail.gmail.com>
On Mon, 30 Aug 2010, Pavel Stehule wrote:
> 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
I know the drawbacks of an EAV design but I don't want to discuss that. I
want to discuss the major performance decrease of PostgreSQL 8.3
(performance was ok) to PostgreSQL 8.4 (performance is NOT ok).
Any further ideas how I can track this down?
Can someone explain the difference in query plan from an optimizer point
of view?
Thnx.
Ciao,
Gerhard
--
http://www.wiesinger.com/
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: lists@wiesinger.com, pavel.stehule@gmail.com, akretschmer@spamfence.net
Subject: Re: Major performance problem after upgrade from 8.3 to 8.4
In-Reply-To: <alpine.LFD.2.01.1008301808330.31277@bbs.intern>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox