On Wed, 2006-08-09 at 18:09 -0400, Gary Oberbrunner wrote: > zdennis wrote: > > Russ Brown wrote: > >>> On Wed, 2006-08-09 at 14:00 -0400, Gary Oberbrunner wrote: > >>>> Hershel Robinson wrote: > >>>>> As far as DB support, we know and use MySQL. Presently 4.1 but we plan > >>>>> to upgrade to 5.1 as soon as it is released (a matter of months it > >>>>> seems, according to MySQL support). > >>>> My humble opinion as a trac user: trac only uses its db to keep track of > >>>> things internal to its operation (the wiki, tickets, etc.). Unless you > >>>> REALLY > >>>> care (e.g. need to manipulate trac's tickets without using its own API), > >>>> you > >>>> should just use the default sqlite db, I think. We use mySQL for > >>>> everything > >>>> else at our site, but are totally happy with the default sqlite back end > >>>> in > >>>> trac. It is fast, reliable, and basically invisible. > >>>> > >>> It does however also suffer from database-level locking, so if you start > >>> use Trac concurrently a lot you'll start to see 'database locked' errors > >>> more and more (as we are ATM). > >>> > > > > Gary, you're stating you get database lock errors with the sqlite backend, > > not mysql correct? i just want to clarify since it may > > not be immediately apparent in thread archives. > > I've never seen a db lock (well, unless I was in the middle of a trac-admin > resync :-)), and we've only ever used sqlite. I think it was Russ getting > those. >
Yes, it was me. I've done tests with the the PostgreSQL backend (which will scale concurrency to silly levels). Seems perfectly stable, but I've not had time to do an 'official' migration as yet. > -- Gary > _______________________________________________ > Trac mailing list > [email protected] > http://lists.edgewall.com/mailman/listinfo/trac _______________________________________________ Trac mailing list [email protected] http://lists.edgewall.com/mailman/listinfo/trac
