> I've written a long paper covering the internals here named "Inside the
> PostgreSQL Buffer Cache" at
> http://www.westnet.com/~gsmith/content/postgresql/ if you want to know
> exactly how this is all implemented.
Greg,
That's exactly what I was looking for,
Regards,
John
--
Sent via pgsql-g
John Moran wrote:
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
When you ask for a database block from disk, it increments a us
John Moran 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,
>
Hello,
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
