Movatterモバイル変換

• Changed the default authentication method for installations on SUSE Linux Enterprise Server systems, as well as Red Hat Enterprise Linux 7 and its derivatives. Now local connections use thepeer method, while network connections usemd5. For details on supported authentication methods, seeSection 19.3.

• Backported the patch that addressesdsm_attach() race condition when DSM handles are reused; in vanillaPostgreSQL, this fix is targeted for the future updates only. The patch is hoped to resolve issues when the server reports the following error message:ERROR: dsa_area could not attach to segment.

• Ended support for ALT Linux SPT 6.0 and Windows 7 SP1.

• Updatedpg_pathman module to version 1.5.5. As compared to version 1.5.2 provided in the previousPostgres Pro releases, the following enhancements were introduced:

  • Fixedpg_pathman upgrade scripts to avoid issues caused by a different the number ofpg_config attributes inpg_pathman 1.4 and 1.5 major versions.

  • Improvedpg_pathman stability:

    • Trying to callpg_pathman functions when this extension is disabled does not cause server failures anymore; now an error is raised instead.

    • Different partitioning strategies can now be successfully applied to the same table.

• Updatedpg_variables module to version 1.2. As compared to the version provided in the previousPostgres Pro releases, the following enhancements were introduced:

  • Added support for array types.

  • Improved module stability.

  • Changed empty package handling. An empty package is now removed only after the transaction that emptied it has ended.

  (SeeSection F.37.)

• If you are upgrading your installation from a binary package, and your database is in the default location,pgpro_upgrade is run automatically, unless you are prompted to run it manually.

• If you compiled Postgres Pro from source code or created your database in a non-default location, you must runpgpro_upgrade script manually.

Important

Before launchingpgpro_upgrade manually, you must stop thepostgres service. The script must be run on behalf of the user owning the database (typically postgres). Runningpgpro_upgrade as root will result in an error. For details, seepgpro_upgrade.