Hi,
In HEAD, when autovacuum is disabled, autovacuum process is not
launched forcibly to prevent XID wraparound even if we go through
autovacuum_freeze_max_age. This seems to be because
ShmemVariableCache-xidVacLimit is not initialized (i.e.,
SetTransactionIdLimit() is not called) until VACUUM is
Fujii Masao escribió:
Hi,
In HEAD, when autovacuum is disabled, autovacuum process is not
launched forcibly to prevent XID wraparound even if we go through
autovacuum_freeze_max_age. This seems to be because
ShmemVariableCache-xidVacLimit is not initialized (i.e.,
SetTransactionIdLimit()
Alvaro Herrera alvhe...@commandprompt.com writes:
Fujii Masao escribió:
In HEAD, when autovacuum is disabled, autovacuum process is not
launched forcibly to prevent XID wraparound even if we go through
autovacuum_freeze_max_age. This seems to be because
ShmemVariableCache-xidVacLimit is not
Alvaro Herrera alvhe...@commandprompt.com writes:
Maybe check at backend startup whether the limit is valid, and call
SetTransactionIdLimit if not?
Actually, the intent was that that would get called during startup,
but it seems I forgot to actually plug that in :-(. Loose wires now
reattached
On Wed, Feb 17, 2010 at 12:12 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Alvaro Herrera alvhe...@commandprompt.com writes:
Maybe check at backend startup whether the limit is valid, and call
SetTransactionIdLimit if not?
Actually, the intent was that that would get called during startup,
but it
