pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Craig Thomas <craiger@osdl.org>
To: scott.marlowe@ihs.com
Cc: lists2@tokar.ru
Cc: pgsql-performance@postgresql.org
Subject: Re: Tables on multiple disk drives
Date: Tue, 17 Feb 2004 09:35:38 -0800 (PST)
Message-ID: <64789.4.5.9.170.1077039338.squirrel@www.osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.33.0402171017170.30606-100000@css120.ihs.com>
References: <1379274019.20040217155454@tokar.ru>
	<Pine.LNX.4.33.0402171017170.30606-100000@css120.ihs.com>

> 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






view thread (9+ messages)  latest in thread

Message-ID: <64789.4.5.9.170.1077039338.squirrel@www.osdl.org>
Permalink:  ../64789.4.5.9.170.1077039338.squirrel@www.osdl.org/
Also on:    postgresql.org/message-id/64789.4.5.9.170.1077039338.squirrel@www.osdl.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: craiger@osdl.org, scott.marlowe@ihs.com, lists2@tokar.ru
  Subject: Re: Tables on multiple disk drives
  In-Reply-To: <64789.4.5.9.170.1077039338.squirrel@www.osdl.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox