On Wed, 2008-07-09 at 11:33 -0700, Toshio Kuratomi wrote: > Since the plan is to move koji to db3 within the week I'd like to hold > off on this. The dump and reload to move to the new server should be > more effective than a manual vacuum. Note that you still need to analyze all the tables after a dump/reload to regenerate database statistics. Otherwise postgres may choose some less-than-optimal query plans. > -Toshio > > -------- Original Message -------- > Subject: Cron <postgres@db2> /var/lib/pgsql/vacstat.py check > Date: Wed, 9 Jul 2008 13:20:05 GMT > From: root@xxxxxxxxxxxxxxxxxxxxxxxxx (Cron Daemon) > To: postgres@xxxxxxxxxxxxxxxxxxxxxxxxx > > 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 > > > _______________________________________________ > Fedora-infrastructure-list mailing list > Fedora-infrastructure-list@xxxxxxxxxx > https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list _______________________________________________ Fedora-infrastructure-list mailing list Fedora-infrastructure-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
