From: Scott Marlowe <scott.marlowe@gmail.com>
To: Duan Ligong <duanlg@nec-as.nec.com.cn>
Cc: Greg Smith <gsmith@gregsmith.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: too many clog files
Date: Fri, 5 Sep 2008 10:39:09 -0600
Message-ID: <dcc563d10809050939y1590a0b6y93d7b98bbcff8548@mail.gmail.com> (raw)
In-Reply-To: <20080905095051.93A6.DUANLG@nec-as.nec.com.cn>
References: <20080902091602.CA09.DUANLG@nec-as.nec.com.cn>
<Pine.GSO.4.64.0809020117030.6014@westnet.com>
<20080905095051.93A6.DUANLG@nec-as.nec.com.cn>
On Thu, Sep 4, 2008 at 8:58 PM, Duan Ligong <duanlg@nec-as.nec.com.cn> wrote:
> Thanks for your reply.
>
> Greg wrote:
>> On Tue, 2 Sep 2008, Duan Ligong wrote:
>> > - Does Vacuum delete the old clog files?
>>
>> Yes, if those transactions are all done. One possibility here is that
>> you've got some really long-running transaction floating around that is
>> keeping normal clog cleanup from happening. Take a look at the output
>> from "select * from pg_stat_activity" and see if there are any really old
>> transactions floating around.
>
> Well, we could not wait so long and just moved the old clog files.
> The postgresql system is running well.
> But now the size of pg_clog has exceeded 50MB and there
> are 457 clog files.
That is absolutely not the thing to do. Put them back, and do a
dump-restore on the database if you need to save a few hundred megs on
the drive. Deleting files from underneath postgresql is a great way
to break your database in new and interesting ways which are often
fatal to your data.
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: scott.marlowe@gmail.com, duanlg@nec-as.nec.com.cn, gsmith@gregsmith.com
Subject: Re: too many clog files
In-Reply-To: <dcc563d10809050939y1590a0b6y93d7b98bbcff8548@mail.gmail.com>
* 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