agora inbox for pgsql-sql@postgresql.org
help / color / mirror / Atom feedFrom: Tom Lane <tgl@sss.pgh.pa.us>
To: Tim Dudgeon <tdudgeon.ml@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: slow sub-query problem
Date: Mon, 17 Nov 2014 15:10:46 -0500
Message-ID: <23343.1416255046@sss.pgh.pa.us> (raw)
In-Reply-To: <546A3FBA.9020901@gmail.com>
References: <546A3FBA.9020901@gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
Tim Dudgeon <tdudgeon.ml@gmail.com> writes:
> I'm having problems optimising a query that's very slow due to a sub-query.
I think it might get better if you could fix this misestimate:
> " -> Bitmap Index Scan on idx_sp_property_id
> (cost=0.00..33.90 rows=1146 width=0) (actual time=51.656..51.656 rows=811892 loops=366)"
> " Index Cond: (property_id = ANY ('{1,643413,1106201}'::integer[]))"
1146 estimated vs 811892 actual is pretty bad, and it doesn't seem like
this is a very hard case to estimate. Are the stats for structure_props
up to date? Maybe you need to increase the statistics target for the
property_id column.
Another component of the bad plan choice is this misestimate:
> " -> HashAggregate (cost=1091.73..1091.75 rows=2 width=4) (actual time=2.829..3.212 rows=366 loops=1)"
> " Group Key: structure_props_1.structure_id"
but it might be harder to do anything about that one, since the result
depends on the property_id being probed; without cross-column statistics
it may be impossible to do much better.
regards, tom lane
--
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql
view thread (10+ messages) latest in thread
Message-ID: <23343.1416255046@sss.pgh.pa.us>
Permalink: ../23343.1416255046@sss.pgh.pa.us/
Also on: postgresql.org/message-id/23343.1416255046@sss.pgh.pa.us
reply
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-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, tdudgeon.ml@gmail.com
Subject: Re: slow sub-query problem
In-Reply-To: <23343.1416255046@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox