Alvaro Herrera wrote:
Pallav Kalva wrote:
Tom Lane wrote:
Probably represents freezing of old tuples, which is a WAL-logged
operation as of 8.2. Is it likely that the data is 200M transactions
old?
If nothing changed on these tables how can it freeze old tuples ?
Does it mean that once it reaches 200M transactions it will do the same
thing all over again ?
No -- once tuples are frozen, they don't need freezing again (unless
they are modified by UPDATE or DELETE).
If I am doing just SELECTS on these tables ? how can there be any
transactions ? or SELECTS considered transactions too ?
Selects are transactions too. They just don't modify data.
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 ?
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
