I have a multisite instance in which a bunch of databases failed to migrate because PG::DuplicateColumn: ERROR: column "bookmarkable_id" of relation "bookmarks" already exists maybe I should go delete that column from that table in those databases? looks like it was because previous migra…

@martin any ideas, may be related to the recent refactors?

Sorry for the false alarm. I so hate when I do this. The issue was that I had SKIP_POST_DEPLOYMENT_MIGRATIONS: 1 set and then didn’t run multisite:migrate. After I did a `SKIP_POST_DEPLOYMENT_MIGRATIONS=- multisite:migrate’ I was then able to bootstrap. I just need to fix my tooling for multisite …

But strange. Recovering from failed/partially applied upgrade seems to have the same issue and it appears to be a standard install .

I would’ve replied to this post, but figured it was the same symptom of a different problem. :slight_smile: I admittedly don’t know enough to confirm either way…

Seems to be related to DEV: Re-add polymorphic bookmark columns (#16261) · discourse/discourse@8040b95 · GitHub This commit is a redo of 2f1ddadff7dd47f824070c8a3f633f00a27aacde which we reverted because it blew up an internal CI check. I looked into it, and it happened because the old migration…

Any update on this? Mine is coming up with the same issue. How would i copy this git into my discourse?

Falha ao prestar atenção às SKIP POST DEPLOYMENT MIGRATIONS causa problemas

Suporte

pfaffman (Jay Pfaffman) Março 24, 2022, 9:28pm 4

Mas estranho. Recovering from failed/partially applied upgrade parece ter o mesmo problema e parece ser uma instalação padrão.

Tópico		Respostas	Visualizações
DuplicateColumn and multisite:migrate failed Bug	5	865	19 de Abril de 2022
Recovering from failed/partially applied upgrade Self-hosting	49	2692	12 de Agosto de 2022
DB migration version 20210714173022 fails when having skipped post deployment migrations before Bug	2	561	29 de Setembro de 2021
Update failed for some reason? Self-hosting	1	698	30 de Março de 2022
New installation fails on migration Bug	4	1166	14 de Abril de 2020

Falha ao prestar atenção às SKIP POST DEPLOYMENT MIGRATIONS causa problemas

Tópicos relacionados