| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Duan Ligong <duanlg(at)nec-as(dot)nec(dot)com(dot)cn> |
| Cc: | Greg Smith <gsmith(at)gregsmith(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: too many clog files |
| Date: | 2008-09-05 16:24:46 |
| Message-ID: | 20080905162446.GF4353@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Duan Ligong wrote:
> 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.
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. This is not something that I'd recommend
doing on a periodic basis ...
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2008-09-05 16:39:09 | Re: too many clog files |
| Previous Message | Vladimir Sitnikov | 2008-09-05 15:10:35 | Re: indexing for distinct search in timestamp based table |