Re: Larger volumes of chronologically ordered data and the planner

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: John Moran <johnfrederickmoran(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Larger volumes of chronologically ordered data and the planner
Date: 2010-03-03 18:36:31
Message-ID: 14435.1267641391@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

John Moran <johnfrederickmoran(at)gmail(dot)com> writes:
> What is PostgreSQL's likely behaviour when it encounters a large
> volume of data that is chronologically ordered (there's a btree index
> on a date column)? Is postgreSQL intelligent enough to discern that
> since the most frequently accessed data is invariably recent data,
> that it should store only that in memory, and efficiently store less
> relevant, older data on disk (the volume of data in production at the
> moment is still small enough to fit entirely in memory)?

There's no dedicated intelligence about such a case, but I don't see why
the ordinary cache management algorithms won't handle it perfectly well.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Steve Atkins 2010-03-03 19:00:41 Re: PQntuples returns an int.
Previous Message Josh Kupershmidt 2010-03-03 18:32:01 Re: stopping processes, preventing connections