mirror of
https://github.com/neondatabase/neon.git
synced 2026-08-18 03:58:19 +00:00
f2892d3798
This helps with identifying thrashing. I don't love the name, but, there is already "close-by-replace". While reading the code, I also found a case where we waste work in a cache pressure situation: https://github.com/neondatabase/neon/issues/6065 refs https://github.com/neondatabase/cloud/issues/8351