From: gmb <gmbouwer@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Performance issue: index not used on GROUP BY...
Date: Wed, 3 Sep 2014 12:50:26 -0700 (PDT)
Message-ID: <1409773826818-5817622.post@n5.nabble.com> (raw)
In-Reply-To: <53FF9585.2020503@agliodbs.com>
References: <1409215840535-5816702.post@n5.nabble.com>
<53FF9585.2020503@agliodbs.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
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-tp5816702p58176...
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
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: gmbouwer@gmail.com
Subject: Re: Performance issue: index not used on GROUP BY...
In-Reply-To: <1409773826818-5817622.post@n5.nabble.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