X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id B2C8ED1D1CD for ; Tue, 17 Feb 2004 17:35:42 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 62595-02 for ; Tue, 17 Feb 2004 13:35:41 -0400 (AST) Received: from mail.osdl.org (fw.osdl.org [65.172.181.6]) by svr1.postgresql.org (Postfix) with ESMTP id 47BE8D1CAF3 for ; Tue, 17 Feb 2004 13:35:40 -0400 (AST) Received: from fire-1.osdl.org (air1.pdx.osdl.net [172.20.0.5]) by mail.osdl.org (8.11.6/8.11.6) with ESMTP id i1HHZcE10517; Tue, 17 Feb 2004 09:35:38 -0800 From: Craig Thomas Received: from osdl.org (fire.osdl.org [65.172.181.4]) by fire-1.osdl.org (8.12.8/8.12.8) with SMTP id i1HHZbrK005014; Tue, 17 Feb 2004 09:35:37 -0800 Received: from 4.5.9.170 (SquirrelMail authenticated user craiger) by www.osdl.org with HTTP; Tue, 17 Feb 2004 09:35:38 -0800 (PST) Message-ID: <64789.4.5.9.170.1077039338.squirrel@www.osdl.org> Date: Tue, 17 Feb 2004 09:35:38 -0800 (PST) Subject: Re: Tables on multiple disk drives To: In-Reply-To: References: <1379274019.20040217155454@tokar.ru> X-Priority: 3 Importance: Normal Cc: , X-Mailer: SquirrelMail (version 1.2.11) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-MIMEDefang-Filter: osdl$Revision: 1.48 $ X-Scanned-By: MIMEDefang 2.36 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/191 X-Sequence-Number: 5715 > On Tue, 17 Feb 2004, Konstantin Tokar wrote: > >> Hi! >> Does PostgreSQL allow to create tables and indices of a single >> database on multiple disk drives with a purpose of increase >> performance as Oracle database does? If a symbolic reference is the >> only method then the next question is: how can it be determined what >> file is referred to what table and index? > > You're life will be simpler, and your setup will be faster without > having to muck about with it, if you just buy a good RAID controller > with battery backed cache. LSI/Megaraid and Adaptec both make > serviceable controllers for reasonable prices, and as you add drives, > the speed just goes up, no muddling around with sym links. This works to a limited extent. For very large databases, maximum throughput of I/O is the paramount factor for database performance. With raid controllers, your LUN is still limited to a small number of disks. PostgreSQL can only write on a file system, but Oracle, SAP DB, DB2, etc can write directly to disk (raw I/O). With large databases it is advantageous to spread a table across 100's of disks, if the table is quite large. I don't know of any manufacturer that creates a 100 disk raid array yet. Some of the problem can be addressed by using a volume manager (such as LVM in Linux, or Veritas on Unix-like systems). This allows one to create a volume using partitions from many disks. One can then create a file system and mount it on the volume. However, to get the best performance, Raw I/O capability is the best way to go. > > > ---------------------------(end of broadcast)--------------------------- > TIP 3: if posting/reading through Usenet, please send an appropriate > subscribe-nomail command to majordomo@postgresql.org so that your > message can get through to the mailing list cleanly