Movatterモバイル変換

• Unified the structure of binary installation packages across all Linux-based distributions. The new package structure differs from that of vanillaPostgreSQL, but offers the following benefits:

  • You do not need to worry about installation specifics on different Linux distributions when migrating between different supported Linux systems.Postgres Pro Standard is now installed to the/opt/pgpro/std-10 directory, while the default database is created in the/var/lib/pgpro/std-10/data directory.

  • You can now fully control the default database creation on all Linux distributions. If you install thepostgrespro-std-10 package, it deploys all thePostgres Pro packages required for your system, creates the default database, and configures the server in a fully automated way. If you install individual packages, you need to configurePostgres Pro yourself. In this case, you have to manually initialize the database cluster and start the server, as well as configure automatic server startup if required.

  • You can installPostgres Pro Standard 10 side by side with otherPostgreSQL-based products for seamless migration or parallel work. If you are using individual packages, your current system configuration will be preserved, so you have to manually configurePostgres Pro, as explained inSection 16.1.3. Do not install thepostgrespro-std-10 package on the same system with otherPostgreSQL-based products to avoid conflicts.

  Note thatpostgrespro-common andpostgrespro-client-common packages are no longer available on Debian-based systems. For details, seeSection 16.1.

• You can specifyicu orlibc as the provider for the default collation when initializing a database cluster or creating a database. By default, theicu provider is used for all locales exceptC andPOSIX. For details, seeSection 22.2.2.

• In B-tree index, duplicate keys are now stored only once, with item pointers located in posting lists. It can significantly reduce the index size for workloads where the same key appears multiple times.

• Covering indices patches (For details, see theINCLUDE clause description inCREATE INDEX.)

• Fixes to win32 build system

• Added pgpro_version SQL function and appropriate defines into pg_config.h

• Integrated PTRACK patch

• For Windows version ofpsql, enabled support for command-line editing usinglibeditline

• hunspell-dict (SeeHunspell Dictionaries Modules)

• jsquery (SeeSection F.26)

• pg_variables (SeeSection F.44)

• pg_pathman (Seepg_pathman)

• pg_query_state (SeeSection F.38)

• shared-ispell (Seeshared_ispell)

• sr_plan (Seesr_plan)

• dump_stat (Seedump_stat)

• pg_buffercache (Seepg_buffercache)

• mchar (SeeSection F.29)

• plantuner (SeeSection F.46)

• fasttrun (SeeSection F.17)

• fulleq (SeeSection F.19)

• online_analyze (SeeSection F.30)

• pg_pathman (Seepg_pathman)

• pg_probackup utility (Seepg_probackup)

Important

ForPostgreSQL 9.5 and 9.5.1, as well asPostgres Pro Standard 9.5.0.1 and 9.5.1.2, you cannot perform an upgrade toPostgres Pro Standard 10 directly. If you are using one of these versions, upgrade your installation to an intermediate version first, such asPostgres Pro Standard 9.5.2.1.

Similarly, if you are runningPostgres Pro Standard 9.6.10.x on Windows, you have to upgrade toPostgres Pro Standard 9.6.11.1 or higher.

• When migrating from vanillaPostgreSQL, specifylibc as the provider for the default collation.

• When upgrading fromPostgres Pro Standard, omit the provider option to select the required collation provider automatically. In this case,libc provider will be used for databases with C and POSIX locales, as well as for all databases with single-byte encodings, whileicu provider will be used for all the other cases.

• If the new cluster is initialized with locales other than C or POSIX, and the database has an single-byte encoding, set LC_COLLATE to '@libc' for this database.

• If the new cluster is initialized with C or POSIX locale settings and the database has a multi-byte encoding, set LC_COLLATE to'@icu' for this database.

Note

If the previousPostgres Pro Standard installation contained any indexes or constraints depending on collations other than the default collation of the database,C, orPOSIX in databases with multibyte encodings, such databases could contain some data that violated the specified constraints and made indexes inconsistent. On Windows, this situation can also happen if the database with a multibyte encoding contained any indexes or constraints depending on the default collation with a verbose name, such as"Russian_Russia[.encoding]" or"English_United States[.encoding]". In such cases, you can only usepg_upgrade to upgrade toPostgres Pro Standard 10, as a dump/restore scenario may be impossible. To resolve these issues,pg_upgrade declares such indexes and constraints invalid and createsreindex_text_indexes.sql andvalidate_text_contraints.sql, respectively.