From: Vadim Mikheev <vadim@krs.ru>
To: Jan Wieck <jwieck@debis.com>
Cc: s-fery@kkt.sote.hu
Cc: hackers@postgreSQL.org
Subject: Re: [HACKERS] Re: [SQL] cursor and update + view
Date: Thu, 26 Nov 1998 10:27:44 +0700
Message-ID: <365CCAB0.CE4B0143@krs.ru> (raw)
References: <m0zicJk-000EBQC@orion.SAPserv.Hamburg.dsh.de>
Jan Wieck wrote:
>
> > On the other hand, as we talk about query optimization - why
> > rule system should do optimizer' work? Why not just put
> > _any_ VIEW' query into FROM and let optimizer decide
> > could query be rewritten as join or not? Ppl do strange
> > things sometimes -:) Sometimes they use subqueries in
> > WHERE while joins could be used and our optimizer don't
> > try to catch this. I know that Sybase does.
> > And, imho, we should implement this ... sometime -:))
>
> Depends on where the optimization is done. If we do it on the
> parsetree (Query struct), it's the job of the rule system.
> The optimizer does not have to modify the parsetree. If it is
> done on the way from the parsetree to the plan, it is the job
> of the optimizer.
>
> If it is possible to do it on the parsetree, I would do it
> there.
Subquery --> Join transformation/optimization implemented in
rule system will be used for Views only. Being implemented
in optimizer it will be used in all cases.
Vadim
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: vadim@krs.ru, jwieck@debis.com, s-fery@kkt.sote.hu, hackers@postgreSQL.org
Subject: Re: [HACKERS] Re: [SQL] cursor and update + view
In-Reply-To: <365CCAB0.CE4B0143@krs.ru>
References: <m0zicJk-000EBQC@orion.SAPserv.Hamburg.dsh.de> <365CCAB0.CE4B0143@krs.ru>
* 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