Received: from localhost (unknown [200.46.204.187]) by postgresql.org (Postfix) with ESMTP id 7C2609FC6C2 for ; Mon, 22 Oct 2007 15:21:33 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.187]) (amavisd-maia, port 10024) with ESMTP id 90071-01-5 for ; Mon, 22 Oct 2007 15:21:14 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 3FC3C9FC352 for ; Mon, 22 Oct 2007 15:17:36 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id l9MIHWPx019803; Mon, 22 Oct 2007 14:17:32 -0400 (EDT) To: "Mark Steben" cc: pgsql-admin@postgresql.org Subject: Re: bgwriter update question In-reply-to: <000901c814d4$51163010$b501a8c0@D1RPQZB1> References: <000901c814d4$51163010$b501a8c0@D1RPQZB1> Comments: In-reply-to "Mark Steben" message dated "Mon, 22 Oct 2007 13:52:30 -0400" Date: Mon, 22 Oct 2007 14:17:32 -0400 Message-ID: <19802.1193077052@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200710/212 X-Sequence-Number: 27126 "Mark Steben" writes: > I'm running on 7.4.5 (pre bgwriter) and moving to 8.2 in 3 weeks. I turn > fsync off on my testing server. When I update a table I expect the file in > the base directory to remain the same size until the next syncpoint when it > would then update. But it increases immediately. I thought updates remain in > memory until syncpoint in pre-8.0. Am I missing somethng? The updates don't go to disk immediately (they didn't in 7.4 either). But we always allocate disk space immediately when needed, to make sure it's available. Otherwise we could face the embarrassing situation of having noplace to put rows inserted by an already-reported-committed transaction. regards, tom lane