From: Dave Dutcher <dave@tridecap.com>
To: 'Marinos Yannikos' <mjy@geizhals.at>
To: pgsql-performance@postgresql.org
Subject: Re: VACUUM FULL needed sometimes to prevent transaction ID wraparound?
Date: Tue, 22 Aug 2006 14:28:15 -0500
Message-ID: <023601c6c621$1de0f3e0$8300a8c0@tridecap.com> (raw)
In-Reply-To: <44EB48A9.7030704@geizhals.at>
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@postgresql.org
> [mailto:pgsql-performance-owner@postgresql.org] 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 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
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: dave@tridecap.com, mjy@geizhals.at
Subject: Re: VACUUM FULL needed sometimes to prevent transaction ID wraparound?
In-Reply-To: <023601c6c621$1de0f3e0$8300a8c0@tridecap.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox