From: Stephan Szabo <sszabo@megazone23.bigpanda.com>
To: Tomasz Myrta <jasiek@klaster.net>
Cc: pgsql-sql@postgresql.org
Subject: Re: sub-select with aggregate
Date: Thu, 24 Oct 2002 08:19:32 -0700 (PDT)
Message-ID: <20021024081033.U20230-100000@megazone23.bigpanda.com> (raw)
In-Reply-To: <3DB7BF5A.1090606@klaster.net>
On Thu, 24 Oct 2002, Tomasz Myrta wrote:
> Now I know the solution - to speed up this query I have to manually
> expose field from sub-query. It works fine, but I still don't know why I
> can't do this opposite way.
The system doesn't realize that it can limit the subquery when the only
things it has is the join clause and the limiting clause on the other
table. Like Tom's message about the other view, it won't imply that
X.foo=12345 from foo=12345 when the exposed foo is B.foo.
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: sszabo@megazone23.bigpanda.com, jasiek@klaster.net
Subject: Re: sub-select with aggregate
In-Reply-To: <20021024081033.U20230-100000@megazone23.bigpanda.com>
* 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