[rt-users] Size of the database.

Darin Perusich Darin.Perusich at ctg.com
Mon Oct 22 08:26:11 EDT 2012

While my RT installation is tiny, 1gb in comparison, and migrating from 
mysql to postgres was fairly straight forward. I used the rt-mysql2ps 
script at the time with success. I have migrated other databases ranging 
in size from 1gb and 20gb using py-mysql2pgsql with great success as 
well. You mileage may very but these are a few options to try.


On 10/19/2012 10:57 AM, Tim Cutts wrote:
> On 19 Oct 2012, at 15:40, Albert Shih <Albert.Shih at obspm.fr> wrote:
>> Hi all,
>> When I start RT I make a big mistake, I choose mysql as database (instead
>> postgresql). I loose the feature to search inside of the ticket. But well
>> it's the past.
> You can implement full text searches by using Sphinx.  It's a bit of a faff, but it can be made to work.  I have it working here.  And presumably we'll be able to do it without Sphinx once RT works properly with MySQL 5.6, so don't despair.
>> I knwon it's very hard to change the database. As it's very hard to decide if
>> I should break everything and make a new RT+postgresql.
>> What I understand more the size of the database grow up more it's better to
>> run postgresql instead of mysql.
>> I would like to known what size of mysql do you have. From what size I
>> shouldn't use mysql ?
>> When I say mysql I mean «one standard» not some clustering/load-balancing installation.
> I haven't seen a problem here yet, and I'm running MySQL 5.1 and Sphinx 2.0.5 on a VM with 16GB of RAM and 2 virtual CPUs.  Database size is 300,000 tickets, about 33GB on disk.  I run the RT web interface on a separate VM.
> Like you, I wish I'd chosen Postgres instead, but I've tried migrating and it's just too painful.  I'm betting on MySQL 5.6 fixing a lot of the performance issues, and giving us proper full text searches into the bargain.  Fingers crossed.
> Tim

Darin Perusich
Email: Darin.Perusich at ctg.com
Office: 716-888-3690
The information transmitted is intended only for the person or entity to which
it is addressed and may contain confidential and/or privileged material. Any
review, retransmission, dissemination or other use of, or taking of any action
in reliance upon, this information by persons or entities other than the
intended recipient is prohibited. If you are not the intended recipient of this 
message, please contact the sender and delete this material from this computer.

More information about the rt-users mailing list