Added details, like current working directory, the PGDATA directory, etc., to crash_info output files.

Added the increased security requirements for the CREATE PROFILE command. Now the PASSWORD_REQUIRE_COMPLEX parameter requires characters from three different groups. Also, all characters of languages without case distinction (Hindi, Chinese, etc.) in the UTF-8 encoding are considered lowercase.

Added the skip_temp_rel_lock configuration parameter, which allows you to skip locking for temporary relations.

Implemented the following enhancements and bug fixes for CFS:

Fixed an issue with upgrading Postgres Pro Standard to Postgres Pro Enterprise using pg_upgrade, which could fail if the old cluster had an epoch greater than 1 with an error like “could not open file”.

Fixed an issue with handling *.cfm.bck files by pg_upgrade.

Fixed the pg_upgrade --check option to correctly check that pg_upgrade is run on a standby. Previously, it would fail with errors like “cannot assign TransactionIds during recovery”.

Fixed a segmentation fault caused by foreign data wrapper invalidation during autonomous transactions if an autonomous transaction reset global variables while registered callback functions remained active. Now callback functions check for global variables and invalidation data is preserved for parent transactions.

Fixed an issue that caused the server to crash with PANIC instead of returning an appropriate error when deleting tuples from a page where the difference between the minimum transaction ID and the current transaction ID exceeded 2^31.

Fixed pg_multixact bloating by introducing “soft” limits that trigger autovacuum earlier.

Fixed an issue where crash_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 an issue where roles without explicitly set VALID UNTIL attribute and associated with a profile that had PASSWORD_GRACE_TIME set to 0 and PASSWORD_LIFE_TIME set to UNLIMITED incorrectly received password expiration warnings. Now they are correctly considered valid indefinitely.

Fixed a bug that caused problems with starting followers added after execution of ALTER SYSTEM on the initialized leader.

Upgraded the apache_age extension to version 1.5.1.

Upgraded the BiHA solution to provide the following features, optimizations, and bug fixes:

Optimized fasttrun to skip unnecessary truncate operations on empty temporary relations.

Fixed an issue with upgrading pageinspect in some corner cases to 1.10.1 or higher.

Upgraded the pgpro_multiplan extension version 1.1, which provides the following bug fixes:

Upgraded pgbadger to version 13.0.

Upgraded pgbouncer to version 1.24.0.

Upgraded pg_hint_plan to version 1.7.0.3.

Upgraded pg_portal_modify to version 0.3.5.

Upgraded pgpro_anonymizer to version 1.3.2.

Upgraded pg_proaudit to provide the following enhancements:

Upgraded pg_probackup to version 2.8.7 Enterprise, which provides the following optimizations and bug fixes:

Added the pgpro_gbtree extension that enables creation and use of a global index on a partitioned table. The global index is created for one or several columns of a partitioned table and does not include the partition key. It allows you to perform index scan without iterating through all the partitions.

Upgraded pgpro_queue to version 1.1, where the no-longer-required pgpro_queue.launcher_database parameter is removed. Now when trying to specify this parameter, a corresponding warning will be displayed.

Upgraded pgpro_scheduler to version 2.11.1 to fix a segmentation fault, which could occur when pgpro_scheduler did not terminate its processes when the associated extension or schema was dropped. Now it terminates with an error instead of crashing.

Upgraded pgpro_sfile to add a check for the value of the a_sf_index argument of the sf_write function to be greater than zero.

Upgraded pgpro_stats to provide the following bug fixes and improvements:

Fixed an issue with pgpro_usage recording earlier timestamps. Previously, the last usage time of a privilege was recorded based on transaction start time, which could cause the timestamp to move backward if a long-running transaction accessed a table late, while a shorter concurrent transaction accessed it earlier.

Upgraded the proxima extension to provide the following features, optimizations, and bug fixes:

Upgraded the rum module to update an error message for an error that can occur in the case when a SELECT query uses ORDER BY.