From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stefan Keller <sfkeller@gmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Getting query plan alternatives from query planner?
Date: Thu, 20 Mar 2014 13:08:50 -0400
Message-ID: <15606.1395335330@sss.pgh.pa.us> (raw)
In-Reply-To: <CAFcOn2-9j4fTcJ39xvdCByF6dg3U_=TGumCCp1-7SH_J9G+GtA@mail.gmail.com>
References: <CAFcOn2-9j4fTcJ39xvdCByF6dg3U_=TGumCCp1-7SH_J9G+GtA@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Stefan Keller <sfkeller@gmail.com> writes:
> I'd like to know from the query planner which query plan alternatives
> have been generated and rejected. Is this possible?
No, not really. People have occasionally hacked the planner to print
rejected paths before they're discarded, but there's no convenient way
to do anything except send the data to the postmaster log, which isn't
all that convenient. A bigger problem is that people who are asking
for this typically imagine that the planner generates complete plans
before rejecting them; which it does not. Path alternatives are rejected
whenever possible before moving up to the next join level, so that what
we have rejected is actually just a plan fragment in most cases.
regards, tom lane
--
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: tgl@sss.pgh.pa.us, sfkeller@gmail.com
Subject: Re: Getting query plan alternatives from query planner?
In-Reply-To: <15606.1395335330@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