Re Mel Gorman's details in http://article.gmane.org/gmane.linux.kernel/1663694 http://article.gmane.org/gmane.linux.kernel/1663694 I don't understand why Postg

Re Mel Gorman's details in http://article.gmane.org/gmane.linux.kernel/1663694 http://article.gmane.org/gmane.linux.kernel/1663694 I don't understand why PostgreSQL people don't want to write their own IO scheduler and buffer management. It's not that hard to implement (even a MT IO+BM is not really complicated), and there are major advantages: - you become truly platform-independent instead of relying on particulars of some kernel [the only thing you need from the OS is some form of O_DIRECT; it exists also on Win32] - you have total control over buffer memory allocation and IO scheduling - whatever scheduling and buffer management policy you're using, you can more easily adapt it to SSDs and other storage types, which are still in their infancy (e.g., memristors) [thus not depending on the kernel developers' goodwill] I mean, really: these pepole have implemented a RDBMS with a bunch of extensions to standard SQL, and IO+buffer management layer is suddenly complicated, or [quote from the link]: "While some database vendors have this option, the Postgres community do not have the resources to implement something of this magnitude." This smells more like politics than a technical issue.