X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org
Received: from localhost (av.hub.org [200.46.204.144])
	by postgresql.org (Postfix) with ESMTP id D89939DCA38
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Sat, 14 Jan 2006 14:13:41 -0400 (AST)
Received: from postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 17226-08
	for <pgsql-performance-postgresql.org@localhost.postgresql.org>;
	Sat, 14 Jan 2006 14:13:41 -0400 (AST)
Received: from svr4.postgresql.org (svr4.postgresql.org [66.98.251.159])
	by postgresql.org (Postfix) with ESMTP id 71A269DC9FA
	for <pgsql-performance@postgresql.org>;
	Sat, 14 Jan 2006 14:13:39 -0400 (AST)
Received: from mailrelay.t-mobile.com (m6f095e42.tmodns.net [66.94.9.111])
	by svr4.postgresql.org (Postfix) with ESMTP id 1976A5AF0BA
	for <pgsql-performance@postgresql.org>;
	Sat, 14 Jan 2006 18:13:40 +0000 (GMT)
Received: from localhost (localhost [127.0.0.1])
	by mailrelay.t-mobile.com (Postfix) with ESMTP id 8AF2499DF
	for <pgsql-performance@postgresql.org>;
	Sat, 14 Jan 2006 10:13:35 -0800 (PST)
Received: from mailrelay.t-mobile.com ([127.0.0.1])
	by localhost (mailrelay.t-mobile.com [127.0.0.1]) (amavisd-new,
	port 10024)
	with ESMTP id 01237-06 for <pgsql-performance@postgresql.org>;
	Sat, 14 Jan 2006 10:13:34 -0800 (PST)
Received: from uni (250.72.253.10.in-addr.arpa [10.253.72.250])
	by mailrelay.t-mobile.com (Postfix) with ESMTP
	for <pgsql-performance@postgresql.org>;
	Sat, 14 Jan 2006 10:13:34 -0800 (PST)
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>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0007_01C618F3.2A314770"
X-Mailer: Microsoft Office Outlook 11
Thread-Index: AcYZNjdPT1qBlKsyRba3b2Qw0tKXbA==
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2670
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, score=1.333 required=5 tests=[HTML_MESSAGE=0.001,
	RCVD_IN_BL_SPAMCOP_NET=1.332]
X-Spam-Score: 1.333
X-Spam-Level: *
X-Archive-Number: 200601/188
X-Sequence-Number: 16666

This is a multi-part message in MIME format.

------=_NextPart_000_0007_01C618F3.2A314770
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

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

------=_NextPart_000_0007_01C618F3.2A314770
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR></HEAD>
<BODY>
<DIV><SPAN class=3D361280818-14012006><FONT face=3DArial size=3D2>I have =
been working=20
on optimizing a PostgreSQL server for weekly updates where data is only =
updated=20
once a week then for the remaining portion of the week the data is =
static.&nbsp;=20
So far I have set fsync to off and increased the segment size among =
other=20
things.&nbsp; I need to ensure that at the end of the update each =
week&nbsp;the=20
data&nbsp;is in&nbsp;state where a crash will not kill the =
database.&nbsp;=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D361280818-14012006><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D361280818-14012006><FONT face=3DArial size=3D2>Right =
now I run=20
"sync" afte the updates have&nbsp;finished to ensure that the data is =
synced to=20
disk but I am concerned about the segment data and anything else I am =
missing=20
that PostgreSQL explicitly handles.&nbsp; Is there something I can do in =

addition to sync to tell PostgreSQL exlplicitly that it is time to =
ensure=20
everything is stored in its final destionation and =
etc?</FONT></SPAN></DIV>
<DIV><SPAN class=3D361280818-14012006><FONT face=3DArial=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D361280818-14012006><FONT face=3DArial=20
size=3D2>Benjamin</FONT></SPAN></DIV></BODY></HTML>

------=_NextPart_000_0007_01C618F3.2A314770--