Movatterモバイル変換

• Updatedpg_pathman module to version 1.4.8. (SeeSection F.30 andSection F.30.1.1.) As compared to version 1.4.3, the following enhancements were introduced:

  • Improved cache invalidation mechanisms.

  • DisabledCOPYpartitioned_table TO command. UseCOPY (SELECT * FROMpartitioned_table) TO instead.

  • FixedINSTEAD OF triggers on views selected from partitioned tables.

  • ALTER TABLEpartitioned_table RENAME TO now also renames auto naming sequences.

  • Disabled some dangerous optimizations forSELECT ... FOR SHARE/UPDATE onPostgreSQL 9.5.

  • Improved error handling in concurrent partitioning background worker.

  • Prohibited execution of queriesDELETE FROMpartitioned_table_1 USINGpartitioned_table_2... andUPDATEpartitioned_table_1 FROMpartitioned_table_2... if such queries touch more than one partition ofpartitioned_table_1.

  • Fixed a bug causing crashes onRESET ALL.

  • FixedWHERE conditions that point to gaps between partitions.

  • Restored compatibility withpg_repack.

  • For the full list of changes, seepg_pathman Wiki.

• 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.