From: Benjamin Arai <barai@cs.ucr.edu>
To: pgsql-performance@postgresql.org
Subject: Ensuring data integrity with fsync=off
Date: Sat, 14 Jan 2006 10:13:27 -0800
Message-ID: <000601c61936$38548770$fa48fd0a@uni> (raw)
I have been working on optimizing a PostgreSQL server for weekly updates
where data is only updated once a week then for the remaining portion of the
week the data is static. So far I have set fsync to off and increased the
segment size among other things. I need to ensure that at the end of the
update each week the data is in state where a crash will not kill the
database.
Right now I run "sync" afte the updates have finished to ensure that the
data is synced to disk but I am concerned about the segment data and
anything else I am missing that PostgreSQL explicitly handles. Is there
something I can do in addition to sync to tell PostgreSQL exlplicitly that
it is time to ensure everything is stored in its final destionation and etc?
Benjamin
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: barai@cs.ucr.edu
Subject: Re: Ensuring data integrity with fsync=off
In-Reply-To: <000601c61936$38548770$fa48fd0a@uni>
* 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