From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Matthew Wakeling <matthew(at)flymine(dot)org> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: GiST, caching, and consistency |
Date: | 2009-08-05 13:42:54 |
Message-ID: | 603c8f070908050642x4ac57a9ev2e9c64a2352c10b3@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Wed, Aug 5, 2009 at 6:20 AM, Matthew Wakeling<matthew(at)flymine(dot)org> wrote:
> It is certainly doing a sequential scan. So are you saying that it will
> start a sequential scan from a different part of the table each time, even
> in the absence of other simultaneous sequential scans? Looks like I'm going
> to have to remove the limit to get sensible results - I only added that to
> make the query return in a sensible time for performance testing.
>
> Some trivial testing with "select * from location limit 10;" indicates that
> it starts the sequential scan in the same place each time - but is this
> different from the above query?
Maybe it's because of this?
http://www.postgresql.org/docs/8.3/static/runtime-config-compatible.html#GUC-SYNCHRONIZE-SEQSCANS
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Matthew Wakeling | 2009-08-05 13:53:50 | Re: GiST, caching, and consistency |
Previous Message | Matthew Wakeling | 2009-08-05 10:20:18 | Re: GiST, caching, and consistency |