X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id DAF643A298E for ; Tue, 18 Jan 2005 22:03:51 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 76164-08 for ; Tue, 18 Jan 2005 22:03:47 +0000 (GMT) Received: from vscan02.westnet.com.au (vscan02.westnet.com.au [203.10.1.132]) by svr1.postgresql.org (Postfix) with ESMTP id B40483A29A4 for ; Tue, 18 Jan 2005 22:03:47 +0000 (GMT) Received: from localhost (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with ESMTP id 1DD79C727 for ; Wed, 19 Jan 2005 06:03:45 +0800 (WST) Received: from vscan02.westnet.com.au ([127.0.0.1]) by localhost (vscan02.westnet.com.au [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 15923-15 for ; Wed, 19 Jan 2005 06:03:45 +0800 (WST) Received: from mapping12 (dsl-202-173-155-79.vic.westnet.com.au [202.173.155.79]) by vscan02.westnet.com.au (Postfix) with ESMTP id 83426C153 for ; Wed, 19 Jan 2005 06:03:44 +0800 (WST) From: "Benjamin Wragg" To: Subject: Disk configuration Date: Wed, 19 Jan 2005 09:03:44 +1100 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0043_01C4FE05.C7780640" X-Mailer: Microsoft Office Outlook, Build 11.0.5510 thread-index: AcT9qZOEaKOHl7TYQE2pRyMpIuYWZw== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Message-Id: <20050118220344.83426C153@vscan02.westnet.com.au> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.192 tagged_above=0 required=5 tests=AWL, HTML_60_70, HTML_MESSAGE, HTML_TEXT_AFTER_BODY, HTML_TEXT_AFTER_HTML X-Spam-Level: X-Archive-Number: 200501/225 X-Sequence-Number: 9915 This is a multi-part message in MIME format. ------=_NextPart_000_0043_01C4FE05.C7780640 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: 7bit I just wanted to bounce off the list the best way to configure disks for a postgresql server. My gut feeling is as follows: Keep the OS and postgresql install on seperate disks to the postgresql /data directory? Is a single hard disk drive acceptable for the OS and postgresql program, or will this create a bottle neck? Would a multi disk array be more appropriate? Cheers, Benjamin Wragg -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: 17/01/2005 ------=_NextPart_000_0043_01C4FE05.C7780640 Content-Type: text/html; charset="windows-1250" Content-Transfer-Encoding: quoted-printable
I just = wanted to=20 bounce off the list the best way to configure disks for a postgresql = server.=20 My gut=20 feeling is as follows:
 
Keep = the OS and=20 postgresql install on seperate disks to the postgresql /data=20 directory?
Is a = single hard=20 disk drive acceptable for the OS and postgresql program, or will this = create a=20 bottle neck? Would a multi disk array be more = appropriate?
 
Cheers,
 
Benjamin=20 Wragg

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.7.0 - Release Date: = 17/01/2005

------=_NextPart_000_0043_01C4FE05.C7780640--