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 DFF1ED1B53A for ; Tue, 12 Aug 2003 20:10:49 +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 07041-08 for ; Tue, 12 Aug 2003 17:09:17 -0300 (ADT) Received: from davinci.ethosmedia.com (unknown [209.128.84.228]) by svr1.postgresql.org (Postfix) with ESMTP id D9B88D1C4D5 for ; Tue, 12 Aug 2003 17:10:38 -0300 (ADT) Received: from [63.195.55.98] (HELO spooky) by davinci.ethosmedia.com (CommuniGate Pro SMTP 4.0.2) with ESMTP id 3506609; Tue, 12 Aug 2003 13:11:03 -0700 Content-Type: text/plain; charset="windows-1252" From: Josh Berkus Organization: Aglio Database Solutions To: "Gregory S. Williamson" , "Bill Moran" Subject: Re: Filesystems WAS: Perfomance Tuning Date: Tue, 12 Aug 2003 13:09:42 -0700 User-Agent: KMail/1.4.3 Cc: "PgSQL Performance ML" References: <71E37EF6B7DCC1499CEA0316A25683280105705B@loki.globexplorer.com> In-Reply-To: <71E37EF6B7DCC1499CEA0316A25683280105705B@loki.globexplorer.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <200308121309.42169.josh@agliodbs.com> X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/219 X-Sequence-Number: 3036 Greg, > FWIW, Informix can be run using a "cooked" (Unix) file for storing data or > it uses "raw" disk space and bypasses the ordinary (high level) UNIX > controllers and does its own reads/writes. About 10 times faster and safer. > Of course, itmay have taken a lot of programmer time to make that solid. > But the performance gains are significant. Yes, but it's still slower than PostgreSQL on medium-end hardware. ;-) 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: 1) It would interfere with our cross-platform compatibility. PostgreSQL runs on something like 20 OSes. 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". 3) Development of our "own" filesystem would then require PostgreSQL to create and maintain a whole hardware compatibility library, and troubleshoot problems on exotic hardware and wierd RAID configurations. 4) A database FS also often causes side-effect problems; for example, one cannot move or copy a SQL Server partition without destroying it. Of course, that could all change if some corp with deep pockets steps in an decides to create a "postgresFS" and funds and staffs the effort 100%. But it's unlikely to be a priority for the existing development team any time in the forseeable future. -- Josh Berkus Aglio Database Solutions San Francisco