> > Many thanks Mark,
> >
> > I will consider fsync=off only to do an initial load, not for a
> database normal operation.
> >
>
> This approach works well. You just need to remember to shut down the
> database and start it back up again with fsync enabled for it to be safe
> after the initial load.
>
> > I was just thinking about this hipotetical scenario:
> > a) a restore database operation
> > b) fsync off
> > c) write-back on (IDE)
> >
> > As I could understand, in this sceneraio, it´s normal the IDE
> drive be faster than the SCSI, ok?
> >
>
> If fsync is off, then the IDE drive loses its big advantage, so IDE and
> SCSI should be about the same speed.
>
Sorry, I would like to say fsync on instead of fsync off. But I think I
understood.
With fsync off the performance should be almost the same (SCSI and IDE), and
with fsync on
the IDE will be faster, but data are exposed.
Thanks!
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
