Skip site navigation (1) Skip section navigation (2)

Re: too many clog files

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <alvherre(at)commandprompt(dot)com>,<duanlg(at)nec-as(dot)nec(dot)com(dot)cn>,<pgsql-performance(at)postgresql(dot)org>,"Matt Smiley" <mss(at)rentrak(dot)com>
Subject: Re: too many clog files
Date: 2008-09-10 14:58:45
Message-ID: 48C79A55.EE98.0025.0@wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-performance
> "Matt Smiley" <mss(at)rentrak(dot)com> wrote: 
> Alvaro Herrera wrote:
>> Move the old clog files back where they were, and run VACUUM FREEZE
in
>> all your databases.  That should clean up all the old pg_clog files,
if
>> you're really that desperate.
> 
> Has anyone actually seen a CLOG file get removed under 8.2 or 8.3?
 
Some of my high-volume databases don't quite go back to 0000, but this
does seem to be a problem.  I have confirmed that VACUUM FREEZE on all
but template0 (which doesn't allow connections) does not clean them
up.  No long running transactions are present.
 
-Kevin

In response to

Responses

pgsql-performance by date

Next:From: Scott CareyDate: 2008-09-10 16:26:25
Subject: Re: Effects of setting linux block device readahead size
Previous:From: Greg SmithDate: 2008-09-10 14:49:06
Subject: Re: Effects of setting linux block device readahead size

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group