Also for this time we do not have any problems with oracle servers (and we have had many power downs).
> (...stuff...) >
We found that ext3 is less stable comparing to reiserfs and we need to use fsck. We are using ~300 tables with ~3M rows (max) . Also we are using mostly dual pentium + IDE disks.
The problem is invalid shutdowns + IDE. You must turn off write caching at the IDE hard drive level to ensure proper data integrity with Postgres. Oracle gets away with it because it uses a double or triple redo log while Postgres just uses a single write-ahead log.
---------------------------(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
