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 version no later than November 30, 2025.

• Fixed an issue wherecrash_info could fail to write diagnostic files when handling a stack overflow. Previously, the signal handler ran on the same stack that had overflowed, which could prevent it from executing due to lack of available stack space. Now the handler runs on an alternate signal stack.

• Fixed a memory context issue, which could previously cause emitting garbage in logs instead of the host and port details when disconnecting from the remote server.

• Fixed an issue that could occur when a custom scan was used, which could cause an incorrect state of the query plan and could result in an error whenpgpro_stats was involved.

• Added details, like current working directory, thePGDATA directory, etc., tocrash_info output files.

• Optimizedfasttrun to skip unnecessary truncate operations on empty temporary relations.

• Upgradedmamonsu to version 3.5.11 to provide support forpgpro_stats version 1.8.

• Upgradedpgbadger to version 13.0.

• Upgradedpgbouncer to version 1.24.0.

• Upgradedpg_portal_modify to version 0.3.5.

• Upgradedpg_probackup to version 2.8.7, which provides the following optimizations and bug fixes:

  • Fixed an issue of the multi-threaded file copying technique that prevents repeated copying of one file. This issue could previously stop the backup creation under high load on the server.

  • Reduced the log level for“checking WAL file name” messages that are issued when theshow with the--archive option is executed fromINFO toVERBOSE.

  • Updated theadd-instance command logic to make the-D option that specifies the path to the catalog mandatory.add-instance no longer relies on thePGDATA environment variable for the catalog location, but requires explicitly specifying the path to the catalog as the command option.

• Upgradedpgpro_pwr to version 4.8, which provides new features and bug fixes. Notable changes are as follows:

  • Added tracking of extension versions installed in the cluster through a new report section.

  • Added a possibility to hide data for certain databases in the report. To this end, a new parameter that accepts an array of databases to be excluded was added to report generation functions.

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

  • Fixed an issue in that could occur during session tracing and cause errors“could not write file ""pg_stat/pgpro_stats_filters.trace.tmp"": No such file or directory”. Concurrent writing from different sessions to a trace file is fixed now, so processes can write to the trace file in parallel without collisions.

  • Implemented an optimization that lowers the locking time in some cases when copying metrics from the local memory to the shared memory.

• Upgradedpg_variables. TheDISCARD ALL command now discards all packages and variables inpg_variables.

• Upgraded therum module to update an error message for an error that can occur in the case when aSELECT query usesORDER BY.