Skip site navigation (1) Skip section navigation (2)

VACUUM FULL needed sometimes to prevent transaction ID wraparound?

From: Marinos Yannikos <mjy(at)geizhals(dot)at>
To: pgsql-performance(at)postgresql(dot)org
Subject: VACUUM FULL needed sometimes to prevent transaction ID wraparound?
Date: 2006-08-22 18:10:49
Message-ID: 44EB48A9.7030704@geizhals.at (view raw or flat)
Thread:
Lists: pgsql-performance
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

Responses

pgsql-performance by date

Next:From: Thomas SamsonDate: 2006-08-22 18:21:23
Subject: Re: query planner: automatic rescribe of LIKE to BETWEEN ?
Previous:From: Alvaro HerreraDate: 2006-08-22 17:45:39
Subject: Re: query planner: automatic rescribe of LIKE to BETWEEN ?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group