From: Harald Fuchs <hf320@protecting.net>
To: pgsql-admin@postgresql.org
Subject: Re: Raw devices vs. Filesystems
Date: 07 Apr 2004 15:05:55 +0200
Message-ID: <pu3c7gx7ik.fsf@srv.protecting.net> (raw)
References: <71E37EF6B7DCC1499CEA0316A25683280105786A@loki.wc.globexplorer.net>
<603c7gj04h.fsf@dev6.int.libertyrms.info>
<5719.1081315562@sss.pgh.pa.us>
In article <5719.1081315562@sss.pgh.pa.us>,
Tom Lane <tgl@sss.pgh.pa.us> writes:
> But to get back to the point of this discussion: to allow PG to use raw
> devices instead of filesystems, we'd first have to do a ton of
> portability work (since raw disk access is nowhere standard), and
> abandon our principle that Postgres does not run as root (since raw disk
> access is not permitted to non-root processes by any sane sysadmin).
Why not? In MySQL/InnoDB, you do a "chown mysql.daemon /dev/raw/raw1"
(or whatever raw disk you want to access), and that's all.
> After that, we get to implement our own filesystem-equivalent management
> of disk space allocation, disk I/O scheduling, etc. Are we really
> smarter than all those kernel hackers doing this for a living? I doubt it.
Ditto. I don't have hard numbers for MySQL, but I didn't see any
noticeable improvement when messing with raw disks (at least under
Linux).
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: hf320@protecting.net, pgsql-admin@postgresql.org
Subject: Re: Raw devices vs. Filesystems
In-Reply-To: <pu3c7gx7ik.fsf@srv.protecting.net>
* 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