On 12/04/2013 07:33 AM, Jonathan Corbet wrote:
Wow, Josh, I'm surprised to hear this from you.
The active/inactive list mechanism works great for the vast majority of
users. The second-use algorithm prevents a lot of pathological behavior,
like wiping out your entire cache by copying a big file or running a
backup. We *need* that kind of logic in the kernel.
The amount of automated testing, including performance testing, has
increased markedly in the last couple of years. I bet that it would not
be hard at all to get somebody like Fengguang Wu to add some
Postgres-oriented I/O tests to his automatic suite:
https://lwn.net/Articles/571991/
Then we would all have a much better idea of how kernel releases are
affecting one of our most important applications; developers would pay
attention to that information.
Or you could go off and do your own thing, but I believe that would leave
us all poorer.
Thank you for your very well thought out, and knowledgeable response.
This is certainly helpful and highlights what a lot of us were already
stating.
Sincerely,
Joshua D. Drake
--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
