X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [64.117.224.130]) by svr1.postgresql.org (Postfix) with ESMTP id BD66ED1C4B8 for ; Fri, 15 Aug 2003 10:05:09 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (neptune.hub.org [64.117.224.130]) (amavisd-new, port 10024) with ESMTP id 28506-02 for ; Fri, 15 Aug 2003 07:05:01 -0300 (ADT) Received: from host8.checkdomain.de (host8.checkdomain.de [62.116.141.18]) by svr1.postgresql.org (Postfix) with ESMTP id 42EF3D1B539 for ; Fri, 15 Aug 2003 07:04:58 -0300 (ADT) Received: from schlichting.net (pD9E63F3D.dip.t-dialin.net [217.230.63.61]) (authenticated) by host8.checkdomain.de (8.11.2/8.11.6) with ESMTP id h7FA4FE09825; Fri, 15 Aug 2003 12:04:56 +0200 Message-ID: <3F3CB08C.9080308@schlichting.net> Date: Fri, 15 Aug 2003 12:06:04 +0200 From: Toni Schlichting User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030617 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Christopher Browne Cc: pgsql-performance@postgresql.org Subject: Re: On Linux Filesystems References: <20030810200440.B2396@cookie> <3032.1060617279@sss.pgh.pa.us> <20030811100740.D2396@cookie> <3855.1060622959@sss.pgh.pa.us> <20030811104447.G2396@cookie> <4146.1060624411@sss.pgh.pa.us> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200308/273 X-Sequence-Number: 3089 Christopher, I appreciate your comments. At the end it goes down to personal experience with one or the other file system. From that I can tell, that I have made good experience with UFS, EXT2, and XFS. I made catastrophic ex- perience with ReiserFS (not during operation but you are a looser when it fails because the recovery methods are likely to be insufficient) So at the end if somebody runs technical equipment, regardless whether it's a computer or a chemical fab. It can fail and you need to make up your mind about contingency. This is due even before you start operating the equipment. So waste too much time on thinking about the perfect file system. But evaluate the potential damage that can result from failure. Develop a Backup&Recovery strategy and test it, test it and test it again, so that you can do it blindly when it's due. Ciao, Toni >I wish there were more "hard and fast" conclusions to draw, to be able >to conclusively say that one or another Linux filesystem was >unambiguously preferable for use with PostgreSQL. There are not >conclusive metrics, either in terms of speed or of some notion of >"reliability." I'd expect ReiserFS to be the poorest choice, and for >XFS to be the best, but I only have fuzzy reasons, as opposed to >metrics. > >The absence of measurable metrics of the sort is _NOT_ a proof that >(say) FreeBSD is conclusively preferable, whatever your own >preferences (I'll try to avoid characterizing it as "prejudices," as >that would be unkind) may be. That would represent a quite separate >debate, and one that doesn't belong here, certainly not on a thread >where the underlying question was "Which Linux FS is preferred?" > >If the OSDB TPC-like benchmarks can get "packaged" up well enough to >easily run and rerun them, there's hope of getting better answers, >perhaps even including performance metrics for *BSD. That, not >Linux-baiting, is the answer... > >