> 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