Movatterモバイル変換

Important

The final release ofPostgres Pro 13 is scheduled for November 2025. No further updates (including CVE patches and bug fixes) will be provided for this version as of December 1, 2025. If you are using version 13, we recommend that you upgrade to the latest major version no later than November 30, 2025.

• Added theenable_alternative_sorting_cost_model configuration parameter, which allows you to enable or disable the query planner's use of alternative model for estimating the cost of tuple sorting.

• Introduced the following changes to the implementation ofcrash_info:

  • Added handling ofSIGILL signals tocrash_info processing.

  • Added details, like process start time and query text at planning, tocrash_info output files.

  • Fixed incorrect function names in the first 2-3 lines ofcrash_info backtrace stacks.

  • Fixed possible data truncation at the end of SQL query dump files. Previously, a buffer overflow during SQL query dumping could result in incomplete writes, causing truncated data at the end of files produced bycrash_info.

  • Fixed handling of crash information signals (sent using thekill command) by backends. Previously, the first signal would flushcrash_info information to the log, but the process would continue running without producing a core dump, even if configured, and only the second signal would terminate the backend and generate the core dump as expected.

• Fixed an issue with missing statistics about vacuuming when multiple index vacuum workers are used.

• Added thedaterange_inclusive extension, which allows you to include the upper bound of a time range in output.

• Added the new utilitypgpro_tune for automatic tuning ofPostgres Pro configuration parameters for all operating systems, except for Windows.

• Added a newPGPRO_TUNE environment variable toinitdb, which specifies whether to usepgpro_tune without modifying command-line options directly.

• Removed the--tune option frompg-setup. Use the newpgpro_tune utility instead.

• Upgradedoracle_fdw to provide the following enhancements and bug fixes:

  • Increased line size for EXPLAIN output as someOracle catalog queries have long filter conditions. The line size was increased to the value of 3000.

  • Fixed a crash with column options on non-existing columns. If theOracle table has fewer columns than thePostgres Pro and one of these extra columns has a column option set,oracle_fdw would write past the end of an array, leading to memory corruption and crashes. Now options for such columns are ignored.

• Upgradedpg_probackup to version 2.8.9, which provides the following new features, optimizations, and bug fixes:

  • Added themaintain command to resolve issues that can occur during a forced backup termination.

  • Added the--lock-lifetime option that sets the timeout for locks. This option is useful for computational environments with a slow network.

  • Stabilized retaining the initial permissions for directories when running theinit command.

  • Stabilized thecheckdb command on a remote host.

  • Improved the stability of the point-in-time recovery (PITR) with validation.

  • Fixed an incorrect behavior that could occur when launching the wait for a WAL streaming thread in the ARCHIVE WAL delivery mode.

• Upgradedpgpro_pwr to version 4.9, which mainly provides optimizations and bug fixes. Notable changes are as follows:

  • Added support forpgpro_stats 1.9.

  • Added a possibility to define the mode of collecting relation sizes globally through thepgpro_pwr.relsize_collect_mode extension parameter or for a server through theset_server_size_sampling function parameter.

  • Enabled fine-tuning the server statistics collection by calling theset_server_setting function. It allows you to define which statistics should be collected.

  • Added a preview of storage parameters for tables and indexes in the“Schema object statistics” report section.

• Upgradedpgpro_stats to version 1.9, which provides the following bug fixes and improvements:

  • Enhanced session tracing to provide more information. Specifically, the newtime_info filter attribute controls inclusion of additional information in the session-tracing output, and thepgpro_stats.trace_query_text_size configuration parameter can limit the size of the query in the session-tracing output.

  • Aligned the names of theexplain_* filter attributes of the session tracer with the names of session-tracing configuration parameters.

  • Changed the format of the statistics dump file and the corresponding save/load routines.

  • Implemented turning off the session tracer functionality when no session-tracing filters are specified.

  • Prohibited inclusion of bothpgpro_stats andpg_stat_statements in the list ofshared_preload_libraries. If both are included, the database server will not start.

• Upgraded thepg_wait_sampling extension to provide the following bug fixes:

  • Fixed an issue where GUC variables could be overridden when using parallel workers.

  • Fixed an issue with malformed samples caused by a race condition whenpg_wait_sampling.sample_cpu is disabled.