Received: from dwarf.rfb.lv (dwarf.rfb.lv [195.244.137.210]) by hub.org (8.9.2/8.9.1) with ESMTP id LAA52501 for ; Fri, 5 Feb 1999 11:24:18 -0500 (EST) (envelope-from juris@rfb.lv) Received: from rfb.lv ([195.244.137.157]) by dwarf.rfb.lv with esmtp id m108omy-0002gAC (Debian Smail-3.2 1996-Jul-4 #2); Fri, 5 Feb 1999 19:11:32 +0200 (EET) Message-ID: <36BB1B2E.FBB15AFC@rfb.lv> Date: Fri, 05 Feb 1999 18:24:14 +0200 From: Juris X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: pgsql-sql@postgreSQL.org Subject: Re: [SQL] performance problems of a complex query with 2 subselects References: <19990205162258.18987.qmail@desertmoon.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit > You need to 'vacuum analyze ' for each table that you have created > AFTER you've created the indexes for them before the sql optimizer will > use the indexes. This should solve most of your speed issues. I also believe > that this is in the FAQ. I forgot to tell you, but I did do vacuum; vacuum analyze; It seemed to process all tables, so I thought there was no need to vacuum analyze individual tables. I'll try that, thanks. Juris.