X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 535BDD1EECD for ; Mon, 3 May 2004 14:16:12 -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 51650-08 for ; Mon, 3 May 2004 14:15:55 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 8C429D1EF18 for ; Mon, 3 May 2004 14:15:49 -0300 (ADT) 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 i43HFmSx096413 for ; Mon, 3 May 2004 17:15:48 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i43H9uRr087217 for pgsql-performance@postgresql.org; Mon, 3 May 2004 17:09:56 GMT From: Chris Browne X-Newsgroups: comp.databases.postgresql.performance Subject: Re: Recommended File System Configuration Date: Mon, 03 May 2004 12:38:33 -0400 Organization: cbbrowne Computing Inc Lines: 43 Message-ID: <60zn8pcvp2.fsf@dev6.int.libertyrms.info> References: <4094AD20.6090707@jamesthornton.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.110002 (No Gnus v0.2) XEmacs/21.4 (Security Through Obscurity, linux) Cancel-Lock: sha1:3KfTEXaC2Mi1CC+e1U6GoFbsbJg= To: pgsql-performance@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200405/13 X-Sequence-Number: 6844 james@jamesthornton.com (James Thornton) writes: > Back in 2001, there was a lengthy thread on the PG Hackers list about > PG and journaling file systems > (http://archives.postgresql.org/pgsql-hackers/2001-05/msg00017.php), > but there was no decisive conclusion regarding what FS to use. At the > time the fly in the XFS ointment was that deletes were slow, but this > was improved with XFS 1.1. > > I think a journaling a FS is needed for PG data since large DBs could > take hours to recover on a non-journaling FS, but what about WAL files? If the WAL files are on a small filesystem, it presumably won't take hours for that filesystem to recover at fsck time. The results have not been totally conclusive... - Several have found JFS to be a bit faster than anything else on Linux, but some data loss problems have been experienced; - ext2 has the significant demerit that with big filesystems, fsck will "take forever" to run; - ext3 appears to be the slowest option out there, and there are some stories of filesystem corruption; - ReiserFS was designed to be real fast with tiny files, which is not the ideal "use case" for PostgreSQL; the designers there are definitely the most aggressive at pushing out "bleeding edge" code, which isn't likely the ideal; - XFS is neither fastest nor slowest, but there has been a lack of reports of "spontaneous data loss" under heavy load, which is a good thing. It's not part of "official 2.4" kernels, requiring backports, but once 2.6 gets more widely deployed, this shouldn't be a demerit anymore... I think that provides a reasonable overview of what has been seen... -- output = reverse("gro.gultn" "@" "enworbbc") http://cbbrowne.com/info/oses.html Donny: Are these the Nazis, Walter? Walter: No, Donny, these men are nihilists. There's nothing to be afraid of. -- The Big Lebowski