ndle disk?
In cases such as this, where an external storage array with a hardware
RAID controller is used, the normal advice to separate the data from the
pg_xlog seems to come unstuck, or are we missing something?
Cheers,
Paul Johnson.
---(end of broadcast)-
Hi all, we have the following setup:
- Sun V250 server
- 2*1.3GHz Sparc IIIi CPU
- 8GB RAM
- 8*73GB SCSI drives
- Solaris 10
- Postgres 8
Disks 0 and 1 are mirrored and contain the OS and the various software
packages, disks 2-7 are configured as a 320GB concatenation mounted on
/data, which is w
512
> set semsys:seminfo_semmsl=1000
> set semsys:seminfo_semmns=512
> * end of shared memory setting
> * Set the hme card to force 100 full duplex and not to autonegotiate
> * since hme does not play well with cisco
> *
> set hme:hme_adv_autoneg_cap=0
> set hme:hme_adv_100fdx_cap
Hi Josh, there are 8 internal disks - all are [EMAIL PROTECTED],000 RPM, fibre
connected.
The O/S is on 2 mirrored disks, the Postgres cluster is on the /data1
filesystem that is striped across the other 6 disks.
The shared_buffers value is a semi-educated guess based on having made 4GB
shared me
Hi all, we have an Sun E3500 running Solaris 9. It's got 6x336MHz CPU and
10GB RAM.
I would like to know what /etc/system and postgresql_conf values are
recommended to deliver as much system resource as possible to Postgres. We
use this Sun box solely for single user Postgres data warehousing
work
