Re: Dangers of fsync = off

From: Scott Ribe <scott_ribe(at)killerbytes(dot)com>
To: Postgres general mailing list <pgsql-general(at)postgresql(dot)org>
Subject: Re: Dangers of fsync = off
Date: 2007-05-09 14:26:52
Message-ID: C267364C.73635%scott_ribe@killerbytes.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> I still wouldn't trust Slony with fsync off. Another scenario would be
> the Slony trigger writes a change to the Slony DB, the db crashes before
> it gets committed to disk. When the DB is started, no errors prevent
> startup, but that transaction is lost.

I'm not sure, but I think the questioner was proposing a policy of "if it
crashes, we go to the standby, no attempt at recovery, ever", and I think
that would be safe.

And, personally, given my experience with pg, I think that's reasonable.
Because the day I see pg crash I'm going to assume I have a hardware problem
;-)

--
Scott Ribe
scott_ribe(at)killerbytes(dot)com
http://www.killerbytes.com/
(303) 722-0567 voice

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2007-05-09 14:39:25 Re: are foreign keys realized as indexes?
Previous Message Merlin Moncure 2007-05-09 14:16:40 Re: Views- Advantages and Disadvantages