Received: from danbo.digsys.bg (root@danbo.digsys.bg [192.92.129.10]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA98634; Wed, 3 Nov 1999 10:45:50 -0500 (EST) (envelope-from genov@lorna.digsys.bg) Received: from lorna.digsys.bg (root@lorna.digsys.bg [193.68.6.15]) by danbo.digsys.bg (8.9.0/8.9.0) with ESMTP id RAA00304; Wed, 3 Nov 1999 17:45:48 +0200 (EET) Received: from lorna.digsys.bg (genov@localhost.digsys.bg [127.0.0.1]) by lorna.digsys.bg (8.9.0/8.9.0) with ESMTP id RAA13904; Wed, 3 Nov 1999 17:45:44 +0200 (EET) Message-Id: <199911031545.RAA13904@lorna.digsys.bg> To: pgsql-sql@postgreSQL.org cc: pgsql-novice@postgreSQL.org Subject: Optimizing a query through its syntax and indices Date: Wed, 03 Nov 1999 17:45:44 +0200 From: Stoyan Genov Hello, I talk PostgreSQL 6.5.2 ... Suppose we have some tables we join using some of their fields. Suppose there are "restrictions" for the values of some (or all) of the tables' fields of this kind: tableM.fieldN [ NOT ] IN (constA,constB,constC), tableP.fieldQ [ NOT ] IN (constD,constE,constF), etc... These restrictions can occur for the fields by which we join the tables, as well as for fields of tables we do not use for joins. Are there (can there be) general ( or not so general :-) ) rules for optimizing the query ( and the performance and the speed ) through the particular order we put the join statements in the WHERE clause, trough mixing/ordering the join parts and the restrictions ( in the means defined above ) in the values of the fields in the WHERE clause, through changing the syntax ( for example, using UNION or EXCEPT clauses ), or through using one- or more-than-one-field indices, or through doubling some of the restrictions if they refer to a field we join by ( for example, "... WHERE tableM.fieldN = tableP.fieldQ and tableM.fieldN in (constA,constB)" complemented by " and tableP.fieldQ in (constA ,constB)" ). I hope I was clear enough for my question to be understood. Any help will be appretiated. Regards, Stoyan Genov