From: Tom Lane <tgl@sss.pgh.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: Wed, 23 Feb 2005 17:56:41 -0500
Message-ID: <23063.1109199401@sss.pgh.pa.us> (raw)
In-Reply-To: <421D0543.6020308@samurai.com>
References: <6BCB9D8A16AC4241919521715F4D8BCE47697A@algol.sollentuna.se>
<421D0543.6020308@samurai.com>
Neil Conway <neilc@samurai.com> writes:
> 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).
That interlock already exists, in the form of the bufmgr LSN logic.
I think this "feature" might be as simple as
XLogFlush(recptr);
becomes
/* Must flush if we are deleting files... */
if (PerCommitFlush || nrels > 0)
XLogFlush(recptr);
in RecordTransactionCommit.
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, neilc@samurai.com, mha@sollentuna.net, Sandor.Vig@audi.hu
Subject: Re: PostgreSQL is extremely slow on Windows
In-Reply-To: <23063.1109199401@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