Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to PostgreSQL 17 #1936

Merged
merged 2 commits into from
Jan 30, 2025

Conversation

sgillespie
Copy link
Contributor

@sgillespie sgillespie commented Jan 27, 2025

Description

Add support for PostgreSQL 17. Note that for static building, we still need pg16 for the time being

Checklist

  • Commit sequence broadly makes sense
  • Commits have useful messages
  • New tests are added if needed and existing tests are updated
  • Any changes are noted in the changelog
  • Code is formatted with fourmolu on version 0.10.1.0 (which can be run with scripts/fourmolize.sh)
  • Self-reviewed the diff

Migrations

  • The pr causes a breaking change of type a,b or c
  • If there is a breaking change, the pr includes a database migration and/or a fix process for old values, so that upgrade is possible
  • Resyncing and running the migrations provided will result in the same database semantically

If there is a breaking change, especially a big one, please add a justification here. Please elaborate
more what the migration achieves, what it cannot achieve or why a migration is not possible.

@sgillespie sgillespie marked this pull request as ready for review January 27, 2025 20:01
@sgillespie sgillespie requested a review from a team as a code owner January 27, 2025 20:01
@rdlrt rdlrt mentioned this pull request Jan 28, 2025
15 tasks
@sgillespie sgillespie requested a review from a team as a code owner January 28, 2025 15:13
@@ -24,6 +24,10 @@
url = "github:IntersectMBO/cardano-haskell-packages?ref=repo";
flake = false;
};
# Note[PostgreSQL 17]: This is a workaround to get postgresql_17 from nixpkgs. It's
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we could maybe create an issue and link it here so we can track it being done

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point, we had the original discussion here: #1875

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sweet if that will jog memories then ✅

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sweet if that will jog memories then ✅

Do you think we should create another issue, just repurpose #1875 above?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

totally up to you, new issue always helps with "throughput"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, I just renamed it. I think a whole new ticket would make it a blatant duplicate

@sgillespie sgillespie merged commit cea19a3 into IntersectMBO:master Jan 30, 2025
10 of 11 checks passed
@sgillespie sgillespie deleted the feature/postgres-17 branch January 30, 2025 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants