Re: Interpreting statistics collector output - Mailing list pgsql-general

From Decibel!
Subject Re: Interpreting statistics collector output
Date
Msg-id 85A10DB4-B0A2-4C30-BCA2-2A1487113CEB@decibel.org
Whole thread Raw
In response to Re: Interpreting statistics collector output  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Interpreting statistics collector output
List pgsql-general
On Aug 15, 2007, at 2:11 PM, Gregory Stark wrote:
> "Decibel!" <decibel@decibel.org> writes:
>> On Wed, Aug 15, 2007 at 01:26:02PM -0400, Steve Madsen wrote:
>>> On Aug 15, 2007, at 11:52 AM, Decibel! wrote:
>>>> I can't really think of a case where a seqscan wouldn't return
>>>> all the
>>>> rows in the table... that's what it's meant to do.
>
> LIMIT

Ok, you got me. :P But normally you wouldn't do a LIMIT without some
kind of an ORDER BY, which would mean scanning the whole table.

In any case, it's not a perfect metric, but in general use it seems
to be "good enough".
--
Decibel!, aka Jim Nasby                        decibel@decibel.org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)



pgsql-general by date:

Previous
From: Naz Gassiep
Date:
Subject: Re: User-Friendly TimeZone List
Next
From: "Phoenix Kiula"
Date:
Subject: Fastest way to import only ONE column into a table? (COPY doesn't work)