If I were to specify in the pg_autovacuum catalog that certain high
volume partitioned tables(that get dropped daily) be ignored, then when
autovacuum finishes, will it update the transaction id wraparound
counter (this way, I can get autovacuum to finish quickly )

OR



Will I still need to periodically do vacuumdb -a to take care of the
wraparound problem.

Sriram Dandapani wrote:
>
> If I were to specify in the pg_autovacuum catalog that certain high
> volume partitioned tables(that get dropped daily) be ignored, then
> when autovacuum finishes, will it update the transaction id wraparound
> counter (this way, I can get autovacuum to finish quickly )
>
> OR
>
> Will I still need to periodically do vacuumdb ¡Va to take care of the
> wraparound problem.
>

You don't need to do a manual vacuumdb -a since autovacuum will do this
once it decides you are getting too close to the wraparound point. I
believe this has been improved in the upcoming 8.2 release where
autovacuum no longer need to vacuum the whole database at once, rather
XID wraparound is now tracked on a per table basis.


---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org