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 7F4ECD1B911; Wed, 7 Apr 2004 04:19:03 -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 49595-06; Wed, 7 Apr 2004 04:19:02 -0300 (ADT) Received: from elbereth.noviforum.si (unknown [193.189.169.66]) by svr1.postgresql.org (Postfix) with ESMTP id 5A853D1B515; Wed, 7 Apr 2004 04:19:00 -0300 (ADT) Received: from elbereth.noviforum.si (localhost [127.0.0.1]) by elbereth.noviforum.si (8.12.10/8.12.10) with ESMTP id i377IxHh014859; Wed, 7 Apr 2004 09:18:59 +0200 Received: (from gregab@localhost) by elbereth.noviforum.si (8.12.10/8.12.10/Submit) id i377IwPq014845; Wed, 7 Apr 2004 09:18:58 +0200 Date: Wed, 7 Apr 2004 09:18:58 +0200 From: Grega Bremec To: Tom Lane Cc: Chris Browne , pgsql-admin@postgresql.org, pgsql-performance@postgresql.org Subject: Re: Raw devices vs. Filesystems Message-ID: <20040407071858.GA7973@elbereth.noviforum.si> References: <71E37EF6B7DCC1499CEA0316A25683280105786A@loki.wc.globexplorer.net> <603c7gj04h.fsf@dev6.int.libertyrms.info> <5719.1081315562@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline In-Reply-To: <5719.1081315562@sss.pgh.pa.us> User-Agent: Mutt/1.4.2i Organization: Noviforum, Ltd., Software & Media X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200404/102 X-Sequence-Number: 13075 --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable ...and on Wed, Apr 07, 2004 at 01:26:02AM -0400, Tom Lane used the keyboard: >=20 > 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 i= t. >=20 > After that, we get to re-optimize all the existing Postgres behaviors > that are designed to sit on top of a standard Unix buffering filesystem > layer. >=20 > After that, we might reap some performance benefits. Or maybe not. > There's not a heck of a lot of hard evidence that we would --- and > what there is traces to twenty-year-old assumptions about disk drive > and OS behavior, which are quite unlikely to still apply today. >=20 > Personally, I have a lot of more-promising projects to pursue... >=20 Has anyone tried PostgreSQL on top of OCFS? Personally, I'm not sure it would even work, as Oracle clearly state that OCFS was _never_ meant to be a fully fledged UNIX filesystem with POSIX features such as correct timestamp updates, inode changes, etc., but OCFSv2 brings some features that might lead one into thinking they're about to make it suitable for uses beyond that of just having Oracle databases sitting on top of it. Furthermore, this filesystem would be a blazing one stop solution for all replication issues PostgreSQL currently suffers from, as its main design goal was to present "a consistent file system image across the servers in a cluster". Now, if both goals can be achieved in one go, hell, I'm willing to try it out myself in an attempt to extract off of it, some performance indicators that could be compared to other database performance tests sent to both this and the PERFORM mailing list. So, anyone? :) Cheers, --=20 Grega Bremec Senior Administrator Noviforum Ltd., Software & Media http://www.noviforum.si/ --k1lZvvs/B4yU6o8G Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAc6tiDo/EMYD4+osRAu+xAJ4t6r9JMoTTgMH2q5I3ab6A0pqRUwCfU8Ky o6Pu6BIKTMZw/dfgbdcY47M= =029G -----END PGP SIGNATURE----- --k1lZvvs/B4yU6o8G--