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.
-Toshio
-------- Original Message -------- Subject: Cron postgres@db2 /var/lib/pgsql/vacstat.py check Date: Wed, 9 Jul 2008 13:20:05 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
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@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
Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
Mike Bonnet wrote:
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.
Good point.
Also note, we're currently debating whether to move to postgres-8.3 for koji now or later. 8.3 has a whole slew of enhancements that could make our lives better[1]_. On the debit side we haven't tested koji with 8.3 here. However, dgilmore has been running sparc.koji.fp.o (FC6) with pg-8.3 which is pretty similar to our environment.
.. _[1]: Combing the NEWS for changes from 8.1=>8.3 I came up with the list here: https://fedorahosted.org/fedora-infrastructure/ticket/547
-Toshio
On Wed, 2008-07-09 at 12:27 -0700, Toshio Kuratomi wrote:
Mike Bonnet wrote:
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.
Good point.
Also note, we're currently debating whether to move to postgres-8.3 for koji now or later. 8.3 has a whole slew of enhancements that could make our lives better[1]_. On the debit side we haven't tested koji with 8.3 here. However, dgilmore has been running sparc.koji.fp.o (FC6) with pg-8.3 which is pretty similar to our environment.
If dgilmore hasn't seen any issues with Postgres 8.3, I'm all for using that. In addition, if we do run into performance/scaling issues, I'm sure the Postgres developers will be much more eager to assist us with them if we're running 8.3 rather than an older version.
.. _[1]: Combing the NEWS for changes from 8.1=>8.3 I came up with the list here: https://fedorahosted.org/fedora-infrastructure/ticket/547
-Toshio
Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
infrastructure@lists.fedoraproject.org