Robert Haas <robertmh...@gmail.com> writes:
> I don't see that as a problem. What we're struggling with today is
> that, until we fsync(), the system is too lazy about writing back
> dirty pages. And then when we fsync(), it becomes very aggressive and
> system-wide throughput goes into the tank. What we're aiming to do
> here is get is to start the writeback sooner than it would otherwise
> start so that it is spread out over a longer period of time.
Yeah. It's sounding more and more like the right semantics are to
give the kernel a hint that we're going to fsync these files later,
so it ought to get on with writing them anytime the disk has nothing
better to do. I'm not sure if there's value in being specific about
how much later; that would probably depend on details of the scheduler
that I don't know.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
