From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Scott Marlowe <scott.marlowe@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: alvherre@commandprompt.com
Cc: duanlg@nec-as.nec.com.cn
Cc: pgsql-performance@postgresql.org
Cc: Matt Smiley <mss@rentrak.com>
Subject: Re: too many clog files
Date: Wed, 10 Sep 2008 12:47:54 -0500
Message-ID: <48C7C1FA.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <2257.1221068560@sss.pgh.pa.us>
References: <48C5CC04.D078.0028.0@rentrak.com>
<48C6F7A5.D078.0028.0@rentrak.com>
<48C79A55.EE98.0025.0@wicourts.gov>
<dcc563d10809101018u1f77199bpcc134121d7d040ad@mail.gmail.com>
<dcc563d10809101018u1f77199bpcc134121d7d040ad@mail.gmail.com>
<2257.1221068560@sss.pgh.pa.us>
>>> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, scott.marlowe@gmail.com, tgl@sss.pgh.pa.us, alvherre@commandprompt.com, duanlg@nec-as.nec.com.cn, mss@rentrak.com
Subject: Re: too many clog files
In-Reply-To: <48C7C1FA.EE98.0025.0@wicourts.gov>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox