From: hyelluas <helen_yelluas@mcafee.com>
To: pgsql-performance@postgresql.org
Subject: Re: How to see memory usage using explain analyze ?
Date: Wed, 17 Aug 2011 11:51:59 -0700 (PDT)
Message-ID: <1313607119621-4709415.post@n5.nabble.com> (raw)
In-Reply-To: <1313184591789-4694681.post@n5.nabble.com>
References: <1313184591789-4694681.post@n5.nabble.com>
Igor,
Thank you for the hint, I read about the planner, added "vacuum analyze " to
my procedures.
There is no join in my query but GROUP BY that is taking all the time and I
don't know how to tune it.
It gets executed by the procedure, the execution time requirement is < 4
sec,
but it takes 8-11 sec against 3 partitions , 9 mln rec each, it goes to 22
sec for 5 partitions.
I've been testing PostgreSQL performance for the last 2 months, comparing it
whith MySQL,
PostgreSQL performance with 5+ mln records on the table with 14 columns is
worse.
Is 14 columns is a big table for Postgres or 5mln rec is a big table?
The whole picture is that there are 2 databases : OLTP & "OLAP" that use to
be on different machines and on different databases.
The new project requires to put it on one database & machine.
I preferred Postgres ( poorly designed oltp would not suffer even more on
mysql) and now I'm trying to tune OLAP db.
thank you.
Helen
--
View this message in context: http://postgresql.1045698.n5.nabble.com/How-to-see-memory-usage-using-explain-analyze-tp4694962p4709...
Sent from the PostgreSQL - performance mailing list archive at Nabble.com.
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: helen_yelluas@mcafee.com
Subject: Re: How to see memory usage using explain analyze ?
In-Reply-To: <1313607119621-4709415.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