Hi,
We've a fedora core 3 box with PostgreSQL 8.0.
There is some performance problems with the server and I discovered with vmstat tool that there is some process writing a lot of information in the disk subsystem.
I stopped the database and even so vmstat showed the same rates of disk write
> > 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
Many thanks Mark,
I will consider fsync=off only to do an initial load, not for a database normal
operation.
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 dr
> <[EMAIL PROTECTED]> writes:
> > I would like to know if my supposition is right.
>
> > Considering an environment with only one hard disk attached to
> a server, an
> > initial loading of the database probably is much faster using an IDE/ATA
> > interface with write-back on than using an SCSI int
Hi,
I would like to know if my supposition is right.
Considering an environment with only one hard disk attached to a server, an
initial loading of the database probably is much faster using an IDE/ATA
interface with write-back on than using an SCSI interface. That´s because of
the SCSI command i
