From: Amit Kapila <amit.kapila@huawei.com>
To: <fburgess@radiantblue.com>
CC: <pgsql-performance@postgresql.org>
References: 
 <20130522093304.5a830134ae84016b0174832fdc1a3173.018dc1af79.wbe@email11.secureserver.net>
In-Reply-To: 
 <20130522093304.5a830134ae84016b0174832fdc1a3173.018dc1af79.wbe@email11.secureserver.net>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Thread-Index: Ac5XCgoJzglTJl+PTm2y7HDHabuSRwAcTZfQ
Content-Language: en-us
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

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=3Doff;

And see what is the plan it chooses and does it pick up index scan on large=
r table?

Could you please output of \d SARS_ACTS and \d SARS_ACTS_RUN?


With Regards,
Amit Kapila.


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