From Jo (seeds.no)

As you can see we decide to send all queries inside a transaction to the
master database server. The problem occurs on creating new objects/versions
where an version is created on the master server, then a query tries to get
this object right after but is redirected to the slave (which haven’t had
time to update yet). This problem might occur several places with
transactions, but this patch fixes it all. A problem with the patch might be
if you have a (stupid) transaction that only contains selects. Then this
will be sent to the master server and might slow the query a little bit
down.

From pek (ez.no)

Let's also hope that ezp has transactions everywhere they are needed.

Steps to reproduce

The problem occurs on creating new objects/versions
where an version is created on the master server, then a query tries to get
this object right after but is redirected to the slave (which haven’t had
time to update yet)