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 D6E413A548D for ; Wed, 1 Dec 2004 04:38:52 +0000 (GMT) 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 63601-04 for ; Wed, 1 Dec 2004 04:38:47 +0000 (GMT) Received: from fine4.fine.co.kr (unknown [211.238.40.4]) by svr1.postgresql.org (Postfix) with ESMTP id C19003A5484 for ; Wed, 1 Dec 2004 04:38:44 +0000 (GMT) Received: from [192.168.0.240] ([192.168.0.240]) (authenticated bits=0) by fine4.fine.co.kr (8.13.1/8.13.1) with ESMTP id iB14ca0n029785; Wed, 1 Dec 2004 13:38:37 +0900 Message-ID: <41AD4AD0.908@siche.net> Date: Wed, 01 Dec 2004 13:38:40 +0900 From: "Hyun-Sung, Jang" User-Agent: ¨È| eÈ 0.9 (Windows/20041103) X-Accept-Language: ko-kr, ko, en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-performance@postgresql.org Subject: Re: Using "LIMIT" is much faster even though, searching References: <41AD4433.1030909@siche.net> <1390.1101875171@sss.pgh.pa.us> In-Reply-To: <1390.1101875171@sss.pgh.pa.us> Content-Type: multipart/alternative; boundary="------------080103070908010700070206" X-Virus-Scanned: by amavisd-new at hub.org X-Amavis-Alert: BAD HEADER Non-encoded 8-bit data (char A8 hex) in message header 'User-Agent': User-Agent: \250\310| e\310 0.9 (Wind... X-Spam-Status: No, hits=0.048 tagged_above=0 required=5 tests=AWL, HTML_50_60, HTML_MESSAGE X-Spam-Level: X-Archive-Number: 200412/10 X-Sequence-Number: 9385 This is a multi-part message in MIME format. --------------080103070908010700070206 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit before test, I already executed VACUUM FULL. this result show up after vacuum full. Tom Lane ì“´ 글: >=?UTF-8?B?7J6l7ZiE7ISx?= 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 > > > --------------080103070908010700070206 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit 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

  

--------------080103070908010700070206--