X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id AE7065E46C5 for ; Thu, 19 Aug 2004 17:13:06 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 68419-04 for ; Thu, 19 Aug 2004 20:12:57 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id C37BF5E3631 for ; Thu, 19 Aug 2004 17:12:56 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i7JKCtiG071519 for ; Thu, 19 Aug 2004 20:12:55 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i7JJuoaf066502 for pgsql-performance@postgresql.org; Thu, 19 Aug 2004 19:56:50 GMT From: Gaetano Mendola X-Newsgroups: comp.databases.postgresql.performance Subject: Re: using an index worst performances Date: Thu, 19 Aug 2004 21:56:38 +0200 Organization: PYRENET Midi-pyrenees Provider Lines: 34 Message-ID: <412505F6.6080000@bigfoot.com> References: <4124ECF3.6040901@archonet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Complaints-To: abuse@pyrenet.fr To: Richard Huxton User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en In-Reply-To: <4124ECF3.6040901@archonet.com> X-Enigmail-Version: 0.84.2.0 X-Enigmail-Supports: pgp-inline, pgp-mime To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/295 X-Sequence-Number: 7931 Richard Huxton wrote: > Gaetano Mendola wrote: > >> Hi all, >> I'm tring to optimize the following query: >> >> http://rafb.net/paste/results/YdO9vM69.html >> >> as you can see from the explain after defining the >> index the performance is worst. >> >> If I raise the default_statistic_target to 200 >> then the performance are worst then before: >> >> >> Without index: 1.140 ms >> With index: 1.400 ms >> With default_statistic_targer = 200: 1.800 ms > > > Can I just check that 1.800ms means 1.8 secs (You're using . as the > thousands separator)? > > If it means 1.8ms then frankly the times are too short to mean anything > without running them 100 times and averaging. It mean 1.8 ms and that execution time is sticky to that value even with 1000 times. Regards Gaetano Mendola