pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Christopher Browne <cbbrowne@acm.org>
To: pgsql-admin@postgresql.org
Subject: Re: Raw devices vs. Filesystems
Date: Mon, 29 Mar 2004 13:28:47 -0500
Message-ID: <m3oeqf4ie8.fsf@wolfe.cbbrowne.com> (raw)
References: <BAY8-F1017z7ahbwlpd00012a78@hotmail.com>

After takin a swig o' Arrakan spice grog, el_vigia_ec@hotmail.com ("Jaime Casanova") belched out:
> Can you tell me (or at least guide me to a palce where i can find the
> answer) what are the benefits of filesystems over raw devices?

For PostgreSQL, filesystems have the merit that you can actually use
them.  PostgreSQL doesn't support use of "raw devices."

Two major benefits of using filesystems as opposed to raw devices are
that:

a) The use of raw devices is dramatically non-portable; you have to
   reimplement data access on every platform you are trying to
   support; 

b) The use of raw devices essentially mandates that you implement
   some form of generic filesystem on top of them, which adds
   considerable complexity to your code.

Two benefits to raw devices are claimed...

c) It's faster.  But that assumes that the "cooked" filesystems are
   implemented fairly badly.  That was typically true, a dozen
   years ago, but it isn't so typical now, particularly with a
   fancy cacheing controller.

d) It guarantees application control of update ordering.  Of course,
   with a cacheing controller, or disk drives that lie to one degree
   or another, those guarantees might be gone anyways.

There are other filesystem advantages, such as

e) Shifting "cooked" data around may be as simple as a "mv," whereas
   reorganizing on raw disk requires DB-specific tools...

> And what filesystem is the best for postgresql performance?

That would depend, assortedly, on what OS you are using, what kind of
hardware you are running on, what kind of usage patterns you have, as
well as on how you define the notion of "best."

Absent of any indication of any of those things, the best that can be
said is "that depends..."
-- 
(format nil "~S@~S" "cbbrowne" "acm.org")
http://cbbrowne.com/info/languages.html
TTY Message from The-XGP at MIT-AI:
The-XGP@AI 02/59/69 02:59:69
Your XGP output is startling.



view thread (17+ messages)  latest in thread

Message-ID: <m3oeqf4ie8.fsf@wolfe.cbbrowne.com>
Permalink:  ../m3oeqf4ie8.fsf@wolfe.cbbrowne.com/
Also on:    postgresql.org/message-id/m3oeqf4ie8.fsf@wolfe.cbbrowne.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-admin@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: Raw devices vs. Filesystems
  In-Reply-To: <m3oeqf4ie8.fsf@wolfe.cbbrowne.com>
  References: <BAY8-F1017z7ahbwlpd00012a78@hotmail.com> <m3oeqf4ie8.fsf@wolfe.cbbrowne.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