Re: too many clog files
От | Scott Marlowe |
---|---|
Тема | Re: too many clog files |
Дата | |
Msg-id | dcc563d10809101018u1f77199bpcc134121d7d040ad@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: too many clog files ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>) |
Ответы |
Re: too many clog files
|
Список | pgsql-performance |
On Wed, Sep 10, 2008 at 8:58 AM, Kevin Grittner <Kevin.Grittner@wicourts.gov> wrote: >> "Matt Smiley" <mss@rentrak.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. I have a pretty high volume server that's been online for one month and it had somewhere around 53, going back in order to 0000, and it was recently vacuumdb -az 'ed. Running another one. No long running transactions, etc...
В списке pgsql-performance по дате отправления: