Mysql vs pgsql (in regards to lock contention)

RT Users
1

Hi.

Just wondering if anyone has done any tests regarding how mysql goes vs
pgsql with RT2, in particular in regards to locking.

I’m currently using mysql, which only seems to support table level locking,
and this causes problems when all our staff and in and hitting RT2 hard.
pgsql supports row locking, which in theory, should have less locking
contention. Anyone tested this??

Anyone using pgsql on a system with a few staff members (we have 15-20
staff using rt2 at a time) getting these locking issues?

Regards.
Matthew Watson
Development, Netspace Online Systems
mwatson@netspace.net.au

2

Hi Matthew,

Sorry for a reply that doesn’t directly answer your question, but…

If you have the time/resources/desire/etc., you could try installing MySQL
4.0 alpha which supports row level locking and import your RT2 database into
it to see how it performs. It seems like you could have 4.0 run on a
different port and then change your config.pm to the new database,
stop/start apache, and start some benchmarking.

Chris

3

Hi,

No really keen to try 4.0a , our rt2 system needs to be up alot, any idea
of the stablility of 4.0a? Do you know if ALL tables support row level? I
read somewhere about dbd tables supporting it.

4

Regarding this…

Anyone tried mysql with InnoDB tables and RT2? InnoDB supports
transactions and row locking (which is what I want) , so i’m not sure how
rt2 will handle is just slotted in? Anyone?

Mat.

5

|+ Anyone tried mysql with InnoDB tables and RT2? InnoDB supports
|+ transactions and row locking (which is what I want) , so i’m not sure how
|+ rt2 will handle is just slotted in? Anyone?

I can’t comment on RT itself, but I have played with InnoDB tables with
other software that I have written in house just for that feature, and
saw no problems. I didn’t have to change any of my code, or make any
huge changes to the database itself, other than to compile InnoDB
support, and create the tables as InnoDB.

-darrin