Liquibase Redshift v4.30 - Error executing SQL SELECT * FROM public.databasechangelog ORDER BY DATEEXECUTED ASC, ORDEREXECUTED ASC: ERROR: current transaction is aborted, commands ignored until end of transaction block

General Discussion
1

We’re getting the below issue on Liquibase v4.30 with Redshift. Same changelogs work when using v4.27 before. extensions are also placed correctly.

  • /usr/bin/internal/lib/liquibase-redshift-4.30.0.jar
  • /usr/bin/internal/lib/redshift-jdbc42-2.1.0.30.jar
Starting Liquibase at 18:34:36 using Java 21.0.5 (version 4.30.0 #4943 built at 2024-10-31 17:00+0000)
[2024-12-18 18:34:38] INFO [liquibase.ui] ERROR: Exception Details
ERROR: Exception Primary Class:  RedshiftException
[2024-12-18 18:34:38] INFO [liquibase.ui] ERROR: Exception Primary Class:  RedshiftException
ERROR: Exception Primary Reason:  ERROR: current transaction is aborted, commands ignored until end of transaction block
[2024-12-18 18:34:38] INFO [liquibase.ui] ERROR: Exception Primary Reason:  ERROR: current transaction is aborted, commands ignored until end of transaction block
ERROR: Exception Primary Source:  Redshift 8.0.2
[2024-12-18 18:34:38] INFO [liquibase.ui] ERROR: Exception Primary Source:  Redshift 8.0.2
2

I am facing the same issue. did you have a work around for this?

3

in the error details, is it showing any details about failed query?

4

I, too am getting this same error.

I created a Stack Overflow question with some additional detail:
https://stackoverflow.com/questions/79611168/liquibase-redshift-setup-current-transaction-is-aborted-error

5

could you please try this after copying liquibase-redshift-4.28.jar instead of
liquibase-redshift-4.31.1.jar. ie.. remove liquibase-redshift-4.31.1.jar and copy liquibase-redshift-4.28.jar

6

Thank you for the suggestion to downgrade the extension! While it didn’t solve the problem, it did lead to a solution.

Downgrading the liquibase-redshift extension to 4.28.0 did not solve the problem with liquibase 4.31.1. But I downgraded liquibase from 4.31.1 all the way to 4.28.0-1 and tried running liquibase at each version. I got the same error running this extension with liquibase versions > 4.28. After downgrading liquibase to 4.28.0-1 it worked! One interesting thing to note though is that with liquibase version 4.31.1 I was using extension version 4.28.0 that I had downloaded to

opt/liquibase/lib

  • which resulted in the same error. However, after downgrading liquibase, and running a

liquibase --version

command, I noticed the location of the liquibase redshift extension had changed to

/usr/bin/lib

In any case, it looks as though I am running liquibase version 4.28.0-1 and liquibase-redshift extension version 4.31.1 and it works.

I am using this as a proof-of-concept project hoping to integrate this into our workflow. However, I am working in a heavily regulated field and running an older version of liquibase (or any software for that matter) poses a compliance risk. Do you have any idea when this issue could be resolved in the later versions of liquibase?