Robert L Mathews schrieb:
(The same goes for bug 518: OTRS is almost unusable with PostgreSQL as the backend with a large number of tickets, so I submitted a patch that fixes the schema to speed up OTRS dramatically and make OTRS work properly. But the patch appears to be languishing and is in danger of getting out of date so that it doesn't apply cleanly any more.)
ACK, ACK, ACK! When it comes to a few 1000 tickets, a PostgreSQL database is merely not usable anymore due to the schema used. I changed my schema without a problem the last days and am experiencing a great improvement in queriying the db. Durations of the queries are lowered to a third in general, at least for the cost-intensive ones. I highly recommend EVERYONE using a PostgreSQL database applying the patch - you WILL run into trouble after a time - believe me, I have seen it. The OTRS team may hereby feel urged to acknowledge the work of Robert L. Mathews and implement his patches. Additionally OTRS should provide a script to convert an existing PG database to a new, 'integered' version. While we are at it: What about a new module taking names/ids of SQL queries and a few params to perform instead of the text of real queries. Designed that way, we could be able to build high/efficient query modules based on the database used. Just my .02, Robert Kehl PS: If you feel you need assistance in tuning your PostgreSQL database the way described above, contact me via PM or via http://roknet.de/contact