From: Greg Smith <gsmith@gregsmith.com>
To: PostgreSQL-patches <pgsql-patches@postgresql.org>
Subject: Re: Maintaining cluster order on insert
Date: Tue, 10 Jul 2007 11:25:30 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0707101045240.2388@westnet.com> (raw)
In-Reply-To: <19371.1184078079@sss.pgh.pa.us>
References: <200705152223.l4FMNJa17969@momjian.us>
<464A33AB.1050401@enterprisedb.com>
<20070516003810.GI20707@nasby.net>
<464B15EF.4000808@enterprisedb.com>
<c2d9e70e0705172153g3207adb6kd4abdfdf3a9215ff@mail.gmail.com>
<464D96D6.1030608@enterprisedb.com>
<457.1184023772@sss.pgh.pa.us>
<Pine.GSO.4.64.0707100815400.22343@westnet.com>
<19371.1184078079@sss.pgh.pa.us>
On Tue, 10 Jul 2007, Tom Lane wrote:
> It's just desktop-grade junk :-(. Feel free to repeat the test on
> something more serious.
Right, but even such junk can be setup such that the disks honor commits,
just wanted to confirm you didn't go out of your way to do that--sounds
like you didn't. My mini-lab at home has two PG test systems, one with a
real write cache, the other has an IDE drive with the cache turned off so
commits actually wait to hit the platter. The painful slowness of writes
in that situation keeps me grounded as to how much data integrity actually
costs if you're not accelerating it, and the differences in benchmarks
between the two systems (which are otherwise a similar class of hardware)
can be informative.
> Anyway the numbers seemed relatively consistent after the setup and
> first test cycle, so I think the part I was actually trying to draw
> conclusions from was probably real enough.
Agreed, just figuring out the test ramp-up situation, and your explanation
for that quirk sounds reasonable.
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
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-hackers@postgresql.org
Cc: gsmith@gregsmith.com, pgsql-patches@postgresql.org
Subject: Re: Maintaining cluster order on insert
In-Reply-To: <Pine.GSO.4.64.0707101045240.2388@westnet.com>
* 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