Received: from trends.net (root@clio.trends.ca [209.47.148.2]) by hub.org (8.9.3/8.9.3) with ESMTP id MAA00586 for ; Wed, 7 Jul 1999 12:08:12 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by trends.net (8.8.8/8.8.8) with ESMTP id LAA19277 for ; Wed, 7 Jul 1999 11:56:09 -0400 (EDT) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA26224; Wed, 7 Jul 1999 11:44:58 -0400 (EDT) To: "Roderick A. Anderson" cc: PG-SQL Subject: Re: [SQL] Good Optimization In-reply-to: Your message of Wed, 7 Jul 1999 08:22:31 -0700 (PDT) Date: Wed, 07 Jul 1999 11:44:58 -0400 Message-ID: <26222.931362298@sss.pgh.pa.us> From: Tom Lane "Roderick A. Anderson" 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