View Issue Details

IDProjectCategoryView StatusLast Update
0006355SymmetricDSBugpublic2024-04-19 21:00
Reporterelong Assigned Toelong  
Status closedResolutionfixed 
Product Version3.15.0 
Target Version3.15.5Fixed in Version3.15.5 
Summary0006355: Support autosave=always mode on PostgreSQL
DescriptionWhen the PostgreSQL JDBC driver has the URL parameter of autosave=always, it will create a savepoint before each DML statement and rollback to it if it fails. SymmetricDS is using logic of "on conflict do nothing" so there is no exception, then it expects to set a savepoint and try again without "on conflict do nothing" to get the exception. The autosave mode is preventing this from getting an exception, so certain errors can't be automatically resolved, like a unique key exception. Instead, if autosave is used, then there is no need for using "on conflict do nothing" because the transaction is still valid to be used.
Tagsdialect: postgresql


There are no notes attached to this issue.

Related Changesets

SymmetricDS: 3.15 b4810b6c

2024-04-19 20:23:00


Details Diff
0006355: Support autosave=always mode on PostgreSQL Affected Issues
mod - symmetric-db/src/main/java/org/jumpmind/db/platform/postgresql/ Diff File
mod - symmetric-jdbc/src/main/java/org/jumpmind/db/platform/postgresql/ Diff File

Issue History

Date Modified Username Field Change
2024-04-19 20:16 elong New Issue
2024-04-19 20:16 elong Status new => assigned
2024-04-19 20:16 elong Assigned To => elong
2024-04-19 20:16 elong Tag Attached: dialect: postgresql
2024-04-19 20:23 elong Status assigned => resolved
2024-04-19 20:23 elong Resolution open => fixed
2024-04-19 20:23 elong Fixed in Version => 3.15.5
2024-04-19 21:00 admin Changeset attached => SymmetricDS 3.15 b4810b6c
2024-04-23 16:58 admin Status resolved => closed