Re: [ADMIN] Multiple disks

2004-04-19 Thread scott.marlowe
On Thu, 15 Apr 2004, Cris Carampa wrote: > scott.marlowe wrote: > > > The current king of putting postgresql on multiple platters and getting > > best overall performance is a battery backed caching raid controller run > > one or more many disk RAID-5 arrays. > > I thought the best choice were

Re: [ADMIN] Multiple disks

2004-04-19 Thread Cris Carampa
scott.marlowe wrote: The current king of putting postgresql on multiple platters and getting best overall performance is a battery backed caching raid controller run one or more many disk RAID-5 arrays. I thought the best choice were RAID-10 (1+0) (when available). There isn't a write penalty w

Re: [ADMIN] Multiple disks

2004-04-09 Thread Tom Lane
"scott.marlowe" <[EMAIL PROTECTED]> writes: > The next way is to individually link thinks like indexes onto other > volumes. The procedure is basically, create the index, figure out which > file in $PGDATA/base/oidofyourdbhere is the index, shut down postgresql, > copy to file elsewhere, softli

Re: [ADMIN] Multiple disks

2004-04-09 Thread scott.marlowe
On Thu, 8 Apr 2004, hal wrote: > What is the best/simplest way to split: > a database > multiple databases > a table > multiple tables > across more than one disk drive? > > I know that this has come up before but I can't find > any info. A pointer to a HOWTO or other inf

Re: [ADMIN] Multiple disks

2004-04-08 Thread Tom Lane
hal <[EMAIL PROTECTED]> writes: > What is the best/simplest way to split: > ... > across more than one disk drive? LVM or RAID solutions should do the job. regards, tom lane ---(end of broadcast)--- TIP 2: you can get off al