| From: | Mark Lewis <mark(dot)lewis(at)mir3(dot)com> |
|---|---|
| To: | carlosreimer(at)terra(dot)com(dot)br |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: RES: RES: Initial database loading and IDE x SCSI |
| Date: | 2006-06-02 20:44:04 |
| Message-ID: | 1149281044.20798.116.camel@archimedes |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, 2006-06-02 at 17:37 -0300, carlosreimer(at)terra(dot)com(dot)br wrote:
> 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.
> Of course, the database is exposed because of the fsync=off, but if you consider only the system performance, then it is true. Isn´t it?
> Thanks,
>
> Reimer
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | carlosreimer | 2006-06-02 20:55:38 | RES: RES: RES: Initial database loading and IDE x SCSI |
| Previous Message | carlosreimer | 2006-06-02 20:37:01 | RES: RES: Initial database loading and IDE x SCSI |