ShedLock does not work with PostgreSQL JDBC Driver version 42.2.11

[kerdotnet]

1. Which version do you use
   shedlock-spring:4.5.1
2. Which Lock Provider
   shedlock-provider-jdbc-template:4.5.1
3. ShedLock configuration
   lockAtLeastFor = "PT10S",
   lockAtMostFor = "PT120S"

Expected behavior
Shedlock can start without errors

Actual behavior
After an update on the latest PostgreSQL JDBC Driver JDBC 4.2 » 42.2.11 and deployment we found that Shedlock can not start because of error:

org.springframework.transaction.TransactionSystemException: Could not commit JDBC transaction; nested exception is org.postgresql.util.PSQLException: The database returned ROLLBACK, so the transaction cannot be committed. Transaction failure cause is <<ERROR: duplicate key value violates unique constraint "shedlock_pkey"
  Detail: Key (name)=(documentProcessingJob) already exists.>>
	at org.springframework.jdbc.datasource.DataSourceTransactionManager.doCommit(DataSourceTransactionManager.java:334)
	at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:744) 

[lukas-krecan]

Thanks for reporting, it's indeed the case. Will take a look at it.

[lukas-krecan]

Caused by pgjdbc/pgjdbc#1729

[lukas-krecan]

Can be fixed by setting raiseExceptionOnSilentRollback=false connection property. Frankly, I think it's a bug in Postgres SQL driver and I will wait before considering implementing a workaround.

[kerdotnet]

Thanks for the information!

[davecramer]

This is NOT. bug in the driver. This was done on purpose as the SQL Standard requires that errors be thrown if the transaction cannot be committed

[lukas-krecan]

Fixed in 4.5.2

[pavel-kiper]

I am just going to leave some keywords here for someone googling this issue in future:

ShedLock, Spring boot upgrade, PostgreSQL.

We have upgraded Sprint Boot from v2.1 to v2.2 and got

Detail: Key (name)=(myclass_mymethod) already exists.>>
	at org.springframework.jdbc.datasource.DataSourceTransactionManager.doCommit(DataSourceTransactionManager.java:335)
...
Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "shedlock_pkey"
  Detail: Key (name)=(myclass_mymethod) already exists.
	at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2578)
...
	at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140)

[davecramer]

FWIW PgJDBC 42.2.12 has been released and this change has been reverted. We (the PgJDBC group are recommending that 42.2.11 not be used and use 42.2.12 instead.
Also note that we will be releasing 42.3.0 with the above mentioned change.