From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Neil Conway <neilc@samurai.com>
Cc: Magnus Hagander <mha@sollentuna.net>
Cc: Vig, Sandor (G/FI-2) <Sandor.Vig@audi.hu>
Cc: pgsql-performance@postgresql.org
Subject: Re: PostgreSQL is extremely slow on Windows
Date: Thu, 24 Feb 2005 16:25:34 -0500 (EST)
Message-ID: <200502242125.j1OLPYF14343@candle.pha.pa.us> (raw)
In-Reply-To: <421D0543.6020308@samurai.com>
Neil Conway wrote:
> Magnus Hagander wrote:
> > Yes, fsync=false is very good for bulk loading *IFF* you can live with
> > data loss in case you get a crash during load.
>
> It's not merely data loss -- you could encounter potentially
> unrecoverable database corruption.
>
> There is a TODO item about allowing the delaying of WAL writes. If we
> maintain the WAL invariant (that is, a WAL record describing a change
> must hit disk before the change itself does) but simply don't flush the
> WAL at transaction commit, we should be able to get better performance
> without the risk of database corruption (so we would need to keep pages
> modified by the committed transaction pinned in memory until the WAL has
> been flushed, which might be done on a periodic basis).
>
> Naturally, there is a risk of losing data in the period between
> transaction commit and syncing the WAL, but no risk of database
> corruption. This seems a reasonable approach to providing better
> performance for people who don't need the strict guarantees provided by
> fsync=true.
Right. Just for clarity, you might lose the last 5 seconds of
transactions, but all transactsions would be completely committed or
aborted in your datbase. Right now with fsync off you can get
transactions partially commited in your database, which is a serious
problem (think moving money from one account to another).
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
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: pgman@candle.pha.pa.us, neilc@samurai.com, mha@sollentuna.net, Sandor.Vig@audi.hu
Subject: Re: PostgreSQL is extremely slow on Windows
In-Reply-To: <200502242125.j1OLPYF14343@candle.pha.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