Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 2B30964FCD2 for ; Wed, 10 Sep 2008 15:03:31 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 64996-05 for ; Wed, 10 Sep 2008 15:03:26 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from mail-gx0-f17.google.com (mail-gx0-f17.google.com [209.85.217.17]) by postgresql.org (Postfix) with ESMTP id 06CB264FCC4 for ; Wed, 10 Sep 2008 15:03:24 -0300 (ADT) Received: by gxk10 with SMTP id 10so14310146gxk.19 for ; Wed, 10 Sep 2008 11:03:23 -0700 (PDT) Received: by 10.142.105.13 with SMTP id d13mr541527wfc.275.1221069326319; Wed, 10 Sep 2008 10:55:26 -0700 (PDT) Received: by 10.143.39.19 with HTTP; Wed, 10 Sep 2008 10:55:26 -0700 (PDT) Message-ID: Date: Wed, 10 Sep 2008 10:55:26 -0700 From: "Scott Carey" To: "Kevin Grittner" Subject: Re: too many clog files Cc: "Scott Marlowe" , "Tom Lane" , alvherre@commandprompt.com, duanlg@nec-as.nec.com.cn, pgsql-performance@postgresql.org, "Matt Smiley" In-Reply-To: <48C7C1FA.EE98.0025.0@wicourts.gov> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_39751_14578852.1221069326299" References: <48C5CC04.D078.0028.0@rentrak.com> <48C6F7A5.D078.0028.0@rentrak.com> <48C79A55.EE98.0025.0@wicourts.gov> <2257.1221068560@sss.pgh.pa.us> <48C7C1FA.EE98.0025.0@wicourts.gov> X-Google-Sender-Auth: 8549495d59c7f02f X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.001 tagged_above=0 required=5 tests=HTML_MESSAGE=0.001 X-Spam-Level: X-Archive-Number: 200809/119 X-Sequence-Number: 31432 ------=_Part_39751_14578852.1221069326299 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline And potentially to tune down the number kept by modifying the appropriate freeze parameter for 8.1 (I'm not sure of the details), so that it keeps perhaps 20MB or so rather than 50MB. On Wed, Sep 10, 2008 at 10:47 AM, Kevin Grittner < Kevin.Grittner@wicourts.gov> wrote: > >>> Tom Lane wrote: > > > The expected behavior (in 8.2 and newer) is to maintain about > > autovacuum_freeze_max_age transactions' worth of clog; which is to > say > > about 50MB at the default settings. > > The active database I checked, where it didn't go all the way back to > 0000, had 50 MB of files; so I guess it is working as intended. > > It sounds like the advice to the OP that running VACUUM FREEZE on all > databases to clean up the files was off base? > > -Kevin > > -- > Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-performance > ------=_Part_39751_14578852.1221069326299 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
And potentially to tune down the number kept by modifying the appropriate freeze parameter for 8.1 (I'm not sure of the details), so that it keeps perhaps 20MB or so rather than 50MB.

On Wed, Sep 10, 2008 at 10:47 AM, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote:
>>> Tom Lane <tgl@sss.pgh.pa.us> wrote:

> The expected behavior (in 8.2 and newer) is to maintain about
> autovacuum_freeze_max_age transactions' worth of clog; which is to
say
> about 50MB at the default settings.

The active database I checked, where it didn't go all the way back to
0000, had 50 MB of files; so I guess it is working as intended.

It sounds like the advice to the OP that running VACUUM FREEZE on all
databases to clean up the files was off base?

-Kevin

--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

------=_Part_39751_14578852.1221069326299--