Issue with `change_column_null` on Neon PostgreSQL during Docuseal Migrations

[fredhii]

trafficstars

Hi guys,

I'm running into a problem when using Neon PostgreSQL (version 15, but seems to apply to other Neon versions too) as the database for Docuseal. During the migrations, some of them fail specifically when calling change_column_null.

For example, this line in a migration:

change_column_null(:submissions, :slug, false, nil)

throws the following error:

PG::InFailedSqlTransaction: ERROR: current transaction is aborted, commands ignored until end of transaction block

The strange thing is this only happens on Neon. If I use the default postgres:15 image provided in the docker-compose.yml, everything works smoothly and all migrations complete without issues.

Setup

Docuseal version: 1.9.8 DB: Neon PostgreSQL (v15) Works fine with: Dockerized Postgres 15

What seems to be the issue It appears that change_column_null is behaving differently on Neon. Possibly related to how it handles empty tables or transaction blocks internally. Since my tables were empty, I expected it to succeed just like with the Docker version.

Would love some input or a workaround for Neon users. Thanks for the awesome tool!

Cheers!

[rrrodzilla]

Exact same issue here.

[dmitrydrynov]

The same