From: Simon Riggs <simon@2ndQuadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: enable_joinremoval
Date: Mon, 29 Mar 2010 18:26:59 +0100
Message-ID: <1269883619.3684.3954.camel@ebony> (raw)
In-Reply-To: <603c8f071003290637q14d431f7j90afabd6fd2ec952@mail.gmail.com>
References: <1269851630.3684.3636.camel@ebony>
<603c8f071003290637q14d431f7j90afabd6fd2ec952@mail.gmail.com>
On Mon, 2010-03-29 at 09:37 -0400, Robert Haas wrote:
> In many
> cases it's not horribly difficult to work around because you can do
> SELECT * FROM ... instead of your original select list, but there
> might be some cases with multiple levels of views where it isn't that
> easy. I think it would be good to add this back.
People have asked me how they would know whether join removal has
worked. If there is a workaround that works for most cases, I think that
might be all we need. Do you have an example where that doesn't work, so
we can judge how common that would be?
--
Simon Riggs www.2ndQuadrant.com
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-hackers@postgresql.org
Cc: simon@2ndQuadrant.com, robertmhaas@gmail.com
Subject: Re: enable_joinremoval
In-Reply-To: <1269883619.3684.3954.camel@ebony>
* 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