View Issue Details

IDProjectCategoryView StatusLast Update
0005045SymmetricDSTaskpublic2022-07-27 15:19 Assigned Toelong  
Status closedResolutionfixed 
Product Version3.12.10 
Target Version3.13.6Fixed in Version3.13.6 
Summary0005045: Errors in "ON CONFLICT " - need a new parameter
DescriptionI'm getting this error on my log:
ERROR: ON CONFLICT does not support deferrable unique constraints/exclusion constraints as arbiters.

This is caused by the "ON CONFLICT DO NOTHING" at the end of insert statements.

Our database have a lot of tables with unique constraints wich have the DEFERRED type.

Can we have a parameter to disabel the use of "ON CONFLICT DO NOTHING"?

Database version:
PostgreSQL 11.5 on x86_64-pc-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-11), 64-bit

Steps To Reproducecreate a table with a constraint like:

tries to activate the data sync and receives the error:

ManageIncomingBatchListener - Failed to load batch xxxxxxxx org.jumpmind.db.sql.SqlException: ERROR: ON CONFLICT does not support deferrable unique constraints/exclusion constraints as arbiters
    at org.jumpmind.db.sql.AbstractSqlTemplate.translate(
    at org.jumpmind.db.sql.AbstractSqlTemplate.translate(
    at org.jumpmind.db.sql.JdbcSqlTransaction.addRow(
    at org.jumpmind.symmetric.model.ProcessInfoDataWriter.write(
    at org.jumpmind.symmetric.service.impl.DataLoaderService$LoadIntoDatabaseOnArrivalListener$
    at org.jumpmind.symmetric.service.impl.DataLoaderService$LoadIntoDatabaseOnArrivalListener$
    at java.util.concurrent.ThreadPoolExecutor.runWorker(
    at java.util.concurrent.ThreadPoolExecutor$
Caused by: org.postgresql.util.PSQLException: ERROR: ON CONFLICT does not support deferrable unique constraints/exclusion constraints as arbiters
    at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(
    at org.postgresql.core.v3.QueryExecutorImpl.processResults(
    at org.postgresql.core.v3.QueryExecutorImpl.execute(
    at org.postgresql.jdbc.PgStatement.executeInternal(
    at org.postgresql.jdbc.PgStatement.execute(
    at org.postgresql.jdbc.PgPreparedStatement.executeWithFlags(
    at org.postgresql.jdbc.PgPreparedStatement.executeUpdate(
    at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(
    at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeUpdate(
    at org.jumpmind.db.sql.JdbcSqlTransaction.executePreparedUpdate(
    at org.jumpmind.db.sql.JdbcSqlTransaction.addRow(
Additional Informationrelated to the task 4975
same solution
TagsNo tags attached.


related to 0005341 closedelong Add system property to control use of "on conflict" on Postgres 


There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2021-06-29 19:08 New Issue
2022-07-27 15:16 elong Relationship added related to 0005341
2022-07-27 15:19 elong Assigned To => elong
2022-07-27 15:19 elong Status new => closed
2022-07-27 15:19 elong Resolution open => fixed
2022-07-27 15:19 elong Fixed in Version => 3.13.6
2022-07-27 15:19 elong Target Version => 3.13.6