Re: Perfrmance Problems (7.4.6)

From: Ruben Rubio Rey <ruben(at)rentalia(dot)com>
To: Doron Baranes <doron(dot)baranes(at)dbnet(dot)co(dot)il>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Perfrmance Problems (7.4.6)
Date: 2006-04-20 10:48:38
Message-ID: 44476706.90303@rentalia.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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
>
>

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Doron Baranes 2006-04-20 12:57:50 Re: Perfrmance Problems (7.4.6)
Previous Message Doron Baranes 2006-04-20 08:23:57 Perfrmance Problems (7.4.6)