From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Jan Wieck <jwieck(at)debis(dot)com> |
Cc: | secret <secret(at)kearneydev(dot)com>, pgsql-sql(at)postgreSQL(dot)org, johnridout(at)ctasystems(dot)co(dot)uk |
Subject: | Re: [SQL] Good Optimization |
Date: | 1999-07-07 18:00:57 |
Message-ID: | 199907071801.OAA05018@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
> > There is a simple way to optimize SQL queries involving joins to
> > PostgreSQL that I think should be handled by Postgre? If one is joining
> > a tables a,b on attribute "x" and if one has something like x=3 then it
> > helps A LOT to say: a.x=3 and b.x=3 in addition to saying a.x=b.x ...
> > The example below shoulds the radical speed gain of doing this, and I
> > think it isn't something real obvious to most people...
> >
> > Of course it could just be a common thing to do in SQL, anyway, just
> > thought I'd let you all know what I discovered.
> >
> >
> >
> > Here is an example:
> > [...]
>
> Hmmmmm,
>
> wouldn't it be nice to do such things automagically
> (rewriter? planner?).
Added to TODO:
* In WHERE x=3 AND x=y, add y=3
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-07-07 18:10:48 | Re: [SQL] Good Optimization |
Previous Message | Jan Wieck | 1999-07-07 17:22:57 | Re: [SQL] Good Optimization |