The latest release of PostgreSQL has brought about several significant improvements and bug fixes. One of the notable changes is the disallowing of certain features that were previously allowed but are no longer necessary or supported.

For instance, COPY TO from an RLS-enabled parent table will no longer copy rows from child tables, which was a potential security risk. Additionally, system columns can no longer be used as elements of foreign keys, and composite types stored in indexes must now be altered using the ALTER TYPE command.

Another significant change is the improvement to the handling of cloned triggers in partitioned tables. Previously, enabling or disabling these triggers would not work correctly, but this issue has been fixed.

The release also includes a fix for a security vulnerability that allowed a user to see or modify rows that they should not have had access to. This was due to a bug in the row-level security policies and has been corrected.

Furthermore, the release prevents users from hijacking the privileges of security definer functions or extension scripts by creating a schema. This ensures that changes made to search_path are respected even within called functions or scripts.

These changes demonstrate the commitment of the PostgreSQL project to ensuring the security and stability of the database management system. The release is a significant step forward for the platform, and users can rest assured that their data is in good hands.

Overall, this latest release of PostgreSQL has brought about several important improvements and bug fixes that enhance the security and performance of the database management system.

Postgresql releases