On Mon, Jun 04, 2007 at 07:34:13AM -0700, Ron St-Pierre wrote:
> >VACUUM FULL _does not_ mean "vacuum everything"!
> What do you mean by this?
Sorry, I was trying to prevent you doing a VACUUM FULL you didn't
want (but another message said you actually intended a vacuum full).
Several people ha
On Mon, Jun 04, 2007 at 07:34:13AM -0700, Ron St-Pierre wrote:
> What do you mean by this? I wanted to do both a VACUUM ANALYZE and a
> VACUUM FULL, so ran VACUUM FULL ANALYZE. Is there something odd about
> VACUUM FULL, other than locking the table it's working on?
It tends to bloat indexes. A
Andrew Sullivan wrote:
On Fri, Jun 01, 2007 at 01:27:14PM -0700, Ron St-Pierre wrote:
imp=# select age(datfrozenxid) from pg_database where datname = 'imp';
age
1571381411
(1 row)
Time to start VACUUM FULL ANALYZE over the weekend.
I guess this comes too late, b
On Fri, Jun 01, 2007 at 01:27:14PM -0700, Ron St-Pierre wrote:
> imp=# select age(datfrozenxid) from pg_database where datname = 'imp';
> age
>
> 1571381411
> (1 row)
>
> Time to start VACUUM FULL ANALYZE over the weekend.
I guess this comes too late, but you don't need VAC
Alvaro Herrera wrote:
FYI, in 8.2 and up the Xid wraparound problem is considered on a table
by table basis, which means that only the tables that have not been
vacuumed recently need to be vacuumed. The need for database wide
vacuuming is gone.
That's good.
Time to start VACUUM FULL ANAL
Ron St-Pierre wrote:
> I stopped using autovacuum months ago because of similar problems
> (version 8.1.4). Because we do some major inserts and updates about four
> times a day, there were a few tables that I didn't want autovacuumed.
> Even after I turned autovacuum off for these tables it sti
I stopped using autovacuum months ago because of similar problems
(version 8.1.4). Because we do some major inserts and updates about four
times a day, there were a few tables that I didn't want autovacuumed.
Even after I turned autovacuum off for these tables it still tried to
vacuum them whil
