Hello community, here is the log from the commit of package postgresql94 for openSUSE:Factory checked in at 2019-02-27 21:14:07 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/postgresql94 (Old) and /work/SRC/openSUSE:Factory/.postgresql94.new.28833 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "postgresql94" Wed Feb 27 21:14:07 2019 rev:16 rq:678951 version:9.4.21 Changes: -------- --- /work/SRC/openSUSE:Factory/postgresql94/postgresql94.changes 2018-12-06 12:15:55.237609785 +0100 +++ /work/SRC/openSUSE:Factory/.postgresql94.new.28833/postgresql94.changes 2019-02-27 21:14:13.727160751 +0100 @@ -1,0 +2,11 @@ +Mon Feb 25 13:59:02 UTC 2019 - Reinhard Max <[email protected]> + +- Update to 9.4.21: + * https://www.postgresql.org/docs/9.4/release-9-4-21.html + * https://www.postgresql.org/about/news/1920/ + * By default, panic instead of retrying after fsync() failure, + to avoid possible data corruption. + * Numerous other bug fixes. +- Overhaul README.SUSE + +------------------------------------------------------------------- Old: ---- postgresql-9.4.20.tar.bz2 New: ---- postgresql-9.4.21.tar.bz2 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ postgresql94.spec ++++++ --- /var/tmp/diff_new_pack.Q6mzvx/_old 2019-02-27 21:14:14.367160587 +0100 +++ /var/tmp/diff_new_pack.Q6mzvx/_new 2019-02-27 21:14:14.371160586 +0100 @@ -1,7 +1,7 @@ # # spec file for package postgresql94 # -# Copyright (c) 2018 SUSE LINUX GmbH, Nuernberg, Germany. +# Copyright (c) 2019 SUSE LINUX GmbH, Nuernberg, Germany. # # All modifications and additions to the file contributed by third parties # remain the property of their copyright owners, unless otherwise agreed @@ -71,7 +71,7 @@ Summary: Basic Clients and Utilities for PostgreSQL License: PostgreSQL Group: Productivity/Databases/Tools -Version: 9.4.20 +Version: 9.4.21 Release: 0 %define pg_minor_version %(echo %version | sed -r 's/^([0-9]+\\.[0-9]+).*/\\1/') Source0: https://ftp.postgresql.org/pub/source/v%{version}/postgresql-%{version}.tar.bz2 ++++++ postgresql-9.4.20.tar.bz2 -> postgresql-9.4.21.tar.bz2 ++++++ /work/SRC/openSUSE:Factory/postgresql94/postgresql-9.4.20.tar.bz2 /work/SRC/openSUSE:Factory/.postgresql94.new.28833/postgresql-9.4.21.tar.bz2 differ: char 11, line 1 ++++++ postgresql-README.SUSE ++++++ --- /var/tmp/diff_new_pack.Q6mzvx/_old 2019-02-27 21:14:14.419160574 +0100 +++ /var/tmp/diff_new_pack.Q6mzvx/_new 2019-02-27 21:14:14.423160573 +0100 @@ -1,22 +1,41 @@ -Newer versions of PostgreSQL come with the pg_upgrade tool that +Unix-Domain Socket Directory +============================ + + + +Upgrading PostgreSQL on openSUSE and SUSE Linux Enterprise Server +================================================================= + +Current versions of PostgreSQL come with the pg_upgrade tool that simplifies and speeds up the migration of a PostgreSQL installation to -a new version. Formerly dump and restore was needed that was much -slower. +a new version. Before version 9.1 dump and restore was needed which +was much slower. pg_upgrade needs to have the server binaries of both versions available. To allow this, we had to change the way PostgreSQL is packaged as well as the naming of the packages, so that two or more -versions of PostgreSQL can be installed in parallel. +versions of PostgreSQL can be installed in parallel. The package +names for PostgreSQL contain numbers indicating the major version. + +In PostgreSQL terms for versions up to 9.6 the major version consisted +of the first two components of the three-component version number, +i.e. 8.3, 8.4, 9.0, or 9.1. So, the packages for Postgresql 9.1 are +named postgresql91, postgresql91-server, etc. Inside the packages the +files were moved from their standard locations to a versioned location +such as /usr/lib/postgresql83/bin or /usr/lib/postgresql91/bin to +avoid file conflicts if packages are installed in parallel. + +Starting with version 10 the PostgreSQL project changed their +versioning scheme from from three components to two, which means one +component for the major version and one for the minor. So, the +sequence of major version across the versioning scheme change will be: +9.4, 9.5, 9.6, 10, 11, 12. For versions that use the new versioning +scheme SUSE only puts the single component major version into the +package name, so the postgresql96 package (containg version 9.6 +according to the old versioning scheme) will be followed by +postgresql10, then postgresql11, and so on. -Starting with version 9.1, PostgreSQL package names contain numbers -indicating the major version. In PostgreSQL terms the major version -consists of the first two components of the version number, i.e. 8.3, -8.4, 9.0, or 9.1. So, the packages for Postgresql 9.1 are named -postgresql91, postgresql91-server, etc. Inside the packages the files -were moved from their standard locations to a versioned location such -as /usr/lib/postgresql83/bin or /usr/lib/postgresql91/bin to avoid -file conflicts if packages are installed in parallel. The -update-alternatives mechanism creates and maintains symbolic links +The update-alternatives mechanism creates and maintains symbolic links that cause one version (by default the highest installed version) to re-appear in the standard locations. By default, database data are stored under /var/lib/pgsql/data on SUSE Linux. @@ -26,14 +45,12 @@ 1. If not already done, the packages of the old PostgreSQL version must be upgraded to the new packaging scheme through a maintenance - update. For SLE11 this means to install the patch that upgrades - PostgreSQL from version 8.3.14 to 8.3.19 or higher. + update. 2. The packages of the new PostgreSQL major version need to be - installed. For SLE11 this means to install postgresql91-server and - all the packages it depends on. As pg_upgrade is contained in - postgresql91-contrib, that one has to be installed as well, at least - until the migration is done. + installed. As pg_upgrade is contained in postgresql91-contrib, that + one has to be installed as well, at least until the migration is + done. 3. Unless pg_upgrade is used in link mode, the server must have enough free disk space to temporarily hold a copy of the database @@ -44,17 +61,20 @@ database in the instance to be migrated, but be aware that it might take very long. -Upstream documentation about pg_upgrade including step by step -instructions for performing a database migration can be found under -file:///usr/share/doc/packages/postgresql91/html/pgupgrade.html (if -the postgresql91-docs package is installed), or online under -http://www.postgresql.org/docs/9.1/static/pgupgrade.html . +The latest upstream documentation for pg_upgrade including step by +step instructions for performing a database migration can be found +online under https://www.postgresql.org/docs/current/pgupgrade.html , +or locally under +file:///usr/share/doc/packages/postgresqlXX/html/pgupgrade.html , if +the postgresqlXX-docs package is installed. XX is a place holder for +the respective major version here. NOTE: The online documentation starts with explaining how you can install PostgreSQL from the upstream sources (which is not necessary -on SLES) and also uses other directory names (/usr/local instead of -the update-alternatives based path as described above). - -For background information about the inner workings of pg_admin and a -performance comparison with the old dump and restore method, see -http://momjian.us/main/writings/pgsql/pg_upgrade.pdf . \ No newline at end of file +when you install the SUSE RPMs) and also uses other directory names +(/usr/local instead of the update-alternatives based path as described +above). + +For background information about the inner workings of pg_upgrade and +a performance comparison with the old dump and restore method, see +http://momjian.us/main/writings/pgsql/pg_upgrade.pdf .
