I just noticed while doing some migration work to PostgreSQL 9.3, that they now support per-query lock-timeout setting by issues a `SET lock_timeout = <value>;` query in the transaction / backend acquiring the lock. This would be highly beneficial to have dialect support for and will impact the use of pessimistic locking in the JPA EM as well.

I'm opening this ticket hoping someone else may beat me to implementing it. Since having resolved HHH-8365, at least us PG users can recover from a lock not being immediately available in a graceful manner. Having a true configurable timeout would certainly be more ideal.