From: Ruben Rubio Rey <ruben@rentalia.com>
To: Doron Baranes <doron.baranes@dbnet.co.il>
To: pgsql-performance@postgresql.org
Subject: Re: Perfrmance Problems (7.4.6)
Date: Thu, 20 Apr 2006 16:54:21 +0200
Message-ID: <4447A09D.9070600@rentalia.com> (raw)
In-Reply-To: <0BA77301DFF4B24C9C5DAA74138BF95001E23C@exchange-1.dbnet.co.il>
References: <0BA77301DFF4B24C9C5DAA74138BF95001E23C@exchange-1.dbnet.co.il>
Did you tried to index the expression?
Did it work?
Doron Baranes wrote:
>Ok. But that means I need a trigger on the original column to update the
>new column on each insert/update and that overhead.
>
>-----Original Message-----
>From: Ruben Rubio Rey [mailto:ruben@rentalia.com]
>Sent: Thursday, April 20, 2006 12:49 PM
>To: Doron Baranes; pgsql-performance@postgresql.org
>Subject: Re: [PERFORM] Perfrmance Problems (7.4.6)
>
>I think that the problem is the GROUP BY (datetime) that is
>date_trunc('hour'::text, i.entry_time)
>You should create an indexe with this expression (if its possible).
>
>http://www.postgresql.org/docs/7.4/interactive/indexes-expressional.html
>
>If is not possible, I would create a column with value
>date_trunc('hour'::text, i.entry_time) of each row and then index it.
>
>Hope this helps :)
>
>Doron Baranes wrote:
>
>
>
>>Hi,
>>
>>I am running on postgres 7.4.6.
>>I did a vacuum analyze on the database but there was no change.
>>I Attached here a file with details about the tables, the queries and
>>the Explain analyze plans.
>>Hope this can be helpful to analyze my problem
>>
>>10x
>>Doron
>>
>>
>>-----------------------------------------------------------------------
>>
>>
>-
>
>
>>---------------------------(end of
>>
>>
>broadcast)---------------------------
>
>
>>TIP 9: In versions below 8.0, the planner will ignore your desire to
>> choose an index scan if your joining column's datatypes do not
>> match
>>
>>
>>
>>
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: Don't 'kill -9' the postmaster
>
>
>
>
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: ruben@rentalia.com, doron.baranes@dbnet.co.il
Subject: Re: Perfrmance Problems (7.4.6)
In-Reply-To: <4447A09D.9070600@rentalia.com>
* 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