Date: Wed, 3 Sep 2014 12:50:26 -0700 (PDT)
From: gmb <gmbouwer@gmail.com>
To: pgsql-performance@postgresql.org
Message-ID: <1409773826818-5817622.post@n5.nabble.com>
In-Reply-To: <53FF9585.2020503@agliodbs.com>
References: <1409215840535-5816702.post@n5.nabble.com>
 <53FF9585.2020503@agliodbs.com>
Subject: Re: Performance issue: index not used on GROUP BY...
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Thanks for the feedback, everybody.
I spent a couple of days trying to optimise this;  
As mentioned , the increased memory is not an option for me, as this query
is part of a report that can be run by any user on an ad hoc basis.
Allocating the required memory to any session on demand is not feasible in
this environment.

In the end , it seems to me that a more sustainable solution will be to
introduce an additional table to carry the summarized values and lookup on
that table in this type of scenario.

Regards


--
View this message in context: http://postgresql.1045698.n5.nabble.com/Performance-issue-index-not-used-on-GROUP-BY-tp5816702p5817622.html
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance