pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gaetano Mendola <mendola@bigfoot.com>
To: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: Richard Huxton <dev@archonet.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: using an index worst performances
Date: Fri, 20 Aug 2004 11:37:27 +0200
Message-ID: <4125C657.7000702@bigfoot.com> (raw)
In-Reply-To: <4125565D.3060008@familyhealth.com.au>
References: <cg2nrf$sc1$1@floppy.pyrenet.fr>
	<4124ECF3.6040901@archonet.com>
	<412505F6.6080000@bigfoot.com>
	<4125565D.3060008@familyhealth.com.au>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Christopher Kings-Lynne wrote:

|>>> 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.
|
|
| Given the almost irrelvant difference in the speed of those queries, I'd
| say that with the stats so high, postgres simply takes longer to check
| the statistics to come to the same conclusion.  ie. it has to loop over
| 200 rows instead of just 10.

The time increase seems too much.


Regards
Gaetano Mendola




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBJcZW7UpzwH2SGd4RAuiMAJ971EAtr1RrHu2QMi0YYk0kKeuQmACg9bd3
CFcmq5MRG/Eq3RXdNOdu43Y=
=Bvo8
-----END PGP SIGNATURE-----




view thread (11+ messages)  latest in thread

Message-ID: <4125C657.7000702@bigfoot.com>
Permalink:  ../4125C657.7000702@bigfoot.com/
Also on:    postgresql.org/message-id/4125C657.7000702@bigfoot.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: mendola@bigfoot.com, chriskl@familyhealth.com.au, dev@archonet.com
  Subject: Re: using an index worst performances
  In-Reply-To: <4125C657.7000702@bigfoot.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox