X-Original-To: pgsql-advocacy@postgresql.org Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id 33E54474E4F; Thu, 13 Feb 2003 22:46:42 -0500 (EST) Received: from filer (12-234-86-219.client.attbi.com [12.234.86.219]) by postgresql.org (Postfix) with ESMTP id 9992C474E42; Thu, 13 Feb 2003 22:46:41 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) (uid 1000) by filer with local; Thu, 13 Feb 2003 19:46:46 -0800 Date: Thu, 13 Feb 2003 19:46:46 -0800 From: Kevin Brown To: Hackers , pgsql-performance@postgresql.org, Advocacy Subject: Re: [PERFORM] [HACKERS] More benchmarking of wal_buffers Message-ID: <20030214034646.GA1847@filer> Mail-Followup-To: Kevin Brown , Hackers , pgsql-performance@postgresql.org, Advocacy References: <3331.1045189757@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline In-Reply-To: <3331.1045189757@sss.pgh.pa.us> User-Agent: Mutt/1.4i Organization: Frobozzco International X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200302/72 X-Sequence-Number: 830 Tom Lane wrote: > "Christopher Kings-Lynne" writes: > > I've just spent the last day and a half trying to benchmark our new database > > installation to find a good value for wal_buffers. The quick answer - there > > isn't, just leave it on the default of 8. > > I don't think this is based on a useful test for wal_buffers. The > wal_buffers setting only has to be large enough for the maximum amount > of WAL log data that your system emits between commits, because a commit > (from anyone) is going to flush the WAL data to disk (for everyone). 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... -- Kevin Brown kevin@sysexperts.com