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

Re: [HACKERS] COMMIT NOWAIT Performance Option (patch)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] COMMIT NOWAIT Performance Option (patch)
Date: 2007-02-27 04:07:10
Message-ID: 10522.1172549230@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> On Mon, 2007-02-26 at 18:14 -0500, Tom Lane wrote:
>> What does this accomplish other than adding syntactic sugar over a
>> feature that really doesn't work well anyway?

> This patch doesn't intend to implement group commit. I've changed the
> meaning of commit_delay, sorry if that confuses.

Ah.  The patch was pretty much unintelligible without the discussion
(which got here considerably later :-().  I've still got misgivings
about how safe it really is, but at least this is better than what
commit_delay wishes it could do.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2007-02-27 04:14:01
Subject: Re: Expanding DELETE/UPDATE returning
Previous:From: Jeroen T. VermeulenDate: 2007-02-27 04:05:45
Subject: Re: COMMIT NOWAIT Performance Option

pgsql-patches by date

Next:From: Chris MarcellinoDate: 2007-02-27 05:00:09
Subject: POSIX shared memory support
Previous:From: John BartlettDate: 2007-02-27 03:23:17
Subject:

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