Re: our buffer replacement strategy is kind of lame
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Simon Riggs <simon@2ndQuadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>, Greg Stark <stark@mit.edu>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2012-01-02T17:41:47Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Split work of bgwriter between 2 processes: bgwriter and checkpointer.
- 806a2aee3791 9.2.0 cited
Simon Riggs <simon@2ndQuadrant.com> writes: > Does anyone have a better idea for reducing BufFreelistLock > contention? Something simple that will work for 9.2? Get rid of the freelist? Once shared buffers are full, it's just about useless anyway. But you'd need to think about the test cases that you pay attention to, as there might be scenarios where it remains useful. regards, tom lane