Received: from maia.hub.org (maia-5.hub.org [200.46.204.29])
	by mail.postgresql.org (Postfix) with ESMTP id 8C62B632CCD
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Thu,  8 Jul 2010 16:50:46 -0300 (ADT)
Received: from mail.postgresql.org ([200.46.204.86])
	by maia.hub.org (mx1.hub.org [200.46.204.29]) (amavisd-maia, port 10024)
	with ESMTP id 90429-02
	for <pgsql-performance-postgresql.org@mail.postgresql.org>;
	Thu,  8 Jul 2010 19:50:38 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130])
	by mail.postgresql.org (Postfix) with ESMTP id 618926321A5
	for <pgsql-performance@postgresql.org>;
	Thu,  8 Jul 2010 16:50:38 -0300 (ADT)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id o68JoX2E000785;
	Thu, 8 Jul 2010 15:50:33 -0400 (EDT)
To: Richard Yen <richyen@iparadigms.com>
cc: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>,
	"Robert Haas" <robertmhaas@gmail.com>,
	"Scott Marlowe" <scott.marlowe@gmail.com>, pgsql-performance@postgresql.org
Subject: Re: [Slony1-general] WAL partition overloaded--by autovacuum? 
In-reply-to: <855D47FE-2386-4933-BED3-55FE2BA42CC0@iparadigms.com> 
References: <03D2C5F0-F222-4088-B5E4-8DA688565B70@iparadigms.com>
	<AANLkTik1oR2fMBp9pzpeYUgrANXKpK0B23scXONQEK1z@mail.gmail.com>
	<78E79F0B-5C6C-4BDA-B69C-C0FBF69ABBC7@iparadigms.com>
	<AANLkTim9s_S0LS3VtjxUVGuGOHkl_2n7YfpB3KWwdlm-@mail.gmail.com>
	<4C35DADF020000250003326D@gw.wicourts.gov>
	<855D47FE-2386-4933-BED3-55FE2BA42CC0@iparadigms.com>
Comments: In-reply-to Richard Yen <richyen@iparadigms.com>
	message dated "Thu, 08 Jul 2010 12:25:01 -0700"
Date: Thu, 08 Jul 2010 15:50:33 -0400
Message-ID: <784.1278618633@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: Maia Mailguard 1.0.1
X-Spam-Status: No, hits=-1.91 tagged_above=-10 required=5 tests=BAYES_00=-1.9,
	T_RP_MATCHES_RCVD=-0.01
X-Spam-Level: 
X-Archive-Number: 201007/128
X-Sequence-Number: 39517

Richard Yen <richyen@iparadigms.com> writes:
> My concern is that--as in the original post--there were moments where 129 WAL files were generated in one minute.  Is it plausible that this autovacuum could be responsible for this?

That's not a particularly surprising WAL creation rate for a busy
database.  I wouldn't expect autovacuum to cause it by itself, but
that's true only because autovacuum processing is typically throttled
by autovacuum_vacuum_cost_delay.  Perhaps you had that set to zero?

			regards, tom lane