OTRS with PostgreSQL Cluster

[hellproducts]

Hello.

Recently, we're migrated from MySQL to PostgreSQL and have set up a database cluster on the Postgres ORDBMS. The setup is with one master and two slaves and a pgpool in front of them. Data is written only into the master and read from all the 3 servers.
In the test environment everything went smooth, but when we made the changes into production as well, we started to confront with lots of errors from OTRS saying after random tickets created that it couldn't find a ticket / article id.

After some investigations, we've come to the conclusion that on some occasions, after inserting a new ticket, OTRS would switch to one of the slaves when creating the article or the entry in the ticket_history table. Since the servers do not have enough time to sync between, it's logical that on the slave the new ticket doesn't exist yet, hence our missing id errors.

My question is whether you can direct me into making OTRS run in transactional mode.

Thank you very much in advance.

[crythias]

This doesn't sound like something that you should be requesting from a "free" support ... if your configuration is that complex, I'd strongly suggest professional support.