We use postgresql for 2 internal tracs on 0.12, one is pretty large (6,000 tickets; at least 50 ticket updates per workday and hundreds of wiki pages). The only issues we've had have been occasional plugins that have like one or two lines of SQL that's invalid for Postgresql. We also had one semi-frustrating error message that's since been fixed, http://trac.edgewall.org/ticket/9400. Otherwise it's been a very satisfying experience.
On Wed, Oct 20, 2010 at 4:28 AM, Cooke, Mark <mark.co...@siemens.com> wrote: >> I'm looking into switching from sqlite to postgreSQL as our >> backend. I'm assuming this shouldn't be an issue, but does >> anyone have any good/bad experiences to share? >> >> Ideally I'd like to hear from people using bleeding edge 0.12 >> saying "yep, works just fine" :-) >> > We're still on 0.11 and I started with postgreSQL so did not convert but > I have moved from trial desktop to server with no issues at all. We're > (now) on Windows Server 2003 if that's relevant. > > ~ mark c > > -- > You received this message because you are subscribed to the Google Groups > "Trac Users" group. > To post to this group, send email to trac-us...@googlegroups.com. > To unsubscribe from this group, send email to > trac-users+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/trac-users?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-us...@googlegroups.com. To unsubscribe from this group, send email to trac-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/trac-users?hl=en.
