pgsql: doc: Clean up title case use

doc: Clean up title case use Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/6ef762938eead1a42024b219311f6ede5dc2104a Modified Files -- doc/src/sgml/file-fdw.sgml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

pgsql: Fix typo and comments related to the recent no-wait lock improve

Fix typo and comments related to the recent no-wait lock improvements The argument of dontWait at the top of ProcSleep() was documented backwards, and there was a typo in lock.c. Thinkos in 2346df6fc373. Author: Will Mortensen Reviewed-by: Jingxian Li, Michael Paquier Discussion: https://postgr

pgsql: doc: Fix column_name parameter in ALTER MATERIALIZED VIEW

doc: Fix column_name parameter in ALTER MATERIALIZED VIEW Parameter column_name must be an existing column because ALTER MATERIALIZED VIEW cannot add new columns. The old description was likely copied from ALTER TABLE. Author: Erik Wienhold Discussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5

pgsql: doc: Fix column_name parameter in ALTER MATERIALIZED VIEW

doc: Fix column_name parameter in ALTER MATERIALIZED VIEW Parameter column_name must be an existing column because ALTER MATERIALIZED VIEW cannot add new columns. The old description was likely copied from ALTER TABLE. Author: Erik Wienhold Discussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5

pgsql: doc: Fix column_name parameter in ALTER MATERIALIZED VIEW

doc: Fix column_name parameter in ALTER MATERIALIZED VIEW Parameter column_name must be an existing column because ALTER MATERIALIZED VIEW cannot add new columns. The old description was likely copied from ALTER TABLE. Author: Erik Wienhold Discussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5

pgsql: doc: Fix column_name parameter in ALTER MATERIALIZED VIEW

doc: Fix column_name parameter in ALTER MATERIALIZED VIEW Parameter column_name must be an existing column because ALTER MATERIALIZED VIEW cannot add new columns. The old description was likely copied from ALTER TABLE. Author: Erik Wienhold Discussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5

pgsql: doc: Fix column_name parameter in ALTER MATERIALIZED VIEW

doc: Fix column_name parameter in ALTER MATERIALIZED VIEW Parameter column_name must be an existing column because ALTER MATERIALIZED VIEW cannot add new columns. The old description was likely copied from ALTER TABLE. Author: Erik Wienhold Discussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5

pgsql: doc: Fix column_name parameter in ALTER MATERIALIZED VIEW

doc: Fix column_name parameter in ALTER MATERIALIZED VIEW Parameter column_name must be an existing column because ALTER MATERIALIZED VIEW cannot add new columns. The old description was likely copied from ALTER TABLE. Author: Erik Wienhold Discussion: https://postgr.es/m/6880ca53-7961-4eeb-86d5

pgsql: Fix a couple of outdated comments now that we have MERGE RETURNI

Fix a couple of outdated comments now that we have MERGE RETURNING This has been supported since c649fa24a. Discussion: https://postgr.es/m/caaphdvpqp6vtuzg-_josueibgyqnrnvxj-vdf+hjlxjhdhz...@mail.gmail.com Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/855925209

pgsql: Don't copy extended statistics during MERGE/SPLIT partition oper

