pgsql: Doc: Update information about manually creating slots.

Doc: Update information about manually creating slots. There are some cases (e.g. when the subscription is created using the connect = false option) where the remote replication slot was not created automatically and the user must create it manually before the subscription can be activated. There

pgsql: Improve the description of XLOG_RUNNING_XACTS.

Improve the description of XLOG_RUNNING_XACTS. Previously, the description of XLOG_RUNNING_XACTS showed only top-transaction XIDs and whether subtransactions overflowed. This commit improves it to show individual subtransaction XIDs. This also improves the description of overflowed subtransactions

pgsql: doc: Fix some descriptions related to pg_ident_file_mappings

doc: Fix some descriptions related to pg_ident_file_mappings pg_ident_file_mappings.line_number was described as a line number in pg_ident.conf for a "rule" number, but this should refer to a "map". The same inconsistent term was used in the main paragraph describing the view. Extracted from a pa

pgsql: doc: Fix some descriptions related to pg_ident_file_mappings

doc: Fix some descriptions related to pg_ident_file_mappings pg_ident_file_mappings.line_number was described as a line number in pg_ident.conf for a "rule" number, but this should refer to a "map". The same inconsistent term was used in the main paragraph describing the view. Extracted from a pa

pgsql: Fix outdated comment in tuplesort.h

Fix outdated comment in tuplesort.h This was outdated by 77bae396d. Backpatch-through: 15, where 77bae396d was added Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/23f44276123031d21cffeb699d9863149e1c734f Modified Files -- src/include/utils/tup

pgsql: Fix outdated comment in tuplesort.h

Fix outdated comment in tuplesort.h This was outdated by 77bae396d. Backpatch-through: 15, where 77bae396d was added Branch -- master Details --- https://git.postgresql.org/pg/commitdiff/3712e0ed47d126e9aa656a34dd56d52770b672b7 Modified Files -- src/include/utils/tuplesort.

pgsql: Remove code handling FORCE_NULL and FORCE_NOT_NULL for COPY TO

Remove code handling FORCE_NULL and FORCE_NOT_NULL for COPY TO These two options are only available with COPY FROM, so the extra logic in charge of checking the validity of the attributes given has no purpose. Author: Zhang Mingli Reviewed-by: Richard Guo, Kyotaro Horiguchi Discussion: https://po

pgsql: Add doubly linked count list implementation

Add doubly linked count list implementation We have various requirements when using a dlist_head to keep track of the number of items in the list. This, traditionally, has been done by maintaining a counter variable in the calling code. Here we tidy this up by adding "dclist", which is very simi

pgsql: Add more tests for COPY with incorrect option combinations

Add more tests for COPY with incorrect option combinations Based on the existing coverage report, some combinations were not checked at all, so add some tests to do so. Spotted while looking at the area. Discussion: https://postgr.es/m/y2dnm9u7hzixc...@paquier.xyz Branch -- master Details

pgsql: Update time zone data files to tzdata release 2022f.

Update time zone data files to tzdata release 2022f. DST law changes in Chile, Fiji, Iran, Jordan, Mexico, Palestine, and Syria. Historical corrections for Chile, Crimea, Iran, and Mexico. Also, the Europe/Kiev zone has been renamed to Europe/Kyiv (retaining the old name as a link). The followi

pgsql: Update time zone data files to tzdata release 2022f.

Update time zone data files to tzdata release 2022f. DST law changes in Chile, Fiji, Iran, Jordan, Mexico, Palestine, and Syria. Historical corrections for Chile, Crimea, Iran, and Mexico. Also, the Europe/Kiev zone has been renamed to Europe/Kyiv (retaining the old name as a link). The followi

pgsql: Update time zone data files to tzdata release 2022f.

Update time zone data files to tzdata release 2022f. DST law changes in Chile, Fiji, Iran, Jordan, Mexico, Palestine, and Syria. Historical corrections for Chile, Crimea, Iran, and Mexico. Also, the Europe/Kiev zone has been renamed to Europe/Kyiv (retaining the old name as a link). The followi

pgsql: Update time zone data files to tzdata release 2022f.

Update time zone data files to tzdata release 2022f. DST law changes in Chile, Fiji, Iran, Jordan, Mexico, Palestine, and Syria. Historical corrections for Chile, Crimea, Iran, and Mexico. Also, the Europe/Kiev zone has been renamed to Europe/Kyiv (retaining the old name as a link). The followi

pgsql: Update time zone data files to tzdata release 2022f.

Update time zone data files to tzdata release 2022f. DST law changes in Chile, Fiji, Iran, Jordan, Mexico, Palestine, and Syria. Historical corrections for Chile, Crimea, Iran, and Mexico. Also, the Europe/Kiev zone has been renamed to Europe/Kyiv (retaining the old name as a link). The followi

