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 E8BCA3A540F for ; Wed, 1 Dec 2004 04:26:19 +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 59355-05 for ; Wed, 1 Dec 2004 04:26:13 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 918A63A51B2 for ; Wed, 1 Dec 2004 04:26:12 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iB14QBfJ001391; Tue, 30 Nov 2004 23:26:11 -0500 (EST) To: =?UTF-8?B?7J6l7ZiE7ISx?= Cc: pgsql-performance@postgresql.org Subject: Re: Using "LIMIT" is much faster even though, searching with PK. In-reply-to: <41AD4433.1030909@siche.net> References: <41AD4433.1030909@siche.net> Comments: In-reply-to =?UTF-8?B?7J6l7ZiE7ISx?= message dated "Wed, 01 Dec 2004 13:10:27 +0900" Date: Tue, 30 Nov 2004 23:26:11 -0500 Message-ID: <1390.1101875171@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200412/9 X-Sequence-Number: 9384 =?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