From: William Yu <wyu@talisys.com>
To: pgsql-performance@postgresql.org
Subject: Re: Update on putting WAL on ramdisk/
Date: Fri, 12 Dec 2003 14:45:31 -0800
Message-ID: <brdge4$2u4v$1@news.hub.org> (raw)
In-Reply-To: <MKEGJINFADFODDNOKEJCIEEFEMAA.rg@tcslon.com>
References: <brddsj$19pn$1@news.hub.org>
<MKEGJINFADFODDNOKEJCIEEFEMAA.rg@tcslon.com>
Russell Garrett wrote:
>>WAL on single drive: 7.990 rec/s
>>WAL on 2nd IDE drive: 8.329 rec/s
>>WAL on tmpfs: 13.172 rec/s
>>
>>A huge jump in performance but a bit scary having a WAL that can
>>disappear at any time. I'm gonna workup a rsync script and do some
>>power-off experiments to see how badly it gets mangled.
>
>
> Surely this is just equivalent to disabling fsync? If you put a WAL on a
> volatile file system, there's not a whole lot of point in having one at all.
These tests were all with fsync off.
And no, it's not equivalent to fsync off since the WAL is always written
immediately regardless of fsync setting.
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: wyu@talisys.com
Subject: Re: Update on putting WAL on ramdisk/
In-Reply-To: <brdge4$2u4v$1@news.hub.org>
* 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