X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id EF29ED1C4B8 for ; Tue, 12 Aug 2003 20:32:42 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 07855-08 for ; Tue, 12 Aug 2003 17:31:10 -0300 (ADT) Received: from krusty-motorsports.com (krusty-motorsports.com [192.94.170.8]) by svr1.postgresql.org (Postfix) with ESMTP id 147C2D1C4CA for ; Tue, 12 Aug 2003 17:32:32 -0300 (ADT) Received: from [24.194.112.77] (helo=skipper.averillpark.net) by krusty-motorsports.com with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.14) id 19mfon-0007Zf-Rx for pgsql-performance@postgresql.org; Tue, 12 Aug 2003 20:32:33 +0000 Received: from rwelty by skipper.averillpark.net with local (Exim 4.14) id 19mfnc-0007W1-8n for pgsql-performance@postgresql.org; Tue, 12 Aug 2003 16:31:20 -0400 Date: Tue, 12 Aug 2003 16:31:19 -0400 (EDT) From: Richard Welty Subject: Re: Filesystems WAS: Perfomance Tuning To: PgSQL Performance ML MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE References: <71E37EF6B7DCC1499CEA0316A25683280105705B@loki.globexplorer.com> <200308121309.42169.josh@agliodbs.com> In-Reply-To: <200308121309.42169.josh@agliodbs.com> X-Mailer: Mahogany 0.64 'Sparc', compiled for Linux 2.4.9-13 i686 Message-Id: X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/220 X-Sequence-Number: 3037 On Tue, 12 Aug 2003 13:09:42 -0700 Josh Berkus wrote: > This idea has been discussed numerous times on the HACKERS list, and is > a > (pretty much) closed issue. While Oracle and SQL Server use their own > filesystems, PostgreSQL will not because: ... > 2) The filesystem projects out there are (mostly) well-staffed and are > constantly advancing using specialized technology and theory. There's > no way > that the PostgreSQL team can do a better job in our "spare time". i consider this a fair answer, but i have a slightly different question to ask, inspired by my discussions with a good friend who is a top notch Informix DBA. there are advantages to being able to split the database across a slew of disk drives. if we accept the notion of using the native OS filesystem on each, it would seem that being able to direct various tables and indices to specific drives might be a valuble capability. i know that i could go into /var/lib/pgsql/data/base and fan the contents out, but this is unweildy and impractical. has any consideration been given to providing a way to manage such a deployment? or is it the judgement of the hackers community that a monsterous raid-10 array offers comparable performance? i forget how large the data store on my friend's current project is, but i'll check. knowing the size and transaction rate he's dealing with might put a finer point on this discussion. richard -- Richard Welty rwelty@averillpark.net Averill Park Networking 518-573-7592 Java, PHP, PostgreSQL, Unix, Linux, IP Network Engineering, Security