Re: too many clog files - Mailing list pgsql-performance

From Scott Carey
Subject Re: too many clog files
Date
Msg-id a1ec7d000809101055m54f27647l4e546ec87e14f4c7@mail.gmail.com
Whole thread Raw
In response to Re: too many clog files  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-performance
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

pgsql-performance by date:

Previous
From: "Scott Carey"
Date:
Subject: Re: Improve COPY performance for large data sets
Next
From: Alvaro Herrera
Date:
Subject: Re: too many clog files