From: Hyun-Sung, Jang <siche@siche.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-performance@postgresql.org
Subject: Re: Using "LIMIT" is much faster even though, searching
Date: Wed, 01 Dec 2004 13:38:40 +0900
Message-ID: <41AD4AD0.908@siche.net> (raw)
In-Reply-To: <1390.1101875171@sss.pgh.pa.us>
References: <41AD4433.1030909@siche.net>
<1390.1101875171@sss.pgh.pa.us>
before test, I already executed VACUUM FULL.
this result show up after vacuum full.
Tom Lane 쓴 글:
>=?UTF-8?B?7J6l7ZiE7ISx?= <siche@siche.net> writes:
>
>
>>but, sequence scan, as you see above result, there is big time
>>difference between using LIMIT and without using it.
>>
>>
>
>You've got a table full of dead rows. Try VACUUM FULL ...
>
> regards, tom lane
>
>
>
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: siche@siche.net, tgl@sss.pgh.pa.us
Subject: Re: Using "LIMIT" is much faster even though, searching
In-Reply-To: <41AD4AD0.908@siche.net>
* 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