On 10/20/2010 12:57 AM, Andy Baker wrote:
Hi All,
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?
I recently did a similar migration, using Postgres 0.11.6. The core Trac
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
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
Hi,
Although my Tracs are not heavily used I use PostgreSQL as my backend
and I do not experience any problems (Debian Squeeze AMD64) . The
installation procedure as described works as described
(http://trac.edgewall.org/wiki/DatabaseBackend).
--
Met vriendelijke groeten,
Joost Kraaijeveld
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
Hi All,
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 :-)
Cheers
Andy
--
You
