Alvaro 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. This is not something that I'd recommend
> doing on a periodic basis ...
Thank you for your suggestions.
I tried it with VACUUM FREEZE, but it still does not work.
VACUUM FULL was also be tried, but it doesn't work, either.
The old files were not be deleted.
I suspect there are some configuration items which disable vacuum's
cleaning old clog files, because it seems that vacuum could not
delete old clog files at all.
My configurations are as follows:
- - - -
tcpip_socket = true
max_connections = 500
port = 5432
shared_buffers = 1000
syslog = 2
log_min_messages = fatal
#others are default values.
- - - -
Thanks
Duan
> 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.
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
