pkalva@livedatagroup.com (Pallav Kalva) writes:
> Mark Lewis wrote:
>> On Fri, 2007-08-31 at 12:25 -0400, Pallav Kalva wrote:
>>
>>> Can you please correct me if I am wrong, I want to understand how
>>> this works.
>>> Based on what you said, it will run autovacuum again when it passes
>>> 200M transactions, as SELECTS are transactions too and are going on
>>> these tables.
>>> But the next time when it runs autovacuum, it shouldnt freeze the
>>> tuples again as they are already frozen and wont generate lot of
>>> archive logs ?
>>> Or is this because of it ran autovacuum for the first time on this
>>> db ? just the first time it does this process ?
>>>
>>
>> That is correct. The tuples are now frozen, which means that they will
>> not need to be frozen ever again unless you insert/update any records.
>>
>>
>
> My main concern is filling up my disk with archive logs, so from all
> the replies I get is that since tuples are already frozen, next time
> when it runs autovacuum it wont generate any archive logs.
>
> Is my assumption right ?
No, your assumption is wrong.
Later vacuums will not generate archive files for the tuples that were
*previously* frozen, but if you have additional tuples that have
gotten old enough to reach the "freeze point," THOSE tuples will get
frozen, and so you'll continue to see archive logs generated.
And this is Certainly Not A Bug. If the system did not do this, those
unfrozen tuples would eventually disappear when your current
transaction XID rolls over. The freezing is *necessary.*
--
let name="cbbrowne" and tld="cbbrowne.com" in name ^ "@" ^ tld;;
http://linuxdatabases.info/info/unix.html
Rules of the Evil Overlord #86. "I will make sure that my doomsday
device is up to code and properly grounded."
<http://www.eviloverlord.com/>
