X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (wm.hub.org [200.46.204.128]) by postgresql.org (Postfix) with ESMTP id 4BCB69FB2CA for ; Fri, 4 Aug 2006 13:07:57 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.128]) (amavisd-new, port 10024) with ESMTP id 68227-09 for ; Fri, 4 Aug 2006 16:07:55 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey- Received: from gauss.credativ.com (ipx11302.ipxserver.de [212.112.227.254]) by postgresql.org (Postfix) with ESMTP id E2B629FB2BE for ; Fri, 4 Aug 2006 13:07:54 -0300 (ADT) Received: from bell.credativ.de (p50897F74.dip.t-dialin.net [80.137.127.116]) (using TLSv1 with cipher EXP1024-RC4-SHA (56/128 bits)) (No client certificate requested) by gauss.credativ.com (Postfix) with ESMTP id 864D4D7916; Fri, 4 Aug 2006 18:07:53 +0200 (CEST) From: Peter Eisentraut To: Tom Lane Subject: Re: Background writer memory bloat? Date: Fri, 4 Aug 2006 18:07:51 +0200 User-Agent: KMail/1.9.1 Cc: pgsql-admin@postgresql.org References: <200608041641.33800.peter_e@gmx.net> <18411.1154703628@sss.pgh.pa.us> In-Reply-To: <18411.1154703628@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200608041807.51624.peter_e@gmx.net> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200608/42 X-Sequence-Number: 22586 Am Freitag, 4. August 2006 17:00 schrieb Tom Lane: > Are you sure it's bloat, and not just a reflection of the fact that it's > touched every page of the shared buffers over its lifespan? That seems to be the explanation. -- Peter Eisentraut http://developer.postgresql.org/~petere/