Revert "Drop unnamed portal immediately after execution to completion"
This reverts commit 1fd981f05369, based on concerns that the logging
improvements do not justify the protocol breakage of dropping an unnamed
portal once its execution has completed.
It seems unlikely that one would try to sen
doc: adjust "Replication Slot" to mention physical & logical
Much of the "Replication Slot" chapter applies to physical and logical
slots, but it was sloppy in mentioning mostly physical slots. This
patch clarified which parts of the text apply to which slot types.
This chapter is referenced fr
doc: clarify "logical" replication slots
Also mention that logical replication slots are created by default when
subscriptions are created. This should clarify the text.
Backpatch-through: master
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/ada78cd7f80a818de19
doc: clarify "physical" replication slot creation on the primary
Previously it was not clear that "physical" replication slots were being
discussed, and that they needed to be created on the primary and not the
standby.
Backpatch-through: master
Branch
--
master
Details
---
https://git.
doc: reorder logical replication benefits in a logical order
The previous ordering was hard to understand and remember. Also adjust
wording to be more consistent with surrounding items.
Backpatch-through: master
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/acb
Document that pg_getaddrinfo_all does not accept null hints
While the underlying getaddrinfo call accepts a null pointer for
the hintp parameter, pg_getaddrinfo_all does not. Document this
difference with a comment to make it clear.
Author: Daniel Gustafsson
Reviewed-by: Tom Lane
Reported-by:
Last-minute updates for release notes.
Security: CVE-2025-12817, CVE-2025-12818
Branch
--
REL_17_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/2c0382f98b3fa05f482b94c706169f6bebbc92ea
Modified Files
--
doc/src/sgml/release-17.sgml | 61 +
Last-minute updates for release notes.
Security: CVE-2025-12817, CVE-2025-12818
Branch
--
REL_14_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/ee953cd8f0a9325ad67fef94539df8b4201efafe
Modified Files
--
doc/src/sgml/release-14.sgml | 61 +
Last-minute updates for release notes.
Security: CVE-2025-12817, CVE-2025-12818
Branch
--
REL_16_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/b2e70cc348992012cab140172d0aaf9a3bec6b0b
Modified Files
--
doc/src/sgml/release-16.sgml | 61 +
Last-minute updates for release notes.
Security: CVE-2025-12817, CVE-2025-12818
Branch
--
REL_13_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/9a219bb0038a7c56eb4ea9680e1d0c7043a81c88
Modified Files
--
doc/src/sgml/release-13.sgml | 61 +
Last-minute updates for release notes.
Security: CVE-2025-12817, CVE-2025-12818
Branch
--
REL_18_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/91d070c7bb1480247cb834c36c89b15a7db5f82d
Modified Files
--
doc/src/sgml/release-18.sgml | 61 +
Check for CREATE privilege on the schema in CREATE STATISTICS.
This omission allowed table owners to create statistics in any
schema, potentially leading to unexpected naming conflicts. For
ALTER TABLE commands that require re-creating statistics objects,
skip this check in case the user has sinc
Check for CREATE privilege on the schema in CREATE STATISTICS.
This omission allowed table owners to create statistics in any
schema, potentially leading to unexpected naming conflicts. For
ALTER TABLE commands that require re-creating statistics objects,
skip this check in case the user has sinc
Last-minute updates for release notes.
Security: CVE-2025-12817, CVE-2025-12818
Branch
--
REL_15_STABLE
Details
---
https://git.postgresql.org/pg/commitdiff/70d03b5f4f9e585a5a1425e89af234015e2c63c5
Modified Files
--
doc/src/sgml/release-15.sgml | 61 +
Check for CREATE privilege on the schema in CREATE STATISTICS.
This omission allowed table owners to create statistics in any
schema, potentially leading to unexpected naming conflicts. For
ALTER TABLE commands that require re-creating statistics objects,
skip this check in case the user has sinc
Check for CREATE privilege on the schema in CREATE STATISTICS.
This omission allowed table owners to create statistics in any
schema, potentially leading to unexpected naming conflicts. For
ALTER TABLE commands that require re-creating statistics objects,
skip this check in case the user has sinc
Check for CREATE privilege on the schema in CREATE STATISTICS.
This omission allowed table owners to create statistics in any
schema, potentially leading to unexpected naming conflicts. For
ALTER TABLE commands that require re-creating statistics objects,
skip this check in case the user has sinc
libpq: Prevent some overflows of int/size_t
Several functions could overflow their size calculations, when presented
with very large inputs from remote and/or untrusted locations, and then
allocate buffers that were too small to hold the intended contents.
Switch from int to size_t where appropri
Check for CREATE privilege on the schema in CREATE STATISTICS.
This omission allowed table owners to create statistics in any
schema, potentially leading to unexpected naming conflicts. For
ALTER TABLE commands that require re-creating statistics objects,
skip this check in case the user has sinc
Check for CREATE privilege on the schema in CREATE STATISTICS.
This omission allowed table owners to create statistics in any
schema, potentially leading to unexpected naming conflicts. For
ALTER TABLE commands that require re-creating statistics objects,
skip this check in case the user has sinc
libpq: Prevent some overflows of int/size_t
Several functions could overflow their size calculations, when presented
with very large inputs from remote and/or untrusted locations, and then
allocate buffers that were too small to hold the intended contents.
Switch from int to size_t where appropri
libpq: Prevent some overflows of int/size_t
Several functions could overflow their size calculations, when presented
with very large inputs from remote and/or untrusted locations, and then
allocate buffers that were too small to hold the intended contents.
Switch from int to size_t where appropri
libpq: Prevent some overflows of int/size_t
Several functions could overflow their size calculations, when presented
with very large inputs from remote and/or untrusted locations, and then
allocate buffers that were too small to hold the intended contents.
Switch from int to size_t where appropri
libpq: Prevent some overflows of int/size_t
Several functions could overflow their size calculations, when presented
with very large inputs from remote and/or untrusted locations, and then
allocate buffers that were too small to hold the intended contents.
Switch from int to size_t where appropri
libpq: Prevent some overflows of int/size_t
Several functions could overflow their size calculations, when presented
with very large inputs from remote and/or untrusted locations, and then
allocate buffers that were too small to hold the intended contents.
Switch from int to size_t where appropri
libpq: Prevent some overflows of int/size_t
Several functions could overflow their size calculations, when presented
with very large inputs from remote and/or untrusted locations, and then
allocate buffers that were too small to hold the intended contents.
Switch from int to size_t where appropri
doc: Improve description of RLS policies applied by command type.
On the CREATE POLICY page, the "Policies Applied by Command Type"
table was missing MERGE ... THEN DELETE and some of the policies
applied during INSERT ... ON CONFLICT and MERGE. Fix that, and try to
improve readability by listing
doc: Improve description of RLS policies applied by command type.
On the CREATE POLICY page, the "Policies Applied by Command Type"
table was missing MERGE ... THEN DELETE and some of the policies
applied during INSERT ... ON CONFLICT and MERGE. Fix that, and try to
improve readability by listing
doc: Improve description of RLS policies applied by command type.
On the CREATE POLICY page, the "Policies Applied by Command Type"
table was missing MERGE ... THEN DELETE and some of the policies
applied during INSERT ... ON CONFLICT and MERGE. Fix that, and try to
improve readability by listing
doc: Improve description of RLS policies applied by command type.
On the CREATE POLICY page, the "Policies Applied by Command Type"
table was missing MERGE ... THEN DELETE and some of the policies
applied during INSERT ... ON CONFLICT and MERGE. Fix that, and try to
improve readability by listing
doc: Improve description of RLS policies applied by command type.
On the CREATE POLICY page, the "Policies Applied by Command Type"
table was missing MERGE ... THEN DELETE and some of the policies
applied during INSERT ... ON CONFLICT and MERGE. Fix that, and try to
improve readability by listing
doc: Improve description of RLS policies applied by command type.
On the CREATE POLICY page, the "Policies Applied by Command Type"
table was missing MERGE ... THEN DELETE and some of the policies
applied during INSERT ... ON CONFLICT and MERGE. Fix that, and try to
improve readability by listing
Add some missing #include .
These files relied on transitive inclusion via port/atomics.h for
constants CHAR_BIT and INT_MAX.
Reviewed-by: Heikki Linnakangas
Discussion: https://postgr.es/m/[email protected]
Branch
--
master
Details
---
https://git.postgresql.
33 matches
Mail list logo
