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

Any plans to update the postgres release used by the forge. #6

Open
elric392 opened this issue Jul 18, 2019 · 3 comments
Open

Any plans to update the postgres release used by the forge. #6

elric392 opened this issue Jul 18, 2019 · 3 comments

Comments

@elric392
Copy link

Currently the forge utilizes the v2.0.0 of the postgres release. While the latest is v3.1.5 released back on Jan 30th.

@jhunt
Copy link
Contributor

jhunt commented Jul 18, 2019

All that is new in the v3.x series of the upstream postgres BOSH release is support for HA via haproxy + keepalived.

What I would like to do is provide some means of deploying recent vintages of PostgreSQL (they've gone to 11 I hear), and allow the Blacksmith operator to select.

@antitux
Copy link

antitux commented Aug 5, 2019

The 3.15 series also still supports the stream-replicated cluster configuration (Where the bootstrap server serves as the master).
Reference:
https://github.com/cloudfoundry-community/postgres-boshrelease/blob/3212dafc0dc1b5b2a11df258fe3ffefc02ce3560/jobs/postgres/spec#L96

I'm actually working on testing this because I need to upgrade to a newer version on a client foundation. I'll cut a PR if I can get it working sanely.

@jhunt jhunt self-assigned this Aug 6, 2019
@jhunt
Copy link
Contributor

jhunt commented Feb 2, 2020

@antitux did you ever get this working sanely?

@jhunt jhunt removed their assignment Feb 10, 2021
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

No branches or pull requests

3 participants