If a pgsql dba is needed, I can step up to that.<br><br><div class="gmail_quote">On Fri, Jun 19, 2009 at 7:01 AM, Howard Butler <span dir="ltr"><<a href="mailto:hobu.inc@gmail.com">hobu.inc@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im"><br>
On Jun 19, 2009, at 6:35 AM, Paolo Cavallini wrote:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi all.<br>
Are there any plans to solve the horrible slowness and tendency to<br>
return errors of the trac? We are working a lot on the qgis trac, but it<br>
is a real pain, to the point that we are kind of thinking to write an<br>
interface to the trac caching the results for quick search (what a waste<br>
of time).<br>
</blockquote>
<br></div>
Paolo,<br>
<br>
The problem is a volunteer manpower one. There are definitely plans, it is just a matter of finding the time in which we can shut down and implement them. I'm sorry that I can't give a better answer than that. If you have time you can devote to the effort, please join the SAC list, and we can get you up to date with all of the issues. We would happily add another administrator of Trac if you have lots of familiarity with it (especially mod_python, mod_wsgi and sqlite{1,3} vs external db like pg).<br>
<font color="#888888">
<br>
Howard_______________________________________________</font><div><div></div><div class="h5"><br>
Discuss mailing list<br>
<a href="mailto:Discuss@lists.osgeo.org" target="_blank">Discuss@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/discuss" target="_blank">http://lists.osgeo.org/mailman/listinfo/discuss</a><br>
</div></div></blockquote></div><br>