X-Original-To: pgsql-advocacy@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id F2112475C2B; Thu, 13 Feb 2003 23:16:48 -0500 (EST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id D8D15475A80; Thu, 13 Feb 2003 23:14:45 -0500 (EST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.6/8.12.6) with ESMTP id h1E4Eo5u003915; Thu, 13 Feb 2003 23:14:50 -0500 (EST) To: Kevin Brown Cc: Hackers , pgsql-performance@postgresql.org, Advocacy Subject: Re: [PERFORM] [HACKERS] More benchmarking of wal_buffers In-reply-to: <20030214034646.GA1847@filer> References: <3331.1045189757@sss.pgh.pa.us> <20030214034646.GA1847@filer> Comments: In-reply-to Kevin Brown message dated "Thu, 13 Feb 2003 19:46:46 -0800" Date: Thu, 13 Feb 2003 23:14:49 -0500 Message-ID: <3914.1045196089@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/74 X-Sequence-Number: 832 Kevin Brown writes: > What happens when the only transaction running emits more WAL log data > than wal_buffers can handle? A flush happens when the WAL buffers > fill up (that's what I'd expect)? Didn't find much in the > documentation about it... A write, not a flush (ie, we don't force an fsync). Also, I think it writes only a few blocks, not all the available data. Don't recall the details on that. regards, tom lane