I'd like to take care of this as soon after change freeze as possible. It's the same as last time:

Disable the pieces of the cron scripts which vacuum koji's dbs in puppet cvs commit; make install; make push HOSTS=db2 ssh db2 screen time sudo -u postgres vacuumdb -vd koji [wait a few hours for this to finish during which koji is somewhat more sluggish but there's no actual outage.] reenable the pieces of the cron scripts which vacuum koji, commit, install, push. Done.

Anyone object to my doing it during the day on Wednesday, May 14th?

-Toshio

-------- Original Message -------- Subject: Cron postgres@db2 /var/lib/pgsql/vacstat.py check Date: Fri, 9 May 2008 13:20:07 GMT From: root@db2.fedora.phx.redhat.com (Cron Daemon) To: postgres@db2.fedora.phx.redhat.com

Traceback (most recent call last): File "/var/lib/pgsql/vacstat.py", line 650, in ? Commands[command](opts) File "/var/lib/pgsql/vacstat.py", line 150, in test_all test_transactions(opts) File "/var/lib/pgsql/vacstat.py", line 147, in test_transactions raise XIDOverflowWarning, '\n'.join(overflows) __main__.XIDOverflowWarning: Used over half the transaction ids for koji. Please schedule a vacuum of that entire database soon: sudo -u postgres vacuumdb -zvd koji