mirror of
https://github.com/postgres/postgres.git
synced 2025-10-27 00:12:01 +03:00
Allow BufferAccessStrategy to limit pin count.
While pinning extra buffers to look ahead, users of strategies are in danger of using too many buffers. For some strategies, that means "escaping" from the ring, and in others it means forcing dirty data to disk very frequently with associated WAL flushing. Since external code has no insight into any of that, allow individual strategy types to expose a clamp that should be applied when deciding how many buffers to pin at once. Reviewed-by: Andres Freund <andres@anarazel.de> Reviewed-by: Melanie Plageman <melanieplageman@gmail.com> Discussion: https://postgr.es/m/CAAKRu_aJXnqsyZt6HwFLnxYEBgE17oypkxbKbT1t1geE_wvH2Q%40mail.gmail.com
This commit is contained in:
@@ -318,6 +318,7 @@ extern BufferAccessStrategy GetAccessStrategy(BufferAccessStrategyType btype);
|
||||
extern BufferAccessStrategy GetAccessStrategyWithSize(BufferAccessStrategyType btype,
|
||||
int ring_size_kb);
|
||||
extern int GetAccessStrategyBufferCount(BufferAccessStrategy strategy);
|
||||
extern int GetAccessStrategyPinLimit(BufferAccessStrategy strategy);
|
||||
|
||||
extern void FreeAccessStrategy(BufferAccessStrategy strategy);
|
||||
|
||||
|
||||
Reference in New Issue
Block a user