From: | Harald Fuchs <hf320(at)protecting(dot)net> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Raw devices vs. Filesystems |
Date: | 2004-04-07 13:05:55 |
Message-ID: | pu3c7gx7ik.fsf@srv.protecting.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-performance |
In article <5719(dot)1081315562(at)sss(dot)pgh(dot)pa(dot)us>,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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).
From | Date | Subject | |
---|---|---|---|
Next Message | Nolte, Ronald C. | 2004-04-07 13:26:52 | installation/verification of postgres w/ pgtcl |
Previous Message | mopeace pliz | 2004-04-07 10:40:41 | installation problem |
From | Date | Subject | |
---|---|---|---|
Next Message | Aaron Werman | 2004-04-07 14:36:48 | Re: good pc but bad performance,why? |
Previous Message | Richard Huxton | 2004-04-07 12:31:30 | Re: plan problem |