On Wed, Dec 8, 2010 at 1:56 PM, Tom Lane <[email protected]> wrote: > Simon Riggs <[email protected]> writes: >> Optimize commit_siblings in two ways to improve group commit. >> First, avoid scanning the whole ProcArray once we know there >> are at least commit_siblings active; second, skip the check >> altogether if commit_siblings = 0. > >> Greg Smith > > I wonder whether we shouldn't change commit_siblings' default value to > zero while we're at it.
Not that I see anything to disagree with in this patch, but what happened to posting patches in advance of committing them? Or did I just miss that part? -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list ([email protected]) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
