Received: from dune.krs.ru (dune.krs.ru [195.161.16.38]) by hub.org (8.8.8/8.7.5) with ESMTP id KAA12343 for ; Tue, 4 Aug 1998 10:18:57 -0400 (EDT) Received: from krs.ru (localhost.krs.ru [127.0.0.1]) by dune.krs.ru (8.8.8/8.8.8) with ESMTP id WAA05936; Tue, 4 Aug 1998 22:16:43 +0800 (KRSS) (envelope-from vadim@krs.ru) Sender: root@dune.krs.ru Message-ID: <35C717CA.5D1395E4@krs.ru> Date: Tue, 04 Aug 1998 22:16:42 +0800 From: Vadim Mikheev Organization: OJSC Rostelecom (Krasnoyarsk) X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.6-RELEASE i386) MIME-Version: 1.0 To: Chris Williams CC: pgsql-sql@postgreSQL.org Subject: Re: [SQL] Which index is better for join operations References: <005d01bdbfae$0eaac810$edfe04c7@itd.sterling.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Chris Williams wrote: > > I have a SQL statement that is SLOW and I am wondering if using a hash index instead of a btree on > the fields that are used for the join operations would be faster? Anyone have any input on this. No. Also, keep in mind that btree-s are more stable and hash index creation takes more time. Did you run vacuum? Also, it's always good to build index after copying data to tables - it's faster and updates statistic about relation. > The query is between 3 tables. If you need any more details, please let me know. Vadim