[JIRA] (HHH-16071) javax.persistence.lock.timeout does not fully work with PostgreSQL
by Gavin King (JIRA)
Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *commented* on HHH-16071 ( https://hibernate.atlassian.net/browse/HHH-16071?atlOrigin=eyJpIjoiNzg2NW... )
Re: javax.persistence.lock.timeout does not fully work with PostgreSQL ( https://hibernate.atlassian.net/browse/HHH-16071?atlOrigin=eyJpIjoiNzg2NW... )
As per discussion on Zulip, this is not a bug, since:
* JPA query hints are optional , and
* Postgres itself does not support statement-level lock timeouts.
Again, as per the discussion there, we think it's in principle possible to implement this using set statements, but that’s not, IMO, a terribly natural implementation, involving multiple round trips to the database for a single query.
So I would sat that, aside from not being a bug, this is also a very low-priority improvement.
( https://hibernate.atlassian.net/browse/HHH-16071#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16071#add-comment?atlOrigin=ey... )
Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=EmailN... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100215- sha1:b88b0a4 )
1 year, 11 months