App wrapper for Postgres

Lightweight PostgreSQL database client

App wrapper for Postgres

Lightweight PostgreSQL database client

Lightweight PostgreSQL database client

Refer the below link for release notes:$$$https://www.postgresql.org/docs/release/16.3/

Refer the below link for release notes:$$$https://www.postgresql.org/docs/release/14.12/

Refer the below link for release notes:$$$https://www.postgresql.org/docs/release/15.7/

Refer the below link for release notes:$$$https://www.postgresql.org/docs/release/16.3/

Refer the below link for release notes:$$$https://www.postgresql.org/docs/release/16.2/

Refer the below link for release notes:$$$https://www.postgresql.org/docs/release/15.6/

Refer the below link for release notes:$$$https://www.postgresql.org/docs/release/14.11/

Refer the below link for release notes:$$$https://www.postgresql.org/docs/release/15.5/

Refer the below link for release notes:$$$https://www.postgresql.org/docs/release/14.10/

Refer the below link for release notes:$$$https://www.postgresql.org/docs/release/16.1/

This release contains a variety of fixes from 15.2. For information about new features in major release 15; see Section E.4.$$$$$$A dump/restore is not required for those running 15.X.$$$$$$However; if you are upgrading from a version earlier than 15.1; see Section E.3.$$$$$$Prevent CREATE SCHEMA from defeating changes in search_path (Alexander Lakhin)$$$$$$Within a CREATE SCHEMA command; objects in the prevailing search_path; as well as those in the newly-created schema; would be visible even within a called function or script that attempted to set a secure search_path. This could allow any user having permission to create a schema to hijack the privileges of a security definer function or extension script.$$$$$$The PostgreSQL Project thanks Alexander Lakhin for reporting this problem. (CVE-2023-2454)$$$$$$Enforce row-level security policies correctly after inlining a set-returning function (Stephen Frost; Tom Lane)$$$$$$If a set-returning SQL-language function refers to a table having row-level security policies; and it can be inlined into a calling query; those RLS policies would not get enforced properly in some cases involving re-using a cached plan under a different role. This could allow a user to see or modify rows that should have been invisible.$$$$$$The PostgreSQL Project thanks Wolfgang Walther for reporting this problem. (CVE-2023-2455)$$$$$$Fix potential corruption of the template (source) database after CREATE DATABASE with the STRATEGY WAL_LOG option (Nathan Bossart; Ryo Matsumura)$$$$$$Improper buffer handling created a risk that any later modification of the templates pg_class catalog would be lost.$$$$$$Fix memory leakage and unnecessary disk reads during CREATE DATABASE with the STRATEGY WAL_LOG option (Andres Freund)$$$$$$Avoid crash when the new schema name is omitted in CREATE SCHEMA (Michael Paquier)$$$$$$The SQL standard allows writing CREATE SCHEMA AUTHORIZATION owner_name; with the schema name defaulting to owner_name. However some code paths expected the schema name to be present and would fail.$$$$$$Fix various planner failures with MERGE commands (Tom Lane)$$$$$$Planning could fail with errors like “variable not found in subplan target list” or “PlaceHolderVar found where not expected”.