Jack Orenstein <[EMAIL PROTECTED]> writes:
> What would be really nice is something like "cluster recent". The idea is to
> cluster only rows added since the last cluster.
And you would put them where?
regards, tom lane
---(end of broadcast)---
Greg Stark wrote:
Can you recommend an application-level workaround that will access pages
in the right order?
Well you could try CLUSTER-ing your table on that index.
For my application, the problem with CLUSTER is that it reclusters the entire
table. So as the table grows, the cost of CLUSTER go
Jack Orenstein <[EMAIL PROTECTED]> writes:
> Alvaro Herrera wrote:
>
> > On Wed, Jun 02, 2004 at 08:38:58PM -0400, Jack Orenstein wrote:
> >
> > >What is the pattern of access to data pages? I can think of two likely
> > >answers:
> > >
> > >1) The index is scanned for ages 30 through 40. As each
On Wed, Jun 02, 2004 at 11:22:53PM -0400, Jack Orenstein wrote:
> Alvaro Herrera wrote:
> >On Wed, Jun 02, 2004 at 08:38:58PM -0400, Jack Orenstein wrote:
> >
> >
> >>What is the pattern of access to data pages? I can think of two likely
> >>answers:
> >>
> >>1) The index is scanned for ages 30 thr
Alvaro Herrera wrote:
On Wed, Jun 02, 2004 at 08:38:58PM -0400, Jack Orenstein wrote:
What is the pattern of access to data pages? I can think of two likely
answers:
1) The index is scanned for ages 30 through 40. As each index entry is
scanned, a row is retrieved.
This one. There have been nois
On Wed, Jun 02, 2004 at 08:38:58PM -0400, Jack Orenstein wrote:
> What is the pattern of access to data pages? I can think of two likely
> answers:
>
> 1) The index is scanned for ages 30 through 40. As each index entry is
> scanned, a row is retrieved.
This one. There have been noises about do
Suppose I have a table as follows:
testdb=> \d person
Table "public.person"
Column | Type | Modifiers
+-+---
id | integer | not null
age| integer
