X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 856A3D1CAC0 for ; Fri, 4 Jun 2004 12:33:36 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 60046-10 for ; Fri, 4 Jun 2004 15:33:33 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 51D0ED1B435 for ; Fri, 4 Jun 2004 12:33:30 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i54FXTg2027975; Fri, 4 Jun 2004 11:33:29 -0400 (EDT) To: CH Cc: pgsql-performance@postgresql.org Subject: Re: filesystem option tuning In-reply-to: <20040604162111.A5057@p15097255.pureserver.info> References: <20040604162111.A5057@p15097255.pureserver.info> Comments: In-reply-to CH message dated "Fri, 04 Jun 2004 16:21:11 +0200" Date: Fri, 04 Jun 2004 11:33:29 -0400 Message-ID: <27974.1086363209@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200406/34 X-Sequence-Number: 7092 CH writes: > So the clog is not written to every time the xlog is written to? No. One clog page holds 32000 transactions' worth of transaction status values, so on average we need only one clog page write per 32000 transactions. > On a related issue, what's the connection between the "fsync" and the > "wal_sync_method" configuration switches? fsync is the master circuit breaker: turn it off, there is no power at the wal_sync_method socket ;-). We stop doing anything special about enforcing write ordering for any files, but just assume that the kernel + hardware can be trusted not to lose data they've been given. With fsync on, wal_sync_method means something. fsync on also enables fsync/sync for the data files at checkpoint times. We don't need to force writes for those between checkpoints, so wal_sync_method doesn't apply to data files (nor clog). regards, tom lane