Re: pg_test_fsync output and commit_delay

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_test_fsync output and commit_delay
Date: 2012-09-08 22:27:33
Message-ID: 504BC655.6080402@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> The attached simple patch alters the output produced by pg_test_fsync,
> so that we also see the average sync time per op.

Good idea. A median would be even better, but harder to calculate, I
imagine. You might consider providing a maximum, too.

> The pg_test_fsync
> docs have had minor alterations too. Hopefully, another doc patch will
> follow that builds upon this, and actually firmly recommends taking a
> particular course of action when setting commit_delay - my previous
> observations about what helped throughput, though supported by Greg
> Smith, have not been scrutinised enough just yet, I feel. For now, the
> equivocated wording of my doc alterations (that raw wal_sync_method
> file sync time might *somehow* be useful here) seems appropriate.

I'll see what I can do.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-09-08 23:18:43 Supporting plpython 2+3 builds better
Previous Message Andrew Dunstan 2012-09-08 21:31:02 pg_upgrade testing for MSVC