From: Amit Kapila <amit.kapila@huawei.com>
To: fburgess@radiantblue.com
Cc: pgsql-performance@postgresql.org
Subject: Re: Very slow inner join query Unacceptable latency.
Date: Thu, 23 May 2013 11:43:44 +0530
Message-ID: <003d01ce577c$af6535d0$0e2fa170$@kapila@huawei.com> (raw)
In-Reply-To: <20130522093304.5a830134ae84016b0174832fdc1a3173.018dc1af79.wbe@email11.secureserver.net>
References: <20130522093304.5a830134ae84016b0174832fdc1a3173.018dc1af79.wbe@email11.secureserver.net>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On Wednesday, May 22, 2013 10:03 PM fburgess wrote:
> I did perform a explain analyze on the query.
Explain analyze doesn't help to collect statistics. You should use Analyze <table_name>.
Ideally optimizer should have slected the best plan, but just to check you can once try with
SET enable_hashjoin=off;
And see what is the plan it chooses and does it pick up index scan on larger table?
Could you please output of \d SARS_ACTS and \d SARS_ACTS_RUN?
With Regards,
Amit Kapila.
--
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: amit.kapila@huawei.com, fburgess@radiantblue.com
Subject: Re: Very slow inner join query Unacceptable latency.
In-Reply-To: <003d01ce577c$af6535d0$0e2fa170$@kapila@huawei.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