Re: Group Commit

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Group Commit
Date: 2008-03-07 00:57:41
Message-ID: 27983.1204851461@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Greg Smith <gsmith(at)gregsmith(dot)com> 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2008-03-07 00:58:47 Re: Idle idea for a feature
Previous Message Greg Smith 2008-03-07 00:35:53 Re: Group Commit