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.
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.
- Reduced WAL size on
CREATE INDEXoperation for GiST, GIN, SP-GiST.
- 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.)
- ICU collation support on all platforms to provide platform-independent sort for various locales. By default, the
icucollation provider is used for all locales except
POSIX. (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.)
pg_recovery_settingsview that displays the current recovery settings stored in the
- Changing parameters in
recovery.confwithout 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 to install different PostgreSQL-based products side by side, without any conflicts. (See Chapter 16.)
Postgres Pro Standard also includes the following additional modules:
- 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
- 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
SELECT INTOoperations applied for affected tables.
- pgbouncer connection pooler.
- pg_pathman module that provides optimized partitioning mechanism and functions to manage partitions.
- 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.
- 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.
- plantuner module that provides hints for the planner to disable or enable indexes for query execution.
- 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.