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

I would guess that you are not running vacuumdb as a user with permission to
vacuum the postgres or template1 databases. Try telling vacuumdb to log in
as postgres or whatever your superuser account is called.

> -----Original Message-----
> From: pgsql-performance-owner(at)postgresql(dot)org
> [mailto:pgsql-performance-owner(at)postgresql(dot)org] On Behalf Of
> Marinos Yannikos
> Sent: Tuesday, August 22, 2006 1:11 PM
> To: pgsql-performance(at)postgresql(dot)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 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:
> http://www.varlena.com/GeneralBits/Tidbits/perf.html#maxfsmp) Is
> this true, or do we have a different issue here? We're using
> 8.1.3 with
> a database generated on 8.1.3 (i.e. not migrated from 7.x or anything
> like that).
>
> Thanks,
> Marinos
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 5: don't forget to increase your free space map settings
>