From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: Dusek, Bob <rd185032@ncr.com>
Cc: Bob Dusek <redusek@gmail.com>
Cc: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: performance config help
Date: Mon, 11 Jan 2010 15:25:57 -0500
Message-ID: <18927.1263241557@sss.pgh.pa.us> (raw)
In-Reply-To: <dcc563d11001111216v34a71959jb32020ecf0071fc7@mail.gmail.com>
References: <dcc563d11001111145t63023051i6f72f495719c0f53@mail.gmail.com>
<6EB5F166D3FA6B499A1A25856BDB9B6085F4A309@susday216.corp.ncr.com>
<dcc563d11001111216v34a71959jb32020ecf0071fc7@mail.gmail.com>
Scott Marlowe <scott.marlowe@gmail.com> writes:
> On Mon, Jan 11, 2010 at 1:13 PM, Dusek, Bob <rd185032@ncr.com> wrote:
>> I haven't been involved in any benchmarking of PG8 with fsync=off, but we certainly did it with PG 7.4. fsync=0ff, for our purposes, was MUCH faster.
> And many changes have been made since then to make fsyncing much
> faster. You may be grinding the valves on a 2009 Ferrari because
> pappy used to have to do it on his 1958 pickup truck here.
Perhaps more to the point, synchronous_commit can get most of the same
speedup with much less risk to your database. You really owe it to
yourself to redo that benchmarking with a recent PG release.
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, scott.marlowe@gmail.com, rd185032@ncr.com, redusek@gmail.com, Kevin.Grittner@wicourts.gov
Subject: Re: performance config help
In-Reply-To: <18927.1263241557@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox