X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 125CAD1B459 for ; Wed, 7 Apr 2004 10:10:40 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 94333-01 for ; Wed, 7 Apr 2004 10:10:41 -0300 (ADT) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by svr1.postgresql.org (Postfix) with ESMTP id 5E5EED1CB3F for ; Wed, 7 Apr 2004 10:10:37 -0300 (ADT) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1BBCpE-0001tD-00 for ; Wed, 07 Apr 2004 15:10:40 +0200 Received: from srv.protecting.net ([212.126.218.242]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 07 Apr 2004 15:10:40 +0200 Received: from hf320 by srv.protecting.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 07 Apr 2004 15:10:40 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-admin@postgresql.org From: Harald Fuchs Subject: Re: Raw devices vs. Filesystems Date: 07 Apr 2004 15:05:55 +0200 Organization: Linux Private Site Lines: 19 Message-ID: References: <71E37EF6B7DCC1499CEA0316A25683280105786A@loki.wc.globexplorer.net> <603c7gj04h.fsf@dev6.int.libertyrms.info> <5719.1081315562@sss.pgh.pa.us> Reply-To: hf320@protecting.net Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: srv.protecting.net X-No-Archive: yes User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7 X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/105 X-Sequence-Number: 13078 In article <5719.1081315562@sss.pgh.pa.us>, Tom Lane 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).