Thread: big bad join problems revisited

big bad join problems revisited

From
Dustin Sallings
Date:
    Wow.  So, the GEQO sped up the planning of my query significantly,
but I just added a another table and it got a little slower and ends up
consuming 64MB of memory.  It's kinda funny since there's only one thing
in my database currently, but won't be funny when two people try to query
it.

--
SA, beyond.com           My girlfriend asked me which one I like better.
pub  1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
|    Key fingerprint =  87 02 57 08 02 D0 DA D6  C8 0F 3E 65 51 98 D8 BE
L_______________________ I hope the answer won't upset her. ____________