vmware / vmware/photon

PostgreSQL packages need an exit path for major upgrades

Open
#431 3 comments 0 reactions 1 assignee View on GitHub

@ppadmavilasom is already working on this.

Since Nov 15, 2016.

Dominant language
C
Stars
3.2k
Forks
692
PR merge metrics
No merged PRs in 30d

Description

As of now, PostgreSQL binaries are installed in /bin/, which completely ignore the fact that major version upgrades with pg_upgrade need to have both the old and new versions coexist together. Other Linux distributions, be they ArchLinux, Fedora, Ubuntu give users the possibility to install past major version binaries, and I suggest that we do that as well.

After looking at that, I would suggest the following (similar to Archlinux): addition of a package postgres-upgrade-X.Y that deploys past versions of Postgres as /opt/pgsql-X.Y (for 9.4 you get /opt/pgsql-9.4), while the latest version is still available in /bin/. Providing a

The latest packages need to be upgraded to 9.5 as well. I don't mind sending patches to address that as need be. As PostgreSQL deployments on Photon do not deploy any service (I don't think they should by default except if user is willing to do so), there is no actual need to have a default upgrade script in those packages.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.