Don't copy extended statistics during MERGE/SPLIT partition operations When MERGE/SPLIT created new partitions, it was cloning the extended statistics of the parent table. However, extended stats on partitioned tables don't behave like indexes on partitioned tables (which exist only to create phy

pgsql: Fix the name collision detection in MERGE/SPLIT partition operat

Fix the name collision detection in MERGE/SPLIT partition operations Both MERGE and SPLIT partition operations support the case when the name of the new partition matches the name of the existing partition to be merged/split. But the name collision detection doesn't always work as intended. The S

pgsql: amcheck: Don't load the right sibling page into BtreeCheckState

amcheck: Don't load the right sibling page into BtreeCheckState 5ae2087202 implemented a cross-page unique constraint check by loading the right sibling to the BtreeCheckState.target variable. This is wrong, because bt_target_page_check() shouldn't change the target page. Also, BtreeCheckState.t

pgsql: amcheck: Refactoring the storage of the last visible entry

amcheck: Refactoring the storage of the last visible entry This commit introduces a new data structure BtreeLastVisibleEntry comprising information about the last visible heap entry with the current value of key. Usage of this data structure allows us to avoid passing all this information as indiv

pgsql: amcheck: Report an error when the next page to a leaf is not a l

amcheck: Report an error when the next page to a leaf is not a leaf This is a very unlikely condition during checking a B-tree unique constraint, meaning that the index structure is violated badly, and we shouldn't continue checking to avoid endless loops, etc. So it's worth immediately throwing

pgsql: doc PG 17 relnotes: fix pg_stat_reset_shared quoting

doc PG 17 relnotes: fix pg_stat_reset_shared quoting Reported-by: torikoshia Discussion: https://postgr.es/m/8ab708436c369d47fcbb23a8ad775...@oss.nttdata.com Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/bac44bc29a64d882e9717672ff788f1

pgsql: doc PG 17 relnotes: fix pg_stat_statements typo

doc PG 17 relnotes: fix pg_stat_statements typo Reported-by: Masahiko Sawada Discussion: https://postgr.es/m/CAD21AoB_MR=S_Gh=oejr4ji0ggy+d8747o-5pycbmbhgomt...@mail.gmail.com Author: Masahiko Sawada Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/p

pgsql: doc PG 17 relnotes: adjust SQL/JSON constructor func. authors

doc PG 17 relnotes: adjust SQL/JSON constructor func. authors Reported-by: Amit Langote Discussion: https://postgr.es/m/CA+HiwqHA2_2V-UtdEEjX3wMUcO=pAwH2D=9p9crygvcnljk...@mail.gmail.com Author: Amit Langote Backpatch-through: master Branch -- master Details --- https://git.postgres

pgsql: doc PG 17 relnotes: adjust builtin collation provider item

doc PG 17 relnotes: adjust builtin collation provider item Reported-by: Jeff Davis Discussion: https://postgr.es/m/92e039f6fabc3567169e95e12b39a04c00f8503b.ca...@j-davis.com Backpatch-through: master Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3551da969e8d4c

pgsql: Fix input of ISO "extended" time format for types time and timet

Fix input of ISO "extended" time format for types time and timetz. Commit 3e1a373e2 missed teaching DecodeTimeOnly the same "ptype" manipulations it added to DecodeDateTime. While likely harmless at the time, it became a problem after 5b3c59535 added an error check that ptype must be zero once we

pgsql: Fix input of ISO "extended" time format for types time and timet

Fix input of ISO "extended" time format for types time and timetz. Commit 3e1a373e2 missed teaching DecodeTimeOnly the same "ptype" manipulations it added to DecodeDateTime. While likely harmless at the time, it became a problem after 5b3c59535 added an error check that ptype must be zero once we

pgsql: doc PG 17 relnotes: add Heikki Linnakangas to vacuum item

doc PG 17 relnotes: add Heikki Linnakangas to vacuum item Reported-by: Melanie Plageman Discussion: https://postgr.es/m/caakru_yyr5mxy-xucpr7dkkugcextsjry9ax8c-z7lka8dd...@mail.gmail.com Author: Melanie Plageman Backpatch-through: master Branch -- master Details --- https://git.post

pgsql: Fix handling of extended expression statistics in CREATE TABLE L

Fix handling of extended expression statistics in CREATE TABLE LIKE. transformTableLikeClause believed that it could process extended statistics immediately because "the representation of CreateStatsStmt doesn't depend on column numbers". That was true when extended stats were first introduced, b

pgsql: Fix handling of extended expression statistics in CREATE TABLE L

Fix handling of extended expression statistics in CREATE TABLE LIKE. transformTableLikeClause believed that it could process extended statistics immediately because "the representation of CreateStatsStmt doesn't depend on column numbers". That was true when extended stats were first introduced, b

pgsql: Fix handling of extended expression statistics in CREATE TABLE L

Fix handling of extended expression statistics in CREATE TABLE LIKE. transformTableLikeClause believed that it could process extended statistics immediately because "the representation of CreateStatsStmt doesn't depend on column numbers". That was true when extended stats were first introduced, b

pgsql: Fix handling of extended expression statistics in CREATE TABLE L

Fix handling of extended expression statistics in CREATE TABLE LIKE. transformTableLikeClause believed that it could process extended statistics immediately because "the representation of CreateStatsStmt doesn't depend on column numbers". That was true when extended stats were first introduced, b

pgsql: Tag refs/tags/REL_17_BETA1 was created

Tag refs/tags/REL_17_BETA1 was created.