Re: pg_test_fsync output and commit_delay - Mailing list pgsql-hackers

From Josh Berkus
Subject Re: pg_test_fsync output and commit_delay
Date
Msg-id 504BC655.6080402@agliodbs.com
Whole thread Raw
In response to pg_test_fsync output and commit_delay  (Peter Geoghegan <peter@2ndquadrant.com>)
List 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



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: pg_upgrade testing for MSVC
Next
From: Tom Lane
Date:
Subject: Supporting plpython 2+3 builds better