mirror of
https://github.com/fosrl/pangolin.git
synced 2026-05-22 09:32:36 -05:00
[GH-ISSUE #1701] Upgrade Issues 1.11.0 Postgres Image #1982
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ex-aequo-et-bono on GitHub (Oct 19, 2025).
Original GitHub issue: https://github.com/fosrl/pangolin/issues/1701
Describe the Bug
Hi all, am having issues with updating the the postgres version of the image to 1.11.0.
Error running migrations: DrizzleQueryError: Failed query: ALTER TABLE "orgs" ADD COLUMN "settings" text; params: at NodePgPreparedQuery.queryWithCache (file:///app/node_modules/drizzle-orm/pg-core/session.js:41:15) at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async Object.migration7 [as run] (file:///app/dist/migrations.mjs:1664:5) ... 3 lines matching cause stack trace ... at async file:///app/dist/migrations.mjs:1814:1 { query: 'ALTER TABLE "orgs" ADD COLUMN "settings" text;', params: [], cause: error: column "settings" of relation "orgs" already exists at /app/node_modules/pg-pool/index.js:45:11 at process.processTicksAndRejections (node:internal/process/task_queues:105:5) at async file:///app/node_modules/drizzle-orm/node-postgres/session.js:113:20 at async NodePgPreparedQuery.queryWithCache (file:///app/node_modules/drizzle-orm/pg-core/session.js:39:16) at async Object.migration7 [as run] (file:///app/dist/migrations.mjs:1664:5) at async executeScripts (file:///app/dist/migrations.mjs:1869:9) at async runMigrations (file:///app/dist/migrations.mjs:1828:7) at async run (file:///app/dist/migrations.mjs:1816:3) at async file:///app/dist/migrations.mjs:1814:1 { length: 131, severity: 'ERROR', code: '42701', detail: undefined, hint: undefined, position: undefined, internalPosition: undefined, internalQuery: undefined, where: undefined, schema: undefined, table: undefined, column: undefined, dataType: undefined, constraint: undefined, file: 'tablecmds.c', line: '7478', routine: 'check_for_column_name_collision' }Environment
To Reproduce
Attempt upgrade with Postgres Image
Expected Behavior
Clean upgrade
@github-actions[bot] commented on GitHub (Nov 3, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@ex-aequo-et-bono commented on GitHub (Nov 7, 2025):
Hi, this is still an issue.
@oschwartz10612 commented on GitHub (Nov 8, 2025):
@ex-aequo-et-bono do you have a old backup to fall back to? Its strange it thinks that column already exists. Is it possible you tried to update once but fell back to the old version? That would mean the columns are still there.
If its out of sync with the migrations and you can not fall back to a backup config I am sad to say the best solution may be to reinstall. You could try this but be warned it might not work...
You could also try an upgrade to 1.12.x and see if it works?
@github-actions[bot] commented on GitHub (Nov 23, 2025):
This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.
@github-actions[bot] commented on GitHub (Dec 8, 2025):
This issue has been automatically closed due to inactivity. If you believe this is still relevant, please open a new issue with up-to-date information.