X-Original-To: pgsql-performance@postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by developer.postgresql.org (Postfix) with ESMTP id C0AFB9232C1 for ; Fri, 30 May 2003 04:59:06 -0400 (EDT) Received: from developer.postgresql.org ([64.117.224.193]) by localhost (developer.postgresql.org [64.117.224.193:10024]) (amavisd-new) with ESMTP id 45550-08 for ; Fri, 30 May 2003 04:59:01 -0400 (EDT) Received: from mail.deltav.hu (unknown [213.163.0.192]) by developer.postgresql.org (Postfix) with ESMTP id 37999925149 for ; Fri, 30 May 2003 04:59:01 -0400 (EDT) Received: from fejleszt4 ([213.163.10.103]) by mail.deltav.hu (Netscape Messaging Server 3.6) with SMTP id AAA2646 for ; Fri, 30 May 2003 10:58:58 +0200 Message-ID: <001c01c32689$82da1050$0403a8c0@fejleszt4> From: =?iso-8859-1?Q?SZUCS_G=E1bor?= To: References: <20030529194451.24416.h006.c001.wm@mail.dilger.cc.criticalpath.net> Subject: Re: Select query takes long to execute Date: Fri, 30 May 2003 10:57:33 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Virus-Scanned: by amavisd-new X-Archive-Number: 200305/269 X-Sequence-Number: 2048 Nikolaus, I think that shouldn't be any more effective. As I experienced, it's irrelevant how many cols an index has as long as you only use the first column. And, after that, if you use another column, how could a missing second column be any better? G. ------------------------------- cut here ------------------------------- ----- Original Message ----- From: "Nikolaus Dilger" Sent: Friday, May 30, 2003 4:44 AM > Kevin, > > How about creating a new index just on column6? > That should be much more effective than the multicolumn > index. > > Regards, > Nikolaus