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 CC220D1BA9E for ; Mon, 29 Mar 2004 19:20:26 +0000 (GMT) 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 42233-01 for ; Mon, 29 Mar 2004 15:20:24 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 31962D1B8CA for ; Mon, 29 Mar 2004 15:20:23 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i2TJKMYn007065 for ; Mon, 29 Mar 2004 19:20:22 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i2TIoYX8000615 for pgsql-admin@postgresql.org; Mon, 29 Mar 2004 18:50:34 GMT From: Christopher Browne X-Newsgroups: comp.databases.postgresql.admin Subject: Re: Raw devices vs. Filesystems Date: Mon, 29 Mar 2004 13:28:47 -0500 Organization: cbbrowne Computing Inc Lines: 48 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org X-message-flag: Outlook is rather hackable, isn't it? X-Home-Page: http://www.cbbrowne.com/info/ X-Affero: http://svcs.affero.net/rm.php?r=cbbrowne User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Security Through Obscurity, linux) Cancel-Lock: sha1:xDj347uONa/ui0/knZ3ztaxXu5E= To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/50 X-Sequence-Number: 13023 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.