Upgrade Task failures for Postgres backed cluster on versions 1.37.3 Enterprise about n8n HOT 5 CLOSED

I'm wondering if this is a new bug, or a race condition with various containers trying to run migrations.
If you restart all containers, do you still see this error?

from n8n.

I think you are correct on the Drop column error. The nodeAccess column doesn't appear to be in the schema any longer.

We are still seeing the other error on repeated restarts.

from n8n.

Those errors look like the postgres user being used with n8n doesn't have all the permissions it needs. You could either:

1. run ALTER USER [[DB_USER]] WITH SUPERUSER; as a superuser to grant the db user all the permissions - not recommended.
2. run CREATE EXTENSION IF NOT EXISTS "uuid-ossp"; as a superuser (in the n8n database) to create the UUID extension, and then ignore the permission warning (if it still continues to show up). - not recommended.
3. run GRANT CREATE ON DATABASE [[DB_NAME]] to [[DB_USER]]; as a superuser to grant correct permissions to the user on the n8n DB - recommended.

from n8n.

This is either new or it was missed in your documentation for postgres permissions. Please have your tech writers update the documentation.

Thanks for sorting this out. I'll close this since all issues are resolved.

from n8n.

I believe this specific bit is documented here.
If GRANT ALL PRIVILEGES ON DATABASE n8n-db TO n8n-user; is run once before the app is started, you should not see this issue.

But, if you think we need to add more details on that page, please let us know.

from n8n.