pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Gregory S. Williamson <gsw@globexplorer.com>
To: Bill Moran <wmoran@potentialtech.com>
Cc: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: Filesystems WAS: Perfomance Tuning
Date: Tue, 12 Aug 2003 13:09:42 -0700
Message-ID: <200308121309.42169.josh@agliodbs.com> (raw)
In-Reply-To: <71E37EF6B7DCC1499CEA0316A25683280105705B@loki.globexplorer.com>
References: <71E37EF6B7DCC1499CEA0316A25683280105705B@loki.globexplorer.com>

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



view thread (8+ messages)  latest in thread

Message-ID: <200308121309.42169.josh@agliodbs.com>
Permalink:  ../200308121309.42169.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200308121309.42169.josh@agliodbs.com

 · 

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: josh@agliodbs.com, gsw@globexplorer.com, wmoran@potentialtech.com
  Subject: Re: Filesystems WAS: Perfomance Tuning
  In-Reply-To: <200308121309.42169.josh@agliodbs.com>
  References: <71E37EF6B7DCC1499CEA0316A25683280105705B@loki.globexplorer.com> <200308121309.42169.josh@agliodbs.com>

* 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