From: Tom Lane <tgl@sss.pgh.pa.us>
To: CH <share-postgres@think42.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: filesystem option tuning
Date: Fri, 04 Jun 2004 11:33:29 -0400
Message-ID: <27974.1086363209@sss.pgh.pa.us> (raw)
In-Reply-To: <20040604162111.A5057@p15097255.pureserver.info>
References: <20040604162111.A5057@p15097255.pureserver.info>
CH <share-postgres@think42.com> writes:
> So the clog is not written to every time the xlog is written to?
No. One clog page holds 32000 transactions' worth of transaction status
values, so on average we need only one clog page write per 32000
transactions.
> On a related issue, what's the connection between the "fsync" and the
> "wal_sync_method" configuration switches?
fsync is the master circuit breaker: turn it off, there is no power at
the wal_sync_method socket ;-). We stop doing anything special about
enforcing write ordering for any files, but just assume that the kernel
+ hardware can be trusted not to lose data they've been given.
With fsync on, wal_sync_method means something.
fsync on also enables fsync/sync for the data files at checkpoint
times. We don't need to force writes for those between checkpoints,
so wal_sync_method doesn't apply to data files (nor clog).
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, share-postgres@think42.com
Subject: Re: filesystem option tuning
In-Reply-To: <27974.1086363209@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