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

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

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [COMMITTERS] pgsql: Optimize commit_siblings in two ways to improve group commit.
Date: 2010-12-08 19:35:05
Message-ID: AANLkTik=ANVc4Na1QxmpmT2KJ+pAoqXp9piR-WjUa6Cg@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
On Wed, Dec 8, 2010 at 2:31 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> 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?
>
> http://archives.postgresql.org/pgsql-performance/2010-12/msg00073.php
>
> Possibly it should have been posted to -hackers instead, but surely you
> read -performance?

Oh, yeah I see it now.  I do read -performance, but with two orders of
magnitude more latency than -hackers.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

pgsql-hackers by date

Next:From: Kevin GrittnerDate: 2010-12-08 19:39:15
Subject: Re: serializable read only deferrable
Previous:From: Tom LaneDate: 2010-12-08 19:31:03
Subject: Re: [COMMITTERS] pgsql: Optimize commit_siblings in two ways to improve group commit.

pgsql-committers by date

Next:From: Greg SmithDate: 2010-12-08 20:58:25
Subject: Re: [COMMITTERS] pgsql: Optimize commit_siblings in two ways to improve group commit.
Previous:From: Tom LaneDate: 2010-12-08 19:31:03
Subject: Re: [COMMITTERS] pgsql: Optimize commit_siblings in two ways to improve group commit.

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