I'm sure it's been done before, but right now I feel smart about the recognition. I want to make postgres' buffer cache take into account whether previous accesses where synchronous or asynchronous:
I.e. tag pages that needed to be read in synchronously with that fact (or reversely ones that were prefetchable).
That's somewhat similar to the old idea of @petervgeoghegan (IIRC) to just always keep inner index pages around more aggressively.
-
-
But I hope it'd be more generic (i.e. also keep randomly accessed table pages around) and resilient (doesn't trigger due to vacuum scanning the index).
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
It actually targeted all index pages - there are so few internal pages that they're bound to stay in buffer cache without any help. pgbench_accounts pkey pages are ~6x more popular than heap pages -- big disparity is normal. That should be represented, somehow.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.