pgsql: Doc: update the "Using EXPLAIN" examples to match current code.

Doc: update the "Using EXPLAIN" examples to match current code. A lot of the examples in this section are quite ancient and no longer match the system's current behavior. I ran through them and updated the sample output to match what I get today. Notably, it seems that the tenk1 table got a few

pgsql: doc PG 17 relnotes: fix author of LLVM item

doc PG 17 relnotes: fix author of LLVM item Discussion: https://postgr.es/m/ca+hukg+yu4+yqscuquzdceetpdu+fjebxgv5fkp6xrtr7ek...@mail.gmail.com Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/6a126d91cd042e708e101acafe23100ffb574251

pgsql: doc: clarify PERIOD and WITHOUT OVERLAPS in CREATE TABLE

doc: clarify PERIOD and WITHOUT OVERLAPS in CREATE TABLE Discussion: https://postgr.es/m/04938501-fc8f-46f3-97a4-9a81a3f24...@illuminatedcomputing.com Author: Paul Jungwirth Backpatch-through: master Branch -- master Details ---

pgsql: Tag refs/tags/REL_16_3 was created

Tag refs/tags/REL_16_3 was created.

pgsql: Tag refs/tags/REL_14_12 was created

Tag refs/tags/REL_14_12 was created.

pgsql: Tag refs/tags/REL_15_7 was created

Tag refs/tags/REL_15_7 was created.

pgsql: Tag refs/tags/REL_12_19 was created

Tag refs/tags/REL_12_19 was created.

pgsql: Tag refs/tags/REL_13_15 was created

Tag refs/tags/REL_13_15 was created.

pgsql: Last-minute updates for release notes.

Last-minute updates for release notes. Security: CVE-2024-4317 Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/7b2ac0f6039f0f64d80c7488f0f718094cfb89a2 Modified Files -- doc/src/sgml/release-15.sgml | 95

pgsql: Last-minute updates for release notes.

Last-minute updates for release notes. Security: CVE-2024-4317 Branch -- REL_16_STABLE Details --- https://git.postgresql.org/pg/commitdiff/a62be834aeb899dfc2e10e3cde6d0f48ba128373 Modified Files -- doc/src/sgml/release-16.sgml | 95

pgsql: Last-minute updates for release notes.

Last-minute updates for release notes. Security: CVE-2024-4317 Branch -- REL_14_STABLE Details --- https://git.postgresql.org/pg/commitdiff/b7712704f0bb3dc82f286516a7057b0fa5b1d260 Modified Files -- doc/src/sgml/release-14.sgml | 95

pgsql: Fix privilege checks in pg_stats_ext and pg_stats_ext_exprs.

Fix privilege checks in pg_stats_ext and pg_stats_ext_exprs. The catalog view pg_stats_ext fails to consider privileges for expression statistics. The catalog view pg_stats_ext_exprs fails to consider privileges and row-level security policies. To fix, restrict the data in these views to table

pgsql: Fix privilege checks in pg_stats_ext and pg_stats_ext_exprs.

Fix privilege checks in pg_stats_ext and pg_stats_ext_exprs. The catalog view pg_stats_ext fails to consider privileges for expression statistics. The catalog view pg_stats_ext_exprs fails to consider privileges and row-level security policies. To fix, restrict the data in these views to table

pgsql: Fix privilege checks in pg_stats_ext and pg_stats_ext_exprs.

Fix privilege checks in pg_stats_ext and pg_stats_ext_exprs. The catalog view pg_stats_ext fails to consider privileges for expression statistics. The catalog view pg_stats_ext_exprs fails to consider privileges and row-level security policies. To fix, restrict the data in these views to table

pgsql: Fix privilege checks in pg_stats_ext and pg_stats_ext_exprs.

Fix privilege checks in pg_stats_ext and pg_stats_ext_exprs. The catalog view pg_stats_ext fails to consider privileges for expression statistics. The catalog view pg_stats_ext_exprs fails to consider privileges and row-level security policies. To fix, restrict the data in these views to table

pgsql: Fix recursive RECORD-returning plpython functions.

