From: | <carlosreimer(at)terra(dot)com(dot)br> |
---|---|
To: | "Mark Lewis" <mark(dot)lewis(at)mir3(dot)com> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | RES: RES: RES: Initial database loading and IDE x SCSI |
Date: | 2006-06-02 20:55:38 |
Message-ID: | PEEPKDFEHHEMKBBFPOOKKEHJCPAA.carlosreimer@terra.com.br |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
> > 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!
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Kirkwood | 2006-06-03 00:13:27 | Re: RES: Initial database loading and IDE x SCSI |
Previous Message | Mark Lewis | 2006-06-02 20:44:04 | Re: RES: RES: Initial database loading and IDE x SCSI |