Received: from serlin.ivsol (IDENT:root@du-148-233-221-42.prodigy.net.mx [148.233.221.42]) by hub.org (8.10.1/8.10.1) with ESMTP id e7KFuHm35180 for ; Sun, 20 Aug 2000 11:56:17 -0400 (EDT) Received: from fralet (fralet.ivsol [192.168.1.11]) by serlin.ivsol (8.9.3/8.8.7) with SMTP id LAA00936 for ; Sun, 20 Aug 2000 11:01:39 -0500 Message-ID: <010501c00ac0$72d47a20$0b01a8c0@ivsol> From: "Franz J Fortuny" To: "pgSQL" Subject: Speed or configuration Date: Sun, 20 Aug 2000 11:05:24 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Archive-Number: 200008/187 At our company we are presently using a commercial database that generates results from this query: select xx1,xx2,xx3 from tableX where field1 in (select field1 from tableY where field2=NNN and field3=NNN2 and field4=NNN4) tableX has 790,000 rows, and an index on field1 tableY has abou 175,000 rows and an index that includes field2,field3,field4 (and 2 other fields not being used here) Of course, the order in the indexes is the logical one. I have made copies of the tables from the commercial SQL server to PostgreSQL and PostgreSQL is consistently faster in things like count(*) and certain other queries. But when it comes to the above mentioned query, PostgreSQL simply stays there, forever. The postgres backend must be killed in order to free the client program. Any suggestions? Franz J Fortuny