Fix recursive RECORD-returning plpython functions. If we recursed to a new call of the same function, with a different coldeflist (AS clause), it would fail because the inner call would overwrite the outer call's idea of what to return. This is vaguely like 1d2fe56e4 and c5bec5426, but it's not

pgsql: Fix recursive RECORD-returning plpython functions.

Fix recursive RECORD-returning plpython functions. If we recursed to a new call of the same function, with a different coldeflist (AS clause), it would fail because the inner call would overwrite the outer call's idea of what to return. This is vaguely like 1d2fe56e4 and c5bec5426, but it's not

pgsql: Fix recursive RECORD-returning plpython functions.

Fix recursive RECORD-returning plpython functions. If we recursed to a new call of the same function, with a different coldeflist (AS clause), it would fail because the inner call would overwrite the outer call's idea of what to return. This is vaguely like 1d2fe56e4 and c5bec5426, but it's not

pgsql: Fix recursive RECORD-returning plpython functions.

Fix recursive RECORD-returning plpython functions. If we recursed to a new call of the same function, with a different coldeflist (AS clause), it would fail because the inner call would overwrite the outer call's idea of what to return. This is vaguely like 1d2fe56e4 and c5bec5426, but it's not

pgsql: Fix recursive RECORD-returning plpython functions.

Fix recursive RECORD-returning plpython functions. If we recursed to a new call of the same function, with a different coldeflist (AS clause), it would fail because the inner call would overwrite the outer call's idea of what to return. This is vaguely like 1d2fe56e4 and c5bec5426, but it's not

pgsql: Fix recursive RECORD-returning plpython functions.

Fix recursive RECORD-returning plpython functions. If we recursed to a new call of the same function, with a different coldeflist (AS clause), it would fail because the inner call would overwrite the outer call's idea of what to return. This is vaguely like 1d2fe56e4 and c5bec5426, but it's not

pgsql: doc PG 17 relnotes: Visual Studio clarification

doc PG 17 relnotes: Visual Studio clarification Reported-by: Andrew Dunstan Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/b538e692493be30132c0ee5984bc53f51920cded Modified Files -- doc/src/sgml/release-17.sgml | 4 ++-- 1

pgsql: Repair ALTER EXTENSION ... SET SCHEMA.

Repair ALTER EXTENSION ... SET SCHEMA. It turns out that we broke this in commit e5bc9454e, because the code was assuming that no dependent types would appear among the extension's direct dependencies, and now they do. This isn't terribly hard to fix: just skip dependent types, expecting that we

pgsql: doc PG 17 relnotes: Fixes from jian he

doc PG 17 relnotes: Fixes from jian he Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/d82ab9fc31aa62d94c26d7df98e65c6ceaadb01f Modified Files -- doc/src/sgml/release-17.sgml | 10 +- 1 file changed, 5 insertions(+), 5

pgsql: doc PG 17 relnotes: various fixes

doc PG 17 relnotes: various fixes Fixes suggested by David Rowley, Bertrand Drouvot, Masahiko Sawada, Richard Guo, jian he, Dagfinn Ilmari Mannsåker Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/45ea5b0a2732849ef8bfb695808943d0d940abeb

pgsql: Make left-join removal safe under -DREALLOCATE_BITMAPSETS.

Make left-join removal safe under -DREALLOCATE_BITMAPSETS. The initial building of RestrictInfos and SpecialJoinInfos tends to create structures that share relid sets (such as syn_lefthand and outer_relids). There's nothing wrong with that in itself, but when we modify those relid sets during

pgsql: psql: Add missing punctuation in help output

psql: Add missing punctuation in help output Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/e2d5508c501a3cfd47df49ce88669bec7df2e426 Modified Files -- src/bin/psql/help.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

pgsql: doc: Use better placeholder in COPY synopsis

doc: Use better placeholder in COPY synopsis Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/1c4429e703b2caf7fc865c2fc0a94f3557e5b356 Modified Files -- doc/src/sgml/ref/copy.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

pgsql: Fix inconsistencies in error messages

Fix inconsistencies in error messages Reported by Kyotaro Horiguchi Also some comments mentioning wrong version numbers, spotted by Justin Pryzby. Discussion: https://postgr.es/m/20240507.171724.750916195320223609.horikyota@gmail.com Discussion: