Horton
Menu

Re: Re: Doc patch making firm recommendation for setting the value of commit_delay

Peter Geoghegan <peter.geoghegan86@gmail.com>

View thread
From: Peter Geoghegan <peter.geoghegan86@gmail.com>
To: Noah Misch <noah@leadboat.com>
Cc: PG Hackers <pgsql-hackers@postgresql.org>
Date: 2013-01-28T04:48:56Z
Lists: pgsql-hackers 
On 28 January 2013 03:34, Noah Misch <noah@leadboat.com> wrote:
> Would you commit to the same git repository the pgbench-tools data for the
> graphs appearing in that blog post?  I couldn't readily tell what was
> happening below 16 clients due to the graphed data points blending together.

I'm afraid that I no longer have that data. Of course, I could fairly
easily recreate it, but I don't think I'll have time tomorrow. Is it
important? Are you interested in both the insert and tpc-b cases?

-- 
Regards,
Peter Geoghegan

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add microsecs/op display to pg_test_fsync utility