From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Roderick A(dot) Anderson" <raanders(at)altoplanos(dot)net> |
Cc: | PG-SQL <pgsql-sql(at)postgreSQL(dot)org> |
Subject: | Re: [SQL] Good Optimization |
Date: | 1999-07-07 15:44:58 |
Message-ID: | 26222.931362298@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
"Roderick A. Anderson" <raanders(at)altoplanos(dot)net> writes:
> Also if the optimizer works similar to Oracle then the order of
> where statements would also help in actual performance. I'm mostly a
> lurker on this list but have never seen anything about this issue.
> When using Oracle, and won't it be nice when people mention PostgreSQL
> functionality when comparing other databases, the statements at the
> bottom should be the most restrictive and joins should be near the top.
The Postgres optimizer doesn't care about the order of where clauses;
it'll pick out the clauses it thinks are most effective regardless
of the order you write them in.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Roderick A. Anderson | 1999-07-07 16:10:13 | Re: [SQL] Good Optimization |
Previous Message | Tom Lane | 1999-07-07 15:42:37 | Re: [SQL] Good Optimization |