Horton
Menu

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

Peter Geoghegan <peter@2ndquadrant.com>

View thread
From: Peter Geoghegan <peter@2ndquadrant.com>
To: Noah Misch <noah@leadboat.com>
Cc: PG Hackers <pgsql-hackers@postgresql.org>, Greg Smith <greg@2ndquadrant.com>
Date: 2013-01-21T14:33:52Z
Lists: pgsql-hackers 
On 21 January 2013 13:10, Noah Misch <noah@leadboat.com> wrote:
> What filesystem did you use for testing?  Would you also provide /proc/cpuinfo
> or a rough description of the system's CPUs?

Unfortunately, I don't have access to that server at the moment. It's
under Greg Smith's control. I believe you yourself had an account on
this server at one point. I do know that the CPU is an Intel Core
i7-870:

http://ark.intel.com/products/41315/Intel-Core-i7-870-Processor-8M-Cache-2_93-GHz

I am pretty sure that the filesystem that the various block devices
were mounted with was ext4 (without LVM), but it might have been XFS.
I don't recall. The operating system was Debian Lenny.

-- 
Peter Geoghegan       http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training and Services

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