Simon Riggs <simon(at)2ndQuadrant(dot)com> 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.

			regards, tom lane

In response to

• pgsql: Optimize commit_siblings in two ways to improve group commit. at 2010-12-08 18:51:36 from Simon Riggs

Responses

• Re: [COMMITTERS] pgsql: Optimize commit_siblings in two ways to improve group commit. at 2010-12-08 19:25:57 from Robert Haas

pgsql-hackers by date

Next:	From: Kevin Grittner	Date: 2010-12-08 19:08:48
	Subject: Re: serializable read only deferrable
Previous:	From: Simon Riggs	Date: 2010-12-08 18:51:36
	Subject: pgsql: Optimize commit_siblings in two ways to improve group commit.

pgsql-committers by date

Next:	From: Robert Haas	Date: 2010-12-08 19:25:57
	Subject: Re: [COMMITTERS] pgsql: Optimize commit_siblings in two ways to improve group commit.
Previous:	From: Simon Riggs	Date: 2010-12-08 18:51:36
	Subject: pgsql: Optimize commit_siblings in two ways to improve group commit.