Skip to content

Upgrade postgres 15.8 #5420

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Upgrade postgres 15.8 #5420

wants to merge 2 commits into from

Conversation

annagav
Copy link
Contributor

@annagav annagav commented Apr 9, 2025

What are the relevant tickets?

Fix https://github.com/mitodl/hq/issues/6579

Description (What does it do?)

Upgrade postgres 15.8

How can this be tested?

Everything should work as expected

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Hello @annagav, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

This pull request upgrades the Postgres version in the docker-compose.yml file from 12.7 to 15.8. It also adds a volume for the database to persist data across container restarts. The stated intent is to address issue #6579.

Highlights

  • Postgres Version Upgrade: The Postgres version has been upgraded from 12.7 to 15.8 in the docker-compose.yml file.
  • Database Volume Addition: A new volume db-data has been added to the docker-compose.yml file to persist the Postgres database data.

Changelog

  • docker-compose.yml
    • Upgraded the Postgres image version from 12.7 to 15.8 on line 23.
    • Added a volume mount for the db service to persist data at /var/lib/postgresql/data on lines 28-29.
    • Added a db-data volume definition on line 132.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.


A database's upgrade,
To newer version's stage,
Data persists now,
No more data pow,
Volumes save the day, hooray!

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request upgrades the Postgres version in the docker-compose file. The changes seem straightforward and necessary for keeping the application up-to-date with security patches and new features. The addition of a volume for the database is also a good practice for persisting data.

Merge Readiness

The changes appear to be correct and necessary. However, it's crucial to ensure that all application components are compatible with the new Postgres version. Since the description mentions 'Everything should work as expected', it's assumed that compatibility testing has been performed. Given the absence of any critical or high severity issues, the pull request seems ready for merging, contingent upon successful compatibility testing. I am unable to directly approve the pull request, and other reviewers should review and approve this code before merging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant