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

Re: CommitDelay performance improvement

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: CommitDelay performance improvement
Date: 2001-02-26 00:55:10
Message-ID: 22140.983148910@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
>> I could find the sciript but seem to have missed your change
>> about commit_siblings. Where could I get it ?

> Er ... duh ... I didn't commit it yet.  Well, it's harmless enough
> as long as commit_delay defaults to 0, so I'll go ahead and commit.

In CVS now.

However, it might be well to wait to run tests until we tweak pgbench
to measure the average elapsed time for a transaction.  As you pointed
out earlier today, overall TPS is not the only figure of merit we need
to worry about.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Lincoln YeohDate: 2001-02-26 01:26:47
Subject: Re: Re: offset and limit in update and subselect
Previous:From: Tom LaneDate: 2001-02-26 00:35:47
Subject: Re: CommitDelay performance improvement

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