Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 5E7939FB530 for ; Mon, 22 Oct 2007 23:24:51 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 23989-05 for ; Mon, 22 Oct 2007 23:24:40 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.5 Received: from web50901.mail.re2.yahoo.com (web50901.mail.re2.yahoo.com [206.190.38.121]) by postgresql.org (Postfix) with SMTP id 8EC3D9FA320 for ; Mon, 22 Oct 2007 23:24:44 -0300 (ADT) Received: (qmail 9151 invoked by uid 60001); 23 Oct 2007 02:24:39 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=3SKok1nsrO9KtN1wIcDc+DvsfXm+sh0Kl2aJTP6b8WJS7AvdHz+Df25PFz3b9qhfMoq8vS1/zaJErpp2bJ3xuNUH2qOTka6jg/ZqCTzSEndKBjwKpsjzof8w/FBTu43Ni8CVwZhsuqR5FviPkNC+Kl+nrEkiDK0R/sKArU4cs/g=; X-YMail-OSG: BRMbse0VM1k0P06we_KDZ5jkHBOMD71REXhxJL6RYE891r_jz25DpK2suJUdwtRmrwG4W5NNrm6oIIo8ee5cYGjaAqbMl0PpU4EJytDb22DWa79YfLNtKAFtYjIxo4rDgEEAieCbfQ2SYRrjwM7QQc5fSg-- Received: from [201.255.107.232] by web50901.mail.re2.yahoo.com via HTTP; Mon, 22 Oct 2007 19:24:39 PDT Date: Mon, 22 Oct 2007 19:24:39 -0700 (PDT) From: Adrian Demaestri Subject: Seqscan To: pgsql-performance@postgresql.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1054677571-1193106279=:8751" Content-Transfer-Encoding: 8bit Message-ID: <853733.8751.qm@web50901.mail.re2.yahoo.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.985 tagged_above=0 required=5 tests=AWL=0.983, BAYES_50=0.001, HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200710/245 X-Sequence-Number: 27267 --0-1054677571-1193106279=:8751 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi, I think planner should use other plans than seqscan to solve querys like select * from hugetable limit 1, especially when the talbe is very large. Is it solved in newer versions or is there some open issues about it?. thanks I'm working with postgres 8.0.1, --------------------------------- ¡Sé un mejor fotógrafo! Perfecciona tu técnica y encuentra las mejores fotos en: http://telemundo.yahoo.com/promos/mejorfotografo.html --0-1054677571-1193106279=:8751 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi,
I think planner should use other plans than seqscan to solve querys like select * from hugetable limit 1, especially when the talbe is very large. Is it solved in newer versions or is there some open issues about it?.
thanks
I'm working with postgres 8.0.1,


¡Sé un mejor fotógrafo!
Perfecciona tu técnica y encuentra las mejores fotos en:
http://telemundo.yahoo.com/promos/mejorfotografo.html --0-1054677571-1193106279=:8751--