Upgrade to Postgres 11.3 once it's out

[vito]

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]

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]

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

[vito]

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

[cirocosta]

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]

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

[vito]

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