Skip site navigation (1) Skip section navigation (2)

Re: [COMMITTERS] pgsql: Optimize commit_siblings in two ways to improve group commit.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Optimize commit_siblings in two ways to improve group commit.
Date: 2010-12-08 18:56:12
Message-ID: 18903.1291834572@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
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

Responses

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2010-12-08 19:08:48
Subject: Re: serializable read only deferrable
Previous:From: Simon RiggsDate: 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 HaasDate: 2010-12-08 19:25:57
Subject: Re: [COMMITTERS] pgsql: Optimize commit_siblings in two ways to improve group commit.
Previous:From: Simon RiggsDate: 2010-12-08 18:51:36
Subject: pgsql: Optimize commit_siblings in two ways to improve group commit.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group