Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Right now with fsync off you can get transactions partially commited in your
> database, which is a serious problem (think moving money from one account to
> another).
It's worse than that. You can get a totally corrupted database. Things like
duplicated records (the before and after image of an update). Or indexes that
are out of sync with the table. This can cause strange inconsistent results
depending on the plan queries use, or outright database crashes.
--
greg
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
