I'm replicating a postgreSQL 7.3.2 database using erserver 1.2 that contains Hibernate 2.1 and am having constraint issues.

It seems that erserver does not apply the changes to the standby database in the same order that they are done to the online, so we were getting constraint violations. I fixed it by dropping the Hibernate constraints on the standby database server and re-applying them when it becomes the online. That seems to work just fine.

But I'm wondering if there is a better way. Can Hibernate be configured to create its constraints with the 'DEFERRABLE" property, which would ask postgres to hold off applying constraints until the end of the current transaction? That may allow me to not have to monkey around with the constraints as I have been.