From: Tom Lane <tgl@sss.pgh.pa.us>
To: Віталій Тимчишин <tivv00@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Exists, limit and alternate plans
Date: Mon, 12 Jul 2010 10:45:14 -0400
Message-ID: <15039.1278945914@sss.pgh.pa.us> (raw)
In-Reply-To: <AANLkTikRAHA-kTh5q65zdSQvaiAPEewMj01yf16mNPIa@mail.gmail.com>
References: <AANLkTikRAHA-kTh5q65zdSQvaiAPEewMj01yf16mNPIa@mail.gmail.com>
=?KOI8-U?B?96bUwcymyiD0yc3eydvJzg==?= <tivv00@gmail.com> writes:
> So, my Qs:
> 1) Do we really have alternative plans for SubPlan that are selected at
> runtime? Wow.
Yup, see the AlternativeSubPlan stuff.
> 2) Why "Seq scan" plan is selected by default? Is it because of outer limit
> not being applied when calculating costs for subplans at runtime?
It's currently driven off the estimated rowcount for the parent plan
node --- 6831169 in your example. The subplan cannot see that the
parent plan node will be terminated short of full execution, so it
thinks that hashing the whole investor table will be a win.
Obviously it'd be nice to improve that for cases like upper LIMITs.
> 3) Why does limit inside exists helps?
I think it defeats the applicability of the hash-the-whole-subtable
approach.
regards, tom lane
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: tgl@sss.pgh.pa.us, tivv00@gmail.com
Subject: Re: Exists, limit and alternate plans
In-Reply-To: <15039.1278945914@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 DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox