pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: wieck@debis.com
To: kudo@partitur.se
Cc: maillist@candle.pha.pa.us
Cc: pgsql-sql@postgreSQL.org
Subject: Re: [SQL] Good Optimization
Date: Thu, 8 Jul 1999 11:04:26 +0200 (MET DST)
Message-ID: <m112A6U-0003ktC@orion.SAPserv.Hamburg.dsh.de> (raw)
In-Reply-To: <37845CC3.A2391717@partitur.se>

>
> Bruce Momjian wrote:
> >=20
> > Added to TODO:
> >=20
> >         * In WHERE x=3D3 AND x=3Dy, add y=3D3
>
> I don't know if I'm way off, but wouldn't removing "x=3Dy" improve
> performance further?

    Maybe  in  the simple case above. But it will probably change
    the result set if someone issues

        SELECT a.x, b.y FROM a, b WHERE a.x >= 10
                                    AND a.x <= 19
                                    AND a.x = b.x;

    which should then get rewritten into

        SELECT a.x, b.y FROM a, b WHERE a.x >= 10
                                    AND a.x <= 19
                                    AND a.x = b.x
                                    AND b.x >= 10
                                    AND b.x <= 19;

    This time the "a.x = b.x" is important!

    IMHO we're improving optimization more and more on  the  cost
    of  query  parse/rewrite/optimize/plan time. Thus performance
    of statements that EXECUTE fast slows  down  more  and  more.
    Isn't   it   time   to   think   about  some  (maybe  shared)
    "parsetree->plan" cache that provides ready to use  plans  if
    only Const values have changed?


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #





view thread (27+ messages)  latest in thread

Message-ID: <m112A6U-0003ktC@orion.SAPserv.Hamburg.dsh.de>
Permalink:  ../m112A6U-0003ktC@orion.SAPserv.Hamburg.dsh.de/
Also on:    postgresql.org/message-id/m112A6U-0003ktC@orion.SAPserv.Hamburg.dsh.de

 · 

reply

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: wieck@debis.com, kudo@partitur.se, maillist@candle.pha.pa.us
  Subject: Re: [SQL] Good Optimization
  In-Reply-To: <m112A6U-0003ktC@orion.SAPserv.Hamburg.dsh.de>
  References: <37845CC3.A2391717@partitur.se> <m112A6U-0003ktC@orion.SAPserv.Hamburg.dsh.de>

* 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