[PERFORM] VACUUM FULL needed sometimes to prevent transaction ID wraparound?

Hello, we're looking into the reason why we are getting warnings about transaction ID wraparound despite a daily vaccumdb -qaz. Someone is claiming that VACUUM without FULL cannot reassign XIDs properly when max_fsm_pages was set too low (it says so here too, but this is rather old:

Re: [PERFORM] VACUUM FULL needed sometimes to prevent transaction ID wraparound?

Marinos Yannikos wrote: Hello, we're looking into the reason why we are getting warnings about transaction ID wraparound despite a daily vaccumdb -qaz. Someone is claiming that VACUUM without FULL cannot reassign XIDs properly when max_fsm_pages was set too low (it says so here too, but

Re: [PERFORM] VACUUM FULL needed sometimes to prevent transaction ID wraparound?

] On Behalf Of Marinos Yannikos Sent: Tuesday, August 22, 2006 1:11 PM To: pgsql-performance@postgresql.org Subject: [PERFORM] VACUUM FULL needed sometimes to prevent transaction ID wraparound? Hello, we're looking into the reason why we are getting warnings about transaction ID