John Moran <johnfrederickmoran@xxxxxxxxx> 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 -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
