coop-cloud/discourse
0
0
Fork 2
Code Issues 10 Pull Requests 1 Projects Releases Wiki Activity

fix(db): make pg_upgrade 13->17 idempotent and use the cluster's real install user #15

Merged
notplants merged 1 commits from idempotent into main 2026-06-16 18:36:01 +00:00
Conversation 0 Commits 1 Files Changed 2 +29 -11
notplants commented 2026-06-16 18:33:30 +00:00
Owner
Copy Link

while deploying the previous PR (#14) to an older client, ran into an issue with the bespoke postgres update script (the install user used to originally create the database was different than expected)

this PR fixes the issue, so I am merging now, in case anyone upgrading from a very old deployment also has this issue

but it raises the desire to get off of this bespoke upgrade script and instead use pgautoupgrade. as mentioned in the other PR, this is unfortunately currently incompatible with pgvector or any of the existing published discourse images that I know of (the best solution may require publishing our own discourse image that uses pgautoupgrade and does not depend on pgvector)

however, merging this for now as this is the most immediate fix to keep the upgrade path seamless

while deploying the previous PR (https://git.coopcloud.tech/coop-cloud/discourse/pulls/14) to an older client, ran into an issue with the bespoke postgres update script (the install user used to originally create the database was different than expected) this PR fixes the issue, so I am merging now, in case anyone upgrading from a very old deployment also has this issue but it raises the desire to get off of this bespoke upgrade script and instead use pgautoupgrade. as mentioned in the other PR, this is unfortunately currently incompatible with pgvector or any of the existing published discourse images that I know of (the best solution may require publishing our own discourse image that uses pgautoupgrade and does not depend on pgvector) however, merging this for now as this is the most immediate fix to keep the upgrade path seamless
notplants added 1 commit 2026-06-16 18:33:31 +00:00
fix(db): make pg_upgrade 13->17 idempotent and use the cluster's real install user
Some checks failed
continuous-integration/drone/pr Build is failing
Details
a9f08eed28
notplants merged commit 2b28de444d into main 2026-06-16 18:36:01 +00:00
notplants deleted branch idempotent 2026-06-16 18:36:02 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
3wordchant aadil abra-bot ammaratef45 amras Apfelwurm appletalk arjan basebuilder BornDeleuze Brooke carla cas codegod100 coopcloud cyrnel decentral1se dede devydave fauno flancian Frando iexos jade javielico jjsfunhouse jmakdah2 joe-irving kawaiipunk knoflook kolaente lambdabundesverband linnealovespie marlon mayel mirsal moosemower moritz nicksellen notplants oxaliq p4u1 pau pharaohgraphy PhiNatalie renovate-bot ripclap rix rscmbbng sef simon sixsmith stevensting tobias trav val vaznasty virtualboys wolcen wykwit xynosis yksflip
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: coop-cloud/discourse#15
No description provided.
Delete Branch "idempotent"

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?