[haiku-web] Re: Postponing the Trac move

Hi Charlie,

2008/6/16 Charlie Clark <charlie@xxxxxxxxxxxxxx>:
> I can't imagine the DB being big enough to cause problems yet even if
> Postgres' default configuration is a bit mean. Is auto-vacuum running?
> VACUUM ANALYZE is always worth running as it updates the query planner to
> reflect the current database structure. Otherwise EXPLAIN on any of the
> queries that seem to be running slow is helpful. If this really does need
> looking at then I might be able to help at the weekend.

Well, it turned out to be database-related, but not the database
itself. The problem was in the the 'pyPgSql' binding. I have replaced
it with the 'psycopg2' database binding, and the roadmap, query and
timeline pages feel so much faster. I also haven't seen any more
errors logged in Trac's log.

Only the 'ticket details' option on the Timeline page still takes
longer than on the old server, but I will get to that.

I think I nailed it. Thanks for the help offer!

Niels
-----------------------------------------------------------------------
haiku-web@xxxxxxxxxxxxx - Haiku Web & Developer Support Discussion List

Other related posts: