Hi all,
I’m in the process of initiating a movement in our
company to move towards open source software use. As part of this movement I
will be recommending PostgreSQL as an alternative to
the currently used MSSQL. I’m going with PostgreSQL
over MySQL because of the much more complete f
Martin Foster <[EMAIL PROTECTED]> writes:
> As a side note, would you recommend disabling
> fsync for added performance?
Only if you are willing to sacrifice crash-safety in the name of speed.
regards, tom lane
---(end of broadcast)---
Tom Lane wrote:
force Postgres into using Indexes when available.So I changed the
following two lines in the .conf file:
enable_seqscan = false
enable_nestloop = false
>This was recommended in the documentation,
Where would you say that setting those off in the config file is
"recomm
Back in the day, we got good performance from similar sized tables
using VMS, a small VAX with only 256MB RAM and narrow SCSI 1GB disks.
The RDBMS was DEC's own Rdb/VMS. A "small" mainframe (6 MIPS, 8MB
RAM) also gave good performance.
So, this old curmudgeon asks, why such beefy h/w for such sm
Alexandre,
Since you want the fastest speed I would do the 2 data
disks in RAID 0 (striping) not RAID 1 (mirroring).
If you would care about not loosing any transactions
you would keep all 3 disks in RAID 5.
Don't know the answer to the Hyperthreading question.
Why don't you run a test to find
