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 Postgres 11.3 once it's out #50

Closed
vito opened this issue May 6, 2019 · 6 comments

Comments

Projects
None yet
4 participants
@vito
Copy link

commented May 6, 2019

Hi there! We on Concourse team are affected by a bug present in Postgres 11.2 that causes Postgres to lock up until it's force-restarted. The fix is expected to be in 11.3, which should be out this week (on May 9) according to their roadmap.

We're at a point where we're evaluating downgrading to to Postgres 9.6, switching to CloudSQL, or just waiting on 11.3 and force-restarting our Postgres whenever it falls over. The last item involves the least amount of work, so I figured I'd open this preemptively in hopes y'all have bandwidth to publish a new release shortly after it's out. 🙂

Alternatively, we may be able to work-around the bug by disabling parallel queries, so no rush.

Thanks!

@cf-gitbot

This comment has been minimized.

Copy link
Collaborator

commented May 6, 2019

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/165824790

The labels on this github issue will be updated when the story is started.

@valeriap

This comment has been minimized.

Copy link
Member

commented May 7, 2019

@vito Thanks for raising it. We will upgrade to 11.3 once published.

@cf-gitbot cf-gitbot added scheduled and removed unscheduled labels May 7, 2019

@vito

This comment has been minimized.

Copy link
Author

commented May 9, 2019

Looks like it just came out: https://www.postgresql.org/docs/11/release-11-3.html

@cirocosta

This comment has been minimized.

Copy link

commented May 9, 2019

Fix race conditions in management of dynamic shared memory (Thomas Munro)
These could lead to “dsa_area could not attach to segment” or “cannot unpin a segment that is not pinned” errors.

🙌

@valeriap

This comment has been minimized.

Copy link
Member

commented May 11, 2019

@vito postgres release v37 has been released with the upgrade to PostgreSQL 11.3.

@vito

This comment has been minimized.

Copy link
Author

commented May 13, 2019

@valeriap Thanks! Looks like our pipeline deployed it already. I'll close this out. 👍

@vito vito closed this May 13, 2019

@cf-gitbot cf-gitbot removed the accepted label May 13, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.