2. Difference between Postgres Pro Standard and PostgreSQL
Postgres Pro provides the most actual PostgreSQL version with some additional patches applied and extensions added. It includes new features developed by Postgres Professional, as well as third-party patches already accepted by the PostgreSQL community for the upcoming PostgreSQL versions. Postgres Pro Standard users thus have early access to important features and fixes.
Note
Postgres Pro Standard is provided under the following license: https://postgrespro.com/products/postgrespro/eula. Make sure to review the license terms before downloading Postgres Pro Standard.
Postgres Pro Standard provides the following enhancements over PostgreSQL:
- Improved deadlock detection mechanism that does not cause performance degradation.
- Better planning speed and accuracy for various query types.
- Reduced memory consumption in complex queries that involve multiple tables.
- Displaying planning time in the output of the auto_explain module.
NUL byte replacement with the specified ASCII code while loading data using the
COPY FROMcommand. (See nul_byte_replacement_on_import parameter description.)'\u0000'character replacement with the specified unicode character when calling a function processing JSONB (See unicode_nul_character_replacement_in_jsonb parameter description.)- ICU collation support on all platforms to provide platform-independent sort for various locales. By default, the
icucollation provider is used for all locales exceptCandPOSIX. (See Section 22.2.2.) - PTRACK implementation, which enables pg_probackup to track page changes on the fly when creating incremental backups.
- Consistent reads on standby servers. (See WAITLSN.)
- Support for reading
pg_controlof previous PostgreSQL major versions by pg_controldata. - Cluster compatibility verification, which allows you to determine whether the current Postgres Pro version is compatible with the specified cluster and identify all parameters that can affect the compatibility without starting the cluster. (See
-z/-Zoption descriptions in postgres.) - Changing
primary_conninfo,restore_command, andprimary_slot_nameparameters without restarting the server. - Improvements for command-line editing using WinEditLine in the Windows version of psql, including autocomplete support in psql console and changing the psql default encoding to UTF-8.
- Unified structure of binary installation packages across all Linux distributions, which facilitates migration between them and allows installing PostgreSQL-based products side by side, without any conflicts. (See Chapter 16.)
- Collection of statistics about vacuuming tables and indexes. The collected information is displayed by pgpro_stats and pgpro_pwr.
- Getting information on crashes of a backend, which is enabled by the crash_info configuration parameter and controlled by more of them.
- Optimized memory consumption during selectivity estimation for each array element.
Postgres Pro Standard also includes the following additional modules and applications:
- dump_stat module that allows to save and restore database statistics when dumping/restoring the database.
- fasttrun module that provides transaction-unsafe function to truncate temporary tables without growing
pg_classsize. - fulleq module that provides additional equivalence operator for compatibility with Microsoft SQL Server.
- hunspell-dict module that provides dictionaries for several languages.
- jsquery module that provides a specific language for effective index-supported querying of JSONB data.
- mamonsu monitoring service, which is implemented as a Zabbix agent.
- mchar module that provides additional data type for compatibility with Microsoft SQL Server.
- online_analyze module that provides a set of changes to immediately update statistics after
INSERT,UPDATE,DELETEorSELECT INTOoperations applied for affected tables. - pgbadger application that rapidly analyzes Postgres Pro logs, producing detailed reports and graphs.
- pgbouncer connection pooler.
- pg_pathman module that provides optimized partitioning mechanism and functions to manage partitions. Starting from Postgres Pro 12, using pg_pathman is not recommended. Use vanilla declarative partitioning instead, as described in Section 5.11.
- pg_probackup, a backup and recovery manager.
- pgpro_controldata, an application to display control information of a PostgreSQL/Postgres Pro database cluster and compatibility information for a cluster and/or server.
- pgpro_pwr extension that enables you to generate workload reports, which help to discover most resource-intensive activities in your database.
- pgpro_stats extension that tracks execution statistics of SQL statements, calculates wait event statistics and provides other useful metrics that are not collected elsewhere in PostgreSQL. It also provides tracing of application sessions and can create views that emulate other statistic collecting extensions.
- pg_query_state module that enables you to get the current state of query execution for a backend.
- pg_repack utility for reorganizing tables.
- pg_tsparser module, which is an alternative text search parser.
- pg_variables module that provides functions for working with variables of various types. To facilitate migration of Oracle code that processes collections, these functions include those that allow working with general collection variables, whose elements can be accessed by a key that can have either integer or text type, and those that provide iterator functionality for any collections.
- pg_wait_sampling extension for sampling-based statistics of wait events. With this extension, you can get an insight into the server activity, including the current wait events for all processes and background workers.
- plantuner module that provides hints for the planner to disable or enable indexes for query execution.
- rum module that provides RUM index based on GIN.
- shared_ispell module that enables storing dictionaries in shared memory.
- sr_plan module that allows to save and restore query plans.
Postgres Pro Standard releases follow PostgreSQL releases, though sometimes occur more frequently. The Postgres Pro Standard versioning scheme is based on the PostgreSQL one and has an additional decimal place.