Skip to content

Upgrade to postgres 14#8518

Merged
night-jellyfish merged 2 commits intomainfrom
brittany/upgrade_to_postgres_14
Jun 1, 2023
Merged

Upgrade to postgres 14#8518
night-jellyfish merged 2 commits intomainfrom
brittany/upgrade_to_postgres_14

Conversation

@night-jellyfish
Copy link
Contributor

🛠 Summary of changes

In #8475, we chose to keep Postgres at version 13 so that it could
match production.

However, when trying to continue on the postgis work, I found that
when installing postgis, brew installs 14 anyway, as a dependency of
postgis. There doesn't seem to be an easy way to tell Brew not to
install 14, or postgis to use 13 instead. This becomes an issue then
when the app is using 13, but postgis is using 14.

I thought it'd be better to change this now than wait for the postgis
work to be ready, as it would potentially stop folks from installing an
extra version of postgres.

There may be another workaround, but after reading a homebrew issue
about versioning issues with postgres and postgis
, which included
suggestions like making your own copy of postgis and changing its
dependencies
, it seemed like upgrading postgres was a
better solution.

While it will mean dev is on a different version than prod, most folks
have been using 14 or even 15, so we don't expect issues to arise.

Brittany Greaner added 2 commits May 31, 2023 16:52
In #8475, we chose to keep Postgres at version 13 so that it could
[match production](https://github.com/18F/identity-devops/blob/33ba02736b37f3a79c50479892a03c6f3e920041/terraform/app/rds-variables.tf#L82).

However, when trying to continue on the `postgis` work, I found that
when installing `postgis`, `brew` installs 14 anyway, as a dependency of
`postgis`. There doesn't seem to be an easy way to tell Brew not to
install 14, or postgis to use 13 instead. This becomes an issue then
when the app is using 13, but `postgis` is using 14.

I thought it'd be better to change this now than wait for the postgis
work to be ready, as it would potentially stop folks from installing an
extra version of postgres.

There may be another workaround, but after reading [a homebrew issue
about versioning issues with postgres and postgis](Homebrew/homebrew-core#86709), which included
suggestions like [making your own copy of `postgis` and changing its
dependencies](Homebrew/homebrew-core#86709 (comment)), it seemed like upgrading `postgres` was a
better solution.

While it will mean dev is on a different version than prod, most folks
have been using 14 or even 15, so we don't expect issues to arise.
Copy link
Contributor

@zachmargolis zachmargolis left a comment

Choose a reason for hiding this comment

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

LGTM

@night-jellyfish night-jellyfish merged commit 407b4fa into main Jun 1, 2023
@night-jellyfish night-jellyfish deleted the brittany/upgrade_to_postgres_14 branch June 1, 2023 16:56
This was referenced Jun 6, 2023
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.

2 participants