Greg Smith <[EMAIL PROTECTED]> writes:
> I actually have a paper design for something that builds a little model
> for how likely it is another commit will be coming soon that essentially
> turns this into something that can be tuned automatically, better than any
> person can do it. No idea if I'll actually build that thing, but I hope
> it's obvious that there's some possibility to improve this area for
> applications that can't use async commit. If you're going to dump the
> feature, I'd suggest at least waiting until later in the 8.4 cycle to see
> if something better comes along first.
What about the other idea of just having committers wait for the next
walwriter-cycle flush before reporting commit?
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
