From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: Hyun-Sung, Jang <siche@siche.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Subject: Re: Using "LIMIT" is much faster even though, searching
Date: Tue, 30 Nov 2004 21:03:51 -0800
Message-ID: <200411302103.51643.josh@agliodbs.com> (raw)
In-Reply-To: <41AD4AD0.908@siche.net>
References: <41AD4433.1030909@siche.net>
<1390.1101875171@sss.pgh.pa.us>
<41AD4AD0.908@siche.net>
Hyun-Sang,
> before test, I already executed VACUUM FULL.
> this result show up after vacuum full.
Really? Your results really look like a bloated table. Can you run VACUUM
FULL ANALYZE VERBOSE on the table and post the output?
> When I using index scan, the result was almost same, that means, there
> was no time difference, so i'll not mention about index scan.
Can we see an index scan plan anyway? EXPLAIN ANALYZE?
Oh, and if this is a zip codes table, why are you using a sequence as the
primary key instead of just using the zip code?
--
Josh Berkus
Aglio Database Solutions
San Francisco
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: josh@agliodbs.com, siche@siche.net, tgl@sss.pgh.pa.us
Subject: Re: Using "LIMIT" is much faster even though, searching
In-Reply-To: <200411302103.51643.josh@agliodbs.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