| From: | Decibel! <decibel(at)decibel(dot)org> |
|---|---|
| To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
| Cc: | "Steve Madsen" <steve(at)lightyearsoftware(dot)com>, <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Interpreting statistics collector output |
| Date: | 2007-08-16 04:47:07 |
| Message-ID: | 85A10DB4-B0A2-4C30-BCA2-2A1487113CEB@decibel.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Aug 15, 2007, at 2:11 PM, Gregory Stark wrote:
> "Decibel!" <decibel(at)decibel(dot)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(at)decibel(dot)org
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rodrigo De León | 2007-08-16 05:21:29 | Re: Fastest way to import only ONE column into a table? (COPY doesn't work) |
| Previous Message | Phoenix Kiula | 2007-08-16 04:46:22 | Fastest way to import only ONE column into a table? (COPY doesn't work) |