pgsql: Update time zone data files to tzdata release 2022f.

Update time zone data files to tzdata release 2022f. DST law changes in Chile, Fiji, Iran, Jordan, Mexico, Palestine, and Syria. Historical corrections for Chile, Crimea, Iran, and Mexico. Also, the Europe/Kiev zone has been renamed to Europe/Kyiv (retaining the old name as a link). The followi

pgsql: Update time zone data files to tzdata release 2022f.

Update time zone data files to tzdata release 2022f. DST law changes in Chile, Fiji, Iran, Jordan, Mexico, Palestine, and Syria. Historical corrections for Chile, Crimea, Iran, and Mexico. Also, the Europe/Kiev zone has been renamed to Europe/Kyiv (retaining the old name as a link). The followi

pgsql: Fix planner failure with extended statistics on partitioned tabl

Fix planner failure with extended statistics on partitioned tables. Some cases would result in "cache lookup failed for statistics object", due to trying to fetch inherited statistics when only non-inherited ones are available or vice versa. Richard Guo and Justin Pryzby Discussion: https://post

pgsql: Fix planner failure with extended statistics on partitioned tabl

Fix planner failure with extended statistics on partitioned tables. Some cases would result in "cache lookup failed for statistics object", due to trying to fetch inherited statistics when only non-inherited ones are available or vice versa. Richard Guo and Justin Pryzby Discussion: https://post

pgsql: pg_stat_statements: fetch stmt location/length before it disappe

pg_stat_statements: fetch stmt location/length before it disappears. When executing a utility statement, we must fetch everything we need out of the PlannedStmt data structure before calling standard_ProcessUtility. In certain cases (possibly only ROLLBACK in extended query protocol), that data s

pgsql: pg_stat_statements: fetch stmt location/length before it disappe

pg_stat_statements: fetch stmt location/length before it disappears. When executing a utility statement, we must fetch everything we need out of the PlannedStmt data structure before calling standard_ProcessUtility. In certain cases (possibly only ROLLBACK in extended query protocol), that data s

pgsql: pg_stat_statements: fetch stmt location/length before it disappe

pg_stat_statements: fetch stmt location/length before it disappears. When executing a utility statement, we must fetch everything we need out of the PlannedStmt data structure before calling standard_ProcessUtility. In certain cases (possibly only ROLLBACK in extended query protocol), that data s

pgsql: pg_stat_statements: fetch stmt location/length before it disappe

pg_stat_statements: fetch stmt location/length before it disappears. When executing a utility statement, we must fetch everything we need out of the PlannedStmt data structure before calling standard_ProcessUtility. In certain cases (possibly only ROLLBACK in extended query protocol), that data s

pgsql: pg_stat_statements: fetch stmt location/length before it disappe

pg_stat_statements: fetch stmt location/length before it disappears. When executing a utility statement, we must fetch everything we need out of the PlannedStmt data structure before calling standard_ProcessUtility. In certain cases (possibly only ROLLBACK in extended query protocol), that data s

pgsql: pg_stat_statements: fetch stmt location/length before it disappe

pg_stat_statements: fetch stmt location/length before it disappears. When executing a utility statement, we must fetch everything we need out of the PlannedStmt data structure before calling standard_ProcessUtility. In certain cases (possibly only ROLLBACK in extended query protocol), that data s

pgsql: pg_stat_statements: fetch stmt location/length before it disappe

pg_stat_statements: fetch stmt location/length before it disappears. When executing a utility statement, we must fetch everything we need out of the PlannedStmt data structure before calling standard_ProcessUtility. In certain cases (possibly only ROLLBACK in extended query protocol), that data s

pgsql: doc: Add note about lack of publication privileges

doc: Add note about lack of publication privileges This gives some additional advice on using row filters and column lists on publications securely. Author: Antonin Houska Reviewed-by: Euler Taveira Discussion: https://www.postgresql.org/message-id/flat/20330.1652105397@antos Branch -- mas

pgsql: Remove incorrect name from release notes

Remove incorrect name from release notes This name was incorrect in the underlying commit message. (The correct name is already listed.) Reported-by: Mark Wong Branch -- REL_15_STABLE Details --- https://git.postgresql.org/pg/commitdiff/d2354b6eecccb78fe697a270bd97298cbc63f477 Modifie

pgsql: psql: Improve tab completion for ALTER TABLE on identity columns

psql: Improve tab completion for ALTER TABLE on identity columns - Add tab completion for ALTER SEQUENCE … START … - Add tab completion for ALTER COLUMN … SET GENERATED … - Add tab completion for ALTER COLUMN … SET - Add tab completion for ALTER COLUMN … ADD GENERATED … AS IDENTITY Author: Dagfi