pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
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 12:48:38 +0200
Message-ID: <44476706.90303@rentalia.com> (raw)
In-Reply-To: <0BA77301DFF4B24C9C5DAA74138BF95001E231@exchange-1.dbnet.co.il>
References: <0BA77301DFF4B24C9C5DAA74138BF95001E231@exchange-1.dbnet.co.il>

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




view thread (4+ messages)  latest in thread

Message-ID: <44476706.90303@rentalia.com>
Permalink:  ../44476706.90303@rentalia.com/
Also on:    postgresql.org/message-id/44476706.90303@rentalia.com

 · 

reply

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: <44476706.90303@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