Maybe I'm thinking wrong, but I have a problem like yours; and I realize
that the vacuum Freeze that does that work.
I have read that somewhere in the net, that I don't remember now.
To prevent that I created a proccess that run every night, that vacuums the
database, and started the vacuum daemon.
All machines I had problems are Slony-slaves.
2008/9/30 Steve Crawford <scrawford(at)pinpointresearch(dot)com>
> Carol Walter wrote:
>> Ah-h-h, that's exactly my question. What part of Postgres "takes care of
>> this itself." I'm asking because I had 86 pg_clog files dated back to
>> mid-May. I got the impression from something Tom said that backups should
>> prune this directory. Perhaps my "impression" was wrong. Most databases
>> I've used in the past have gotten rid of the transaction logs, etc, when a
>> backup is done. The restore process used that last backup and then applied
>> the transaction logs to it. Once another backup was completed the old
>> transaction logs were no longer needed. I'm trying to understand what
>> happens "under the hood" so to speak. What checkpoint_settings value are
>> you referring to?
> Sorry. I had a brain/fingers disconnect. I meant the "checkpoint_segments"
> setting. Anyway, answers to a number of your questions regarding write-ahead
> logging may be found here:
> Sent via pgsql-admin mailing list (pgsql-admin(at)postgresql(dot)org)
> To make changes to your subscription:
In response to
pgsql-admin by date
|Next:||From: Craig Perras||Date: 2008-10-01 01:21:08|
|Subject: sspi authentication|
|Previous:||From: Rafael Domiciano||Date: 2008-10-01 00:54:09|
|Subject: Re: [GENERAL] Functions|