A dump/restore is not required for those running 17.X.
\nHowever, the first three security entries below describe configuration adjustments and data cleanups that you may need to make after updating.
\nAlso, if you use contrib/btree_gist or contrib/ltree, you may need to reindex indexes made with those extensions; see the relevant entries below.
Also, if you are upgrading from a version earlier than 17.6, see Section E.6.
", "compatibility_count": 0, "label": "17.11", "status_label": "Supported", "eol": "2029-11-08", "age_days": 44, "support_days": 1139}, "to_release": {"date": "2026-08-13", "build": "18.6", "major": "18", "minor": 6, "manual": "18", "status": "stable", "doc_git": "", "version": "18.6", "eol_date": "2030-11-14", "date_text": "2026-08-13", "supported": true, "manual_url": "/docs/18/release-18-6.html", "source_url": "/docs/release/18.6/", "entry_count": 140, "placeholder": false, "content_hash": "575a5072ec6e2481991ad0b4cdb89c632870708db9b883a92a47d5e531533bab", "manual_build": "18.6", "source_as_of": "", "changes_count": 140, "doc_loaded_at": "2026-09-25T02:22:44.760693", "migration_html": "A dump/restore is not required for those running 18.X.
\nHowever, the first three security entries below describe configuration adjustments and data cleanups that you may need to make after updating.
\nAlso, if you have any GIN indexes, see the changelog entry below about possibly-corrupt reltuples values for their tables.
Also, if you use contrib/btree_gist or contrib/ltree, you may need to reindex indexes made with those extensions; see the relevant entries below.
Also, if you are upgrading from a version earlier than 18.2, see Section E.4.
", "compatibility_count": 0, "label": "18.6", "status_label": "Supported", "eol": "2030-11-14", "age_days": 44, "support_days": 1510}, "groups": [{"date": "2026-08-13", "build": "18.6", "major": "18", "minor": 6, "manual": "18", "status": "stable", "doc_git": "", "version": "18.6", "eol_date": "2030-11-14", "date_text": "2026-08-13", "supported": true, "manual_url": "/docs/18/release-18-6.html", "source_url": "/docs/release/18.6/", "entry_count": 140, "placeholder": false, "content_hash": "575a5072ec6e2481991ad0b4cdb89c632870708db9b883a92a47d5e531533bab", "manual_build": "18.6", "source_as_of": "", "changes_count": 140, "doc_loaded_at": "2026-09-25T02:22:44.760693", "migration_html": "A dump/restore is not required for those running 18.X.
\nHowever, the first three security entries below describe configuration adjustments and data cleanups that you may need to make after updating.
\nAlso, if you have any GIN indexes, see the changelog entry below about possibly-corrupt reltuples values for their tables.
Also, if you use contrib/btree_gist or contrib/ltree, you may need to reindex indexes made with those extensions; see the relevant entries below.
Also, if you are upgrading from a version earlier than 18.2, see Section E.4.
", "compatibility_count": 0, "label": "18.6", "status_label": "Supported", "eol": "2030-11-14", "age_days": 44, "support_days": 1510, "entries": [{"id": "18.6-771506a0ec518830", "cves": [], "html": "Ensure that parallel GIN index builds update the table's pg_class.reltuples value correctly (Jan Nidzwetzki, Tomas Vondra) §
A parallel worker could report an uninitialized value for the number of rows it processed, leading to a bogus value for reltuples, even Infinity or NaN. Such values could lead to subsequent autovacuum and autoanalyze operations never deciding that the table needs to be processed. If so, the situation will not self-heal. A manual ANALYZE command, or creation of another index, will be needed to reset reltuples to the correct value. If you have any tables with GIN indexes, it's recommended to check to see if their reltuples entries look sane. A query such as this may be helpful:
SELECT DISTINCT t.oid::regclass, t.reltuples\nFROM pg_class t\n JOIN pg_index i ON t.oid = i.indrelid\n JOIN pg_class ic ON i.indexrelid = ic.oid\nWHERE t.relhasindex AND ic.relam = 2742;\n", "text": "Ensure that parallel GIN index builds update the table's pg_class.reltuples value correctly (Jan Nidzwetzki, Tomas Vondra) § A parallel worker could report an uninitialized value for the number of rows it processed, leading to a bogus value for reltuples, even Infinity or NaN. Such values could lead to subsequent autovacuum and autoanalyze operations never deciding that the table needs to be processed. If so, the situation will not self-heal. A manual ANALYZE command, or creation of another index, will be needed to reset reltuples to the correct value. If you have any tables with GIN indexes, it's recommended to check to see if their reltuples entries look sane. A query such as this may be helpful: SELECT DISTINCT t.oid::regclass, t.reltuples FROM pg_class t JOIN pg_index i ON t.oid = i.indrelid JOIN pg_class ic ON i.indexrelid = ic.oid WHERE t.relhasindex AND ic.relam = 2742;", "title": "Ensure that parallel GIN index builds update the table's pg_class.reltuples value correctly", "commits": ["d4420a972"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "42d01e124a3d70ce5a6d4df2a04917ae62cfd6ff67c4928b7730b4452367807c", "section_path": ["Changes"], "commit_groups": [["1232f7a08", "5707d7517", "d4420a972"]], "identity_text": "Ensure that parallel GIN index builds update the table's pg_class.reltuples value correctly (Jan Nidzwetzki, Tomas Vondra) A parallel worker could report an uninitialized value for the number of rows it processed, leading to a bogus value for reltuples, even Infinity or NaN. Such values could lead to subsequent autovacuum and autoanalyze operations never deciding that the table needs to be processed. If so, the situation will not self-heal. A manual ANALYZE command, or creation of another index, will be needed to reset reltuples to the correct value. If you have any tables with GIN indexes, it's recommended to check to see if their reltuples entries look sane. A query such as this may be helpful: SELECT DISTINCT t.oid::regclass, t.reltuples FROM pg_class t JOIN pg_index i ON t.oid = i.indrelid JOIN pg_class ic ON i.indexrelid = ic.oid WHERE t.relhasindex AND ic.relam = 2742;", "commit_aliases": ["1232f7a08", "5707d7517", "d4420a972"], "source_commits": ["d4420a972"], "source_entry_id": "18.6/changes/029", "db_id": "2bea73c0e3659c8ea68597bc29d434fd", "patch_ids": ["3ba1d61fdeb3854b8d7595ad4bc67069"], "statement_hash": "5febee3004e16621892415adb2d6ad17f0f816a84f510b674120400b485b14ac", "relations": [], "version": "18.6", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-1cf05c7dcd8bb2fd", "cves": [], "html": "
Correctly update foreign-data-wrapper state in a ModifyTable plan node after pruning result relations (Ayush Tiwari, Rafia Sabih) § §
\nPreviously, if run-time partition pruning determined that some partitions of a partitioned target table need not be scanned and the table had any foreign-table partitions, a crash or erroneous behavior was likely.
", "text": "Correctly update foreign-data-wrapper state in a ModifyTable plan node after pruning result relations (Ayush Tiwari, Rafia Sabih) § § Previously, if run-time partition pruning determined that some partitions of a partitioned target table need not be scanned and the table had any foreign-table partitions, a crash or erroneous behavior was likely.", "title": "Correctly update foreign-data-wrapper state in a ModifyTable plan node after pruning result relations", "commits": ["1ef917e3a", "bba4e095d"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "9097b4cd39a85f24d5f6c0e2fa3135319dd9d272e7e93aca7e7e9932563698d2", "section_path": ["Changes"], "commit_groups": [["1ef917e3a", "b43f8aa4c"], ["bba4e095d"]], "identity_text": "Correctly update foreign-data-wrapper state in a ModifyTable plan node after pruning result relations (Ayush Tiwari, Rafia Sabih) Previously, if run-time partition pruning determined that some partitions of a partitioned target table need not be scanned and the table had any foreign-table partitions, a crash or erroneous behavior was likely.", "commit_aliases": ["1ef917e3a", "b43f8aa4c", "bba4e095d"], "source_commits": ["1ef917e3a", "bba4e095d"], "source_entry_id": "18.6/changes/032", "db_id": "2b8134603cff445d9ecd4c835cbe2a6e", "patch_ids": ["46e6b35613de84cd63addb686c943afb", "7972012e2e1068ee15bfecc0258e4f2a"], "statement_hash": "c3f25655c3d5080eb4703b55d0bbd7dd434df2bff0f889c492e293272595f57d", "relations": [], "version": "18.6", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-4a48d24c7f8eeec1", "cves": [], "html": "Fix missed concurrent update in UPDATE with RETURNING OLD on a table that has a BEFORE UPDATE trigger (Dean Rasheed) §
If the target row was concurrently updated, then at isolation level READ COMMITTED any OLD values in RETURNING should reflect the updated row. But stale values were returned if there was a trigger (although the trigger itself, and the final output row, saw the correct values).
Fix hash join performance issue when there are multiple join keys and many NULL values (David Rowley) §
\nNull-keyed tuples should not get inserted into the hash table, since they will never match any other tuples. The code got this wrong if the null was in a non-last join column, bloating the hash table quite a lot if many inputs contain nulls.
", "text": "Fix hash join performance issue when there are multiple join keys and many NULL values (David Rowley) § Null-keyed tuples should not get inserted into the hash table, since they will never match any other tuples. The code got this wrong if the null was in a non-last join column, bloating the hash table quite a lot if many inputs contain nulls.", "title": "Fix hash join performance issue when there are multiple join keys and many NULL values", "commits": ["f70acc8a2"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "a2215a6115900b68d1877c40187dbb0cf3142d42635ac903a285d313f595979c", "section_path": ["Changes"], "commit_groups": [["60826a352", "a71a348ed", "f70acc8a2"]], "identity_text": "Fix hash join performance issue when there are multiple join keys and many NULL values (David Rowley) Null-keyed tuples should not get inserted into the hash table, since they will never match any other tuples. The code got this wrong if the null was in a non-last join column, bloating the hash table quite a lot if many inputs contain nulls.", "commit_aliases": ["60826a352", "a71a348ed", "f70acc8a2"], "source_commits": ["f70acc8a2"], "source_entry_id": "18.6/changes/034", "db_id": "b86d64491c7200dcd007d54d6a962628", "patch_ids": ["697f23d3ba44fd5f0f409f3e57d332b0"], "statement_hash": "9cb938e6d1f9c4bd4956e1e17c2a8c000498ab703f9836c62d8937f30c3dfeaf", "relations": [], "version": "18.6", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-c5b329365b75d540", "cves": [], "html": "Fix parsing of parenthesized OLD/NEW in RETURNING expressions (Marko Grujic) §
Expressions such as (old).colname and (old).* were mis-handled, effectively converting them to NEW references.
Clean up PlaceHolderVars more thoroughly during join removal (Richard Guo, Arne Roland) § §
\nThis fix corrects various edge cases that could trip assertions or result in incorrect plans.
", "text": "Clean up PlaceHolderVars more thoroughly during join removal (Richard Guo, Arne Roland) § § This fix corrects various edge cases that could trip assertions or result in incorrect plans.", "title": "Clean up PlaceHolderVars more thoroughly during join removal", "commits": ["18105e6db", "e02526795"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "7baeb4799ba10a67535a51042cb67368e6f775deb642040394941009b4d2631c", "section_path": ["Changes"], "commit_groups": [["18105e6db", "aae47813a", "d68576bcf"], ["9a60f295b", "e02526795"]], "identity_text": "Clean up PlaceHolderVars more thoroughly during join removal (Richard Guo, Arne Roland) This fix corrects various edge cases that could trip assertions or result in incorrect plans.", "commit_aliases": ["18105e6db", "9a60f295b", "aae47813a", "d68576bcf", "e02526795"], "source_commits": ["18105e6db", "e02526795"], "source_entry_id": "18.6/changes/038", "db_id": "7287a2439ac16ed2b13a58ded903d600", "patch_ids": ["dad98679fdb945f46899a1cf96a43235", "efd98d1529cbbfc26850e87cacb3d2d3"], "statement_hash": "8ac2ba046ee3e00a0a68bc894a425dc73015f576c3ed6cc93d8f10f0a991adec", "relations": [], "version": "18.6", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-671435cc27948d1c", "cves": [], "html": "Avoid pushing WHERE clauses down past a grouping step that has a different equivalence rule (Richard Guo) §
A test on a grouping column that is grouped by a nondeterministic collation is safe to push down only if it is a comparison using that same collation. Otherwise it might filter some rows the grouping would have merged.
", "text": "Avoid pushing WHERE clauses down past a grouping step that has a different equivalence rule (Richard Guo) § A test on a grouping column that is grouped by a nondeterministic collation is safe to push down only if it is a comparison using that same collation. Otherwise it might filter some rows the grouping would have merged.", "title": "Avoid pushing WHERE clauses down past a grouping step that has a different equivalence rule", "commits": ["fe5d62951"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "48b740a410e4123a116a78b26c3c7594ce144c3b75195fbc3b847e3990659bc6", "section_path": ["Changes"], "commit_groups": [["44fb59fc6", "98d5d7ee6", "fe5d62951"]], "identity_text": "Avoid pushing WHERE clauses down past a grouping step that has a different equivalence rule (Richard Guo) A test on a grouping column that is grouped by a nondeterministic collation is safe to push down only if it is a comparison using that same collation. Otherwise it might filter some rows the grouping would have merged.", "commit_aliases": ["44fb59fc6", "98d5d7ee6", "fe5d62951"], "source_commits": ["fe5d62951"], "source_entry_id": "18.6/changes/040", "db_id": "8a5302ba87723cdae5cab329b237ef44", "patch_ids": ["797e4b8a009ec7e54b9f5e0d46c255b2"], "statement_hash": "06dd2db2f4d9fa1b243241abc89c3c8c94b969cacd2dee10ca07caa830e7c4e4", "relations": [], "version": "18.6", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-e9b3bdb4cdd524a5", "cves": [], "html": "Avoid “cache lookup failed for collation 0” error when planner looks up statistics for a column of type \"char\" (Feng Wu) §
Prevent setting NO INHERIT on partitioned NOT NULL constraints via ALTER CONSTRAINT (Andreas Karlsson) §
NOT NULL constraints on partitioned tables are supposed to be inherited by all partitions, and therefore must not be marked NO INHERIT. This rule was correctly enforced by constraint creation, but not by ALTER TABLE ... ALTER CONSTRAINT.
Fix LIKE matching with nondeterministic collations and backslashes (Nitin Motiani, Tom Lane) § §
When using a nondeterministic collation, LIKE mishandled an escaped backslash (\\\\), treating it as effectively not there. It also did the wrong thing with a leading backslash preceding an ordinary character; in that case the backslash should be effectively ignored, but it caused the ordinary character to be matched exactly rather than allowing the nondeterministic collation to decide if there's a match.
Fix LIKE/regex optimization for indexscan with exact-match pattern (Jelte Fennema-Nio) §
Refactoring for LIKE with non-deterministic collations accidentally broke the optimization for converting a LIKE or regex exact-match pattern to an equality index condition when the index collation doesn't match the expression collation. Among other things, that made psql's \\d command much slower.tablename
Fix matching of localized month/day names in to_date() (Heikki Linnakangas) § §
The matching logic misbehaved in cases where case-folding changes the byte length of the string.
", "text": "Fix matching of localized month/day names in to_date() (Heikki Linnakangas) § § The matching logic misbehaved in cases where case-folding changes the byte length of the string.", "title": "Fix matching of localized month/day names in to_date()", "commits": ["011384ba4", "5f003855e"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "9fe2ae50e9bfc4ced876406d6b2428ee94aab62e6e58788cfe5038327a31c0c3", "section_path": ["Changes"], "commit_groups": [["011384ba4", "0de744cd5", "49a712f32", "55ea76426", "8acfaa12a", "b594efe52", "fd2b89854"], ["5f003855e"]], "identity_text": "Fix matching of localized month/day names in to_date() (Heikki Linnakangas) The matching logic misbehaved in cases where case-folding changes the byte length of the string.", "commit_aliases": ["011384ba4", "0de744cd5", "49a712f32", "55ea76426", "5f003855e", "8acfaa12a", "b594efe52", "fd2b89854"], "source_commits": ["011384ba4", "5f003855e"], "source_entry_id": "18.6/changes/052", "db_id": "eb74da46a95f0db0c15adface2feaffa", "patch_ids": ["34110329d25e6401c920fba619dc5a15", "b8ca654311e23485845960b9d01e76fc"], "statement_hash": "ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da", "relations": [{"rule": 2, "type": "related", "target": "0800233346f3a252c62d9a6f579d5573", "evidence": {"same_day": true, "patch_ids": ["b8ca654311e23485845960b9d01e76fc"], "statement_hash": "ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"}}, {"rule": 2, "type": "related", "target": "08bd69e7cd8f7b8bd4623958f924ac19", "evidence": {"same_day": true, "patch_ids": ["b8ca654311e23485845960b9d01e76fc"], "statement_hash": "ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"}}, {"rule": 2, "type": "related", "target": "b0d8986fede0f1216361d5a43a076e4e", "evidence": {"same_day": true, "patch_ids": ["b8ca654311e23485845960b9d01e76fc"], "statement_hash": "ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"}}, {"rule": 2, "type": "related", "target": "d3800c6695b429dd746c574f0d0d93e5", "evidence": {"same_day": true, "patch_ids": ["b8ca654311e23485845960b9d01e76fc"], "statement_hash": "ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"}}], "version": "18.6", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": [{"db_id": "b0d8986fede0f1216361d5a43a076e4e", "kind": "related", "version": "17.11", "label": "17.11", "title": "Fix matching of localized month/day names in to_date()", "evidence": {"same_day": true, "patch_ids": ["b8ca654311e23485845960b9d01e76fc"], "statement_hash": "ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"}, "url": "/docs/compare/?release=17.11#17.11-8557fc5fb2204540", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES"}, {"db_id": "08bd69e7cd8f7b8bd4623958f924ac19", "kind": "related", "version": "16.15", "label": "16.15", "title": "Fix matching of localized month/day names in to_date()", "evidence": {"same_day": true, "patch_ids": ["b8ca654311e23485845960b9d01e76fc"], "statement_hash": "ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"}, "url": "/docs/compare/?release=16.15#16.15-6af7d41f64cafafa", "source_url": "/docs/release/16.15/#RELEASE-16-15-CHANGES"}, {"db_id": "0800233346f3a252c62d9a6f579d5573", "kind": "related", "version": "15.19", "label": "15.19", "title": "Fix matching of localized month/day names in to_date()", "evidence": {"same_day": true, "patch_ids": ["b8ca654311e23485845960b9d01e76fc"], "statement_hash": "ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"}, "url": "/docs/compare/?release=15.19#15.19-a96cc8b4c22ffe2e", "source_url": "/docs/release/15.19/#id-1.11.6.6.5"}, {"db_id": "d3800c6695b429dd746c574f0d0d93e5", "kind": "related", "version": "14.24", "label": "14.24", "title": "Fix matching of localized month/day names in to_date()", "evidence": {"same_day": true, "patch_ids": ["b8ca654311e23485845960b9d01e76fc"], "statement_hash": "ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"}, "url": "/docs/compare/?release=14.24#14.24-8ab3e783a00643a8", "source_url": "/docs/release/14.24/#id-1.11.6.6.6"}]}, {"id": "18.6-e4b72f9a6fc1a4a4", "cves": [], "html": "Correct case-folding rules for Greek final sigma (Jeff Davis) §
\nIf the string is preceded only by Case Ignorable characters, don't consider it to be a final sigma. This only affects the built-in pg_unicode_fast locale.
Reject out-of-range timestamp shift values in uuidv7() (Baji Shaik) §
The shift value must not be so large as to produce a timestamp out of the range that a v7 UUID can represent. Previously, a garbage UUID value was produced.
", "text": "Reject out-of-range timestamp shift values in uuidv7() (Baji Shaik) § The shift value must not be so large as to produce a timestamp out of the range that a v7 UUID can represent. Previously, a garbage UUID value was produced.", "title": "Reject out-of-range timestamp shift values in uuidv7()", "commits": ["c31b0fca0"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "02eb6fc1f39bf79a5e9ad65d69a91d28ac6cdc3b2f7832b8811f2fd6ad0fff1f", "section_path": ["Changes"], "commit_groups": [["2a933deaa", "7575215e0", "c31b0fca0"]], "identity_text": "Reject out-of-range timestamp shift values in uuidv7() (Baji Shaik) The shift value must not be so large as to produce a timestamp out of the range that a v7 UUID can represent. Previously, a garbage UUID value was produced.", "commit_aliases": ["2a933deaa", "7575215e0", "c31b0fca0"], "source_commits": ["c31b0fca0"], "source_entry_id": "18.6/changes/061", "db_id": "4ba47e1101fe0dc93dfdf09978a397f7", "patch_ids": ["98b79989c57e289aff70a4f3cb8d7680"], "statement_hash": "30752f07a027de559876959a4bd468e260cc47a4bc30f24960ea23366b39f35e", "relations": [], "version": "18.6", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-d9671d1ad39e8c30", "cves": [], "html": "Prevent “no empty local buffer available” errors during temporary table access (Melanie Plageman) §
\nLimit the number of local buffers that the read streaming mechanism is allowed to use. Previously, a large value of effective_io_concurrency could allow a single stream to use all the buffers, resulting in failure.
Restore full use of shared buffer pool in VACUUM's wraparound failsafe mode (Melanie Plageman) § §
An ordinary VACUUM is limited to use just a few shared buffers, so as not to impinge too much on other processing. However, in failsafe mode we want to reclaim transaction IDs as quickly as possible, so that limit is supposed to be abandoned to allow vacuuming to proceed as fast as possible. This behavior was accidentally broken during refactoring in v18; restore it.
Fix JIT-compiled tuple deconstruction code to account correctly for virtual generated columns (David Rowley) §
", "text": "Fix JIT-compiled tuple deconstruction code to account correctly for virtual generated columns (David Rowley) §", "title": "Fix JIT-compiled tuple deconstruction code to account correctly for virtual generated columns", "commits": ["e9692de1d"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "d8b6408afef1a01cea4ed9e7255b21a66f6a2269a77fb40199d08aed00ee87a7", "section_path": ["Changes"], "commit_groups": [["dc5116780", "e9692de1d"]], "identity_text": "Fix JIT-compiled tuple deconstruction code to account correctly for virtual generated columns (David Rowley)", "commit_aliases": ["dc5116780", "e9692de1d"], "source_commits": ["e9692de1d"], "source_entry_id": "18.6/changes/079", "db_id": "5d966088a095e18332fc3fae2df8943c", "patch_ids": ["5b06ca9ccac80b782c6215117ad2b6f3"], "statement_hash": "108a7033ad22cb766018c23cec70aac4e45d29f7e41fbdfe619f05d9039da69e", "relations": [], "version": "18.6", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-fe809e2024f47bd3", "cves": [], "html": "Prevent accepting hot-standby connections before WAL replay has reached a consistent database state (Nikhil Sontakke) §
", "text": "Prevent accepting hot-standby connections before WAL replay has reached a consistent database state (Nikhil Sontakke) §", "title": "Prevent accepting hot-standby connections before WAL replay has reached a consistent database state", "commits": ["311e66df9"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "8b317869ae141be91e8dec8efd1716dafab967ff2900378e9d1e5e1a60e43286", "section_path": ["Changes"], "commit_groups": [["311e66df9", "7673dfe77", "b59783502"]], "identity_text": "Prevent accepting hot-standby connections before WAL replay has reached a consistent database state (Nikhil Sontakke)", "commit_aliases": ["311e66df9", "7673dfe77", "b59783502"], "source_commits": ["311e66df9"], "source_entry_id": "18.6/changes/093", "db_id": "ca322b7422c7864dcfe83a827441f183", "patch_ids": ["c006640df5f2be4c0af354adc9b3739e"], "statement_hash": "c2216840c8e764a88ae341a1741319888a2b275d882def3b439922ca5a525ddc", "relations": [], "version": "18.6", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-62f8d7fac7e94f66", "cves": [], "html": "Avoid recording incorrect I/O operation statistics after a failed read or write (Bertrand Drouvot) §
", "text": "Avoid recording incorrect I/O operation statistics after a failed read or write (Bertrand Drouvot) §", "title": "Avoid recording incorrect I/O operation statistics after a failed read or write", "commits": ["13f940b4b"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "8c2ec8b48869b5269106dca7f2cac2aa798943ce27c0456e0988651fa1953022", "section_path": ["Changes"], "commit_groups": [["13f940b4b", "3048e8130"]], "identity_text": "Avoid recording incorrect I/O operation statistics after a failed read or write (Bertrand Drouvot)", "commit_aliases": ["13f940b4b", "3048e8130"], "source_commits": ["13f940b4b"], "source_entry_id": "18.6/changes/101", "db_id": "eb60b9ab1b9e4814af98c8013ccaaefc", "patch_ids": ["51ef28bcac96b451b9c22362030f5034"], "statement_hash": "1ee5c678ab1708424e1e440c9385d800ef55fb4ff8fab375174baaad825421f1", "relations": [], "version": "18.6", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-1ca0e17d82442acb", "cves": [], "html": "Improve libpq's handling of out-of-memory conditions (Anthonin Bonnefoy) §
", "text": "Improve libpq's handling of out-of-memory conditions (Anthonin Bonnefoy) §", "title": "Improve libpq's handling of out-of-memory conditions", "commits": ["6b46a5d1b"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "38431992340fffe07fa78ab8d91ba4e891f245a36569221cb9ed86b13074c4bf", "section_path": ["Changes"], "commit_groups": [["676bf48e1", "6b46a5d1b", "8380013cd"]], "identity_text": "Improve libpq's handling of out-of-memory conditions (Anthonin Bonnefoy)", "commit_aliases": ["676bf48e1", "6b46a5d1b", "8380013cd"], "source_commits": ["6b46a5d1b"], "source_entry_id": "18.6/changes/105", "db_id": "702619bca4eafa5ec897c54c44899700", "patch_ids": ["ac21c3ce2ae02e085ed3866481058001"], "statement_hash": "eec6ec640464f740117d7e235a58f7b9f7d0ab46f08ef5a5d2037538eab150c9", "relations": [], "version": "18.6", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-2070f350641c3bd5", "cves": [], "html": "Fix libpq's trace facility to print new-style BackendKeyData and CancelRequest messages correctly (Anthonin Bonnefoy) §
", "text": "Fix libpq's trace facility to print new-style BackendKeyData and CancelRequest messages correctly (Anthonin Bonnefoy) §", "title": "Fix libpq's trace facility to print new-style BackendKeyData and CancelRequest messages correctly", "commits": ["dd5eca055"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "5f13cf168ff8b4075ae64e38a62713e18f734eca0e447ebefd908379324afed9", "section_path": ["Changes"], "commit_groups": [["0766bc57e", "b22b61905", "dd5eca055"]], "identity_text": "Fix libpq's trace facility to print new-style BackendKeyData and CancelRequest messages correctly (Anthonin Bonnefoy)", "commit_aliases": ["0766bc57e", "b22b61905", "dd5eca055"], "source_commits": ["dd5eca055"], "source_entry_id": "18.6/changes/106", "db_id": "fd5dcb29b0fd1252d10a21b8c0cdcb8c", "patch_ids": ["c7d629e80647c3be8fd73079d8a1b5ce"], "statement_hash": "f7529c3c3921210742bad5f01a4dc3306780887b530249441e741d2209b3e067", "relations": [], "version": "18.6", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-7aa882d7346d6ba9", "cves": [], "html": "Fix null-pointer crash in ecpg compiler (Jehan-Guillaume de Rorthais) §
\necpg failed on a DECLARE section containing a union nested inside a struct.
Fix issues with deferred errors in pipeline mode in psql (Michael Paquier) §
\npsql could get stuck or suffer an assertion failure in some scenarios where the server reports an error in response to a Sync message, such as a deferred constraint violation.
", "text": "Fix issues with deferred errors in pipeline mode in psql (Michael Paquier) § psql could get stuck or suffer an assertion failure in some scenarios where the server reports an error in response to a Sync message, such as a deferred constraint violation.", "title": "Fix issues with deferred errors in pipeline mode in psql", "commits": ["1e9bc4074"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "0b6a251cbdd63ef30c411a5700968044736d26485b0b2c00c8ca1c01814cb13e", "section_path": ["Changes"], "commit_groups": [["1e9bc4074", "d21604e17"]], "identity_text": "Fix issues with deferred errors in pipeline mode in psql (Michael Paquier) psql could get stuck or suffer an assertion failure in some scenarios where the server reports an error in response to a Sync message, such as a deferred constraint violation.", "commit_aliases": ["1e9bc4074", "d21604e17"], "source_commits": ["1e9bc4074"], "source_entry_id": "18.6/changes/110", "db_id": "72a7f65480654f93eac8950b0559cbc0", "patch_ids": ["fd3b0e71a3f8eb28e4ab3713dc100752"], "statement_hash": "9b5d97f70333cd1039a7854f6dd2a1fd15944a41f9681c94182b6c05e41f7ed4", "relations": [], "version": "18.6", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-f4ed56f70dce1993", "cves": [], "html": "Enforce the intended upper limit for psql's special variable WATCH_INTERVAL (Sven Klemm, Daniel Gustafsson) §
If a too-large value was given, psql reported an error but applied the setting anyway.
", "text": "Enforce the intended upper limit for psql's special variable WATCH_INTERVAL (Sven Klemm, Daniel Gustafsson) § If a too-large value was given, psql reported an error but applied the setting anyway.", "title": "Enforce the intended upper limit for psql's special variable WATCH_INTERVAL", "commits": ["e0c641ebb"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "ab27f170112801ffa643398355061630ad04b9a25cfe9388df28aace143d3e11", "section_path": ["Changes"], "commit_groups": [["e04910a9a", "e0c641ebb"]], "identity_text": "Enforce the intended upper limit for psql's special variable WATCH_INTERVAL (Sven Klemm, Daniel Gustafsson) If a too-large value was given, psql reported an error but applied the setting anyway.", "commit_aliases": ["e04910a9a", "e0c641ebb"], "source_commits": ["e0c641ebb"], "source_entry_id": "18.6/changes/112", "db_id": "da4e14855386a41b1b007342405420fd", "patch_ids": ["89fd801900bdac240cfcf7a7e686b427"], "statement_hash": "642fd9555fa98a6c5630f67a94fa38617df76e4b28a80be73c949d4f69a344f4", "relations": [], "version": "18.6", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-5e4a18698665afbd", "cves": [], "html": "Fix inconsistent behavior of pg_restore with --statistics or --statistics-only (Chao Li, Michael Paquier) § §
When combined with other selective-restore options such as --schema, these options failed to restore the expected items, unlike pg_dump with similar options.
Fix vacuumdb --missing-stats-only to ignore partitioned expression indexes (Baji Shaik) §
Previously, vacuumdb would always attempt to ANALYZE the partitioned table, accomplishing nothing since statistics are never created for partitioned indexes, only for their leaf indexes.
In contrib/amcheck, fix failure to report corruption of a btree metapage's allequalimage flag (Chao Li) §
In contrib/amcheck, fix query-lifespan memory leak while verifying a GIN index (Kirill Reshke) §
In contrib/btree_gist, fix sorting of bit/varbit entries during GiST index construction (Tom Lane) §
Values of bit types were sorted as though they were byteas, which did not cause any obvious failure but would result in an inefficient index, since the types' representations are different. It is recommended to reindex btree_gist indexes on bit columns after installing this update.
In contrib/dblink and contrib/postgres_fdw, ensure that a user-mapping setting for use_scram_passthrough overrides one for a foreign server (Matheus Alcantara) § §
Previously the precedence went the other way, but that is inconsistent with the behavior of other foreign-table options.
", "text": "In contrib/dblink and contrib/postgres_fdw, ensure that a user-mapping setting for use_scram_passthrough overrides one for a foreign server (Matheus Alcantara) § § Previously the precedence went the other way, but that is inconsistent with the behavior of other foreign-table options.", "title": "In contrib/dblink and contrib/postgres_fdw, ensure that a user-mapping setting for use_scram_passthrough overrides one for a foreign server", "commits": ["130396e6c", "88d7748d2"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "dbd1d91619b17788c51ca8c36aeebec53d14f2020589b52c793e5a750ad59f83", "section_path": ["Changes"], "commit_groups": [["130396e6c", "5f5165e2f"], ["88d7748d2", "97f6fc10f"]], "identity_text": "In contrib/dblink and contrib/postgres_fdw, ensure that a user-mapping setting for use_scram_passthrough overrides one for a foreign server (Matheus Alcantara) Previously the precedence went the other way, but that is inconsistent with the behavior of other foreign-table options.", "commit_aliases": ["130396e6c", "5f5165e2f", "88d7748d2", "97f6fc10f"], "source_commits": ["130396e6c", "88d7748d2"], "source_entry_id": "18.6/changes/127", "db_id": "063f2bffd0990ef3fcf1cfb885de863c", "patch_ids": ["b1b74b0cc1463725747a8653fc6f9171", "bd57ecb015393dce39ef90b46d9e0490"], "statement_hash": "db8d7ee5007bfdda5824537bec6f7ef8dab92f90ad711e9f78d654634734b9ce", "relations": [], "version": "18.6", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-ff5e4d8a0c43e0de", "cves": [], "html": "Reject setting use_scram_passthrough on contrib/dblink foreign-data wrappers (Matheus Alcantara) §
This option is only meaningful on foreign servers and user mappings, but dblink incorrectly allowed it at the FDW level as well (and then ignored it).
", "text": "Reject setting use_scram_passthrough on contrib/dblink foreign-data wrappers (Matheus Alcantara) § This option is only meaningful on foreign servers and user mappings, but dblink incorrectly allowed it at the FDW level as well (and then ignored it).", "title": "Reject setting use_scram_passthrough on contrib/dblink foreign-data wrappers", "commits": ["cd777e27e"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "70de6bc6d249294e8fdeab1a24f46b7dd7ba562fcc13795d138d7ee697b1aa0f", "section_path": ["Changes"], "commit_groups": [["cd777e27e", "e2b881340"]], "identity_text": "Reject setting use_scram_passthrough on contrib/dblink foreign-data wrappers (Matheus Alcantara) This option is only meaningful on foreign servers and user mappings, but dblink incorrectly allowed it at the FDW level as well (and then ignored it).", "commit_aliases": ["cd777e27e", "e2b881340"], "source_commits": ["cd777e27e"], "source_entry_id": "18.6/changes/128", "db_id": "fcf062a479f1adf951f0e01ba9085269", "patch_ids": ["42c3eee21590032a02c95eee1fb701ea"], "statement_hash": "901c22f80f76bf023745d17a817b1d44b8d41905f41f65deeb6c657adf7865a9", "relations": [], "version": "18.6", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.6-4e6978b69317c416", "cves": [], "html": "Fix out-of-bounds access in contrib/pg_prewarm's autoprewarm worker (Matheus Alcantara) §
The code tried to fetch a value from one past the end of an array, risking a segfault.
", "text": "Fix out-of-bounds access in contrib/pg_prewarm's autoprewarm worker (Matheus Alcantara) § The code tried to fetch a value from one past the end of an array, risking a segfault.", "title": "Fix out-of-bounds access in contrib/pg_prewarm's autoprewarm worker", "commits": ["3bf2cb225"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "4fe07e991a81e828486f77914f9731842bee8fceb0d84b70e025b680b9f06924", "section_path": ["Changes"], "commit_groups": [["3bf2cb225", "dac36601f"]], "identity_text": "Fix out-of-bounds access in contrib/pg_prewarm's autoprewarm worker (Matheus Alcantara) The code tried to fetch a value from one past the end of an array, risking a segfault.", "commit_aliases": ["3bf2cb225", "dac36601f"], "source_commits": ["3bf2cb225"], "source_entry_id": "18.6/changes/133", "db_id": "deeb54842607dd110ef702b21efa1e40", "patch_ids": ["b8e5ecd5e13f4cc5d49f2b89c1f08c28"], "statement_hash": "78dd0ea4ace46cf7dd61d2a6c030af907036f2e92bdfeaf6006e3958c5b09372", "relations": [], "version": "18.6", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}]}, {"date": "2026-05-14", "build": "18.4", "major": "18", "minor": 4, "manual": "18", "status": "stable", "doc_git": "", "version": "18.4", "eol_date": "2030-11-14", "date_text": "2026-05-14", "supported": true, "manual_url": "/docs/18/release-18-4.html", "source_url": "/docs/release/18.4/", "entry_count": 74, "placeholder": false, "content_hash": "5a493ad50c657f9f1d75227f03f55e685a5c3b253f73bbfbf0f5849ce14a1328", "manual_build": "18.6", "source_as_of": "", "changes_count": 74, "doc_loaded_at": "2026-09-25T02:22:44.760693", "migration_html": "A dump/restore is not required for those running 18.X.
\nHowever, if you are upgrading from a version earlier than 18.2, see Section E.4.
", "compatibility_count": 0, "label": "18.4", "status_label": "Supported", "eol": "2030-11-14", "age_days": 135, "support_days": 1510, "entries": [{"id": "18.4-b66bfac9ca625fe0", "cves": ["CVE-2026-6575"], "html": "Detect faulty input when restoring attribute MCV statistics (Michael Paquier) §
\nThe statistics restore functions were insufficiently careful about validating most-common-value statistics, and would accept values that could crash the planner later on.
\nThe PostgreSQL Project thanks Jeroen Gui for reporting this problem. (CVE-2026-6575)
", "text": "Detect faulty input when restoring attribute MCV statistics (Michael Paquier) § The statistics restore functions were insufficiently careful about validating most-common-value statistics, and would accept values that could crash the planner later on. The PostgreSQL Project thanks Jeroen Gui for reporting this problem. (CVE-2026-6575)", "title": "Detect faulty input when restoring attribute MCV statistics", "commits": ["661095c40"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "2ed57c28e3aa4cbc7c04ba7942002bce58bb97ccc26a76547ddb32caf7c1ce65", "section_path": ["Changes"], "commit_groups": [["661095c40", "6d6348f03"]], "identity_text": "Detect faulty input when restoring attribute MCV statistics (Michael Paquier) The statistics restore functions were insufficiently careful about validating most-common-value statistics, and would accept values that could crash the planner later on. The PostgreSQL Project thanks Jeroen Gui for reporting this problem. (CVE-2026-6575)", "commit_aliases": ["661095c40", "6d6348f03"], "source_commits": ["661095c40"], "source_entry_id": "18.4/changes/006", "db_id": "ce14ae2a212d2d178a6aba00d5dd585b", "patch_ids": ["14b76df22d84c41c9cd0c4bba781d01d"], "statement_hash": "d9012182ea9860adfbb2bc765d8e5b34569eadbd1aa9127209aa68e3c78fe1f0", "relations": [], "version": "18.4", "category_label": "Security", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.4-fcf247ac879d30ab", "cves": [], "html": "Improve planner's matching of partition key columns to sub-query outputs (Richard Guo) §
\nStrip no-op PlaceHolderVars from operands before comparing them to partition keys. This change enables partition pruning to succeed in some cases where it previously failed to recognize that a partition need not be scanned.
", "text": "Improve planner's matching of partition key columns to sub-query outputs (Richard Guo) § Strip no-op PlaceHolderVars from operands before comparing them to partition keys. This change enables partition pruning to succeed in some cases where it previously failed to recognize that a partition need not be scanned.", "title": "Improve planner's matching of partition key columns to sub-query outputs", "commits": ["8e8b2bef7"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "04cfa65c27a90398206b1ff4221c2fa00dc5946461f9188c0da94f7471717161", "section_path": ["Changes"], "commit_groups": [["8e8b2bef7", "c1408956e"]], "identity_text": "Improve planner's matching of partition key columns to sub-query outputs (Richard Guo) Strip no-op PlaceHolderVars from operands before comparing them to partition keys. This change enables partition pruning to succeed in some cases where it previously failed to recognize that a partition need not be scanned.", "commit_aliases": ["8e8b2bef7", "c1408956e"], "source_commits": ["8e8b2bef7"], "source_entry_id": "18.4/changes/017", "db_id": "43a62fc09aea76b18f3d3f019ecc7d49", "patch_ids": ["ddbca8eddff456bfa8f4cca750f65073"], "statement_hash": "d93745d6ff9d6631eb0626d27278a8e4a41b1ec44b9ae76802033575d6e229b5", "relations": [], "version": "18.4", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.4-7be51988e3e04ad1", "cves": [], "html": "Fix self-join removal to handle join clauses that are bare boolean columns, e.g. ON t1.boolcol (Andrei Lepikhov, Tender Wang, Alexander Korotkov) §
Previously such a case led to a “no relation entry for relid N” error.
Fix UPDATE/DELETE ... WHERE CURRENT OF to work on tables with virtual generated columns (Satyanarayana Narlapuram, Dean Rasheed) §
Fix expansion of virtual generated columns in EXCLUDED column references in INSERT ... ON CONFLICT (Satyanarayana Narlapuram, Dean Rasheed) §
Fix spurious “indexes on virtual generated columns are not supported” errors (Robert Haas) §
\nCreation of an expression index could sometimes incorrectly report this error.
", "text": "Fix spurious “indexes on virtual generated columns are not supported” errors (Robert Haas) § Creation of an expression index could sometimes incorrectly report this error.", "title": "Fix spurious “indexes on virtual generated columns are not supported” errors", "commits": ["cceb9c18a"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "e8ac75ceb5a337d641a8170260673923d297cef2ecbba9406f19e8a55ad0722a", "section_path": ["Changes"], "commit_groups": [["570e2fcc0", "cceb9c18a"]], "identity_text": "Fix spurious indexes on virtual generated columns are not supported errors (Robert Haas) Creation of an expression index could sometimes incorrectly report this error.", "commit_aliases": ["570e2fcc0", "cceb9c18a"], "source_commits": ["cceb9c18a"], "source_entry_id": "18.4/changes/022", "db_id": "10809b505e53f4caa2198df75ce3f735", "patch_ids": ["bada2bc45007a3aca1d5b8712ebf2e04"], "statement_hash": "98a3d07fd5c51c5e159270aa6be7f88c123bf9cdcaacda474b4b39e5bc976e87", "relations": [], "version": "18.4", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.4-655416f730344aaf", "cves": [], "html": "Fix ALTER TABLE ... SET NOT NULL to invoke object-access hook functions only after completing the catalog change (Artur Zakirov) §
Fix loss of deferrability of foreign-key triggers (Yasuo Honda) §
\nPreviously, a foreign key defined as DEFERRABLE INITIALLY DEFERRED would behave as NOT DEFERRABLE after being set to NOT ENFORCED status and then back to ENFORCED.
If you have a foreign key with this problem, it can be repaired (after installing this update) by again setting it to NOT ENFORCED and then back to ENFORCED.
Fix WITHOUT OVERLAPS to allow domains (Jian He) §
UNIQUE/PRIMARY KEY ... WITHOUT OVERLAPS requires the no-overlap column to be a range or multirange, but it should allow a domain over such a type too.
Make the pg_aios system view's pid column show NULL not 0 when an entry has no owning process (ChangAo Chen) §
Fix under-allocation of shared memory used for parallel btree index scans (Siddharth Kothari) §
\nIn edge cases this could result in a server crash.
", "text": "Fix under-allocation of shared memory used for parallel btree index scans (Siddharth Kothari) § In edge cases this could result in a server crash.", "title": "Fix under-allocation of shared memory used for parallel btree index scans", "commits": ["1e71970d2"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "1ef3d6cea990bd1dcf9ef51cc71e396b6f1f0d1befdde45495a99af305979d45", "section_path": ["Changes"], "commit_groups": [["1e71970d2", "748d871b7"]], "identity_text": "Fix under-allocation of shared memory used for parallel btree index scans (Siddharth Kothari) In edge cases this could result in a server crash.", "commit_aliases": ["1e71970d2", "748d871b7"], "source_commits": ["1e71970d2"], "source_entry_id": "18.4/changes/051", "db_id": "98b5ca4b1ed9b2c07fdfe2cdb0d69c16", "patch_ids": ["2fc6e3250377e522a3426425b060e9c3"], "statement_hash": "2e4818f716b54a67ca93894bb2763fe0ec497edda3ec9887d07fefe174034d01", "relations": [], "version": "18.4", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.4-d741c04b8ba8da80", "cves": [], "html": "Fix array overrun when too many EXPLAIN extension options are installed (Joel Jacobson) §
Correctly display join alias Vars that are used in GROUP BY (Tom Lane) §
In views containing queries like SELECT ... t1 LEFT JOIN t2 USING (x) GROUP BY x, the GROUP BY clause could be displayed incorrectly by deparsing, leading to dump/restore failures. Failures occurred only if t1.x and t2.x were not of identical data types and t1.x was the side that required an implicit coercion.
Harden tar-file parsing logic against archives it can't handle (Tom Lane) §
\nThe tar-file reading code used in pg_basebackup and pg_verifybackup failed to verify that the input is a tar file at all, let alone that it fits into the subset of valid tar files that we can handle. This isn't a problem for the normal scenario where the input file was generated by PostgreSQL code, but it can be an issue if the input has been generated by some other tar program.
", "text": "Harden tar-file parsing logic against archives it can't handle (Tom Lane) § The tar-file reading code used in pg_basebackup and pg_verifybackup failed to verify that the input is a tar file at all, let alone that it fits into the subset of valid tar files that we can handle. This isn't a problem for the normal scenario where the input file was generated by PostgreSQL code, but it can be an issue if the input has been generated by some other tar program.", "title": "Harden tar-file parsing logic against archives it can't handle", "commits": ["698eae7db"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "578b25b94ff8020a981a088d55d8d16dfbcf6e5b8065316d692942d65af1a5bc", "section_path": ["Changes"], "commit_groups": [["698eae7db", "bc30c704a"]], "identity_text": "Harden tar-file parsing logic against archives it can't handle (Tom Lane) The tar-file reading code used in pg_basebackup and pg_verifybackup failed to verify that the input is a tar file at all, let alone that it fits into the subset of valid tar files that we can handle. This isn't a problem for the normal scenario where the input file was generated by PostgreSQL code, but it can be an issue if the input has been generated by some other tar program.", "commit_aliases": ["698eae7db", "bc30c704a"], "source_commits": ["698eae7db"], "source_entry_id": "18.4/changes/064", "db_id": "cfbe37010505dabb9d8718a926fa7918", "patch_ids": ["ce75739c3a49f201e6f23d201ae3df1f"], "statement_hash": "b88cecc4f1e07d97baf49826b0e6852cf61b8c4b3817c2da613355e317b533cd", "relations": [], "version": "18.4", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.4-cc6458aa3ad5fac1", "cves": [], "html": "In pg_dump, preserve NO INHERIT property of NOT NULL constraints (Jian He) §
Some cases missed printing the NO INHERIT clause.
Fix mis-structured output from contrib/pg_overexplain's RANGE_TABLE option (Satyanarayana Narlapuram) §
Some fields were misplaced in JSON, YAML, and XML formats, resulting in structurally invalid output.
", "text": "Fix mis-structured output from contrib/pg_overexplain's RANGE_TABLE option (Satyanarayana Narlapuram) § Some fields were misplaced in JSON, YAML, and XML formats, resulting in structurally invalid output.", "title": "Fix mis-structured output from contrib/pg_overexplain's RANGE_TABLE option", "commits": ["6723d462d"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "29c20b68392e7cfc54d80f25d77055ad68bce244a0febb29053ed40d82d3d99d", "section_path": ["Changes"], "commit_groups": [["059cf7f58", "6723d462d"]], "identity_text": "Fix mis-structured output from contrib/pg_overexplain's RANGE_TABLE option (Satyanarayana Narlapuram) Some fields were misplaced in JSON, YAML, and XML formats, resulting in structurally invalid output.", "commit_aliases": ["059cf7f58", "6723d462d"], "source_commits": ["6723d462d"], "source_entry_id": "18.4/changes/071", "db_id": "a966a7e34390a814b0814712e4a00fdb", "patch_ids": ["7fbc73f17a809373752c95effd8e6508"], "statement_hash": "58504c6ef9233ef351280878eed22065a06df00f1c6e2baf450c3f48ff8a566a", "relations": [], "version": "18.4", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}]}, {"date": "2026-02-26", "build": "18.3", "major": "18", "minor": 3, "manual": "18", "status": "stable", "doc_git": "", "version": "18.3", "eol_date": "2030-11-14", "date_text": "2026-02-26", "supported": true, "manual_url": "/docs/18/release-18-3.html", "source_url": "/docs/release/18.3/", "entry_count": 9, "placeholder": false, "content_hash": "0818a2beffd0714ee0bc46a9c4d50bb727030a489b1fd4d7a5774592f6c607cb", "manual_build": "18.6", "source_as_of": "", "changes_count": 9, "doc_loaded_at": "2026-09-25T02:22:44.760693", "migration_html": "A dump/restore is not required for those running 18.X.
\nHowever, if you are upgrading from a version earlier than 18.2, see Section E.4.
", "compatibility_count": 0, "label": "18.3", "status_label": "Supported", "eol": "2030-11-14", "age_days": 212, "support_days": 1510, "entries": [{"id": "18.3-760673c96f02dc6a", "cves": ["CVE-2026-2007"], "html": "Fix oversight in the fix for CVE-2026-2007 (Zsolt Parragi) §
\nIf the “bounds” array needed to be expanded, because the input contained more trigrams than the initial guess, generate_trgm_only didn't return the modified array pointer to its caller. That would lead to incorrect output from strict_word_similarity() and related functions, or in rare cases a crash. The faulty code is reached if the input string becomes longer when it's converted to lower case. The only known instances of that occur when an ICU locale is used with certain single-byte encodings.
Fix the volatility marking of json_strip_nulls() and jsonb_strip_nulls() (Andrew Dunstan) §
These functions have always been considered immutable, but refactoring in version 18 accidentally marked them stable instead. That prevents their use in index expressions and could cause unnecessary repeat evaluations in queries. This fix corrects the marking in newly-initialized database clusters (including clusters that are pg_upgrade'd to 18.3 or later). However it will not help existing clusters made using 18.0 through 18.2.
\nIf this mistake affects your usage of these functions, the recommended fix for an existing cluster is a manual catalog update. As superuser, perform
\nUPDATE pg_catalog.pg_proc SET provolatile = 'i' WHERE oid IN ('3261','3262');\n\nin each affected database. Update template0 and template1 as well, so that databases made in future will have the fix.
Avoid name collisions between user-written constraints and automatically-named NOT NULL constraints (Laurenz Albe) §
As of version 18, NOT NULL constraints have full-fledged pg_constraint entries, and therefore require names. The logic for choosing a name for an unnamed NOT NULL constraint failed to avoid conflicts with user-written constraints elsewhere in the same CREATE TABLE statement.
A dump/restore is not required for those running 18.X.
\nHowever, if you have any indexes on ltree columns, it may be necessary to reindex them after updating. See the sixth changelog entry below.
Harden contrib/pg_trgm against changes in string lowercasing behavior (Heikki Linnakangas) § §
Fix potential buffer overruns arising from the fact that in some locales lower-casing a string can produce more characters (not bytes) than were in the original. That behavior is new in version 18, and so is the bug.
\nThe PostgreSQL Project thanks Heikki Linnakangas for reporting this problem. (CVE-2026-2007)
", "text": "Harden contrib/pg_trgm against changes in string lowercasing behavior (Heikki Linnakangas) § § Fix potential buffer overruns arising from the fact that in some locales lower-casing a string can produce more characters (not bytes) than were in the original. That behavior is new in version 18, and so is the bug. The PostgreSQL Project thanks Heikki Linnakangas for reporting this problem. (CVE-2026-2007)", "title": "Harden contrib/pg_trgm against changes in string lowercasing behavior", "commits": ["18548681d", "e0965fb1a"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "4ca1b05495d40ac64500fd5b28f5325eae1f38a331b7a0742faa0c82d591ebed", "section_path": ["Changes"], "commit_groups": [["00896ddaf", "e0965fb1a"], ["18548681d", "54598670f"]], "identity_text": "Harden contrib/pg_trgm against changes in string lowercasing behavior (Heikki Linnakangas) Fix potential buffer overruns arising from the fact that in some locales lower-casing a string can produce more characters (not bytes) than were in the original. That behavior is new in version 18, and so is the bug. The PostgreSQL Project thanks Heikki Linnakangas for reporting this problem. (CVE-2026-2007)", "commit_aliases": ["00896ddaf", "18548681d", "54598670f", "e0965fb1a"], "source_commits": ["18548681d", "e0965fb1a"], "source_entry_id": "18.2/changes/005", "db_id": "95fa609ca10598fcbb0e28380f59c52b", "patch_ids": ["5701670e8636f3ad6e90ece759b0f13c", "58324894c92d02a2d347ffa71bcabd58"], "statement_hash": "842194f3cb8ebb43fc2cf44a76c56bf4cdf698c126f74cd0b634e06ad05f42e6", "relations": [], "version": "18.2", "category_label": "Security", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-8107ada0cc1987cf", "cves": [], "html": "Fix inconsistent case-insensitive matching in contrib/ltree (Jeff Davis) § §
Index-related routines in ltree used a different implementation of case-folding than the primary operators did. Their behavior was equivalent only if the default collation provider was libc and the encoding was single-byte.
To fix, change the code to use case-folding with the database's default collation. This change will require reindexing indexes on ltree columns (regardless of the index access method) unless the database uses libc as collation provider and its encoding is single-byte. Without that, searches of such indexes will fail to locate relevant entries.
When using ALTER TABLE ... ADD CONSTRAINT to add a not-null constraint with an explicit name, if the column is already marked NOT NULL, require that the provided name match the existing constraint name (Álvaro Herrera, Srinath Reddy Sadipiralla) §
Fix incorrect pruning of rowmarks belonging to non-relation rangetable entries, such as subqueries (Dean Rasheed) §
\nThis led to incorrect results if a proposed row update needed to be modified by EvalPlanQual rechecking, as could happen if there was a concurrent update to that row.
", "text": "Fix incorrect pruning of rowmarks belonging to non-relation rangetable entries, such as subqueries (Dean Rasheed) § This led to incorrect results if a proposed row update needed to be modified by EvalPlanQual rechecking, as could happen if there was a concurrent update to that row.", "title": "Fix incorrect pruning of rowmarks belonging to non-relation rangetable entries, such as subqueries", "commits": ["f335457e8"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "95c63c924f06095199dadafd4b211e2cb34c79ddccf7c381c757e7449284fd4f", "section_path": ["Changes"], "commit_groups": [["889676a0d", "f335457e8"]], "identity_text": "Fix incorrect pruning of rowmarks belonging to non-relation rangetable entries, such as subqueries (Dean Rasheed) This led to incorrect results if a proposed row update needed to be modified by EvalPlanQual rechecking, as could happen if there was a concurrent update to that row.", "commit_aliases": ["889676a0d", "f335457e8"], "source_commits": ["f335457e8"], "source_entry_id": "18.2/changes/010", "db_id": "caf0b499119457e7b5f32e7812786e45", "patch_ids": ["cc7499fdc74374d0838681b0e4e6cbce"], "statement_hash": "1302bad0f15fa4ccc1f2e489bbe7c15b86ea748af40600dd43abfa98cb1694f5", "relations": [], "version": "18.2", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-76075de65b93bee4", "cves": [], "html": "Fix expression evaluation bug for a sub-select within an array subscript (Andres Freund) §
", "text": "Fix expression evaluation bug for a sub-select within an array subscript (Andres Freund) §", "title": "Fix expression evaluation bug for a sub-select within an array subscript", "commits": ["bdc5dedfc"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "cc7d39b69e97d5475b6643118ea3c371f3d8748bd98ed00644a2d6c2e2e83bce", "section_path": ["Changes"], "commit_groups": [["75609fded", "bdc5dedfc"]], "identity_text": "Fix expression evaluation bug for a sub-select within an array subscript (Andres Freund)", "commit_aliases": ["75609fded", "bdc5dedfc"], "source_commits": ["bdc5dedfc"], "source_entry_id": "18.2/changes/012", "db_id": "d51cc67df421ce0b185e4351a475c98c", "patch_ids": ["5908ce8e0da90c8b77e7a7d38c3e1377"], "statement_hash": "2125e6ce990cf454284474b773e9091e1c42ad8ba7465f081da4fd84ee20d578", "relations": [], "version": "18.2", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-ae79adaf8f257b64", "cves": [], "html": "Fix text substring search for non-deterministic collations (Laurenz Albe) §
\nWhen using a non-deterministic collation, we failed to detect a match occurring at the very end of the searched string.
", "text": "Fix text substring search for non-deterministic collations (Laurenz Albe) § When using a non-deterministic collation, we failed to detect a match occurring at the very end of the searched string.", "title": "Fix text substring search for non-deterministic collations", "commits": ["18b349315"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "d0c98fcaf9a96ad1be16714c11aab51affff7efb750446d6d233191c575718d6", "section_path": ["Changes"], "commit_groups": [["18b349315", "6dfce8420"]], "identity_text": "Fix text substring search for non-deterministic collations (Laurenz Albe) When using a non-deterministic collation, we failed to detect a match occurring at the very end of the searched string.", "commit_aliases": ["18b349315", "6dfce8420"], "source_commits": ["18b349315"], "source_entry_id": "18.2/changes/013", "db_id": "6b7eab2a0410d798bfe50ae7628ef2dc", "patch_ids": ["ea38b18c588f3f94f7b67f3c7c313412"], "statement_hash": "310b7de794986202c641c1b8c3d90b363fa90fb99c78c23f1c7cff31b4f4747b", "relations": [], "version": "18.2", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-649e6794b398ddbb", "cves": [], "html": "Fix planner error with set-returning functions and grouping sets (Richard Guo) §
\nWhen constructing a ProjectSet plan node, the planner failed to detect that subexpressions involving grouping expressions were already computed by the input plan. This led to inefficient plans or errors such as “variable not found in subplan target list”.
", "text": "Fix planner error with set-returning functions and grouping sets (Richard Guo) § When constructing a ProjectSet plan node, the planner failed to detect that subexpressions involving grouping expressions were already computed by the input plan. This led to inefficient plans or errors such as “variable not found in subplan target list”.", "title": "Fix planner error with set-returning functions and grouping sets", "commits": ["382ce9cb7"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "bfe0c00a4c0bd63be1d00cedf698d85b72a12a918ad78e6380acde776206dc0e", "section_path": ["Changes"], "commit_groups": [["325808cac", "382ce9cb7"]], "identity_text": "Fix planner error with set-returning functions and grouping sets (Richard Guo) When constructing a ProjectSet plan node, the planner failed to detect that subexpressions involving grouping expressions were already computed by the input plan. This led to inefficient plans or errors such as variable not found in subplan target list.", "commit_aliases": ["325808cac", "382ce9cb7"], "source_commits": ["382ce9cb7"], "source_entry_id": "18.2/changes/015", "db_id": "bc2a159eaf3974e7716604942064c56f", "patch_ids": ["eeb8feeb82fe026545fa79e36fe8e45a"], "statement_hash": "1c3b6e833fd7b899cf7ef68c26c207cfe9f1fd37cce060a0ea001c22d4e52b17", "relations": [], "version": "18.2", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-6765d768956aae6e", "cves": [], "html": "Avoid incorrect optimization when a subquery's grouping clause contains a volatile or set-returning function (Richard Guo) §
\nThe planner was willing to push down outer-query restrictions referencing such a grouping column, leading to incorrect behavior due to multiple evaluation of a volatile function, or errors caused by introduction of a set-returning function into the subquery's WHERE/HAVING clauses.
Look through PlaceHolderVar nodes when searching for statistics about an expression (Richard Guo) §
\nThis change allows the planner to find relevant statistics about expressions pulled up from subqueries or used in GROUP BY, avoiding falling back to a default estimate. (Arguably we should adjust any found statistics to account for an increased probability of the value being NULL, but we've never done the equivalent thing for plain Vars either.) While this restriction is old, changes in PostgreSQL version 18 made PlaceHolderVars more common than before, so make the change to avoid plan regressions in affected cases.
Look through no-op PlaceHolderVar nodes when matching expressions to indexes (Richard Guo) §
\nBecause PostgreSQL version 18 uses PlaceHolderVars in more cases than before, some queries that formerly could use an index failed to do so. Add logic to prevent that regression.
", "text": "Look through no-op PlaceHolderVar nodes when matching expressions to indexes (Richard Guo) § Because PostgreSQL version 18 uses PlaceHolderVars in more cases than before, some queries that formerly could use an index failed to do so. Add logic to prevent that regression.", "title": "Look through no-op PlaceHolderVar nodes when matching expressions to indexes", "commits": ["b4cf74420"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "a22a975a62936995e5c733505e5cb2413d8e0ffe0fc8ea23bab714f1ed47ce58", "section_path": ["Changes"], "commit_groups": [["ad66f705f", "b4cf74420"]], "identity_text": "Look through no-op PlaceHolderVar nodes when matching expressions to indexes (Richard Guo) Because PostgreSQL version 18 uses PlaceHolderVars in more cases than before, some queries that formerly could use an index failed to do so. Add logic to prevent that regression.", "commit_aliases": ["ad66f705f", "b4cf74420"], "source_commits": ["b4cf74420"], "source_entry_id": "18.2/changes/018", "db_id": "210a202963ef31d2c268f29448660f49", "patch_ids": ["53d01d1a3c53c6464ef09ecc976ee332"], "statement_hash": "499947e9b2731bd734d2d41a7fb4749ea9665bdf69c9076c6227ba0edaaa6c0c", "relations": [], "version": "18.2", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-df3239546e44b0cd", "cves": [], "html": "Fix planner's conversion of OR clauses to ScalarArrayOp index conditions (Tender Wang, Tom Lane) §
The code did not handle RelabelType nodes correctly, and could generate invalid expressions or fail to perform a valid conversion.
", "text": "Fix planner's conversion of OR clauses to ScalarArrayOp index conditions (Tender Wang, Tom Lane) § The code did not handle RelabelType nodes correctly, and could generate invalid expressions or fail to perform a valid conversion.", "title": "Fix planner's conversion of OR clauses to ScalarArrayOp index conditions", "commits": ["bf5b13a8a"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "3ed87fea3bb1e7df63b1e9929de9df6e3de1977345d1ad50cab3a41567b78a13", "section_path": ["Changes"], "commit_groups": [["bf5b13a8a", "ed931377a"]], "identity_text": "Fix planner's conversion of OR clauses to ScalarArrayOp index conditions (Tender Wang, Tom Lane) The code did not handle RelabelType nodes correctly, and could generate invalid expressions or fail to perform a valid conversion.", "commit_aliases": ["bf5b13a8a", "ed931377a"], "source_commits": ["bf5b13a8a"], "source_entry_id": "18.2/changes/019", "db_id": "94eedc608f36ae44537859b8b9484ab3", "patch_ids": ["1c449b40bb86e705289bfa79952a34a2"], "statement_hash": "4613d2cb8f7f4c9cb614a7c8886084608316d9fe5c1bbb70ce9149628a5849c7", "relations": [], "version": "18.2", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-f25edebc3313b2e9", "cves": [], "html": "Use the correct ordering function in parallel GIN index builds (Tomas Vondra) §
\nThe parallel code used the default ordering operator (which is determined by the column data type's btree opclass), whereas it should use the ordering function specified by the GIN opclass, if any. This led to a failure if the data type has no btree opclass, or to an invalid index if the opclass specifies an ordering function that doesn't agree with the btree opclass.
", "text": "Use the correct ordering function in parallel GIN index builds (Tomas Vondra) § The parallel code used the default ordering operator (which is determined by the column data type's btree opclass), whereas it should use the ordering function specified by the GIN opclass, if any. This led to a failure if the data type has no btree opclass, or to an invalid index if the opclass specifies an ordering function that doesn't agree with the btree opclass.", "title": "Use the correct ordering function in parallel GIN index builds", "commits": ["eee71a66c"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "973146437be60c25c40e87f556a60ea70c774a8c9dfe17423d4113036c477198", "section_path": ["Changes"], "commit_groups": [["db14dcdec", "eee71a66c"]], "identity_text": "Use the correct ordering function in parallel GIN index builds (Tomas Vondra) The parallel code used the default ordering operator (which is determined by the column data type's btree opclass), whereas it should use the ordering function specified by the GIN opclass, if any. This led to a failure if the data type has no btree opclass, or to an invalid index if the opclass specifies an ordering function that doesn't agree with the btree opclass.", "commit_aliases": ["db14dcdec", "eee71a66c"], "source_commits": ["eee71a66c"], "source_entry_id": "18.2/changes/022", "db_id": "8bb71f9af38e5b5860817aa7de5e1ab4", "patch_ids": ["aa226fd5175b721e5e2259a6364ccac6"], "statement_hash": "318cfc6b1c80caebb91eb100312a972bee87e50eb8e5e2b385370bf2723cca6d", "relations": [], "version": "18.2", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-c776aad9e4397483", "cves": [], "html": "Consider grouping expressions when computing a query ID hash (Jian He) §
\nPreviously, two queries that were the same except in GROUP BY expressions would be merged by contrib/pg_stat_statements and other users of query IDs.
Fix race condition in async I/O code (Andres Freund) §
\nIt was possible for the result code of an asynchronous I/O operation to be overwritten before it was fetched.
", "text": "Fix race condition in async I/O code (Andres Freund) § It was possible for the result code of an asynchronous I/O operation to be overwritten before it was fetched.", "title": "Fix race condition in async I/O code", "commits": ["7f1b3a4ce"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "5af700db1614d279fcb4fcebf26c8689988d0b9bde5b133a056adcd4a9552070", "section_path": ["Changes"], "commit_groups": [["7f1b3a4ce", "807764990"]], "identity_text": "Fix race condition in async I/O code (Andres Freund) It was possible for the result code of an asynchronous I/O operation to be overwritten before it was fetched.", "commit_aliases": ["7f1b3a4ce", "807764990"], "source_commits": ["7f1b3a4ce"], "source_entry_id": "18.2/changes/030", "db_id": "d7b9af6aba344aaf3e300ba043f6e676", "patch_ids": ["eadaff6d2b44dde4bfed1267e5de7286"], "statement_hash": "1ed0580c38ed15716eec1bf553a375fa0748d46936276494503831223d421a84", "relations": [], "version": "18.2", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-41d3c4fc60b60873", "cves": [], "html": "Avoid failure of NUMA status views when a page has been swapped out (Tomas Vondra) §
", "text": "Avoid failure of NUMA status views when a page has been swapped out (Tomas Vondra) §", "title": "Avoid failure of NUMA status views when a page has been swapped out", "commits": ["9796c4f56"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "38d4ca5996782890ca2a8d47c302f2fba325fe4e6d025da506c9c1c097171cfe", "section_path": ["Changes"], "commit_groups": [["3fccbd94c", "9796c4f56"]], "identity_text": "Avoid failure of NUMA status views when a page has been swapped out (Tomas Vondra)", "commit_aliases": ["3fccbd94c", "9796c4f56"], "source_commits": ["9796c4f56"], "source_entry_id": "18.2/changes/038", "db_id": "a4a4627ccc48db9aa301be1c008e8e7a", "patch_ids": ["c1934fec3a67006ff496ce9fb844191b"], "statement_hash": "981fce7d7bf6866f425cbf1dc7f0d13d35e9addf7428a9dce5e55e3c69b9c85d", "relations": [], "version": "18.2", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-33eb39d50d6770e0", "cves": [], "html": "Avoid “operation not permitted” errors when querying NUMA page status with older libnuma versions (Tomas Vondra) §
", "text": "Avoid “operation not permitted” errors when querying NUMA page status with older libnuma versions (Tomas Vondra) §", "title": "Avoid “operation not permitted” errors when querying NUMA page status with older libnuma versions", "commits": ["482e98ac4"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "10794498f6ae24d9bfbee4b67ef15fa1893a35ad5b80ba4d3f628c72faed942c", "section_path": ["Changes"], "commit_groups": [["482e98ac4", "599336c64"]], "identity_text": "Avoid operation not permitted errors when querying NUMA page status with older libnuma versions (Tomas Vondra)", "commit_aliases": ["482e98ac4", "599336c64"], "source_commits": ["482e98ac4"], "source_entry_id": "18.2/changes/039", "db_id": "f1a5fdf26515c807e56ed1d6de014dd1", "patch_ids": ["639b15538137cdc707818eaccc7bb5ba"], "statement_hash": "d7f2ab1d3fb2329282928f089cffff62ce9cd74b3faa5a45573d6cf600c28439", "relations": [], "version": "18.2", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-af5fc26e8f8168d4", "cves": [], "html": "Fix aarch64-specific code to build with old (RHEL7-era) system header files (Tom Lane) § §
", "text": "Fix aarch64-specific code to build with old (RHEL7-era) system header files (Tom Lane) § §", "title": "Fix aarch64-specific code to build with old (RHEL7-era) system header files", "commits": ["6a5170755", "db4eba152"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "529bcd93c047b2ef7eec0c93454effdb7bf1dc30a7e787b9cdc4b0f1eba54689", "section_path": ["Changes"], "commit_groups": [["3e83bdd35", "6a5170755"], ["6d969ca68", "db4eba152"]], "identity_text": "Fix aarch64-specific code to build with old (RHEL7-era) system header files (Tom Lane)", "commit_aliases": ["3e83bdd35", "6a5170755", "6d969ca68", "db4eba152"], "source_commits": ["6a5170755", "db4eba152"], "source_entry_id": "18.2/changes/054", "db_id": "a44abc9297ae39cc8abcc977a7a85ce4", "patch_ids": ["2792ee2090bd3b24ee2601afc2231214", "341f355bf2e1a82a85b3bc4ddacd7e41"], "statement_hash": "029c7334d68c62bf885d8809ad4d9b0c95dcd9472fff890d2839cbdcfca4b7eb", "relations": [], "version": "18.2", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-86262bb2b8fa68fb", "cves": [], "html": "Fix incorrect configure probe for io_uring_queue_init_mem() (Masahiko Sawada) §
This error resulted in failure to optimize async I/O buffer allocations in autotools-based builds, though the code did work when building with meson. The main impact of the omission was slower-than-necessary backend process exits.
", "text": "Fix incorrect configure probe for io_uring_queue_init_mem() (Masahiko Sawada) § This error resulted in failure to optimize async I/O buffer allocations in autotools-based builds, though the code did work when building with meson. The main impact of the omission was slower-than-necessary backend process exits.", "title": "Fix incorrect configure probe for io_uring_queue_init_mem()", "commits": ["640772c6d"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "ad451119c2c42159d919470bd46bbc04ff30fcfd36273c4c496e4e04cd4a44a7", "section_path": ["Changes"], "commit_groups": [["640772c6d", "85d5bd308"]], "identity_text": "Fix incorrect configure probe for io_uring_queue_init_mem() (Masahiko Sawada) This error resulted in failure to optimize async I/O buffer allocations in autotools-based builds, though the code did work when building with meson. The main impact of the omission was slower-than-necessary backend process exits.", "commit_aliases": ["640772c6d", "85d5bd308"], "source_commits": ["640772c6d"], "source_entry_id": "18.2/changes/055", "db_id": "d68ab5c932a807f00f02a3ef1979ea8e", "patch_ids": ["31cbb2c33e39c0e4ef28cc6890ff10f4"], "statement_hash": "d8fc17387f6344b93284d7852d2f78ec8e602fcb2a9c3aaa1c5d271b3ab58ea4", "relations": [], "version": "18.2", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-208ee506bc091a4e", "cves": [], "html": "Fix psql's tab completion for VACUUM option values (Yugo Nagata) §
In psql command prompts, do not show a value for %P (pipeline status) when there is no server connection (Chao Li) §
This makes %P act like other prompt escape sequences whose values depend on the active connection.
Fix pg_dump's logic for collecting sequence values (Nathan Bossart) § §
\npg_dump failed if a sequence was dropped concurrently with the dump, even if the sequence was not among the database objects to be dumped. Also, if the calling user lacks privileges to read a sequence's value, pg_dump emitted incorrect values rather than failing as expected.
", "text": "Fix pg_dump's logic for collecting sequence values (Nathan Bossart) § § pg_dump failed if a sequence was dropped concurrently with the dump, even if the sequence was not among the database objects to be dumped. Also, if the calling user lacks privileges to read a sequence's value, pg_dump emitted incorrect values rather than failing as expected.", "title": "Fix pg_dump's logic for collecting sequence values", "commits": ["39d555576", "56e1f5010"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "37f2d4cc5be5c650e6934efeddfac614410556bf5d2ba2916471c87b81d6781e", "section_path": ["Changes"], "commit_groups": [["39d555576", "7a485bd64"], ["56e1f5010", "5d1f5079a"]], "identity_text": "Fix pg_dump's logic for collecting sequence values (Nathan Bossart) pg_dump failed if a sequence was dropped concurrently with the dump, even if the sequence was not among the database objects to be dumped. Also, if the calling user lacks privileges to read a sequence's value, pg_dump emitted incorrect values rather than failing as expected.", "commit_aliases": ["39d555576", "56e1f5010", "5d1f5079a", "7a485bd64"], "source_commits": ["39d555576", "56e1f5010"], "source_entry_id": "18.2/changes/062", "db_id": "6a88db926279b2de84f76189b0b7b586", "patch_ids": ["09260790fdc4775cb78273043d8cf1be", "eaea0ffb838affab367b400e8c79884f"], "statement_hash": "ce18d8cd7ca3634349a95b8901669acb169663943174c58ace92a87d8eb5a4ae", "relations": [], "version": "18.2", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-f023cfdc0ce6569e", "cves": [], "html": "Fix potentially-incorrect quoting of oauth_validator_libraries values by pg_dump (ChangAo Chen) §
pg_dump applied the wrong quoting rule if it needed to dump a value of this setting.
", "text": "Fix potentially-incorrect quoting of oauth_validator_libraries values by pg_dump (ChangAo Chen) § pg_dump applied the wrong quoting rule if it needed to dump a value of this setting.", "title": "Fix potentially-incorrect quoting of oauth_validator_libraries values by pg_dump", "commits": ["61c78e1f4"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "b70c2051bd8c92a107757fad0742c202ef62cfffe67c8c80e96122f38bd6cf65", "section_path": ["Changes"], "commit_groups": [["61c78e1f4", "ec0da9b89"]], "identity_text": "Fix potentially-incorrect quoting of oauth_validator_libraries values by pg_dump (ChangAo Chen) pg_dump applied the wrong quoting rule if it needed to dump a value of this setting.", "commit_aliases": ["61c78e1f4", "ec0da9b89"], "source_commits": ["61c78e1f4"], "source_entry_id": "18.2/changes/063", "db_id": "2edcdf4c426f73af4c504d84d937d988", "patch_ids": ["862047a17a76ec23fcd2672f659199b1"], "statement_hash": "d589bfa7906038771b189bb28737cfa67b315269b47561f913b9ac6b9a230781", "relations": [], "version": "18.2", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-78621868f8a48d3e", "cves": [], "html": "Fix excessive memory allocation in contrib/pg_buffercache (David Geier) §
The code allocated twice as much memory as it needed for NUMA page status.
", "text": "Fix excessive memory allocation in contrib/pg_buffercache (David Geier) § The code allocated twice as much memory as it needed for NUMA page status.", "title": "Fix excessive memory allocation in contrib/pg_buffercache", "commits": ["580b5c2f3"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "88873f3cec0f4d824b5d7ec01e5819d140fc5921a33dd96de5c0410e14d7329b", "section_path": ["Changes"], "commit_groups": [["3f83de20b", "580b5c2f3"]], "identity_text": "Fix excessive memory allocation in contrib/pg_buffercache (David Geier) The code allocated twice as much memory as it needed for NUMA page status.", "commit_aliases": ["3f83de20b", "580b5c2f3"], "source_commits": ["580b5c2f3"], "source_entry_id": "18.2/changes/071", "db_id": "2a469e87e461518ff6a0c895df4011c4", "patch_ids": ["68296f37cd0ce327bf140bb0b4bfe511"], "statement_hash": "1042007c5ddc717af06afcddccb20c95b2ab0127baff1887603f236846d07dd3", "relations": [], "version": "18.2", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.2-88be8c9b8608cbbe", "cves": [], "html": "Avoid crash in contrib/pg_stat_statements when an IN list contains both constants and non-constant expressions (Sami Imseih) §
A dump/restore is not required for those running 18.X.
", "compatibility_count": 0, "label": "18.1", "status_label": "Supported", "eol": "2030-11-14", "age_days": 317, "support_days": 1510, "entries": [{"id": "18.1-3c477bf7c9a2885e", "cves": [], "html": "Avoid incorrect optimization of variable-free HAVING clauses with grouping sets (Richard Guo) § §
Do not use parallelism in hash right semi joins (Richard Guo) §
\nThe case does not work reliably due to a race condition in updating the join's shared hash table.
", "text": "Do not use parallelism in hash right semi joins (Richard Guo) § The case does not work reliably due to a race condition in updating the join's shared hash table.", "title": "Do not use parallelism in hash right semi joins", "commits": ["ef6168baf"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "39312baafff0331dc6e11307f7638efa4a10bda18328fc33401949b670dd2c7a", "section_path": ["Changes"], "commit_groups": [["257ee7834", "ef6168baf"]], "identity_text": "Do not use parallelism in hash right semi joins (Richard Guo) The case does not work reliably due to a race condition in updating the join's shared hash table.", "commit_aliases": ["257ee7834", "ef6168baf"], "source_commits": ["ef6168baf"], "source_entry_id": "18.1/changes/005", "db_id": "ed09728e7057ba0bd58174091cf36572", "patch_ids": ["f3845afa0fdccbe6d8cbb30c204eadc5"], "statement_hash": "3f17b0b718491fbba177f4509a3ce7371c9be8208074eb0f788005239524f671", "relations": [], "version": "18.1", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.1-5ec2ebf5e9d409d9", "cves": [], "html": "Avoid possible division-by-zero when creating ordered-append plans (Richard Guo) §
\nThis mistake could result in incorrect selection of the cheapest path, or in an assertion failure in debug builds.
", "text": "Avoid possible division-by-zero when creating ordered-append plans (Richard Guo) § This mistake could result in incorrect selection of the cheapest path, or in an assertion failure in debug builds.", "title": "Avoid possible division-by-zero when creating ordered-append plans", "commits": ["500f64636"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "05094dbe1a52e137262c79803f4a98e69d7150808221f3286b1687f51db2a39b", "section_path": ["Changes"], "commit_groups": [["500f64636", "c1777f2d6"]], "identity_text": "Avoid possible division-by-zero when creating ordered-append plans (Richard Guo) This mistake could result in incorrect selection of the cheapest path, or in an assertion failure in debug builds.", "commit_aliases": ["500f64636", "c1777f2d6"], "source_commits": ["500f64636"], "source_entry_id": "18.1/changes/006", "db_id": "805d87830e137872aeddda00e5eb47fa", "patch_ids": ["9414b4063f9e09aec7dbfc033ff0d56c"], "statement_hash": "9ab1c92995e5dc19b2f8430a87e9fe9e0f7b8dac32500b13b471acc4c3e4632a", "relations": [], "version": "18.1", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.1-c0b31ef03ca6b8d1", "cves": [], "html": "Fix planner failure with index types that can do ordered access but not index-only scans (Maxime Schoemans) §
\nThis oversight resulted in errors like “no data returned for index-only scan”. The case does not arise with any in-core index type, but some extensions encountered the problem.
", "text": "Fix planner failure with index types that can do ordered access but not index-only scans (Maxime Schoemans) § This oversight resulted in errors like “no data returned for index-only scan”. The case does not arise with any in-core index type, but some extensions encountered the problem.", "title": "Fix planner failure with index types that can do ordered access but not index-only scans", "commits": ["74197bdc8"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "57874e5db38d38966d2b710cf21e5580b67abd8ab00c1e2cd67449f3d5a529a0", "section_path": ["Changes"], "commit_groups": [["35e53b684", "74197bdc8"]], "identity_text": "Fix planner failure with index types that can do ordered access but not index-only scans (Maxime Schoemans) This oversight resulted in errors like no data returned for index-only scan. The case does not arise with any in-core index type, but some extensions encountered the problem.", "commit_aliases": ["35e53b684", "74197bdc8"], "source_commits": ["74197bdc8"], "source_entry_id": "18.1/changes/007", "db_id": "48e2cdd93edf3d7841847a6e50d6cef2", "patch_ids": ["cccb634623d2b8f1ee8f5067fca472e2"], "statement_hash": "24cae600a957284e060515856c041bc697d4b1ccf9e6f631f35d5bdbade1bc28", "relations": [], "version": "18.1", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.1-37c61345d3eacb08", "cves": [], "html": "Avoid possible out-of-memory or “invalid memory alloc request size” failures during parallel GIN index build (Tomas Vondra) §
", "text": "Avoid possible out-of-memory or “invalid memory alloc request size” failures during parallel GIN index build (Tomas Vondra) §", "title": "Avoid possible out-of-memory or “invalid memory alloc request size” failures during parallel GIN index build", "commits": ["a26b753a0"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "fb8079b2782c06b6778225c99b5fd0371cff81d513d4d0cff5381c5dacf27249", "section_path": ["Changes"], "commit_groups": [["a26b753a0", "c98dffcb7"]], "identity_text": "Avoid possible out-of-memory or invalid memory alloc request size failures during parallel GIN index build (Tomas Vondra)", "commit_aliases": ["a26b753a0", "c98dffcb7"], "source_commits": ["a26b753a0"], "source_entry_id": "18.1/changes/009", "db_id": "e3a6863618f309db1f698b4f2fcc8973", "patch_ids": ["2cfdabaf231689f023ac206f2d6e0d32"], "statement_hash": "5743d4aa1ec81c0d062d02b160bfecf8805fd2e5abb8be2006065e2655b7797e", "relations": [], "version": "18.1", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.1-86469df42b03e324", "cves": [], "html": "Fix rare crash when processing hashed GROUPING SETS queries (David Rowley) §
Repair faulty hash-table-size-choosing logic in hash joins (Tomas Vondra) §
\nHash joins sometimes used more memory than intended, or failed to divide it in an efficient way.
", "text": "Repair faulty hash-table-size-choosing logic in hash joins (Tomas Vondra) § Hash joins sometimes used more memory than intended, or failed to divide it in an efficient way.", "title": "Repair faulty hash-table-size-choosing logic in hash joins", "commits": ["aa151022e"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "2f1f77c5b58aad4080d3f53a2ed5a3111544020d333a1a2c3c94f1a0b67b0fff", "section_path": ["Changes"], "commit_groups": [["aa151022e", "b85c4700f"]], "identity_text": "Repair faulty hash-table-size-choosing logic in hash joins (Tomas Vondra) Hash joins sometimes used more memory than intended, or failed to divide it in an efficient way.", "commit_aliases": ["aa151022e", "b85c4700f"], "source_commits": ["aa151022e"], "source_entry_id": "18.1/changes/014", "db_id": "a3653066758eab729f75956e87c77d7e", "patch_ids": ["e7109e998d0ab28d4a07d7656b59c540"], "statement_hash": "673e758ffe8bfaad06735b49302d3951f81c17011e37608c1152b407bc0c3e5b", "relations": [], "version": "18.1", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.1-db784857980e4eb2", "cves": [], "html": "Improve relation lookup logic in statistics manipulation functions (Nathan Bossart) § §
\nFix pg_restore_relation_stats(), pg_clear_relation_stats(), pg_restore_attribute_stats(), and pg_clear_attribute_stats() to check privileges before acquiring lock on the target relation rather than after.
Fix crash during EvalPlanQual rechecks on partitioned tables (David Rowley, Amit Langote) §
", "text": "Fix crash during EvalPlanQual rechecks on partitioned tables (David Rowley, Amit Langote) §", "title": "Fix crash during EvalPlanQual rechecks on partitioned tables", "commits": ["1296dcf18"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "2bb2eab84c9d0aef8280d0f562760f0381fcab6030475f916b6ae62ee941d8c4", "section_path": ["Changes"], "commit_groups": [["1296dcf18", "905e932f0"]], "identity_text": "Fix crash during EvalPlanQual rechecks on partitioned tables (David Rowley, Amit Langote)", "commit_aliases": ["1296dcf18", "905e932f0"], "source_commits": ["1296dcf18"], "source_entry_id": "18.1/changes/017", "db_id": "a0c4022eb806e7bff85e5e4f45d350da", "patch_ids": ["cfaa90e1fdcf18ac6f3f0eafaf77ada8"], "statement_hash": "9669bf1f77810bf9ebd51d3fc0ea281b8ca1e3a90f20cee99402fbc39242eea5", "relations": [], "version": "18.1", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.1-8cabd69c2fc9923e", "cves": [], "html": "Prevent setting a column as identity if it has a not-null constraint but the constraint is marked as invalid (Jian He) §
\nIdentity columns must be not-null, but the check for that missed this edge case.
", "text": "Prevent setting a column as identity if it has a not-null constraint but the constraint is marked as invalid (Jian He) § Identity columns must be not-null, but the check for that missed this edge case.", "title": "Prevent setting a column as identity if it has a not-null constraint but the constraint is marked as invalid", "commits": ["d9ffc2729"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "2363f4d7bfd86ce33ae953ccf4e4c56d7128d64840b12913cbbdb8adf4dc9418", "section_path": ["Changes"], "commit_groups": [["cf8be0225", "d9ffc2729"]], "identity_text": "Prevent setting a column as identity if it has a not-null constraint but the constraint is marked as invalid (Jian He) Identity columns must be not-null, but the check for that missed this edge case.", "commit_aliases": ["cf8be0225", "d9ffc2729"], "source_commits": ["d9ffc2729"], "source_entry_id": "18.1/changes/022", "db_id": "1cc2ad2f1d77c84c94244519b7c21f49", "patch_ids": ["98b878ffaecd78024f87c7da5729ffae"], "statement_hash": "eb006304791e8ea1548b9c4a7928a374c1b1a1f0d2a2219dc90b3744065f5b53", "relations": [], "version": "18.1", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.1-33661c84650917d0", "cves": [], "html": "Re-establish special case for C collation in locale setup (Jeff Davis) §
This fixes a regression in access to shared catalogs early in backend startup, before a database has been selected. It is not known to be a problem for any core PostgreSQL code, but some extensions were broken.
", "text": "Re-establish special case for C collation in locale setup (Jeff Davis) § This fixes a regression in access to shared catalogs early in backend startup, before a database has been selected. It is not known to be a problem for any core PostgreSQL code, but some extensions were broken.", "title": "Re-establish special case for C collation in locale setup", "commits": ["3ebea75f9"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "5967144f5a9ac390e5f43e37e44136126f8a69ddef70fa46672228f341690c6e", "section_path": ["Changes"], "commit_groups": [["3ebea75f9", "d115de9d8"]], "identity_text": "Re-establish special case for C collation in locale setup (Jeff Davis) This fixes a regression in access to shared catalogs early in backend startup, before a database has been selected. It is not known to be a problem for any core PostgreSQL code, but some extensions were broken.", "commit_aliases": ["3ebea75f9", "d115de9d8"], "source_commits": ["3ebea75f9"], "source_entry_id": "18.1/changes/034", "db_id": "f3a09ba6d76319872cf3c57dfe3cbb7f", "patch_ids": ["8a35575852644cce7c43988f09a72271"], "statement_hash": "a7ae6078a0c5cd7c2be592c68fcd68fe554b04a4788ec782c9e11a5f99e01b1d", "relations": [], "version": "18.1", "category_label": "Improvements", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.1-a7e88dbb0ea69eea", "cves": [], "html": "In contrib/pg_stat_statements, avoid crash when two or more constants are marked as having the same location in the SQL statement text (Sami Imseih, Dmitry Dolgov) §
A dump/restore using pg_dumpall or use of pg_upgrade or logical replication is required for those wishing to migrate data from any previous release. See Section 18.6 for general information on migrating to new major releases.
\nVersion 18 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:
\nChange initdb default to enable data checksums (Greg Sabino Mullane) §
\nChecksums can be disabled with the new initdb option --no-data-checksums. pg_upgrade requires matching cluster checksum settings, so this new option can be useful to upgrade non-checksum old clusters.
Change time zone abbreviation handling (Tom Lane) §
\nThe system will now favor the current session's time zone abbreviations before checking the server variable timezone_abbreviations. Previously timezone_abbreviations was checked first.
Deprecate MD5 password authentication (Nathan Bossart) §
\nSupport for MD5 passwords will be removed in a future major version release. CREATE ROLE and ALTER ROLE now emit deprecation warnings when setting MD5 passwords. These warnings can be disabled by setting the md5_password_warnings parameter to off.
Change VACUUM and ANALYZE to process the inheritance children of a parent (Michael Harris) §
\nThe previous behavior can be performed by using the new ONLY option.
Prevent COPY FROM from treating \\. as an end-of-file marker when reading CSV files (Daniel Vérité, Tom Lane) § §
psql will still treat \\. as an end-of-file marker when reading CSV files from STDIN. Older psql clients connecting to PostgreSQL 18 servers might experience \\copy problems. This release also enforces that \\. must appear alone on a line.
Disallow unlogged partitioned tables (Michael Paquier) §
\nPreviously ALTER TABLE SET [UN]LOGGED did nothing, and the creation of an unlogged partitioned table did not cause its children to be unlogged.
Execute AFTER triggers as the role that was active when trigger events were queued (Laurenz Albe) §
Previously such triggers were run as the role that was active at trigger execution time (e.g., at COMMIT). This is significant for cases where the role is changed between queue time and transaction commit.
", "text": "Execute AFTER triggers as the role that was active when trigger events were queued (Laurenz Albe) § Previously such triggers were run as the role that was active at trigger execution time (e.g., at COMMIT). This is significant for cases where the role is changed between queue time and transaction commit.", "title": "Execute AFTER triggers as the role that was active when trigger events were queued", "commits": ["01463e1cc"], "section": "Compatibility", "category": "compatibility", "source_url": "/docs/release/18.0/#RELEASE-18-MIGRATION", "source_hash": "f10785acbe9b26f28a8c98e9a00c1d2a4e8afa8c0b7f7291f990211dfc079f53", "section_path": ["Compatibility"], "commit_groups": [["01463e1cc"]], "identity_text": "Execute AFTER triggers as the role that was active when trigger events were queued (Laurenz Albe) Previously such triggers were run as the role that was active at trigger execution time (e.g., at sql-commit ). This is significant for cases where the role is changed between queue time and transaction commit.", "commit_aliases": ["01463e1cc"], "source_commits": ["01463e1cc"], "source_entry_id": "18.0/migration/007", "db_id": "ae8521434650fe5524c9fcaa38acac84", "patch_ids": ["917ba717810e74a1c7c638690cf0f5eb"], "statement_hash": "f0612c07183e11ac71073f5d359d3b0a521ebcc0822d94befe83c23059d03016", "relations": [], "version": "18.0", "category_label": "Compatibility", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-607cc591e9d82ae8", "cves": [], "html": "Remove non-functional support for rule privileges in GRANT/REVOKE (Fujii Masao) §
\nThese have been non-functional since PostgreSQL 8.2.
", "text": "Remove non-functional support for rule privileges in GRANT/REVOKE (Fujii Masao) § These have been non-functional since PostgreSQL 8.2.", "title": "Remove non-functional support for rule privileges in GRANT/REVOKE", "commits": ["fefa76f70"], "section": "Compatibility", "category": "compatibility", "source_url": "/docs/release/18.0/#RELEASE-18-MIGRATION", "source_hash": "db08cd3d3ddd023cec8d6165fd052ba6e7d655cc958d6c238b6f02af024dc1a1", "section_path": ["Compatibility"], "commit_groups": [["fefa76f70"]], "identity_text": "Remove non-functional support for rule privileges in sql-grant / sql-revoke (Fujii Masao) These have been non-functional since PostgreSQL 8.2.", "commit_aliases": ["fefa76f70"], "source_commits": ["fefa76f70"], "source_entry_id": "18.0/migration/008", "db_id": "421b9236b8ba45e9981de4acb0936336", "patch_ids": ["1a39a92752613c9674e39e99f119c2de"], "statement_hash": "9a9f6ec57f00ae867aca818ec5c55d43899650a49ee6ab2ce0bed4d154bb41b9", "relations": [], "version": "18.0", "category_label": "Compatibility", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-558a645d00b3f47b", "cves": [], "html": "Remove column pg_backend_memory_contexts.parent (Melih Mutlu) §
This is no longer needed since pg_backend_memory_contexts.path was added.
Change pg_backend_memory_contexts.level and pg_log_backend_memory_contexts() to be one-based (Melih Mutlu, Atsushi Torikoshi, David Rowley, Fujii Masao) § § §
These were previously zero-based.
", "text": "Change pg_backend_memory_contexts.level and pg_log_backend_memory_contexts() to be one-based (Melih Mutlu, Atsushi Torikoshi, David Rowley, Fujii Masao) § § § These were previously zero-based.", "title": "Change pg_backend_memory_contexts.level and pg_log_backend_memory_contexts() to be one-based", "commits": ["32d3ed816", "706cbed35", "d9e03864b"], "section": "Compatibility", "category": "compatibility", "source_url": "/docs/release/18.0/#RELEASE-18-MIGRATION", "source_hash": "50bbd1729e746a694a3df7d491e7ab79d0b57696ebbb5127fdc124520b03ee7c", "section_path": ["Compatibility"], "commit_groups": [["32d3ed816"], ["706cbed35"], ["d9e03864b"]], "identity_text": "Change pg_backend_memory_contexts.level and pg_log_backend_memory_contexts() to be one-based (Melih Mutlu, Atsushi Torikoshi, David Rowley, Fujii Masao) These were previously zero-based.", "commit_aliases": ["32d3ed816", "706cbed35", "d9e03864b"], "source_commits": ["32d3ed816", "706cbed35", "d9e03864b"], "source_entry_id": "18.0/migration/010", "db_id": "b8c57d935d8b183f9ee20e7477f90abd", "patch_ids": ["3d61500ab7649ba207c5b4742ce83946", "845864cc388c5f840e08c3fdf9f3032a", "eaa8db2e49e44f9880c123bf159cab42"], "statement_hash": "c56bfdda9e9b110545ab282f1be71da486fd1e7af030b2a5c125fe4d37560c98", "relations": [{"rule": 2, "type": "related", "target": "7ed5d279df474d7ce518a2cd605d091d", "evidence": {"same_day": true, "patch_ids": ["eaa8db2e49e44f9880c123bf159cab42"]}}], "version": "18.0", "category_label": "Compatibility", "also_in": [], "variants": [], "related_changes": [{"db_id": "7ed5d279df474d7ce518a2cd605d091d", "kind": "related", "version": "18.0", "label": "18.0", "title": "Add column pg_backend_memory_contexts.path to show memory context parents", "evidence": {"same_day": true, "patch_ids": ["eaa8db2e49e44f9880c123bf159cab42"]}, "url": "/docs/compare/?release=18.0#18.0-f9c2e124d8a94a20", "source_url": "/docs/release/18.0/#RELEASE-18-MONITORING"}]}, {"id": "18.0-63b962f0125472b6", "cves": [], "html": "Change full text search to use the default collation provider of the cluster to read configuration files and dictionaries, rather than always using libc (Peter Eisentraut) §
\nClusters that default to non-libc collation providers (e.g., ICU, builtin) that behave differently than libc for characters processed by LC_CTYPE could observe changes in behavior of some full-text search functions, as well as the pg_trgm extension. When upgrading such clusters using pg_upgrade, it is recommended to reindex all indexes related to full-text search and pg_trgm after the upgrade.
", "text": "Change full text search to use the default collation provider of the cluster to read configuration files and dictionaries, rather than always using libc (Peter Eisentraut) § Clusters that default to non-libc collation providers (e.g., ICU, builtin) that behave differently than libc for characters processed by LC_CTYPE could observe changes in behavior of some full-text search functions, as well as the pg_trgm extension. When upgrading such clusters using pg_upgrade, it is recommended to reindex all indexes related to full-text search and pg_trgm after the upgrade.", "title": "Change full text search to use the default collation provider of the cluster to read configuration files and dictionaries, rather than always using libc", "commits": ["fb1a18810f0"], "section": "Compatibility", "category": "compatibility", "source_url": "/docs/release/18.0/#RELEASE-18-MIGRATION", "source_hash": "e3ce56b4fc2a72cd171306a24ddd0b8daecb530f1409e98a57781871e32f9519", "section_path": ["Compatibility"], "commit_groups": [["fb1a18810f0"]], "identity_text": "Change full text search to use the default collation provider of the cluster to read configuration files and dictionaries, rather than always using libc (Peter Eisentraut) Clusters that default to non-libc collation providers (e.g., ICU, builtin) that behave differently than libc for characters processed by LC_CTYPE could observe changes in behavior of some full-text search functions, as well as the pgtrgm extension. When upgrading such clusters using pgupgrade , it is recommended to reindex all indexes related to full-text search and pg_trgm after the upgrade.", "commit_aliases": ["fb1a18810f0"], "source_commits": ["fb1a18810f0"], "source_entry_id": "18.0/migration/011", "db_id": "14f7ec96f489178a5ba54f0173a2002a", "patch_ids": ["d34589a0ca33552be8913ecb392dc365"], "statement_hash": "0d016706c1da5d040bed5653360eaa27ed050c9172ff53f737e1221153008011", "relations": [], "version": "18.0", "category_label": "Compatibility", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-680d6a94e6af24a0", "cves": [], "html": "Automatically remove some unnecessary table self-joins (Andrey Lepikhov, Alexander Kuzmenkov, Alexander Korotkov, Alena Rybakina) §
\nThis optimization can be disabled using server variable enable_self_join_elimination.
", "text": "Automatically remove some unnecessary table self-joins (Andrey Lepikhov, Alexander Kuzmenkov, Alexander Korotkov, Alena Rybakina) § This optimization can be disabled using server variable enable_self_join_elimination.", "title": "Automatically remove some unnecessary table self-joins", "commits": ["fc069a3a6"], "section": "Server / Optimizer", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-OPTIMIZER", "source_hash": "40c3196e66530b1ad6c86357db78c6683c075a289ecc4fdc11ccdd15d42dafad", "section_path": ["Server", "Optimizer"], "commit_groups": [["fc069a3a6"]], "identity_text": "Automatically remove some unnecessary table self-joins (Andrey Lepikhov, Alexander Kuzmenkov, Alexander Korotkov, Alena Rybakina) This optimization can be disabled using server variable guc-enable-self-join-elimination .", "commit_aliases": ["fc069a3a6"], "source_commits": ["fc069a3a6"], "source_entry_id": "18.0/changes/001", "db_id": "e93aac468afc7b983da5961bc89a6570", "patch_ids": ["f4668f24b918872b344ea179b57163cf"], "statement_hash": "235c5aa78ae11057e82ffcaba18192f08d816b80c7a4abeb2ccab576de5173f7", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-d841fa8566ba0e41", "cves": [], "html": "Convert some IN (VALUES ...) to x = ANY ... for better optimizer statistics (Alena Rybakina, Andrei Lepikhov) §
Allow transforming OR-clauses to arrays for faster index processing (Alexander Korotkov, Andrey Lepikhov) §
Speed up the processing of INTERSECT, EXCEPT, window aggregates, and view column aliases (Tom Lane, David Rowley) § § § §
Allow the keys of SELECT DISTINCT to be internally reordered to avoid sorting (Richard Guo) §
This optimization can be disabled using enable_distinct_reordering.
", "text": "Allow the keys of SELECT DISTINCT to be internally reordered to avoid sorting (Richard Guo) § This optimization can be disabled using enable_distinct_reordering.", "title": "Allow the keys of SELECT DISTINCT to be internally reordered to avoid sorting", "commits": ["a8ccf4e93"], "section": "Server / Optimizer", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-OPTIMIZER", "source_hash": "0b3d9b69f68103fec0e196e120de31d7d5ccbd1c26beea05060ff6a886ab9130", "section_path": ["Server", "Optimizer"], "commit_groups": [["a8ccf4e93"]], "identity_text": "Allow the keys of SELECT DISTINCT to be internally reordered to avoid sorting (Richard Guo) This optimization can be disabled using guc-enable-distinct-reordering .", "commit_aliases": ["a8ccf4e93"], "source_commits": ["a8ccf4e93"], "source_entry_id": "18.0/changes/005", "db_id": "e1633e7353cb2e283e589f245c02709b", "patch_ids": ["2a4dc17b68562e6259b7bb1052fff9ad"], "statement_hash": "8e10ed699456a43e5c53f99fc9ddb0ec2951686ee8551c8e706fbd1d1b10766c", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-723dd69ea02477f1", "cves": [], "html": "Ignore GROUP BY columns that are functionally dependent on other columns (Zhang Mingli, Jian He, David Rowley) §
If a GROUP BY clause includes all columns of a unique index, as well as other columns of the same table, those other columns are redundant and can be dropped from the grouping. This was already true for non-deferred primary keys.
Allow some HAVING clauses on GROUPING SETS to be pushed to WHERE clauses (Richard Guo) § § § §
This allows earlier row filtering. This release also fixes some GROUPING SETS queries that used to return incorrect results.
Improve row estimates for generate_series() using numeric and timestamp values (David Rowley, Song Jinzhou) § §
Allow the optimizer to use Right Semi Join plans (Richard Guo) §
Semi-joins are used when needing to find if there is at least one match.
", "text": "Allow the optimizer to use Right Semi Join plans (Richard Guo) § Semi-joins are used when needing to find if there is at least one match.", "title": "Allow the optimizer to use Right Semi Join plans", "commits": ["aa86129e1"], "section": "Server / Optimizer", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-OPTIMIZER", "source_hash": "619b5f1bfc705891d795ac9ab763f6362d300120b9a2d649250a5fb0fe617a45", "section_path": ["Server", "Optimizer"], "commit_groups": [["aa86129e1"]], "identity_text": "Allow the optimizer to use Right Semi Join plans (Richard Guo) Semi-joins are used when needing to find if there is at least one match.", "commit_aliases": ["aa86129e1"], "source_commits": ["aa86129e1"], "source_entry_id": "18.0/changes/009", "db_id": "f76a8468845b91ddcffeaa33fa3400a0", "patch_ids": ["79e6e1842e88c7f535ade4eaba7be513"], "statement_hash": "117c31abccc7e061fab7475bec0bdf75e420f53925d5e95de87e71dad3cea951", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-0bf93b27e1b1c8e2", "cves": [], "html": "Allow merge joins to use incremental sorts (Richard Guo) §
", "text": "Allow merge joins to use incremental sorts (Richard Guo) §", "title": "Allow merge joins to use incremental sorts", "commits": ["828e94c9d"], "section": "Server / Optimizer", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-OPTIMIZER", "source_hash": "232faeb186a197cb2d471ce89d7969bca2593ea44e545f90f86f5ec9974800b1", "section_path": ["Server", "Optimizer"], "commit_groups": [["828e94c9d"]], "identity_text": "Allow merge joins to use incremental sorts (Richard Guo)", "commit_aliases": ["828e94c9d"], "source_commits": ["828e94c9d"], "source_entry_id": "18.0/changes/010", "db_id": "7e8d7bcff75eca9f6d3794b3ed0388fb", "patch_ids": ["22cb8f9f6594048e5c90b7c0a948ea39"], "statement_hash": "c730545e91cae06688ba34e2ac9097a5800e1f311eaa283af2f272f7a1ac2767", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-200b52f9d63401ad", "cves": [], "html": "Improve the efficiency of planning queries accessing many partitions (Ashutosh Bapat, Yuya Watari, David Rowley) § §
", "text": "Improve the efficiency of planning queries accessing many partitions (Ashutosh Bapat, Yuya Watari, David Rowley) § §", "title": "Improve the efficiency of planning queries accessing many partitions", "commits": ["88f55bc97", "d69d45a5a"], "section": "Server / Optimizer", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-OPTIMIZER", "source_hash": "7cec6b7a3c4b0b96689bd0d68404844c350a00677ea88e38b124b1582f228d77", "section_path": ["Server", "Optimizer"], "commit_groups": [["88f55bc97"], ["d69d45a5a"]], "identity_text": "Improve the efficiency of planning queries accessing many partitions (Ashutosh Bapat, Yuya Watari, David Rowley)", "commit_aliases": ["88f55bc97", "d69d45a5a"], "source_commits": ["88f55bc97", "d69d45a5a"], "source_entry_id": "18.0/changes/011", "db_id": "6365c622e7f4156b307f731e72d9a3de", "patch_ids": ["15b3816633681459d9dd93e64a48ce0d", "ba8aa7045b27e8a9467ad9df65f2a614"], "statement_hash": "abf3aa0c2277a1dc8d9ddb61b3ffe1d2c987f7e7d4295a9d96f9ad75fa3f8e2a", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-cd058ce20aafebed", "cves": [], "html": "Allow partitionwise joins in more cases, and reduce its memory usage (Richard Guo, Tom Lane, Ashutosh Bapat) § §
", "text": "Allow partitionwise joins in more cases, and reduce its memory usage (Richard Guo, Tom Lane, Ashutosh Bapat) § §", "title": "Allow partitionwise joins in more cases, and reduce its memory usage", "commits": ["513f4472a", "9b282a935"], "section": "Server / Optimizer", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-OPTIMIZER", "source_hash": "cccb81e8d167297ee2b086955ed9914693ecfdb1803b07df4ff007a993b1d1bd", "section_path": ["Server", "Optimizer"], "commit_groups": [["513f4472a"], ["9b282a935"]], "identity_text": "Allow partitionwise joins in more cases, and reduce its memory usage (Richard Guo, Tom Lane, Ashutosh Bapat)", "commit_aliases": ["513f4472a", "9b282a935"], "source_commits": ["513f4472a", "9b282a935"], "source_entry_id": "18.0/changes/012", "db_id": "e1323b3c594bfa821577fa9462f03cdb", "patch_ids": ["2ff70c110f54ba540a2cece6e3a512cd", "dd416b1d8a4d68e28e16f90c7055e0bb"], "statement_hash": "40327e199cf2577490955fbcc74c05fe2901108bec3acfe4621734a986af7685", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-0a96c3f22c743902", "cves": [], "html": "Improve cost estimates of partition queries (Nikita Malakhov, Andrei Lepikhov) §
", "text": "Improve cost estimates of partition queries (Nikita Malakhov, Andrei Lepikhov) §", "title": "Improve cost estimates of partition queries", "commits": ["fae535da0"], "section": "Server / Optimizer", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-OPTIMIZER", "source_hash": "ad72fe467357e9b21f201ea22bac15faa0c66b16f28d43cb9b3f490b554ae9db", "section_path": ["Server", "Optimizer"], "commit_groups": [["fae535da0"]], "identity_text": "Improve cost estimates of partition queries (Nikita Malakhov, Andrei Lepikhov)", "commit_aliases": ["fae535da0"], "source_commits": ["fae535da0"], "source_entry_id": "18.0/changes/013", "db_id": "c65e9805a7d1ddaa6d1373559e4cc29f", "patch_ids": ["61b7fea36f21c950e67f8bac538e8fce"], "statement_hash": "a36db3cf18d61186e69ff7181df62ed65dd845c1892191555ce2f6c4eecb52bd", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-0ed62a6dcc6eb60c", "cves": [], "html": "Improve SQL-language function plan caching (Alexander Pyhalov, Tom Lane) § §
", "text": "Improve SQL-language function plan caching (Alexander Pyhalov, Tom Lane) § §", "title": "Improve SQL-language function plan caching", "commits": ["09b07c295", "0dca5d68d"], "section": "Server / Optimizer", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-OPTIMIZER", "source_hash": "624d5ebd4fbd3484e763f4ffd477ed7308b2ba7c3b507bfe163d59e440d1c9f2", "section_path": ["Server", "Optimizer"], "commit_groups": [["09b07c295"], ["0dca5d68d"]], "identity_text": "Improve SQL-language function plan caching (Alexander Pyhalov, Tom Lane)", "commit_aliases": ["09b07c295", "0dca5d68d"], "source_commits": ["09b07c295", "0dca5d68d"], "source_entry_id": "18.0/changes/014", "db_id": "de187fd5833da9236d39e17a824451c0", "patch_ids": ["254214644dc444095fdc1eed63435eea", "aca8b43ca22cd7e20074fc7a0a7722ba"], "statement_hash": "146626d1f5aff4758ae17dc01f8d5f905420813c8aeb98087d9ca08c5471eb23", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-81f4be5c092dad16", "cves": [], "html": "Improve handling of disabled optimizer features (Robert Haas) §
", "text": "Improve handling of disabled optimizer features (Robert Haas) §", "title": "Improve handling of disabled optimizer features", "commits": ["e22253467"], "section": "Server / Optimizer", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-OPTIMIZER", "source_hash": "3ac7c9a012dfeb824499ec299452a4443f811573d8cdc48a32a87591feb62e84", "section_path": ["Server", "Optimizer"], "commit_groups": [["e22253467"]], "identity_text": "Improve handling of disabled optimizer features (Robert Haas)", "commit_aliases": ["e22253467"], "source_commits": ["e22253467"], "source_entry_id": "18.0/changes/015", "db_id": "6af674fe85c6718d1c2ae803cc5fa2d4", "patch_ids": ["78269645a1e3bdd21fcde369b7fb1c82"], "statement_hash": "0dcbf8861cd7ba230ddcdaf5746f5f46a4f85aa3e242a34f907c8eadbc61f43c", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-5c8b8535c34dd690", "cves": [], "html": "Allow skip scans of btree indexes (Peter Geoghegan) § §
\nThis allows multi-column btree indexes to be used in more cases such as when there are no restrictions on the first or early indexed columns (or there are non-equality ones), and there are useful restrictions on later indexed columns.
", "text": "Allow skip scans of btree indexes (Peter Geoghegan) § § This allows multi-column btree indexes to be used in more cases such as when there are no restrictions on the first or early indexed columns (or there are non-equality ones), and there are useful restrictions on later indexed columns.", "title": "Allow skip scans of btree indexes", "commits": ["8a510275d", "92fe23d93"], "section": "Server / Indexes", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-INDEXES", "source_hash": "6fc7b9601b88e3906c876c63e64c4ed31901ffef59984e3a9f3c5467cf0e520e", "section_path": ["Server", "Indexes"], "commit_groups": [["8a510275d"], ["92fe23d93"]], "identity_text": "Allow skip scans of btree indexes (Peter Geoghegan) This allows multi-column btree indexes to be used in more cases such as when there are no restrictions on the first or early indexed columns (or there are non-equality ones), and there are useful restrictions on later indexed columns.", "commit_aliases": ["8a510275d", "92fe23d93"], "source_commits": ["8a510275d", "92fe23d93"], "source_entry_id": "18.0/changes/016", "db_id": "d6862625b987b44876b5f8813415e301", "patch_ids": ["635b38c19244d008c0a276c87c34aabf", "e61ae831ab07aa91f44cf34554c51986"], "statement_hash": "5f70bac2450552918acb0585c69d065150051c94ca3fd7c0e78accb784965d18", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-50b6cc437d755b78", "cves": [], "html": "Allow non-btree unique indexes to be used as partition keys and in materialized views (Mark Dilger) § §
\nThe index type must still support equality.
", "text": "Allow non-btree unique indexes to be used as partition keys and in materialized views (Mark Dilger) § § The index type must still support equality.", "title": "Allow non-btree unique indexes to be used as partition keys and in materialized views", "commits": ["9d6db8bec", "f278e1fe3"], "section": "Server / Indexes", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-INDEXES", "source_hash": "48d1dc2e21671ed03ec096681269e55993854a87f636152113525b845910da6b", "section_path": ["Server", "Indexes"], "commit_groups": [["9d6db8bec"], ["f278e1fe3"]], "identity_text": "Allow non-btree unique indexes to be used as partition keys and in materialized views (Mark Dilger) The index type must still support equality.", "commit_aliases": ["9d6db8bec", "f278e1fe3"], "source_commits": ["9d6db8bec", "f278e1fe3"], "source_entry_id": "18.0/changes/017", "db_id": "494315b065e8cf257c51cc573e8cd5ba", "patch_ids": ["5bf1633970b359c47772a29d428891b9", "afc683b089394ea6ac807e8fc8c1d9ac"], "statement_hash": "8627db4022a3b996448b3199a1438d065510142c1a86887f48fb1af1aa338936", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-456432f04301fe8e", "cves": [], "html": "Allow GIN indexes to be created in parallel (Tomas Vondra, Matthias van de Meent) §
Allow values to be sorted to speed range-type GiST and btree index builds (Bernd Helmle) §
", "text": "Allow values to be sorted to speed range-type GiST and btree index builds (Bernd Helmle) §", "title": "Allow values to be sorted to speed range-type GiST and btree index builds", "commits": ["e9e7b6604"], "section": "Server / Indexes", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-INDEXES", "source_hash": "ac18bed164464842781add926baf8a19f9b384695cfa6ffc14d622e837b24226", "section_path": ["Server", "Indexes"], "commit_groups": [["e9e7b6604"]], "identity_text": "Allow values to be sorted to speed range-type GiST and btree index builds (Bernd Helmle)", "commit_aliases": ["e9e7b6604"], "source_commits": ["e9e7b6604"], "source_entry_id": "18.0/changes/019", "db_id": "bb89183dc8713a98a5f1732f23ebf357", "patch_ids": ["21b0be863bb11025af07f036adc715cd"], "statement_hash": "1110884a4b4193d0fb56b65604f1f84d06c9b027816ac2b2f97f7eb335548e6f", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-fa23d49e1bbd33bf", "cves": [], "html": "Add an asynchronous I/O subsystem (Andres Freund, Thomas Munro, Nazir Bilal Yavuz, Melanie Plageman) § § § § § § § § § § §
\nThis feature allows backends to queue multiple read requests, which allows for more efficient sequential scans, bitmap heap scans, vacuums, etc. This is enabled by server variable io_method, with server variables io_combine_limit and io_max_combine_limit added to control it. This also enables effective_io_concurrency and maintenance_io_concurrency values greater than zero for systems without fadvise() support. The new system view pg_aios shows the file handles being used for asynchronous I/O.
Improve the locking performance of queries that access many relations (Tomas Vondra) §
", "text": "Improve the locking performance of queries that access many relations (Tomas Vondra) §", "title": "Improve the locking performance of queries that access many relations", "commits": ["c4d5cb71d"], "section": "Server / General Performance", "category": "performance", "source_url": "/docs/release/18.0/#RELEASE-18-PERFORMANCE", "source_hash": "166ed61e81ac65ed621694d2130b525d95cd6eabf81198d9051b9df5a5471b51", "section_path": ["Server", "General Performance"], "commit_groups": [["c4d5cb71d"]], "identity_text": "Improve the locking performance of queries that access many relations (Tomas Vondra)", "commit_aliases": ["c4d5cb71d"], "source_commits": ["c4d5cb71d"], "source_entry_id": "18.0/changes/021", "db_id": "aff48c3c83b235bf18a030e9ccc9c3b8", "patch_ids": ["fc2837c0cff32783885ae70d5fbb55db"], "statement_hash": "bbf31aaa998b69605f19fb5f3337b504b4ae92cf39abf056f16dadd0b84efe2d", "relations": [], "version": "18.0", "category_label": "Performance", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-b0a8003dc1022a25", "cves": [], "html": "Improve the performance and reduce memory usage of hash joins and GROUP BY (David Rowley, Jeff Davis) § § § § §
This also improves hash set operations used by EXCEPT, and hash lookups of subplan values.
Allow normal vacuums to freeze some pages, even though they are all-visible (Melanie Plageman) § §
\nThis reduces the overhead of later full-relation freezing. The aggressiveness of this can be controlled by server variable and per-table setting vacuum_max_eager_freeze_failure_rate. Previously vacuum never processed all-visible pages until freezing was required.
", "text": "Allow normal vacuums to freeze some pages, even though they are all-visible (Melanie Plageman) § § This reduces the overhead of later full-relation freezing. The aggressiveness of this can be controlled by server variable and per-table setting vacuum_max_eager_freeze_failure_rate. Previously vacuum never processed all-visible pages until freezing was required.", "title": "Allow normal vacuums to freeze some pages, even though they are all-visible", "commits": ["052026c9b", "06eae9e62"], "section": "Server / General Performance", "category": "performance", "source_url": "/docs/release/18.0/#RELEASE-18-PERFORMANCE", "source_hash": "067908e36f6001abfd9b89898d6468091c7c408aba70fd6644ef0e6e78945b17", "section_path": ["Server", "General Performance"], "commit_groups": [["052026c9b"], ["06eae9e62"]], "identity_text": "Allow normal vacuums to freeze some pages, even though they are all-visible (Melanie Plageman) This reduces the overhead of later full-relation freezing. The aggressiveness of this can be controlled by server variable and per-table setting guc-vacuum-max-eager-freeze-failure-rate . Previously vacuum never processed all-visible pages until freezing was required.", "commit_aliases": ["052026c9b", "06eae9e62"], "source_commits": ["052026c9b", "06eae9e62"], "source_entry_id": "18.0/changes/023", "db_id": "b143946a18139ecebf85f4773c7419b5", "patch_ids": ["67ea98ee74614c1e13cce028969b4f44", "d3f807b22dffb17b1216f302711474dd"], "statement_hash": "1d01a6afb8bdd666bc7b3013928540e3f748fdac185055067dcbcfcb19976f2d", "relations": [], "version": "18.0", "category_label": "Performance", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-f532d30d19208618", "cves": [], "html": "Add server variable vacuum_truncate to control file truncation during VACUUM (Nathan Bossart, Gurjeet Singh) §
\nA storage-level parameter with the same name and behavior already existed.
", "text": "Add server variable vacuum_truncate to control file truncation during VACUUM (Nathan Bossart, Gurjeet Singh) § A storage-level parameter with the same name and behavior already existed.", "title": "Add server variable vacuum_truncate to control file truncation during VACUUM", "commits": ["0164a0f9e"], "section": "Server / General Performance", "category": "performance", "source_url": "/docs/release/18.0/#RELEASE-18-PERFORMANCE", "source_hash": "3bdf7d1f300811ca038842a0cc4e774e2520f4329d021c60a179b690525ba77f", "section_path": ["Server", "General Performance"], "commit_groups": [["0164a0f9e"]], "identity_text": "Add server variable guc-vacuum-truncate to control file truncation during sql-vacuum (Nathan Bossart, Gurjeet Singh) A storage-level parameter with the same name and behavior already existed.", "commit_aliases": ["0164a0f9e"], "source_commits": ["0164a0f9e"], "source_entry_id": "18.0/changes/024", "db_id": "d1bf74ed1cb4e3fbacc9001855d15f16", "patch_ids": ["be7bc9e56cdce4915b9e4a702d43e637"], "statement_hash": "944b8ce94c10828d6d6910957cf641b88dc95d22b1b8115647738cec01db9fbe", "relations": [], "version": "18.0", "category_label": "Performance", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-6a0f68c7a6c59848", "cves": [], "html": "Increase server variables effective_io_concurrency's and maintenance_io_concurrency's default values to 16 (Melanie Plageman) § §
\nThis more accurately reflects modern hardware.
", "text": "Increase server variables effective_io_concurrency's and maintenance_io_concurrency's default values to 16 (Melanie Plageman) § § This more accurately reflects modern hardware.", "title": "Increase server variables effective_io_concurrency's and maintenance_io_concurrency's default values to 16", "commits": ["cc6be07eb", "ff79b5b2a"], "section": "Server / General Performance", "category": "performance", "source_url": "/docs/release/18.0/#RELEASE-18-PERFORMANCE", "source_hash": "5ed1ab656f1d067bc897340478dcbb402d18bafb76ff5da9b9bec5940ff0e6da", "section_path": ["Server", "General Performance"], "commit_groups": [["cc6be07eb"], ["ff79b5b2a"]], "identity_text": "Increase server variables guc-effective-io-concurrency 's and guc-maintenance-io-concurrency 's default values to 16 (Melanie Plageman) This more accurately reflects modern hardware.", "commit_aliases": ["cc6be07eb", "ff79b5b2a"], "source_commits": ["cc6be07eb", "ff79b5b2a"], "source_entry_id": "18.0/changes/025", "db_id": "426d3063330d1605a0f8dada895702c7", "patch_ids": ["5048dc209f8f981f9a097d9636573570", "711b2163ed88e992fa8f7ebd50bcabfe"], "statement_hash": "2388b7de66243eaf67d83494c797d6d1e1d27a9f5ff72da1c364e2e04896d1a4", "relations": [], "version": "18.0", "category_label": "Performance", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-7eca16540c485be9", "cves": [], "html": "Increase the logging granularity of server variable log_connections (Melanie Plageman) §
\nThis server variable was previously only boolean, which is still supported.
", "text": "Increase the logging granularity of server variable log_connections (Melanie Plageman) § This server variable was previously only boolean, which is still supported.", "title": "Increase the logging granularity of server variable log_connections", "commits": ["9219093ca"], "section": "Server / Monitoring", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MONITORING", "source_hash": "42fa035457ddebe4280da1ffdf030abca58669ddee1f4de16c1998a7b9a4dfb2", "section_path": ["Server", "Monitoring"], "commit_groups": [["9219093ca"]], "identity_text": "Increase the logging granularity of server variable guc-log-connections (Melanie Plageman) This server variable was previously only boolean, which is still supported.", "commit_aliases": ["9219093ca"], "source_commits": ["9219093ca"], "source_entry_id": "18.0/changes/026", "db_id": "ff5e5f18a1f9dca408cdf9912c05dbc0", "patch_ids": ["a7e481af208e8edfa0f5fb1487d6f5da"], "statement_hash": "bdb1f75b5ad766542e4be765b90646c65665a1de272e063859e8ddf2ad109820", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-5ced21ab8b3e15c8", "cves": [], "html": "Add log_connections option to report the duration of connection stages (Melanie Plageman) §
Add log_line_prefix escape %L to output the client IP address (Greg Sabino Mullane) §
Add server variable log_lock_failures to log lock acquisition failures (Yuki Seino, Fujii Masao) § §
\nSpecifically it reports SELECT ... NOWAIT lock failures.
Modify pg_stat_all_tables and its variants to report the time spent in VACUUM, ANALYZE, and their automatic variants (Sami Imseih) §
The new columns are total_vacuum_time, total_autovacuum_time, total_analyze_time, and total_autoanalyze_time.
Add delay time reporting to VACUUM and ANALYZE (Bertrand Drouvot, Nathan Bossart) § §
\nThis information appears in the server log, the system views pg_stat_progress_vacuum and pg_stat_progress_analyze, and the output of VACUUM and ANALYZE when in VERBOSE mode; tracking must be enabled with the server variable track_cost_delay_timing.
Add WAL, CPU, and average read statistics output to ANALYZE VERBOSE (Anthonin Bonnefoy) § §
Add full WAL buffer count to VACUUM/ANALYZE (VERBOSE) and autovacuum log output (Bertrand Drouvot) §
Add per-backend I/O statistics reporting (Bertrand Drouvot) § §
\nThe statistics are accessed via pg_stat_get_backend_io(). Per-backend I/O statistics can be cleared via pg_stat_reset_backend_stats().
Add pg_stat_io columns to report I/O activity in bytes (Nazir Bilal Yavuz) §
The new columns are read_bytes, write_bytes, and extend_bytes. The op_bytes column, which always equaled BLCKSZ, has been removed.
Add WAL I/O activity rows to pg_stat_io (Nazir Bilal Yavuz, Bertrand Drouvot, Michael Paquier) § § §
This includes WAL receiver activity and a wait event for such writes.
", "text": "Add WAL I/O activity rows to pg_stat_io (Nazir Bilal Yavuz, Bertrand Drouvot, Michael Paquier) § § § This includes WAL receiver activity and a wait event for such writes.", "title": "Add WAL I/O activity rows to pg_stat_io", "commits": ["4538bd3f1", "7f7f324eb", "a051e71e2"], "section": "Server / Monitoring", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MONITORING", "source_hash": "1073fae0e1addc89e2446fa37b2acba1f913d9723e1c4429053ee3268c3f10de", "section_path": ["Server", "Monitoring"], "commit_groups": [["4538bd3f1"], ["7f7f324eb"], ["a051e71e2"]], "identity_text": "Add WAL I/O activity rows to pg_stat_io (Nazir Bilal Yavuz, Bertrand Drouvot, Michael Paquier) This includes WAL receiver activity and a wait event for such writes.", "commit_aliases": ["4538bd3f1", "7f7f324eb", "a051e71e2"], "source_commits": ["4538bd3f1", "7f7f324eb", "a051e71e2"], "source_entry_id": "18.0/changes/036", "db_id": "4e8a04b21c8fb51fcf294e0a57d8462f", "patch_ids": ["0abab9a405c724624eabd4509d63171e", "3d509df32980788958c9572c50adb4fd", "bef53f830f1ba9f3cda0cc8ff4ed91e6"], "statement_hash": "c5453439738584b897b3afc314105f41051f5aa95d24752734738916b65af097", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-6c1a9bdb1bd7fe74", "cves": [], "html": "Change server variable track_wal_io_timing to control tracking WAL timing in pg_stat_io instead of pg_stat_wal (Bertrand Drouvot) §
Remove read/sync columns from pg_stat_wal (Bertrand Drouvot) § §
This removes columns wal_write, wal_sync, wal_write_time, and wal_sync_time.
Add function pg_stat_get_backend_wal() to return per-backend WAL statistics (Bertrand Drouvot) §
Per-backend WAL statistics can be cleared via pg_stat_reset_backend_stats().
Add function pg_ls_summariesdir() to specifically list the contents of PGDATA/pg_wal/summaries (Yushi Ogiwara) §
Add column pg_stat_checkpointer.num_done to report the number of completed checkpoints (Anton A. Melnikov) §
Columns num_timed and num_requested count both completed and skipped checkpoints.
Add column pg_stat_checkpointer.slru_written to report SLRU buffers written (Nitin Jadhav) §
Also, modify the checkpoint server log message to report separate shared buffer and SLRU buffer values.
", "text": "Add column pg_stat_checkpointer.slru_written to report SLRU buffers written (Nitin Jadhav) § Also, modify the checkpoint server log message to report separate shared buffer and SLRU buffer values.", "title": "Add column pg_stat_checkpointer.slru_written to report SLRU buffers written", "commits": ["17cc5f666"], "section": "Server / Monitoring", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MONITORING", "source_hash": "e3cd14d094f854569dcf0a7ec616f689d1baac8a113db529f691cfd28c517c08", "section_path": ["Server", "Monitoring"], "commit_groups": [["17cc5f666"]], "identity_text": "Add column pg_stat_checkpointer.slru_written to report SLRU buffers written (Nitin Jadhav) Also, modify the checkpoint server log message to report separate shared buffer and SLRU buffer values.", "commit_aliases": ["17cc5f666"], "source_commits": ["17cc5f666"], "source_entry_id": "18.0/changes/042", "db_id": "c727bac201403ee5787ce91519d78b8f", "patch_ids": ["d6837b0ccfa7bed8d3ef332bff20c386"], "statement_hash": "d75f1cff8692d2b125311380a9eb939eed72a5eec22bed4041dad77e8aed16e7", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-50beb09b38031570", "cves": [], "html": "Add columns to pg_stat_database to report parallel worker activity (Benoit Lobréau) §
The new columns are parallel_workers_to_launch and parallel_workers_launched.
Have query id computation of constant lists consider only the first and last constants (Dmitry Dolgov, Sami Imseih) § § §
\nJumbling is used by pg_stat_statements.
", "text": "Have query id computation of constant lists consider only the first and last constants (Dmitry Dolgov, Sami Imseih) § § § Jumbling is used by pg_stat_statements.", "title": "Have query id computation of constant lists consider only the first and last constants", "commits": ["62d712ecf", "9fbd53dea", "c2da1a5d6"], "section": "Server / Monitoring", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MONITORING", "source_hash": "2cf9373f5b7eddab9fd5ff38dada6cd3257b8f28a837aed595560e11f200a37d", "section_path": ["Server", "Monitoring"], "commit_groups": [["62d712ecf"], ["9fbd53dea"], ["c2da1a5d6"]], "identity_text": "Have query id computation of constant lists consider only the first and last constants (Dmitry Dolgov, Sami Imseih) Jumbling is used by pgstatstatements .", "commit_aliases": ["62d712ecf", "9fbd53dea", "c2da1a5d6"], "source_commits": ["62d712ecf", "9fbd53dea", "c2da1a5d6"], "source_entry_id": "18.0/changes/044", "db_id": "602391884e0f9956bc8189e3df9fa46c", "patch_ids": ["5788e402f9a32d0839d25eda04d2e777", "892e3023e3eb75d6d37898823ef6e17d", "b602290e314da4eb2c893c183d542ea2"], "statement_hash": "15594176dafd96eadc8774ee3c07b03bfac584e26aab1114deaf08975c0d6fa7", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-4bd7c5c5ceccdfa2", "cves": [], "html": "Adjust query id computations to group together queries using the same relation name (Michael Paquier, Sami Imseih) §
\nThis is true even if the tables in different schemas have different column names.
", "text": "Adjust query id computations to group together queries using the same relation name (Michael Paquier, Sami Imseih) § This is true even if the tables in different schemas have different column names.", "title": "Adjust query id computations to group together queries using the same relation name", "commits": ["787514b30"], "section": "Server / Monitoring", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MONITORING", "source_hash": "09abeab4f5099639b5d52aa31679edc914c3b3c20594c0d395bf45bf491d5e09", "section_path": ["Server", "Monitoring"], "commit_groups": [["787514b30"]], "identity_text": "Adjust query id computations to group together queries using the same relation name (Michael Paquier, Sami Imseih) This is true even if the tables in different schemas have different column names.", "commit_aliases": ["787514b30"], "source_commits": ["787514b30"], "source_entry_id": "18.0/changes/045", "db_id": "b3b7d2a11d4d31f38f5974d4bc93b3e3", "patch_ids": ["79273c32213aef68723d02e288664812"], "statement_hash": "4cd23dc47a6dcb75efe88b4674803607d5b63bfc8d8855e3822b801ecc934093", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-3402d3ff0e2cd897", "cves": [], "html": "Add column pg_backend_memory_contexts.type to report the type of memory context (David Rowley) §
Add column pg_backend_memory_contexts.path to show memory context parents (Melih Mutlu) §
Add function pg_get_acl() to retrieve database access control details (Joel Jacobson) § §
Add function has_largeobject_privilege() to check large object privileges (Yugo Nagata) §
Allow ALTER DEFAULT PRIVILEGES to define large object default privileges (Takatsuka Haruka, Yugo Nagata, Laurenz Albe) §
", "text": "Allow ALTER DEFAULT PRIVILEGES to define large object default privileges (Takatsuka Haruka, Yugo Nagata, Laurenz Albe) §", "title": "Allow ALTER DEFAULT PRIVILEGES to define large object default privileges", "commits": ["0d6c47766"], "section": "Server / Privileges", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-PRIVILEGES", "source_hash": "4c91df429994b748ca8f11482114f697801f5b8c6c8b714ebf14f04619bf4653", "section_path": ["Server", "Privileges"], "commit_groups": [["0d6c47766"]], "identity_text": "Allow sql-alterdefaultprivileges to define large object default privileges (Takatsuka Haruka, Yugo Nagata, Laurenz Albe)", "commit_aliases": ["0d6c47766"], "source_commits": ["0d6c47766"], "source_entry_id": "18.0/changes/050", "db_id": "2115b59fe3ecb850d34420db9087d6ee", "patch_ids": ["8bd885a988ec8e858d73081f630fd33d"], "statement_hash": "91512a6ced76577a52c71c7f1692309e60bb18dc1ce44331c056f04fd50fb429", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-63bd5329a9fe779c", "cves": [], "html": "Add predefined role pg_signal_autovacuum_worker (Kirill Reshke) §
This allows sending signals to autovacuum workers.
", "text": "Add predefined role pg_signal_autovacuum_worker (Kirill Reshke) § This allows sending signals to autovacuum workers.", "title": "Add predefined role pg_signal_autovacuum_worker", "commits": ["ccd38024b"], "section": "Server / Privileges", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-PRIVILEGES", "source_hash": "bfdef5e379e1781509025a5997d7b24eee477202a1c63fdf10ed414f0ba7b3e4", "section_path": ["Server", "Privileges"], "commit_groups": [["ccd38024b"]], "identity_text": "Add predefined role pg_signal_autovacuum_worker (Kirill Reshke) This allows sending signals to autovacuum workers.", "commit_aliases": ["ccd38024b"], "source_commits": ["ccd38024b"], "source_entry_id": "18.0/changes/051", "db_id": "20b3f6628c87707ad4d0eb8fd8768e0a", "patch_ids": ["a254744dab5b2721c5babac8740a351d"], "statement_hash": "c15408fea664f43b416b4b112fe35a5f8e4c76546718ab374fef03190e47327d", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-8937e04e6f598c9a", "cves": [], "html": "Add support for the OAuth authentication method (Jacob Champion, Daniel Gustafsson, Thomas Munro) §
\nThis adds an oauth authentication method to pg_hba.conf, libpq OAuth options, a server variable oauth_validator_libraries to load token validation libraries, and a configure flag --with-libcurl to add the required compile-time libraries.
Add server variable ssl_tls13_ciphers to allow specification of multiple colon-separated TLSv1.3 cipher suites (Erica Zhang, Daniel Gustafsson) §
", "text": "Add server variable ssl_tls13_ciphers to allow specification of multiple colon-separated TLSv1.3 cipher suites (Erica Zhang, Daniel Gustafsson) §", "title": "Add server variable ssl_tls13_ciphers to allow specification of multiple colon-separated TLSv1.3 cipher suites", "commits": ["45188c2ea"], "section": "Server / Server Configuration", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SERVER-CONFIG", "source_hash": "5d256d99caaf5046100077cd472e922ae375d82b0f5b45bcfbac3a79833692b5", "section_path": ["Server", "Server Configuration"], "commit_groups": [["45188c2ea"]], "identity_text": "Add server variable guc-ssl-tls13-ciphers to allow specification of multiple colon-separated TLSv1.3 cipher suites (Erica Zhang, Daniel Gustafsson)", "commit_aliases": ["45188c2ea"], "source_commits": ["45188c2ea"], "source_entry_id": "18.0/changes/053", "db_id": "13b081fb2e1030e7c402c99be84d674e", "patch_ids": ["b918cd02542986f670ea5e4ccce7bed8"], "statement_hash": "ffe4b310bcfc2b812bd9ca43729c6e6988676e615fa96ac501930ef3cd998db9", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-7ae83796934b368a", "cves": [], "html": "Change server variable ssl_groups's default to include elliptic curve X25519 (Daniel Gustafsson, Jacob Champion) §
", "text": "Change server variable ssl_groups's default to include elliptic curve X25519 (Daniel Gustafsson, Jacob Champion) §", "title": "Change server variable ssl_groups's default to include elliptic curve X25519", "commits": ["daa02c6bd"], "section": "Server / Server Configuration", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SERVER-CONFIG", "source_hash": "769ef4c7a0e583d2f4cb847ab408143dd1d5d440e558c0b751debd0c43265451", "section_path": ["Server", "Server Configuration"], "commit_groups": [["daa02c6bd"]], "identity_text": "Change server variable guc-ssl-groups 's default to include elliptic curve X25519 (Daniel Gustafsson, Jacob Champion)", "commit_aliases": ["daa02c6bd"], "source_commits": ["daa02c6bd"], "source_entry_id": "18.0/changes/054", "db_id": "0ff6b951577e789ccfcf50c5fdd16250", "patch_ids": ["b6419e2ab5092340bdb51279a882c575"], "statement_hash": "79f1b0ec5dbbc9c41cfae0c653c6b8af2978a2d458009ec866463efb3c895406", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-ec11a3f47cab5302", "cves": [], "html": "Rename server variable ssl_ecdh_curve to ssl_groups and allow multiple colon-separated ECDH curves to be specified (Erica Zhang, Daniel Gustafsson) §
The previous name still works.
", "text": "Rename server variable ssl_ecdh_curve to ssl_groups and allow multiple colon-separated ECDH curves to be specified (Erica Zhang, Daniel Gustafsson) § The previous name still works.", "title": "Rename server variable ssl_ecdh_curve to ssl_groups and allow multiple colon-separated ECDH curves to be specified", "commits": ["3d1ef3a15"], "section": "Server / Server Configuration", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SERVER-CONFIG", "source_hash": "69fc229fb451ba3569f10661789b08fd931063d5102c111408c2c761550da092", "section_path": ["Server", "Server Configuration"], "commit_groups": [["3d1ef3a15"]], "identity_text": "Rename server variable ssl_ecdh_curve to guc-ssl-groups and allow multiple colon-separated ECDH curves to be specified (Erica Zhang, Daniel Gustafsson) The previous name still works.", "commit_aliases": ["3d1ef3a15"], "source_commits": ["3d1ef3a15"], "source_entry_id": "18.0/changes/055", "db_id": "96a81164afdac0bf4ed0486ab950b9cc", "patch_ids": ["c2561d4875ae281fdaea78d9e93eaee2"], "statement_hash": "af282a32e71f1303e38dd9f838dce742a3ea5e5033c66e5a334acc730ab67445", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-fc222bd600eb20c7", "cves": [], "html": "Make cancel request keys 256 bits (Heikki Linnakangas, Jelte Fennema-Nio) § §
\nThis is only possible when the server and client support wire protocol version 3.2, introduced in this release.
", "text": "Make cancel request keys 256 bits (Heikki Linnakangas, Jelte Fennema-Nio) § § This is only possible when the server and client support wire protocol version 3.2, introduced in this release.", "title": "Make cancel request keys 256 bits", "commits": ["9d9b9d46f", "a460251f0"], "section": "Server / Server Configuration", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SERVER-CONFIG", "source_hash": "4da7c6464ec24190e054671959a89c1342b41fd9c2df30a579e2cb4c8e608823", "section_path": ["Server", "Server Configuration"], "commit_groups": [["9d9b9d46f"], ["a460251f0"]], "identity_text": "Make cancel request keys 256 bits (Heikki Linnakangas, Jelte Fennema-Nio) This is only possible when the server and client support wire protocol version 3.2, introduced in this release.", "commit_aliases": ["9d9b9d46f", "a460251f0"], "source_commits": ["9d9b9d46f", "a460251f0"], "source_entry_id": "18.0/changes/056", "db_id": "d4bdcc752134e88e3b6f69045f91e32f", "patch_ids": ["3374f7d4348f979a16fb3f835b1434dd", "78aeb882063c4d9c0113cb769f6f63c8"], "statement_hash": "bf970fd6a3a870ec104cf3173699ac7821ccb4e686bb18b2d9050cfee203c953", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-fad3071db20b5849", "cves": [], "html": "Add server variable autovacuum_worker_slots to specify the maximum number of background workers (Nathan Bossart) §
\nWith this variable set, autovacuum_max_workers can be adjusted at runtime up to this maximum without a server restart.
", "text": "Add server variable autovacuum_worker_slots to specify the maximum number of background workers (Nathan Bossart) § With this variable set, autovacuum_max_workers can be adjusted at runtime up to this maximum without a server restart.", "title": "Add server variable autovacuum_worker_slots to specify the maximum number of background workers", "commits": ["c758119e5"], "section": "Server / Server Configuration", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SERVER-CONFIG", "source_hash": "cccf9f941c4560c33011e635dcab0b9c28ae26749ffd1608f7169c4ecf499acc", "section_path": ["Server", "Server Configuration"], "commit_groups": [["c758119e5"]], "identity_text": "Add server variable guc-autovacuum-worker-slots to specify the maximum number of background workers (Nathan Bossart) With this variable set, guc-autovacuum-max-workers can be adjusted at runtime up to this maximum without a server restart.", "commit_aliases": ["c758119e5"], "source_commits": ["c758119e5"], "source_entry_id": "18.0/changes/057", "db_id": "14193c2c6216dac54ee9f03d74597315", "patch_ids": ["17efa2578b6fdfca54d1895a47b5d85c"], "statement_hash": "2340cf9dd0c8914c3ae78fcca1d6cb8a3eec267275fe98352062b37d256a1302", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-cc3cc0af71ac8fcd", "cves": [], "html": "Allow specification of the fixed number of dead tuples that will trigger an autovacuum (Nathan Bossart, Frédéric Yhuel) §
\nThe server variable is autovacuum_vacuum_max_threshold. Percentages are still used for triggering.
", "text": "Allow specification of the fixed number of dead tuples that will trigger an autovacuum (Nathan Bossart, Frédéric Yhuel) § The server variable is autovacuum_vacuum_max_threshold. Percentages are still used for triggering.", "title": "Allow specification of the fixed number of dead tuples that will trigger an autovacuum", "commits": ["306dc520b"], "section": "Server / Server Configuration", "category": "bugfix", "source_url": "/docs/release/18.0/#RELEASE-18-SERVER-CONFIG", "source_hash": "fd553683edfb9d3b450f0a00d5e58d81232bb84ff144ad688ad048e97b11922e", "section_path": ["Server", "Server Configuration"], "commit_groups": [["306dc520b"]], "identity_text": "Allow specification of the fixed number of dead tuples that will trigger an autovacuum (Nathan Bossart, Frédéric Yhuel) The server variable is guc-autovacuum-vacuum-max-threshold . Percentages are still used for triggering.", "commit_aliases": ["306dc520b"], "source_commits": ["306dc520b"], "source_entry_id": "18.0/changes/058", "db_id": "c6c8d0da14fc739954f67e4c3e8e297c", "patch_ids": ["fede0a2ed06d94a30aac6de8675efbce"], "statement_hash": "f26aed72e786336ffb0181c576796c1b0d66b6c0c79fa7ab8337a9deb9a04a70", "relations": [], "version": "18.0", "category_label": "Bug fixes", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-88c8af4f4659a505", "cves": [], "html": "Change server variable max_files_per_process to limit only files opened by a backend (Andres Freund) §
\nPreviously files opened by the postmaster were also counted toward this limit.
", "text": "Change server variable max_files_per_process to limit only files opened by a backend (Andres Freund) § Previously files opened by the postmaster were also counted toward this limit.", "title": "Change server variable max_files_per_process to limit only files opened by a backend", "commits": ["adb5f85fa"], "section": "Server / Server Configuration", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SERVER-CONFIG", "source_hash": "2618bfe12d00c39268c401694e59d9fad97443ba987c22b6d62e307da9068d9a", "section_path": ["Server", "Server Configuration"], "commit_groups": [["adb5f85fa"]], "identity_text": "Change server variable guc-max-files-per-process to limit only files opened by a backend (Andres Freund) Previously files opened by the postmaster were also counted toward this limit.", "commit_aliases": ["adb5f85fa"], "source_commits": ["adb5f85fa"], "source_entry_id": "18.0/changes/059", "db_id": "7d0f8a8401a0235fee5c42443323fd9f", "patch_ids": ["1253eb7b68a386abd794c882137adc02"], "statement_hash": "04e1a6687e91598505d1cd8239184c483171e03aa143374ed943a3e8b71c817c", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-a70925addf13174f", "cves": [], "html": "Add server variable num_os_semaphores to report the required number of semaphores (Nathan Bossart) §
\nThis is useful for operating system configuration.
", "text": "Add server variable num_os_semaphores to report the required number of semaphores (Nathan Bossart) § This is useful for operating system configuration.", "title": "Add server variable num_os_semaphores to report the required number of semaphores", "commits": ["0dcaea569"], "section": "Server / Server Configuration", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SERVER-CONFIG", "source_hash": "9ab5511113bd82e70e3a03fc12538f6345af41f77c718778b40bf3d3a03203b6", "section_path": ["Server", "Server Configuration"], "commit_groups": [["0dcaea569"]], "identity_text": "Add server variable guc-num-os-semaphores to report the required number of semaphores (Nathan Bossart) This is useful for operating system configuration.", "commit_aliases": ["0dcaea569"], "source_commits": ["0dcaea569"], "source_entry_id": "18.0/changes/060", "db_id": "baa925cc966c3797d6c1baeb8600b3af", "patch_ids": ["7cab2bba487b8dfdc88b894d86ebcb31"], "statement_hash": "db627bdf62b6a351d882ccec445c9221ec8e4d930aed5bf5e6b0b5b611bd8094", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-fcaec73419edafbc", "cves": [], "html": "Add server variable extension_control_path to specify the location of extension control files (Peter Eisentraut, Matheus Alcantara) § §
", "text": "Add server variable extension_control_path to specify the location of extension control files (Peter Eisentraut, Matheus Alcantara) § §", "title": "Add server variable extension_control_path to specify the location of extension control files", "commits": ["4f7f7b037", "81eaaa2c4"], "section": "Server / Server Configuration", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SERVER-CONFIG", "source_hash": "9d62b8c0663f70e4f69542ec94abb0e3f367bb880d1661fa4b5ee26a52495548", "section_path": ["Server", "Server Configuration"], "commit_groups": [["4f7f7b037"], ["81eaaa2c4"]], "identity_text": "Add server variable guc-extension-control-path to specify the location of extension control files (Peter Eisentraut, Matheus Alcantara)", "commit_aliases": ["4f7f7b037", "81eaaa2c4"], "source_commits": ["4f7f7b037", "81eaaa2c4"], "source_entry_id": "18.0/changes/061", "db_id": "9a0ac630df36e673c00b61131cd0c2ff", "patch_ids": ["2c992ea1a18c7e56b1999e13915ad2f8", "95178da37b740ae32403368a9d5de091"], "statement_hash": "b2d063e72b9d991ddf32656536cdf6aa960609b5293a9f7685124d9018ed0d46", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-d6cdb50cb80abdda", "cves": [], "html": "Allow inactive replication slots to be automatically invalidated using server variable idle_replication_slot_timeout (Nisha Moond, Bharath Rupireddy) §
", "text": "Allow inactive replication slots to be automatically invalidated using server variable idle_replication_slot_timeout (Nisha Moond, Bharath Rupireddy) §", "title": "Allow inactive replication slots to be automatically invalidated using server variable idle_replication_slot_timeout", "commits": ["ac0e33136"], "section": "Server / Streaming Replication and Recovery", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-REPLICATION", "source_hash": "8c442254dde2045ae1b1e87460c9e70a650a5b8afddfac774dc1463a967d81ba", "section_path": ["Server", "Streaming Replication and Recovery"], "commit_groups": [["ac0e33136"]], "identity_text": "Allow inactive replication slots to be automatically invalidated using server variable guc-idle-replication-slot-timeout (Nisha Moond, Bharath Rupireddy)", "commit_aliases": ["ac0e33136"], "source_commits": ["ac0e33136"], "source_entry_id": "18.0/changes/062", "db_id": "7e52ed73d316bf78778f528fedb05f84", "patch_ids": ["df8d31e4efb6cb139d5c669e2215050c"], "statement_hash": "eb9a1e5c89e5b4fa71a37fedc208ddb8c2f0f95fbc1eec06821cbc772f3bd8fc", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-03713c460c2a7d56", "cves": [], "html": "Add server variable max_active_replication_origins to control the maximum active replication origins (Euler Taveira) §
\nThis was previously controlled by max_replication_slots, but this new setting allows a higher origin count in cases where fewer slots are required.
", "text": "Add server variable max_active_replication_origins to control the maximum active replication origins (Euler Taveira) § This was previously controlled by max_replication_slots, but this new setting allows a higher origin count in cases where fewer slots are required.", "title": "Add server variable max_active_replication_origins to control the maximum active replication origins", "commits": ["04ff636cb"], "section": "Server / Streaming Replication and Recovery", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-REPLICATION", "source_hash": "33b1bea544f15476df511f7f493e700d5039ed734c0053ce03bf246913999aca", "section_path": ["Server", "Streaming Replication and Recovery"], "commit_groups": [["04ff636cb"]], "identity_text": "Add server variable guc-max-active-replication-origins to control the maximum active replication origins (Euler Taveira) This was previously controlled by guc-max-replication-slots , but this new setting allows a higher origin count in cases where fewer slots are required.", "commit_aliases": ["04ff636cb"], "source_commits": ["04ff636cb"], "source_entry_id": "18.0/changes/063", "db_id": "1428b3f7f6cc1a4506850622a40c3ffb", "patch_ids": ["a8c08a420a79bd1a161ea23d9bef6d71"], "statement_hash": "9e85b8d9968595a466cfb230295bcf24c446ed069e908115b73bf70ddbaf2392", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-b3be55f006e9da56", "cves": [], "html": "Allow the values of generated columns to be logically replicated (Shubham Khanna, Vignesh C, Zhijie Hou, Shlok Kyal, Peter Smith) § § § §
\nIf the publication specifies a column list, all specified columns, generated and non-generated, are published. Without a specified column list, publication option publish_generated_columns controls whether generated columns are published. Previously generated columns were not replicated and the subscriber had to compute the values if possible; this is particularly useful for non-PostgreSQL subscribers which lack such a capability.
Change the default CREATE SUBSCRIPTION streaming option from off to parallel (Vignesh C) §
Allow ALTER SUBSCRIPTION to change the replication slot's two-phase commit behavior (Hayato Kuroda, Ajin Cherian, Amit Kapila, Zhijie Hou) § §
", "text": "Allow ALTER SUBSCRIPTION to change the replication slot's two-phase commit behavior (Hayato Kuroda, Ajin Cherian, Amit Kapila, Zhijie Hou) § §", "title": "Allow ALTER SUBSCRIPTION to change the replication slot's two-phase commit behavior", "commits": ["1462aad2e", "4868c96bc"], "section": "Server / Logical Replication", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-LOGICAL", "source_hash": "b96743f044a02e2201e5e678b547c8fdb56efd310343f8b3e4919fa6c862dfc7", "section_path": ["Server", "Logical Replication"], "commit_groups": [["1462aad2e"], ["4868c96bc"]], "identity_text": "Allow sql-altersubscription to change the replication slot's two-phase commit behavior (Hayato Kuroda, Ajin Cherian, Amit Kapila, Zhijie Hou)", "commit_aliases": ["1462aad2e", "4868c96bc"], "source_commits": ["1462aad2e", "4868c96bc"], "source_entry_id": "18.0/changes/066", "db_id": "41cd5554ab5a99df850ddc649a630bf5", "patch_ids": ["15c1439cde9cf963e340507c56e6bd57", "fd8060f9266b72de63d063d80a6bb2f9"], "statement_hash": "4c14605560e017cf4d89bb8a33a0ab993f4a9ff353648fde85d7e88cde571530", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-a8d78b040297e9b0", "cves": [], "html": "Log conflicts while applying logical replication changes (Zhijie Hou, Nisha Moond) § § § § §
\nAlso report in new columns of pg_stat_subscription_stats.
Allow generated columns to be virtual, and make them the default (Peter Eisentraut, Jian He, Richard Guo, Dean Rasheed) § § §
\nVirtual generated columns generate their values when the columns are read, not written. The write behavior can still be specified via the STORED option.
Add OLD/NEW support to RETURNING in DML queries (Dean Rasheed) §
Previously RETURNING only returned new values for INSERT and UPDATE, and old values for DELETE; MERGE would return the appropriate value for the internal query executed. This new syntax allows the RETURNING list of INSERT/UPDATE/DELETE/MERGE to explicitly return old and new values by using the special aliases old and new. These aliases can be renamed to avoid identifier conflicts.
Allow foreign tables to be created like existing local tables (Zhang Mingli) §
\nThe syntax is CREATE FOREIGN TABLE ... LIKE.
Allow LIKE with nondeterministic collations (Peter Eisentraut) §
Allow text position search functions with nondeterministic collations (Peter Eisentraut) §
\nThese used to generate an error.
", "text": "Allow text position search functions with nondeterministic collations (Peter Eisentraut) § These used to generate an error.", "title": "Allow text position search functions with nondeterministic collations", "commits": ["329304c90"], "section": "Utility Commands", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-UTILITY", "source_hash": "44de95f0bc4bf8dedce0af6fad80799804648813e2b8d379595f9119068daf23", "section_path": ["Utility Commands"], "commit_groups": [["329304c90"]], "identity_text": "Allow text position search functions with nondeterministic collations (Peter Eisentraut) These used to generate an error.", "commit_aliases": ["329304c90"], "source_commits": ["329304c90"], "source_entry_id": "18.0/changes/072", "db_id": "1633612e398b9d62fc3745ae04ffbdcb", "patch_ids": ["43d52072e1fb7ccdaab204775ce5218b"], "statement_hash": "819c561a7502a24a171a66abb4e6b6d3543683ac066ea66ccff53a0fce4befea", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-353986c77138379c", "cves": [], "html": "Add builtin collation provider PG_UNICODE_FAST (Jeff Davis) §
This locale supports case mapping, but sorts in code point order, not natural language order.
", "text": "Add builtin collation provider PG_UNICODE_FAST (Jeff Davis) § This locale supports case mapping, but sorts in code point order, not natural language order.", "title": "Add builtin collation provider PG_UNICODE_FAST", "commits": ["d3d098316"], "section": "Utility Commands", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-UTILITY", "source_hash": "c67e8fc3c341be4b77ad03dc233abe7dcf8538d89e6aa0f6ccdf7ecd5fced9ee", "section_path": ["Utility Commands"], "commit_groups": [["d3d098316"]], "identity_text": "Add builtin collation provider PG_UNICODE_FAST (Jeff Davis) This locale supports case mapping, but sorts in code point order, not natural language order.", "commit_aliases": ["d3d098316"], "source_commits": ["d3d098316"], "source_entry_id": "18.0/changes/073", "db_id": "30595e5c571a05cc7aee9889ba3a082f", "patch_ids": ["04e3a10e98b76c4d3552450e42090216"], "statement_hash": "a2fd33890c8b434927b30005c495e84f2917c37b0d70177e7af7e169446cb0cc", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-f2283e0ad8b607f4", "cves": [], "html": "Allow VACUUM and ANALYZE to process partitioned tables without processing their children (Michael Harris) §
\nThis is enabled with the new ONLY option. This is useful since autovacuum does not process partitioned tables, just its children.
Add functions to modify per-relation and per-column optimizer statistics (Corey Huinker) § § §
\nThe functions are pg_restore_relation_stats(), pg_restore_attribute_stats(), pg_clear_relation_stats(), and pg_clear_attribute_stats().
Add server variable file_copy_method to control the file copying method (Nazir Bilal Yavuz) §
\nThis controls whether CREATE DATABASE ... STRATEGY=FILE_COPY and ALTER DATABASE ... SET TABLESPACE uses file copy or clone.
Allow the specification of non-overlapping PRIMARY KEY, UNIQUE, and foreign key constraints (Paul A. Jungwirth) § §
This is specified by WITHOUT OVERLAPS for PRIMARY KEY and UNIQUE, and by PERIOD for foreign keys, all applied to the last specified column.
Allow CHECK and foreign key constraints to be specified as NOT ENFORCED (Amul Sul) § §
This also adds column pg_constraint.conenforced.
Require primary/foreign key relationships to use either deterministic collations or the the same nondeterministic collations (Peter Eisentraut) §
\nThe restore of a pg_dump, also used by pg_upgrade, will fail if these requirements are not met; schema changes must be made for these upgrade methods to succeed.
", "text": "Require primary/foreign key relationships to use either deterministic collations or the the same nondeterministic collations (Peter Eisentraut) § The restore of a pg_dump, also used by pg_upgrade, will fail if these requirements are not met; schema changes must be made for these upgrade methods to succeed.", "title": "Require primary/foreign key relationships to use either deterministic collations or the the same nondeterministic collations", "commits": ["9321d2fdf"], "section": "Utility Commands / Constraints", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-CONSTRAINTS", "source_hash": "2b17eb3b34045fd66a066a2076d863f0fa350f40aa79c07d72d3a50fcdeff6f3", "section_path": ["Utility Commands", "Constraints"], "commit_groups": [["9321d2fdf"]], "identity_text": "Require primary/foreign key relationships to use either deterministic collations or the the same nondeterministic collations (Peter Eisentraut) The restore of a app-pgdump , also used by pgupgrade , will fail if these requirements are not met; schema changes must be made for these upgrade methods to succeed.", "commit_aliases": ["9321d2fdf"], "source_commits": ["9321d2fdf"], "source_entry_id": "18.0/changes/079", "db_id": "68a1f7d62d756e8a62c81960b94b7516", "patch_ids": ["0ce5a6d8a11a1381cec57c4513b145b6"], "statement_hash": "2618c39bc6d6dedcb5838152a2f2578f929d0e51755b824342e7609b6456ce31", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-0039523c093ff51f", "cves": [], "html": "Store column NOT NULL specifications in pg_constraint (Álvaro Herrera, Bernd Helmle) § §
This allows names to be specified for NOT NULL constraint. This also adds NOT NULL constraints to foreign tables and NOT NULL inheritance control to local tables.
Allow ALTER TABLE to set the NOT VALID attribute of NOT NULL constraints (Rushabh Lathia, Jian He) §
Allow modification of the inheritability of NOT NULL constraints (Suraj Kharage, Álvaro Herrera) § §
The syntax is ALTER TABLE ... ALTER CONSTRAINT ... [NO] INHERIT.
Allow NOT VALID foreign key constraints on partitioned tables (Amul Sul) §
Allow dropping of constraints ONLY on partitioned tables (Álvaro Herrera) §
This was previously erroneously prohibited.
", "text": "Allow dropping of constraints ONLY on partitioned tables (Álvaro Herrera) § This was previously erroneously prohibited.", "title": "Allow dropping of constraints ONLY on partitioned tables", "commits": ["4dea33ce7"], "section": "Utility Commands / Constraints", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-CONSTRAINTS", "source_hash": "8c1219c56b3716c6e0669450727af7aed75763ee754fd98663afe83cdbb70624", "section_path": ["Utility Commands", "Constraints"], "commit_groups": [["4dea33ce7"]], "identity_text": "Allow dropping of constraints ONLY on partitioned tables (Álvaro Herrera) This was previously erroneously prohibited.", "commit_aliases": ["4dea33ce7"], "source_commits": ["4dea33ce7"], "source_entry_id": "18.0/changes/084", "db_id": "18344143b41582623ed016d08d3724f0", "patch_ids": ["e01f71769bcebafa65ea9e9facbc8f0e"], "statement_hash": "2f709f0920ff299f36d06fa6d2c5e29a93df41901d6a0aa8e7f22d2226fd478d", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-b15309054d630829", "cves": [], "html": "Add REJECT_LIMIT to control the number of invalid rows COPY FROM can ignore (Atsushi Torikoshi) §
This is available when ON_ERROR = 'ignore'.
Allow COPY TO to copy rows from populated materialized views (Jian He) §
Add COPY LOG_VERBOSITY level silent to suppress log output of ignored rows (Atsushi Torikoshi) §
This new level suppresses output for discarded input rows when on_error = 'ignore'.
Disallow COPY FREEZE on foreign tables (Nathan Bossart) §
Previously, the COPY worked but the FREEZE was ignored, so disallow this command.
Automatically include BUFFERS output in EXPLAIN ANALYZE (Guillaume Lelarge, David Rowley) §
Add full WAL buffer count to EXPLAIN (WAL) output (Bertrand Drouvot) §
In EXPLAIN ANALYZE, report the number of index lookups used per index scan node (Peter Geoghegan) §
Modify EXPLAIN to output fractional row counts (Ibrar Ahmed, Ilia Evdokimov, Robert Haas) § §
Add memory and disk usage details to Material, Window Aggregate, and common table expression nodes to EXPLAIN output (David Rowley, Tatsuo Ishii) § § § §
Add details about window function arguments to EXPLAIN output (Tom Lane) §
Add Parallel Bitmap Heap Scan worker cache statistics to EXPLAIN ANALYZE (David Geier, Heikki Linnakangas, Donghang Lin, Alena Rybakina, David Rowley) §
Indicate disabled nodes in EXPLAIN ANALYZE output (Robert Haas, David Rowley, Laurenz Albe) § § §
Improve Unicode full case mapping and conversion (Jeff Davis) § §
\nThis adds the ability to do conditional and title case mapping, and case map single characters to multiple characters.
", "text": "Improve Unicode full case mapping and conversion (Jeff Davis) § § This adds the ability to do conditional and title case mapping, and case map single characters to multiple characters.", "title": "Improve Unicode full case mapping and conversion", "commits": ["286a365b9", "4e7f62bc3"], "section": "Data Types", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-DATATYPES", "source_hash": "44c26c92986f06630e401c20db860295e1e24fcd5259ea9ea934f4bf062fdd8e", "section_path": ["Data Types"], "commit_groups": [["286a365b9"], ["4e7f62bc3"]], "identity_text": "Improve Unicode full case mapping and conversion (Jeff Davis) This adds the ability to do conditional and title case mapping, and case map single characters to multiple characters.", "commit_aliases": ["286a365b9", "4e7f62bc3"], "source_commits": ["286a365b9", "4e7f62bc3"], "source_entry_id": "18.0/changes/097", "db_id": "1b2ed6a4886122496b4235e9bc502410", "patch_ids": ["0bc695a859154bdbe2aa4141a8c131d7", "c4d90a2c6dc576697ae6803230585a80"], "statement_hash": "02776b8149a82584d272cc2094e4a669aca778c5844f65839a5f72cf0687f143", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-e8ea7869a8082253", "cves": [], "html": "Allow jsonb null values to be cast to scalar types as NULL (Tom Lane) §
Previously such casts generated an error.
", "text": "Allow jsonb null values to be cast to scalar types as NULL (Tom Lane) § Previously such casts generated an error.", "title": "Allow jsonb null values to be cast to scalar types as NULL", "commits": ["a5579a90a"], "section": "Data Types", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-DATATYPES", "source_hash": "1e15ce0182df8ba9bb4f5d3c70a693a1c71b87744e48c4280afcb76462804520", "section_path": ["Data Types"], "commit_groups": [["a5579a90a"]], "identity_text": "Allow jsonb null values to be cast to scalar types as NULL (Tom Lane) Previously such casts generated an error.", "commit_aliases": ["a5579a90a"], "source_commits": ["a5579a90a"], "source_entry_id": "18.0/changes/098", "db_id": "707a9526e8d1e6416419dcc4e0f8c1fb", "patch_ids": ["f6184b101cbccd529291b34b9ea43559"], "statement_hash": "e835773742df55f58b57f5dbf777b47ddc9916b939e5f10a60426d8f63610fdd", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-69d404540f719906", "cves": [], "html": "Add optional parameter to json{b}_strip_nulls to allow removal of null array elements (Florents Tselai) §
Add function array_sort() which sorts an array's first dimension (Junwang Zhao, Jian He) §
Add function array_reverse() which reverses an array's first dimension (Aleksander Alekseev) §
Add function reverse() to reverse bytea bytes (Aleksander Alekseev) §
Allow casting between integer types and bytea (Aleksander Alekseev) §
The integer values are stored as bytea two's complement values.
Update Unicode data to Unicode 16.0.0 (Peter Eisentraut) §
", "text": "Update Unicode data to Unicode 16.0.0 (Peter Eisentraut) §", "title": "Update Unicode data to Unicode 16.0.0", "commits": ["82a46cca9"], "section": "Data Types", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-DATATYPES", "source_hash": "7b363edbf7fc1652e00ae639f016a531400b78a1501225262fbf76a7fc2c0dd8", "section_path": ["Data Types"], "commit_groups": [["82a46cca9"]], "identity_text": "Update Unicode data to Unicode 16.0.0 (Peter Eisentraut)", "commit_aliases": ["82a46cca9"], "source_commits": ["82a46cca9"], "source_entry_id": "18.0/changes/104", "db_id": "b3a13160940dac3f7a1a1af7f4cf764d", "patch_ids": ["37e8f514959e205b0155b61312d52d56"], "statement_hash": "dc448dd80b25033f629182d9bb00f6e6eb258933e0fc988309cd3ddbaf4be408", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-5f1391509757dd6d", "cves": [], "html": "Add full text search stemming for Estonian (Tom Lane) §
", "text": "Add full text search stemming for Estonian (Tom Lane) §", "title": "Add full text search stemming for Estonian", "commits": ["b464e51ab"], "section": "Data Types", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-DATATYPES", "source_hash": "dd6878414ee23406689c7eefc1a641935c96e6bd890e0e1431ff6fd28bfca759", "section_path": ["Data Types"], "commit_groups": [["197427fb3", "7edd2cbc5", "8388cae55", "9c46d902b", "b464e51ab", "c0c364fa1"]], "identity_text": "Add full text search stemming for Estonian (Tom Lane)", "commit_aliases": ["197427fb3", "7edd2cbc5", "8388cae55", "9c46d902b", "b464e51ab", "c0c364fa1"], "source_commits": ["b464e51ab"], "source_entry_id": "18.0/changes/105", "db_id": "d02c90e2590d4a47f73a5782496b4966", "patch_ids": ["d20fbffc83ee90d1348f1d03836b8f18"], "statement_hash": "765cc1defacc087129eb32bf5f736de4c5be16883a95fba7b8adca47a87ce874", "relations": [{"rule": 2, "type": "related", "target": "00feddbb8384a7a8cefe4217cd497215", "evidence": {"same_day": false, "patch_ids": ["d20fbffc83ee90d1348f1d03836b8f18"]}}, {"rule": 2, "type": "related", "target": "43dbc69a435522e8a12bbf37193bcbca", "evidence": {"same_day": false, "patch_ids": ["d20fbffc83ee90d1348f1d03836b8f18"]}}, {"rule": 2, "type": "related", "target": "c2850458f2850974df366bef8a85488e", "evidence": {"same_day": false, "patch_ids": ["d20fbffc83ee90d1348f1d03836b8f18"]}}, {"rule": 2, "type": "related", "target": "d6bf0f560b8ac8cad3c1d6a070b45594", "evidence": {"same_day": false, "patch_ids": ["d20fbffc83ee90d1348f1d03836b8f18"]}}, {"rule": 2, "type": "related", "target": "fe6fa87c7f7a2f01e5226fc8b75d4395", "evidence": {"same_day": false, "patch_ids": ["d20fbffc83ee90d1348f1d03836b8f18"]}}], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": [{"db_id": "fe6fa87c7f7a2f01e5226fc8b75d4395", "kind": "related", "version": "17.5", "label": "17.5", "title": "Avoid crash when a Snowball stemmer encounters an out-of-memory condition", "evidence": {"same_day": false, "patch_ids": ["d20fbffc83ee90d1348f1d03836b8f18"]}, "url": "/docs/compare/?release=17.5#17.5-88fad50b7b3b2e15", "source_url": "/docs/release/17.5/#RELEASE-17-5-CHANGES"}, {"db_id": "c2850458f2850974df366bef8a85488e", "kind": "related", "version": "16.9", "label": "16.9", "title": "Avoid crash when a Snowball stemmer encounters an out-of-memory condition", "evidence": {"same_day": false, "patch_ids": ["d20fbffc83ee90d1348f1d03836b8f18"]}, "url": "/docs/compare/?release=16.9#16.9-71f38ed0f1b64f88", "source_url": "/docs/release/16.9/#RELEASE-16-9-CHANGES"}, {"db_id": "00feddbb8384a7a8cefe4217cd497215", "kind": "related", "version": "15.13", "label": "15.13", "title": "Avoid crash when a Snowball stemmer encounters an out-of-memory condition", "evidence": {"same_day": false, "patch_ids": ["d20fbffc83ee90d1348f1d03836b8f18"]}, "url": "/docs/compare/?release=15.13#15.13-6fa1c30b53ef4a7a", "source_url": "/docs/release/15.13/#id-1.11.6.12.5"}, {"db_id": "d6bf0f560b8ac8cad3c1d6a070b45594", "kind": "related", "version": "14.18", "label": "14.18", "title": "Avoid crash when a Snowball stemmer encounters an out-of-memory condition", "evidence": {"same_day": false, "patch_ids": ["d20fbffc83ee90d1348f1d03836b8f18"]}, "url": "/docs/compare/?release=14.18#14.18-813abffbc8584526", "source_url": "/docs/release/14.18/#id-1.11.6.12.5"}, {"db_id": "43dbc69a435522e8a12bbf37193bcbca", "kind": "related", "version": "13.21", "label": "13.21", "title": "Avoid crash when a Snowball stemmer encounters an out-of-memory condition", "evidence": {"same_day": false, "patch_ids": ["d20fbffc83ee90d1348f1d03836b8f18"]}, "url": "/docs/compare/?release=13.21#13.21-7de382d5402e6e82", "source_url": "/docs/release/13.21/#id-1.11.6.8.6"}]}, {"id": "18.0-484da2e971e2ea9a", "cves": [], "html": "Improve the XML error codes to more closely match the SQL standard (Tom Lane) §
These errors are reported via SQLSTATE.
Add function casefold() to allow for more sophisticated case-insensitive matching (Jeff Davis) §
This allows more accurate comparisons, i.e., a character can have multiple upper or lower case equivalents, or upper or lower case conversion changes the number of characters.
", "text": "Add function casefold() to allow for more sophisticated case-insensitive matching (Jeff Davis) § This allows more accurate comparisons, i.e., a character can have multiple upper or lower case equivalents, or upper or lower case conversion changes the number of characters.", "title": "Add function casefold() to allow for more sophisticated case-insensitive matching", "commits": ["bfc599206"], "section": "Functions", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-FUNCTIONS", "source_hash": "45cb069e223659d8f877c9a2110d431b847abaa3d2bf90c2d51977f38f2e6cb4", "section_path": ["Functions"], "commit_groups": [["bfc599206"]], "identity_text": "Add function casefold() to allow for more sophisticated case-insensitive matching (Jeff Davis) This allows more accurate comparisons, i.e., a character can have multiple upper or lower case equivalents, or upper or lower case conversion changes the number of characters.", "commit_aliases": ["bfc599206"], "source_commits": ["bfc599206"], "source_entry_id": "18.0/changes/107", "db_id": "b6349fdce5ba2ae112d0be3d05e38198", "patch_ids": ["0684a21f7afe3e30c9299aaa67789314"], "statement_hash": "c9d001f8f460c1f05dad5d20c8956c701fd640f0996cec7198b5decd3f545c09", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-6997f70f04ef9a9f", "cves": [], "html": "Allow MIN()/MAX() aggregates on arrays and composite types (Aleksander Alekseev, Marat Buharov) § §
Add a WEEK option to EXTRACT() (Tom Lane) §
Improve the output EXTRACT(QUARTER ...) for negative values (Tom Lane) §
Add roman numeral support to to_number() (Hunaid Sohail) §
This is accessed via the RN pattern.
Add UUID version 7 generation function uuidv7() (Andrey Borodin) §
This UUID value is temporally sortable. Function alias uuidv4() has been added to explicitly generate version 4 UUIDs.
Add functions crc32() and crc32c() to compute CRC values (Aleksander Alekseev) §
Add math functions gamma() and lgamma() (Dean Rasheed) §
Allow => syntax for named cursor arguments in PL/pgSQL (Pavel Stehule) §
We previously only accepted :=.
Allow regexp_match[es]()/regexp_like()/regexp_replace()/regexp_count()/regexp_instr()/regexp_substr()/regexp_split_to_table()/regexp_split_to_array() to use named arguments (Jian He) §
Add function PQfullProtocolVersion() to report the full, including minor, protocol version number (Jacob Champion, Jelte Fennema-Nio) §
Add libpq connection parameters and environment variables to specify the minimum and maximum acceptable protocol version for connections (Jelte Fennema-Nio) § §
", "text": "Add libpq connection parameters and environment variables to specify the minimum and maximum acceptable protocol version for connections (Jelte Fennema-Nio) § §", "title": "Add libpq connection parameters and environment variables to specify the minimum and maximum acceptable protocol version for connections", "commits": ["285613c60", "507034910"], "section": "Libpq", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-LIBPQ", "source_hash": "dd8e24e0798022c5e49d33b8f037eae94f69ab39a4a885b8b176f5e16dbcf97e", "section_path": ["Libpq"], "commit_groups": [["285613c60"], ["507034910"]], "identity_text": "Add libpq connection parameters and environment variables to specify the minimum and maximum acceptable protocol version for connections (Jelte Fennema-Nio)", "commit_aliases": ["285613c60", "507034910"], "source_commits": ["285613c60", "507034910"], "source_entry_id": "18.0/changes/118", "db_id": "324ad8ffd0dc73072b6cae1163bbd895", "patch_ids": ["534b2c53e2e1a92c27d124b03e588165", "75729722b6f7aba5cfb305b2f8099d9d"], "statement_hash": "5bc66e57f7b5710b779499207adb20134778a80ccd962165684afde348719556", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-207d234a979be0ba", "cves": [], "html": "Report search_path changes to the client (Alexander Kukushkin, Jelte Fennema-Nio, Tomas Vondra) § §
", "text": "Report search_path changes to the client (Alexander Kukushkin, Jelte Fennema-Nio, Tomas Vondra) § §", "title": "Report search_path changes to the client", "commits": ["0d06a7eac", "28a1121fd"], "section": "Libpq", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-LIBPQ", "source_hash": "1b3b66fd3e804bfd9a8f8eb4900833f7becb2d7ae3e27f57d8450450272b7e24", "section_path": ["Libpq"], "commit_groups": [["0d06a7eac"], ["28a1121fd"]], "identity_text": "Report guc-search-path changes to the client (Alexander Kukushkin, Jelte Fennema-Nio, Tomas Vondra)", "commit_aliases": ["0d06a7eac", "28a1121fd"], "source_commits": ["0d06a7eac", "28a1121fd"], "source_entry_id": "18.0/changes/119", "db_id": "218352fe6746ce16b55b280a597a34c3", "patch_ids": ["5ff7e1b21d24cbfadde9ec259d6a73c7", "6773d35e5f3a311c7ff50c9c2faf3885"], "statement_hash": "50991c451a4bfb5e106b4ba60fe467da4d2e687a547ce099c82004fbe44fd3e9", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-beeeaad682b3e543", "cves": [], "html": "Add PQtrace() output for all message types, including authentication (Jelte Fennema-Nio) § § § § §
Add libpq connection parameter sslkeylogfile which dumps out SSL key material (Abhishek Chanda, Daniel Gustafsson) §
This is useful for debugging.
", "text": "Add libpq connection parameter sslkeylogfile which dumps out SSL key material (Abhishek Chanda, Daniel Gustafsson) § This is useful for debugging.", "title": "Add libpq connection parameter sslkeylogfile which dumps out SSL key material", "commits": ["2da74d8d6"], "section": "Libpq", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-LIBPQ", "source_hash": "8a53c283c907184c5c28dc8b1a80814c955c04574c96f11e2d4b6d6ad07852f9", "section_path": ["Libpq"], "commit_groups": [["2da74d8d6"]], "identity_text": "Add libpq connection parameter sslkeylogfile which dumps out SSL key material (Abhishek Chanda, Daniel Gustafsson) This is useful for debugging.", "commit_aliases": ["2da74d8d6"], "source_commits": ["2da74d8d6"], "source_entry_id": "18.0/changes/121", "db_id": "dec95e8329f62b657fc15ccfb7d006fb", "patch_ids": ["5c9abb135b2e6fb82671370102be25d3"], "statement_hash": "0cbbb246f331bdcf188172740da0fa02fe152d60204197e426ec23a6c89278c5", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-f56e310a693fee70", "cves": [], "html": "Modify some libpq function signatures to use int64_t (Thomas Munro) §
These previously used pg_int64, which is now deprecated.
Allow psql to parse, bind, and close named prepared statements (Anthonin Bonnefoy, Michael Paquier) § §
\nThis is accomplished with new commands \\parse, \\bind_named, and \\close_prepared.
Add psql backslash commands to allowing issuance of pipeline queries (Anthonin Bonnefoy) § § §
\nThe new commands are \\startpipeline, \\syncpipeline, \\sendpipeline, \\endpipeline, \\flushrequest, \\flush, and \\getresults.
Allow adding pipeline status to the psql prompt and add related state variables (Anthonin Bonnefoy) §
\nThe new prompt character is %P and the new psql variables are PIPELINE_SYNC_COUNT, PIPELINE_COMMAND_COUNT, and PIPELINE_RESULT_COUNT.
Allow adding the connection service name to the psql prompt or access it via psql variable (Michael Banck) §
", "text": "Allow adding the connection service name to the psql prompt or access it via psql variable (Michael Banck) §", "title": "Allow adding the connection service name to the psql prompt or access it via psql variable", "commits": ["477728b5d"], "section": "psql", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-PSQL", "source_hash": "d708d70528e3a3f746395fa23b8324b7dfe19e3fa2560f0d3fb61d86a8f4af8b", "section_path": ["psql"], "commit_groups": [["477728b5d"]], "identity_text": "Allow adding the connection service name to the psql prompt or access it via psql variable (Michael Banck)", "commit_aliases": ["477728b5d"], "source_commits": ["477728b5d"], "source_entry_id": "18.0/changes/126", "db_id": "b448890a42701668cc28db2c98fe65af", "patch_ids": ["8bc6eb53f480b1773dba3d9ca6fa27ef"], "statement_hash": "b7b84052ccad3b3cdd4e58fd81d7e92d01dcd30e03a638017f02df36fe51481c", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-b431886faffda5ff", "cves": [], "html": "Add psql option to use expanded mode on all list commands (Dean Rasheed) §
\nAdding backslash suffix x enables this.
Change psql's \\conninfo to use tabular format and include more information (Álvaro Herrera, Maiquel Grassi, Hunaid Sohail) §
Add function's leakproof indicator to psql's \\df+, \\do+, \\dAo+, and \\dC+ outputs (Yugo Nagata) §
Add access method details for partitioned relations in \\dP+ (Justin Pryzby) §
Add default_version to the psql \\dx extension output (Magnus Hagander) §
Add psql variable WATCH_INTERVAL to set the default \\watch wait time (Daniel Gustafsson) §
Change initdb to default to enabling checksums (Greg Sabino Mullane) § §
\nThe new initdb option --no-data-checksums disables checksums.
Add initdb option --no-sync-data-files to avoid syncing heap/index files (Nathan Bossart) §
initdb option --no-sync is still available to avoid syncing any files.
Add vacuumdb option --missing-stats-only to compute only missing optimizer statistics (Corey Huinker, Nathan Bossart) § §
This option can only be run by superusers and can only be used with options --analyze-only and --analyze-in-stages.
Add pg_combinebackup option -k/--link to enable hard linking (Israel Barth Rubio, Robert Haas) §
Only some files can be hard linked. This should not be used if the backups will be used independently.
", "text": "Add pg_combinebackup option -k/--link to enable hard linking (Israel Barth Rubio, Robert Haas) § Only some files can be hard linked. This should not be used if the backups will be used independently.", "title": "Add pg_combinebackup option -k/--link to enable hard linking", "commits": ["99aeb8470"], "section": "Server Applications", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SERVER-APPS", "source_hash": "eefef01cb696f44d91b49f7817d447e5f2b2aeac8ca97a0513d80a36ce3eab22", "section_path": ["Server Applications"], "commit_groups": [["99aeb8470"]], "identity_text": "Add app-pgcombinebackup option -k/--link to enable hard linking (Israel Barth Rubio, Robert Haas) Only some files can be hard linked. This should not be used if the backups will be used independently.", "commit_aliases": ["99aeb8470"], "source_commits": ["99aeb8470"], "source_entry_id": "18.0/changes/136", "db_id": "cbac9921cfb2186e54629d635e3729f3", "patch_ids": ["b2774e6278fb43524469fa415bf7c504"], "statement_hash": "5736af1019c3d5e2bd2ae443e4a9261637afca5e0e0ff655d599e24adaf4ea01", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-75fede038d668a8d", "cves": [], "html": "Allow pg_verifybackup to verify tar-format backups (Amul Sul) §
", "text": "Allow pg_verifybackup to verify tar-format backups (Amul Sul) §", "title": "Allow pg_verifybackup to verify tar-format backups", "commits": ["8dfd31290"], "section": "Server Applications", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SERVER-APPS", "source_hash": "e2b0d86a1a6fe34a3eaef7656a3093c8fef2bcf4bb4045b3b394c42b6e595297", "section_path": ["Server Applications"], "commit_groups": [["8dfd31290"]], "identity_text": "Allow app-pgverifybackup to verify tar-format backups (Amul Sul)", "commit_aliases": ["8dfd31290"], "source_commits": ["8dfd31290"], "source_entry_id": "18.0/changes/137", "db_id": "4a31265bb9d301899f61cbb72dc938fe", "patch_ids": ["f61db0ff36a5aaba1fefc4551593c41a"], "statement_hash": "033fcbd8882efc5f140f40a57fd1009957f6354e0fff3b3c07f05be1d2c1ce01", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-f775ed91253ae2a7", "cves": [], "html": "If pg_rewind's --source-server specifies a database name, use it in --write-recovery-conf output (Masahiko Sawada) §
Add pg_resetwal option --char-signedness to change the default char signedness (Masahiko Sawada) §
Add pg_dump option --statistics (Jeff Davis) § §
Add pg_dump and pg_dumpall option --sequence-data to dump sequence data that would normally be excluded (Nathan Bossart) § §
Add pg_dump, pg_dumpall, and pg_restore options --statistics-only, --no-statistics, --no-data, and --no-schema (Corey Huinker, Jeff Davis) §
Add option --no-policies to disable row level security policy processing in pg_dump, pg_dumpall, pg_restore (Nikolay Samokhvalov) §
This is useful for migrating to systems with different policies.
", "text": "Add option --no-policies to disable row level security policy processing in pg_dump, pg_dumpall, pg_restore (Nikolay Samokhvalov) § This is useful for migrating to systems with different policies.", "title": "Add option --no-policies to disable row level security policy processing in pg_dump, pg_dumpall, pg_restore", "commits": ["cd3c45125"], "section": "Server Applications / pg_dump/pg_dumpall/pg_restore", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-PGDUMP", "source_hash": "9231fdf3af2971c21ef9738044c6bf6fc9a4e82d61c155057f623aeacf8d1381", "section_path": ["Server Applications", "pg_dump/pg_dumpall/pg_restore"], "commit_groups": [["cd3c45125"]], "identity_text": "Add option --no-policies to disable row level security policy processing in app-pgdump , app-pg-dumpall , app-pgrestore (Nikolay Samokhvalov) This is useful for migrating to systems with different policies.", "commit_aliases": ["cd3c45125"], "source_commits": ["cd3c45125"], "source_entry_id": "18.0/changes/143", "db_id": "f65a09f6ed8414315ea3ab15d44b063d", "patch_ids": ["e8632c1f2c717fcff1a04211ab59a0c3"], "statement_hash": "c2544d757037ea2d9f0d54209afb5dfcd831c83b0fb375579be57d3ffb98b730", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-4b580bc4439297d2", "cves": [], "html": "Allow pg_upgrade to preserve optimizer statistics (Corey Huinker, Jeff Davis, Nathan Bossart) § § § §
\nExtended statistics are not preserved. Also add pg_upgrade option --no-statistics to disable statistics preservation.
Allow pg_upgrade to process database checks in parallel (Nathan Bossart) § § § § § § § § § § §
\nThis is controlled by the existing --jobs option.
Add pg_upgrade option --swap to swap directories rather than copy, clone, or link files (Nathan Bossart) §
This mode is potentially the fastest.
", "text": "Add pg_upgrade option --swap to swap directories rather than copy, clone, or link files (Nathan Bossart) § This mode is potentially the fastest.", "title": "Add pg_upgrade option --swap to swap directories rather than copy, clone, or link files", "commits": ["626d7236b"], "section": "Server Applications / pg_upgrade", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-PGUPGRADE", "source_hash": "5105f96fe345879f059f5dec740fcdf62c3fb86f637efc061ea65ff41062563f", "section_path": ["Server Applications", "pg_upgrade"], "commit_groups": [["626d7236b"]], "identity_text": "Add pg_upgrade option --swap to swap directories rather than copy, clone, or link files (Nathan Bossart) This mode is potentially the fastest.", "commit_aliases": ["626d7236b"], "source_commits": ["626d7236b"], "source_entry_id": "18.0/changes/146", "db_id": "f554eecffc9529fc8a7bf5df05f1ee48", "patch_ids": ["925b13034396ed82973d22527b295ac1"], "statement_hash": "446dc8dd0a3efeea98cbe5eef953503f703ba461702c2ad5d7041434781f351e", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-f19ad14633daaefd", "cves": [], "html": "Add pg_upgrade option --set-char-signedness to set the default char signedness of new cluster (Masahiko Sawada) § §
This is to handle cases where a pre-PostgreSQL 18 cluster's default CPU signedness does not match the new cluster.
", "text": "Add pg_upgrade option --set-char-signedness to set the default char signedness of new cluster (Masahiko Sawada) § § This is to handle cases where a pre-PostgreSQL 18 cluster's default CPU signedness does not match the new cluster.", "title": "Add pg_upgrade option --set-char-signedness to set the default char signedness of new cluster", "commits": ["1aab68059", "a8238f87f"], "section": "Server Applications / pg_upgrade", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-PGUPGRADE", "source_hash": "81fc7dfeaecc0c2acbed8c77a91318171c093256de3f1c6509e4ddb9b3506a2b", "section_path": ["Server Applications", "pg_upgrade"], "commit_groups": [["1aab68059"], ["a8238f87f"]], "identity_text": "Add pg_upgrade option --set-char-signedness to set the default char signedness of new cluster (Masahiko Sawada) This is to handle cases where a pre-PostgreSQL 18 cluster's default CPU signedness does not match the new cluster.", "commit_aliases": ["1aab68059", "a8238f87f"], "source_commits": ["1aab68059", "a8238f87f"], "source_entry_id": "18.0/changes/147", "db_id": "512ccd3d1bb4f010fe11b0eb637be55c", "patch_ids": ["85f2c26487e180e9e34c5a419dbbbf35", "b55f3df554d6f4f601f40f9bd71932dc"], "statement_hash": "5d736231626605165fd5a2523999bf34662259ec86505d0abb98425210873d2d", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-326132e0413a2af5", "cves": [], "html": "Add pg_createsubscriber option --all to create logical replicas for all databases (Shubham Khanna) §
Add pg_createsubscriber option --clean to remove publications (Shubham Khanna) § §
Add pg_createsubscriber option --enable-two-phase to enable prepared transactions (Shubham Khanna) §
Add pg_recvlogical option --enable-failover to specify failover slots (Hayato Kuroda) §
Also add option --enable-two-phase as a synonym for --two-phase, and deprecate the latter.
Allow pg_recvlogical --drop-slot to work without --dbname (Hayato Kuroda) §
Separate the loading and running of injection points (Michael Paquier, Heikki Linnakangas) § §
\nInjection points can now be created, but not run, via INJECTION_POINT_LOAD(), and such injection points can be run via INJECTION_POINT_CACHED().
Support runtime arguments in injection points (Michael Paquier) §
", "text": "Support runtime arguments in injection points (Michael Paquier) §", "title": "Support runtime arguments in injection points", "commits": ["371f2db8b"], "section": "Source Code", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SOURCE-CODE", "source_hash": "05301770ccd349689d8b69904a931228a96e0662899a3ade25f228442b6353fc", "section_path": ["Source Code"], "commit_groups": [["371f2db8b"]], "identity_text": "Support runtime arguments in injection points (Michael Paquier)", "commit_aliases": ["371f2db8b"], "source_commits": ["371f2db8b"], "source_entry_id": "18.0/changes/154", "db_id": "18e4ff23a56d78d29d6ae66814cb5956", "patch_ids": ["904e25b09a2067d4faafaee411020747"], "statement_hash": "5628295a828190147d169e94449983354f8ae8ff5a86e747e2323a9fafe55684", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-b8063b04940470a1", "cves": [], "html": "Allow inline injection point test code with IS_INJECTION_POINT_ATTACHED() (Heikki Linnakangas) §
Improve the performance of processing long JSON strings using SIMD (Single Instruction Multiple Data) (David Rowley) §
Speed up CRC32C calculations using x86 AVX-512 instructions (Raghuveer Devulapalli, Paul Amonson) §
", "text": "Speed up CRC32C calculations using x86 AVX-512 instructions (Raghuveer Devulapalli, Paul Amonson) §", "title": "Speed up CRC32C calculations using x86 AVX-512 instructions", "commits": ["3c6e8c123"], "section": "Source Code", "category": "performance", "source_url": "/docs/release/18.0/#RELEASE-18-SOURCE-CODE", "source_hash": "5c411d4b51c4b6be50ef868a21271a59e4a75118bd9ef67ecd94fe284fa402d6", "section_path": ["Source Code"], "commit_groups": [["3c6e8c123"]], "identity_text": "Speed up CRC32C calculations using x86 AVX-512 instructions (Raghuveer Devulapalli, Paul Amonson)", "commit_aliases": ["3c6e8c123"], "source_commits": ["3c6e8c123"], "source_entry_id": "18.0/changes/157", "db_id": "ecafb4a5cc6e92dddebe2ea023f597fc", "patch_ids": ["019ee0d01e78e91881714ff3219df19d"], "statement_hash": "9ebfb29bd90710429d9371df23815bf2b5a56103e50f8fd93d29218148000bd5", "relations": [], "version": "18.0", "category_label": "Performance", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-db83e36c1db3de67", "cves": [], "html": "Add ARM Neon and SVE CPU intrinsics for popcount (integer bit counting) (Chiranmoy Bhattacharya, Devanga Susmitha, Rama Malladi) § §
", "text": "Add ARM Neon and SVE CPU intrinsics for popcount (integer bit counting) (Chiranmoy Bhattacharya, Devanga Susmitha, Rama Malladi) § §", "title": "Add ARM Neon and SVE CPU intrinsics for popcount (integer bit counting)", "commits": ["519338ace", "6be53c276"], "section": "Source Code", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SOURCE-CODE", "source_hash": "09d6f13a948bcd90f3f3ac8e4018d0c533c115226c68a7db35a0bca2856dc813", "section_path": ["Source Code"], "commit_groups": [["519338ace"], ["6be53c276"]], "identity_text": "Add ARM Neon and SVE CPU intrinsics for popcount (integer bit counting) (Chiranmoy Bhattacharya, Devanga Susmitha, Rama Malladi)", "commit_aliases": ["519338ace", "6be53c276"], "source_commits": ["519338ace", "6be53c276"], "source_entry_id": "18.0/changes/158", "db_id": "e50b80ab8e5fdb402e0beb48a5db4bc9", "patch_ids": ["205916923c7dd75d0231c55476cd4c48", "fd2f2d7fbcf88e0449c66f9f417165fc"], "statement_hash": "ee09c22e85fe2068ac5f7492e13742c8aea22c6679a441f8015237ca7bdeeca7", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-ecae7587264d9281", "cves": [], "html": "Improve the speed of numeric multiplication and division (Joel Jacobson, Dean Rasheed) § § § §
", "text": "Improve the speed of numeric multiplication and division (Joel Jacobson, Dean Rasheed) § § § §", "title": "Improve the speed of numeric multiplication and division", "commits": ["8dc28d7eb", "9428c001f", "c4e44224c", "ca481d3c9"], "section": "Source Code", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SOURCE-CODE", "source_hash": "6edd099ca744adedc636a8415e8be30ad6220455ffa27ad1859cf8db0e9e45b0", "section_path": ["Source Code"], "commit_groups": [["8dc28d7eb"], ["9428c001f"], ["c4e44224c"], ["ca481d3c9"]], "identity_text": "Improve the speed of numeric multiplication and division (Joel Jacobson, Dean Rasheed)", "commit_aliases": ["8dc28d7eb", "9428c001f", "c4e44224c", "ca481d3c9"], "source_commits": ["8dc28d7eb", "9428c001f", "c4e44224c", "ca481d3c9"], "source_entry_id": "18.0/changes/159", "db_id": "a7dfad9e7ea9413b1f4feb4de2d8c632", "patch_ids": ["2f55166563d7d9ec64de99e0bf6e591a", "674fb4fd8062e095c5e8fbfa7beab186", "8d573b00acf40046627605c19414157d", "eb6faba6db5698c6310910540adef0d3"], "statement_hash": "8921ae4e40b001cd77fce579693d0a2e93ba934d8c04d74b261b43866655c114", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-fd7d506191195bf5", "cves": [], "html": "Add configure option --with-libnuma to enable NUMA awareness (Jakub Wartak, Bertrand Drouvot) § § §
The function pg_numa_available() reports on NUMA awareness, and system views pg_shmem_allocations_numa and pg_buffercache_numa which report on shared memory distribution across NUMA nodes.
Add TOAST table to pg_index to allow for very large expression indexes (Nathan Bossart) §
Remove column pg_attribute.attcacheoff (David Rowley) §
Add column pg_class.relallfrozen (Melanie Plageman) §
Add amgettreeheight, amconsistentequality, and amconsistentordering to the index access method API (Mark Dilger) § §
Add GiST support function stratnum() (Paul A. Jungwirth) §
Record the default CPU signedness of char in pg_controldata (Masahiko Sawada) §
Add support for Python \"Limited API\" in PL/Python (Peter Eisentraut) § §
\nThis helps prevent problems caused by Python 3.x version mismatches.
", "text": "Add support for Python \"Limited API\" in PL/Python (Peter Eisentraut) § § This helps prevent problems caused by Python 3.x version mismatches.", "title": "Add support for Python \"Limited API\" in PL/Python", "commits": ["0793ab810", "72a3d0462"], "section": "Source Code", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SOURCE-CODE", "source_hash": "f49def5963789b61e9e11e6b78ad16b391ce6657675eb5e12857c3d90c25063f", "section_path": ["Source Code"], "commit_groups": [["0793ab810"], ["72a3d0462"]], "identity_text": "Add support for Python \"Limited API\" in PL/Python (Peter Eisentraut) This helps prevent problems caused by Python 3.x version mismatches.", "commit_aliases": ["0793ab810", "72a3d0462"], "source_commits": ["0793ab810", "72a3d0462"], "source_entry_id": "18.0/changes/167", "db_id": "d9d289d7c17d30019901f5104438a9b5", "patch_ids": ["cbf73ec20c058f368547efbe37a75ed9", "d615c6575bcf9dabc148901891890deb"], "statement_hash": "bf3af05933e7d77673abcb674c13915120867f48aac15d60053f750a42d0d7d0", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-923b07e7289358ea", "cves": [], "html": "Change the minimum supported Python version to 3.6.8 (Jacob Champion) §
", "text": "Change the minimum supported Python version to 3.6.8 (Jacob Champion) §", "title": "Change the minimum supported Python version to 3.6.8", "commits": ["45363fca6"], "section": "Source Code", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SOURCE-CODE", "source_hash": "edfc0a822c1e6decb577eb651c059faf6285be5446a2ae201393b823c93a7b4a", "section_path": ["Source Code"], "commit_groups": [["45363fca6"]], "identity_text": "Change the minimum supported Python version to 3.6.8 (Jacob Champion)", "commit_aliases": ["45363fca6"], "source_commits": ["45363fca6"], "source_entry_id": "18.0/changes/168", "db_id": "3803d2204af4aafb31861db9c07294df", "patch_ids": ["d238a5c385201266bab1298ddc3d6937"], "statement_hash": "8e0582a6e94665c56a736b1daf82f2826837a955bf1ad3c8fed3ee41c1854b9b", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-c729ed080047e9a6", "cves": [], "html": "Remove support for OpenSSL versions older than 1.1.1 (Daniel Gustafsson) § §
", "text": "Remove support for OpenSSL versions older than 1.1.1 (Daniel Gustafsson) § §", "title": "Remove support for OpenSSL versions older than 1.1.1", "commits": ["6c66b7443", "a70e01d43"], "section": "Source Code", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SOURCE-CODE", "source_hash": "fef36e34b98c4cf8afc0e87fda7cd8014955b79b409cd798e1776f2cbb3cc19d", "section_path": ["Source Code"], "commit_groups": [["6c66b7443"], ["a70e01d43"]], "identity_text": "Remove support for OpenSSL versions older than 1.1.1 (Daniel Gustafsson)", "commit_aliases": ["6c66b7443", "a70e01d43"], "source_commits": ["6c66b7443", "a70e01d43"], "source_entry_id": "18.0/changes/169", "db_id": "48cbbe1a33f004fe33768f2881d5d92f", "patch_ids": ["abb2eed446c79007a20dabd90ec11e07", "e230f75c4521f002154fbc695ab93e0a"], "statement_hash": "c8e7dae9a85d85423b23da56e2d21b96b7f26438f93b7ac8c175a38b66b24100", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-48539960f4e6144e", "cves": [], "html": "If LLVM is enabled, require version 14 or later (Thomas Munro) §
", "text": "If LLVM is enabled, require version 14 or later (Thomas Munro) §", "title": "If LLVM is enabled, require version 14 or later", "commits": ["972c2cd28"], "section": "Source Code", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SOURCE-CODE", "source_hash": "312a91a833836d352538d85b42e2e70e2f3593c02b219f7e95f80da5e10bfaf4", "section_path": ["Source Code"], "commit_groups": [["972c2cd28"]], "identity_text": "If LLVM is enabled, require version 14 or later (Thomas Munro)", "commit_aliases": ["972c2cd28"], "source_commits": ["972c2cd28"], "source_entry_id": "18.0/changes/170", "db_id": "50c7a44be3192eea399751ed1200e8e8", "patch_ids": ["8a4ef85fef8148a0752a6381c6a739bb"], "statement_hash": "36fc6c5974c10ca846263ab84a10c91abb0ab4d1f95effb5f1513c71c37a4bbe", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-cc466a564036d579", "cves": [], "html": "Add macro PG_MODULE_MAGIC_EXT to allow extensions to report their name and version (Andrei Lepikhov) §
This information can be access via the new function pg_get_loaded_modules().
Document that SPI_connect()/SPI_connect_ext() always returns success (SPI_OK_CONNECT) (Stepan Neretin) §
Errors are always reported via ereport().
Add documentation section about API and ABI compatibility (David Wheeler, Peter Eisentraut) §
", "text": "Add documentation section about API and ABI compatibility (David Wheeler, Peter Eisentraut) §", "title": "Add documentation section about API and ABI compatibility", "commits": ["e54a42ac9"], "section": "Source Code", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SOURCE-CODE", "source_hash": "90c971529d419760d77397cb587a82b521c16886289aebdd0a9950e6910000f9", "section_path": ["Source Code"], "commit_groups": [["e54a42ac9"]], "identity_text": "Add documentation section about API and ABI compatibility (David Wheeler, Peter Eisentraut)", "commit_aliases": ["e54a42ac9"], "source_commits": ["e54a42ac9"], "source_entry_id": "18.0/changes/173", "db_id": "bce92895bdc4d2128762d0826b82afe5", "patch_ids": ["ed9bc344aa72386c8e767c718632ec82"], "statement_hash": "0295a4b203df0b9501cc58312ecd1041db9220faa5a8a3ae88d0fb981ee922f4", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-c62188fa02597863", "cves": [], "html": "Remove the experimental designation of Meson builds on Windows (Aleksander Alekseev) §
", "text": "Remove the experimental designation of Meson builds on Windows (Aleksander Alekseev) §", "title": "Remove the experimental designation of Meson builds on Windows", "commits": ["5afaba629"], "section": "Source Code", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SOURCE-CODE", "source_hash": "6fa8dda0e2cd9ac5555c784bf5c0ef8242c1206143e83bc3f734bc4ebaecdc2a", "section_path": ["Source Code"], "commit_groups": [["5afaba629"]], "identity_text": "Remove the experimental designation of Meson builds on Windows (Aleksander Alekseev)", "commit_aliases": ["5afaba629"], "source_commits": ["5afaba629"], "source_entry_id": "18.0/changes/174", "db_id": "65f45b8de45e88579fb3a07c1fc5ca82", "patch_ids": ["7f3733853ec88ef6dcc506c3f311ca02"], "statement_hash": "4b791d0ce6d561df0dc9266dbc1c032420c8b1a17d776165cd28778ec4824762", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-b529394c7414f821", "cves": [], "html": "Remove configure options --disable-spinlocks and --disable-atomics (Thomas Munro) § §
Thirty-two-bit atomic operations are now required.
", "text": "Remove configure options --disable-spinlocks and --disable-atomics (Thomas Munro) § § Thirty-two-bit atomic operations are now required.", "title": "Remove configure options --disable-spinlocks and --disable-atomics", "commits": ["813852613", "e25626677"], "section": "Source Code", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SOURCE-CODE", "source_hash": "dea8d45db1e65b97fa1c42d83d77ae1a21b44ff4bf947e134c0ae0c51fec84eb", "section_path": ["Source Code"], "commit_groups": [["813852613"], ["e25626677"]], "identity_text": "Remove configure options --disable-spinlocks and --disable-atomics (Thomas Munro) Thirty-two-bit atomic operations are now required.", "commit_aliases": ["813852613", "e25626677"], "source_commits": ["813852613", "e25626677"], "source_entry_id": "18.0/changes/175", "db_id": "cb76202d341bfde3157c7f5662fdca08", "patch_ids": ["1adba83a13269f9fe1796e4c938f5668", "c5a68b790cc12df3a522cd1c85e50f75"], "statement_hash": "f075e693a989fc62b94be60cc6414f54094d772e3fc9f2cc5a1a1beefdca9437", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-e16d84f131471052", "cves": [], "html": "Remove support for the HPPA/PA-RISC architecture (Tom Lane) §
", "text": "Remove support for the HPPA/PA-RISC architecture (Tom Lane) §", "title": "Remove support for the HPPA/PA-RISC architecture", "commits": ["edadeb071"], "section": "Source Code", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-SOURCE-CODE", "source_hash": "8f4d3cb0f0e25fcd326fb98621d0aefc3e51c019fd35d16cfdf8c01567fe96be", "section_path": ["Source Code"], "commit_groups": [["edadeb071"]], "identity_text": "Remove support for the HPPA/PA-RISC architecture (Tom Lane)", "commit_aliases": ["edadeb071"], "source_commits": ["edadeb071"], "source_entry_id": "18.0/changes/176", "db_id": "a167452f08dbddf1b2de4b6f87175253", "patch_ids": ["4c7fcd694e4cfcfdf4d2b66e07bcc93b"], "statement_hash": "34e0e62ec64cf13e242497f80e1704894b16ff8d2f43db397bcdbb5fd4d87a42", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-7290fc125f61d724", "cves": [], "html": "Add extension pg_logicalinspect to inspect logical snapshots (Bertrand Drouvot) §
", "text": "Add extension pg_logicalinspect to inspect logical snapshots (Bertrand Drouvot) §", "title": "Add extension pg_logicalinspect to inspect logical snapshots", "commits": ["7cdfeee32"], "section": "Additional Modules", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MODULES", "source_hash": "2687560225facdefa50011e45e121f7d2ba43f8c8dbd44cf574154afa1445beb", "section_path": ["Additional Modules"], "commit_groups": [["7cdfeee32"]], "identity_text": "Add extension pglogicalinspect to inspect logical snapshots (Bertrand Drouvot)", "commit_aliases": ["7cdfeee32"], "source_commits": ["7cdfeee32"], "source_entry_id": "18.0/changes/177", "db_id": "67c4f0ce87d750c9d1fc47621ad4ca18", "patch_ids": ["a7b197beccb692abf2aeb8c35a0a48a1"], "statement_hash": "aacda762c76e2c1fbfdaa69e9c927a9740a1692b0b61c349e5016a3c3b699a0a", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-b013c231e39d5be8", "cves": [], "html": "Add extension pg_overexplain which adds debug details to EXPLAIN output (Robert Haas) §
Add output columns to postgres_fdw_get_connections() (Hayato Kuroda, Sagar Dilip Shedge) § § § §
New output column used_in_xact indicates if the foreign data wrapper is being used by a current transaction, closed indicates if it is closed, user_name indicates the user name, and remote_backend_pid indicates the remote backend process identifier.
Allow SCRAM authentication from the client to be passed to postgres_fdw servers (Matheus Alcantara, Peter Eisentraut) §
\nThis avoids storing postgres_fdw authentication information in the database, and is enabled with the postgres_fdw use_scram_passthrough connection option. libpq uses new connection parameters scram_client_key and scram_server_key.
Allow SCRAM authentication from the client to be passed to dblink servers (Matheus Alcantara) §
", "text": "Allow SCRAM authentication from the client to be passed to dblink servers (Matheus Alcantara) §", "title": "Allow SCRAM authentication from the client to be passed to dblink servers", "commits": ["3642df265"], "section": "Additional Modules", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MODULES", "source_hash": "d5d459964678c5f8377c3bd875649fc44172ce4cb2a1b6401f0950b80fc6ba4a", "section_path": ["Additional Modules"], "commit_groups": [["3642df265"]], "identity_text": "Allow SCRAM authentication from the client to be passed to dblink servers (Matheus Alcantara)", "commit_aliases": ["3642df265"], "source_commits": ["3642df265"], "source_entry_id": "18.0/changes/181", "db_id": "db82382f896f8242594f26f0e98cd318", "patch_ids": ["071743b3a560980bed101b42da01a888"], "statement_hash": "606c662a7292efbe14169ab67273e036f3695f6e116ffb4735ab23da0a7f3415", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-be0a5c377c8ad1d6", "cves": [], "html": "Add on_error and log_verbosity options to file_fdw (Atsushi Torikoshi) §
These control how file_fdw handles and reports invalid file rows.
", "text": "Add on_error and log_verbosity options to file_fdw (Atsushi Torikoshi) § These control how file_fdw handles and reports invalid file rows.", "title": "Add on_error and log_verbosity options to file_fdw", "commits": ["a1c4c8a9e"], "section": "Additional Modules", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MODULES", "source_hash": "115a0c8a418b7106acd2734d853b844db562b082c4bda8f83428f4e298314284", "section_path": ["Additional Modules"], "commit_groups": [["a1c4c8a9e"]], "identity_text": "Add on_error and log_verbosity options to file-fdw (Atsushi Torikoshi) These control how file_fdw handles and reports invalid file rows.", "commit_aliases": ["a1c4c8a9e"], "source_commits": ["a1c4c8a9e"], "source_entry_id": "18.0/changes/182", "db_id": "6982b0c41f58b8ad05599dd36f57aaa9", "patch_ids": ["21992e0340c7459eca57bac98530eee3"], "statement_hash": "c5180a0af1dd4fdd3162754e1b488f348273f6c2f9209b82ebf3d374fabffd98", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-d073f00449dd1fe3", "cves": [], "html": "Add reject_limit to control the number of invalid rows file_fdw can ignore (Atsushi Torikoshi) §
This is active when ON_ERROR = 'ignore'.
Add configurable variable min_password_length to passwordcheck (Emanuele Musella, Maurizio Boriani) §
This controls the minimum password length.
", "text": "Add configurable variable min_password_length to passwordcheck (Emanuele Musella, Maurizio Boriani) § This controls the minimum password length.", "title": "Add configurable variable min_password_length to passwordcheck", "commits": ["f7e1b3828"], "section": "Additional Modules", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MODULES", "source_hash": "1b94e879146707658c8624a2cc1d0d5d51823ca6cec56d81901b4e94cb11b78c", "section_path": ["Additional Modules"], "commit_groups": [["f7e1b3828"]], "identity_text": "Add configurable variable min_password_length to passwordcheck (Emanuele Musella, Maurizio Boriani) This controls the minimum password length.", "commit_aliases": ["f7e1b3828"], "source_commits": ["f7e1b3828"], "source_entry_id": "18.0/changes/184", "db_id": "c2f3e4981e48c781d80d8d683bfeafdc", "patch_ids": ["8adca4662ef9e316e20e61eac39f5953"], "statement_hash": "3c96a08392c835400e1601043498429b0df9c4a3c6205b65fa827329a880c71d", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-ccb942ad8d145ac9", "cves": [], "html": "Have pgbench report the number of failed, retried, or skipped transactions in per-script reports (Yugo Nagata) §
", "text": "Have pgbench report the number of failed, retried, or skipped transactions in per-script reports (Yugo Nagata) §", "title": "Have pgbench report the number of failed, retried, or skipped transactions in per-script reports", "commits": ["cae0f3c40"], "section": "Additional Modules", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MODULES", "source_hash": "b6ab8471bd55acbc24e7b6d8e4dbc4490126311ba216112a2325d59926d09340", "section_path": ["Additional Modules"], "commit_groups": [["cae0f3c40"]], "identity_text": "Have pgbench report the number of failed, retried, or skipped transactions in per-script reports (Yugo Nagata)", "commit_aliases": ["cae0f3c40"], "source_commits": ["cae0f3c40"], "source_entry_id": "18.0/changes/185", "db_id": "7d68f2a4e71d87ab7e6b4494d5b3c176", "patch_ids": ["7ae9139da216927d66da497ea952bf95"], "statement_hash": "18f1805b3f36c44aa22e9a7c871bfc854cae06d2d1ba7d54f1c9ef8c03dabac0", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-6929095b04fe5b40", "cves": [], "html": "Add isn server variable weak to control invalid check digit acceptance (Viktor Holmberg) §
This was previously only controlled by function isn_weak().
Allow values to be sorted to speed btree_gist index builds (Bernd Helmle, Andrey Borodin) §
", "text": "Allow values to be sorted to speed btree_gist index builds (Bernd Helmle, Andrey Borodin) §", "title": "Allow values to be sorted to speed btree_gist index builds", "commits": ["e4309f73f"], "section": "Additional Modules", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MODULES", "source_hash": "212669f707e1fce095f4a15af5bba9c3db22d8a44760a389af1d2d2f668d8dde", "section_path": ["Additional Modules"], "commit_groups": [["e4309f73f"]], "identity_text": "Allow values to be sorted to speed btree-gist index builds (Bernd Helmle, Andrey Borodin)", "commit_aliases": ["e4309f73f"], "source_commits": ["e4309f73f"], "source_entry_id": "18.0/changes/187", "db_id": "7e911d1361965be0a82fa600d4ebef9d", "patch_ids": ["cffdd969af417cd314b82e92cb6a914f"], "statement_hash": "cebec6909a36bdf2166bf54e64bff4c820d6b198d1e688f1c4007e765cf72614", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-d35d4aa1899363aa", "cves": [], "html": "Add amcheck check function gin_index_check() to verify GIN indexes (Grigory Kryachko, Heikki Linnakangas, Andrey Borodin) §
Add functions pg_buffercache_evict_relation() and pg_buffercache_evict_all() to evict unpinned shared buffers (Nazir Bilal Yavuz) §
The existing function pg_buffercache_evict() now returns the buffer flush status.
Allow extensions to install custom EXPLAIN options (Robert Haas, Sami Imseih) § § §
", "text": "Allow extensions to install custom EXPLAIN options (Robert Haas, Sami Imseih) § § §", "title": "Allow extensions to install custom EXPLAIN options", "commits": ["4fd02bf7c", "50ba65e73", "c65bc2e1d"], "section": "Additional Modules", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MODULES", "source_hash": "126c1e252fd401d5cbcf8667b52299d2f5510b10142a7ea6310dcbba82c8bd12", "section_path": ["Additional Modules"], "commit_groups": [["4fd02bf7c"], ["50ba65e73"], ["c65bc2e1d"]], "identity_text": "Allow extensions to install custom sql-explain options (Robert Haas, Sami Imseih)", "commit_aliases": ["4fd02bf7c", "50ba65e73", "c65bc2e1d"], "source_commits": ["4fd02bf7c", "50ba65e73", "c65bc2e1d"], "source_entry_id": "18.0/changes/190", "db_id": "17128679b68e62fcef0d48d266afb493", "patch_ids": ["4a90cb7809dd3268e814052cb9d568f6", "a7446b42cbf558abedd81726ef25be11", "b1d23fea200234c95397b7e93fd14848"], "statement_hash": "e8646573cbbb7286af9b4ad50cc583bc6310d49c513b0e947a6bca0270e16301", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-72dccadf752b71eb", "cves": [], "html": "Allow extensions to use the server's cumulative statistics API (Michael Paquier) § §
", "text": "Allow extensions to use the server's cumulative statistics API (Michael Paquier) § §", "title": "Allow extensions to use the server's cumulative statistics API", "commits": ["2eff9e678", "7949d9594"], "section": "Additional Modules", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-MODULES", "source_hash": "7611ce1609aa627ae59449ba16bf0a6a11d238cb4b3f48d277fa6399e2615ef5", "section_path": ["Additional Modules"], "commit_groups": [["2eff9e678"], ["7949d9594"]], "identity_text": "Allow extensions to use the server's cumulative statistics API (Michael Paquier)", "commit_aliases": ["2eff9e678", "7949d9594"], "source_commits": ["2eff9e678", "7949d9594"], "source_entry_id": "18.0/changes/191", "db_id": "51ed37dd51200e7f7a59592baf05f997", "patch_ids": ["3eb79f54769a802749d52f97f9f8c4cd", "4af802e5801cb1008a49bbd7ffb1b4c6"], "statement_hash": "a6e76441b49e4dfc8c5b6323c846f1efe63f20730e0cc0450e6f197b1eb9b2a0", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-f9d180ce3867ba06", "cves": [], "html": "Allow the queries of CREATE TABLE AS and DECLARE to be tracked by pg_stat_statements (Anthonin Bonnefoy) §
\nThey are also now assigned query ids.
", "text": "Allow the queries of CREATE TABLE AS and DECLARE to be tracked by pg_stat_statements (Anthonin Bonnefoy) § They are also now assigned query ids.", "title": "Allow the queries of CREATE TABLE AS and DECLARE to be tracked by pg_stat_statements", "commits": ["6b652e6ce"], "section": "Additional Modules / pg_stat_statements", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-PGSTATSTATEMENTS", "source_hash": "a71330cbf6ff1fcbcb3577f9497064f4234185cd87242388194c557aabf1ba1b", "section_path": ["Additional Modules", "pg_stat_statements"], "commit_groups": [["6b652e6ce"]], "identity_text": "Allow the queries of sql-createtableas and sql-declare to be tracked by pg_stat_statements (Anthonin Bonnefoy) They are also now assigned query ids.", "commit_aliases": ["6b652e6ce"], "source_commits": ["6b652e6ce"], "source_entry_id": "18.0/changes/192", "db_id": "222e3bfb3e07da2a4bb138e9b89a9ea9", "patch_ids": ["6f27bba477d5d34ec287e6d1f0cb4c01"], "statement_hash": "529743a734ea4d3d2e0ab03ec1c2bc3a516f21292fd3896db229b7e1ee80bdfd", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-9feb714b6e408a34", "cves": [], "html": "Allow the parameterization of SET values in pg_stat_statements (Greg Sabino Mullane, Michael Paquier) §
\nThis reduces the bloat caused by SET statements with differing constants.
Add pg_stat_statements columns to report parallel activity (Guillaume Lelarge) §
The new columns are parallel_workers_to_launch and parallel_workers_launched.
Add pg_stat_statements.wal_buffers_full to report full WAL buffers (Bertrand Drouvot) §
Add pgcrypto algorithms sha256crypt and sha512crypt (Bernd Helmle) §
Add CFB mode to pgcrypto encryption and decryption (Umar Hayat) §
", "text": "Add CFB mode to pgcrypto encryption and decryption (Umar Hayat) §", "title": "Add CFB mode to pgcrypto encryption and decryption", "commits": ["9ad1b3d01"], "section": "Additional Modules / pgcrypto", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-PGCRYPTO", "source_hash": "7f5b08debbba5d1cc71560caa889a862bb5b8108f756e758ad8bc02d4921180a", "section_path": ["Additional Modules", "pgcrypto"], "commit_groups": [["9ad1b3d01"]], "identity_text": "Add CFB mode to pgcrypto encryption and decryption (Umar Hayat)", "commit_aliases": ["9ad1b3d01"], "source_commits": ["9ad1b3d01"], "source_entry_id": "18.0/changes/197", "db_id": "ec341ecdfcaabcd1827eb401ea40905d", "patch_ids": ["b040d33a3888055fc5edf9f0c6e56795"], "statement_hash": "7c89f9937951f96c3f497c06864857f8e8c21ba76f5ef791d1eed77d00a71e81", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}, {"id": "18.0-e6ffde3f90c7ca5a", "cves": [], "html": "Add function fips_mode() to report the server's FIPS mode (Daniel Gustafsson) §
Add pgcrypto server variable builtin_crypto_enabled to allow disabling builtin non-FIPS mode cryptographic functions (Daniel Gustafsson, Joe Conway) §
This is useful for guaranteeing FIPS mode behavior.
", "text": "Add pgcrypto server variable builtin_crypto_enabled to allow disabling builtin non-FIPS mode cryptographic functions (Daniel Gustafsson, Joe Conway) § This is useful for guaranteeing FIPS mode behavior.", "title": "Add pgcrypto server variable builtin_crypto_enabled to allow disabling builtin non-FIPS mode cryptographic functions", "commits": ["035f99cbe"], "section": "Additional Modules / pgcrypto", "category": "feature", "source_url": "/docs/release/18.0/#RELEASE-18-PGCRYPTO", "source_hash": "7ec37d9ad093c24c937b540278b9a28ded5495aa79ee7e13b25b399ad32123f6", "section_path": ["Additional Modules", "pgcrypto"], "commit_groups": [["035f99cbe"]], "identity_text": "Add pgcrypto server variable builtin_crypto_enabled to allow disabling builtin non-FIPS mode cryptographic functions (Daniel Gustafsson, Joe Conway) This is useful for guaranteeing FIPS mode behavior.", "commit_aliases": ["035f99cbe"], "source_commits": ["035f99cbe"], "source_entry_id": "18.0/changes/199", "db_id": "85292659fb670a2d9202838e30370170", "patch_ids": ["c996d7a6dfbb6918d1e1c1bdc8763d5d"], "statement_hash": "9c517ea3b0ae09d9ac23588dcc459bf5530faea31bee9ef47a11255f44c8ee81", "relations": [], "version": "18.0", "category_label": "Features", "also_in": [], "variants": [], "related_changes": []}]}], "stats": [{"key": "all", "label": "All changes", "count": 297}, {"key": "feature", "label": "Features", "count": 188}, {"key": "bugfix", "label": "Bug fixes", "count": 49}, {"key": "security", "label": "Security", "count": 3}, {"key": "performance", "label": "Performance", "count": 10}, {"key": "compatibility", "label": "Compatibility", "count": 11}, {"key": "improvement", "label": "Improvements", "count": 36}], "total": 297, "cve_count": 0, "cves": [], "cve_available": true, "security_regressions": [], "remaining_cves": [], "cross_major": true, "excluded_count": 264, "already_in_source_count": 264, "duplicate_count": 0, "candidate_count": 561, "exclusions": [{"id": "18.1-45bd7bfaea1c1e6c", "source_entry_id": "18.1/changes/001", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Check for CREATE privileges on the schema in CREATE STATISTICS", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-36aab10e5138d3d1", "source_entry_id": "17.7/changes/001", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Check for CREATE privileges on the schema in CREATE STATISTICS"}], "entry": {"id": "18.1-45bd7bfaea1c1e6c", "cves": ["CVE-2025-12817"], "html": "Check for CREATE privileges on the schema in CREATE STATISTICS (Jelte Fennema-Nio) §
This omission allowed table owners to create statistics in any schema, potentially leading to unexpected naming conflicts.
\nThe PostgreSQL Project thanks Jelte Fennema-Nio for reporting this problem. (CVE-2025-12817)
", "text": "Check for CREATE privileges on the schema in CREATE STATISTICS (Jelte Fennema-Nio) § This omission allowed table owners to create statistics in any schema, potentially leading to unexpected naming conflicts. The PostgreSQL Project thanks Jelte Fennema-Nio for reporting this problem. (CVE-2025-12817)", "title": "Check for CREATE privileges on the schema in CREATE STATISTICS", "commits": ["00eb646ea"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "7c9fc98fd26352f2c8df8d62ef124c4a11c97ac338af1e68ad9300d406affc69", "section_path": ["Changes"], "commit_groups": [["00eb646ea", "2393d374a", "5e4fcbe53", "8a2530ebc", "95cce5669", "d20abb587", "e2fb3dfa8"]], "identity_text": "Check for CREATE privileges on the schema in CREATE STATISTICS (Jelte Fennema-Nio) This omission allowed table owners to create statistics in any schema, potentially leading to unexpected naming conflicts. The PostgreSQL Project thanks Jelte Fennema-Nio for reporting this problem. (CVE-2025-12817)", "commit_aliases": ["00eb646ea", "2393d374a", "5e4fcbe53", "8a2530ebc", "95cce5669", "d20abb587", "e2fb3dfa8"], "source_commits": ["00eb646ea"], "source_entry_id": "18.1/changes/001", "db_id": "0b1db4254a2e3444434b0ca4004ea84b", "patch_ids": ["99e1ddd8be3f2e70a07b173bce56eec6"], "statement_hash": "2fdab1083a50be24b1dca00ede9ffd5906a617c6df360497714a885f6ff9f704", "relations": [{"rule": 2, "type": "equivalent", "target": "3aabd99e8b497ed573a9c3988472f89b", "evidence": {"same_day": true, "patch_ids": ["99e1ddd8be3f2e70a07b173bce56eec6"], "statement_hash": "2fdab1083a50be24b1dca00ede9ffd5906a617c6df360497714a885f6ff9f704"}}, {"rule": 2, "type": "equivalent", "target": "5434410099d24e095f2f3662e9b084be", "evidence": {"same_day": true, "patch_ids": ["99e1ddd8be3f2e70a07b173bce56eec6"], "statement_hash": "2fdab1083a50be24b1dca00ede9ffd5906a617c6df360497714a885f6ff9f704"}}, {"rule": 2, "type": "equivalent", "target": "6167ff71ba63659939df7295a1784bd5", "evidence": {"same_day": true, "patch_ids": ["99e1ddd8be3f2e70a07b173bce56eec6"], "statement_hash": "2fdab1083a50be24b1dca00ede9ffd5906a617c6df360497714a885f6ff9f704"}}, {"rule": 2, "type": "equivalent", "target": "7a542e168dfd911c88c2817105ab4eb1", "evidence": {"same_day": true, "patch_ids": ["99e1ddd8be3f2e70a07b173bce56eec6"], "statement_hash": "2fdab1083a50be24b1dca00ede9ffd5906a617c6df360497714a885f6ff9f704"}}, {"rule": 2, "type": "equivalent", "target": "fc4febff3c2281775597453f96dfd148", "evidence": {"same_day": true, "patch_ids": ["99e1ddd8be3f2e70a07b173bce56eec6"], "statement_hash": "2fdab1083a50be24b1dca00ede9ffd5906a617c6df360497714a885f6ff9f704"}}]}}, {"id": "18.1-3a4a5ae84a44ca49", "source_entry_id": "18.1/changes/002", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Avoid integer overflow in allocation-size calculations within libpq", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-a326b8fad6479f02", "source_entry_id": "17.7/changes/002", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Avoid integer overflow in allocation-size calculations within libpq"}], "entry": {"id": "18.1-3a4a5ae84a44ca49", "cves": ["CVE-2025-12818"], "html": "Avoid integer overflow in allocation-size calculations within libpq (Jacob Champion) §
\nSeveral places in libpq were not sufficiently careful about computing the required size of a memory allocation. Sufficiently large inputs could cause integer overflow, resulting in an undersized buffer, which would then lead to writing past the end of the buffer.
\nThe PostgreSQL Project thanks Aleksey Solovev of Positive Technologies for reporting this problem. (CVE-2025-12818)
", "text": "Avoid integer overflow in allocation-size calculations within libpq (Jacob Champion) § Several places in libpq were not sufficiently careful about computing the required size of a memory allocation. Sufficiently large inputs could cause integer overflow, resulting in an undersized buffer, which would then lead to writing past the end of the buffer. The PostgreSQL Project thanks Aleksey Solovev of Positive Technologies for reporting this problem. (CVE-2025-12818)", "title": "Avoid integer overflow in allocation-size calculations within libpq", "commits": ["7eb8fcad8"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "b45871c637865cee86198fd246cd8aabd5edf5df7efc227adeb36544fb4819da", "section_path": ["Changes"], "commit_groups": [["585fd9b3c", "600086f47", "7eb8fcad8", "91421565f", "96d2c7e96", "d6f0c0d6d", "f5999f018"]], "identity_text": "Avoid integer overflow in allocation-size calculations within libpq (Jacob Champion) Several places in libpq were not sufficiently careful about computing the required size of a memory allocation. Sufficiently large inputs could cause integer overflow, resulting in an undersized buffer, which would then lead to writing past the end of the buffer. The PostgreSQL Project thanks Aleksey Solovev of Positive Technologies for reporting this problem. (CVE-2025-12818)", "commit_aliases": ["585fd9b3c", "600086f47", "7eb8fcad8", "91421565f", "96d2c7e96", "d6f0c0d6d", "f5999f018"], "source_commits": ["7eb8fcad8"], "source_entry_id": "18.1/changes/002", "db_id": "c53264df3df1081cfca59daebb417ae4", "patch_ids": ["16e4d7f7cb99380bcadbeb1a4c45eac4"], "statement_hash": "42e2acf7dbacc3d12e55dc8cc3dc23c6a2afed82c46ae3bf37cba022acdca1bb", "relations": [{"rule": 2, "type": "equivalent", "target": "10c3ef25a629d41429d514190a9f5584", "evidence": {"same_day": true, "patch_ids": ["16e4d7f7cb99380bcadbeb1a4c45eac4"], "statement_hash": "42e2acf7dbacc3d12e55dc8cc3dc23c6a2afed82c46ae3bf37cba022acdca1bb"}}, {"rule": 2, "type": "equivalent", "target": "1f91b721b071de697f740c95cd556a9e", "evidence": {"same_day": true, "patch_ids": ["16e4d7f7cb99380bcadbeb1a4c45eac4"], "statement_hash": "42e2acf7dbacc3d12e55dc8cc3dc23c6a2afed82c46ae3bf37cba022acdca1bb"}}, {"rule": 2, "type": "equivalent", "target": "601fa44b8aa3f725f41f2320ba9cf51b", "evidence": {"same_day": true, "patch_ids": ["16e4d7f7cb99380bcadbeb1a4c45eac4"], "statement_hash": "42e2acf7dbacc3d12e55dc8cc3dc23c6a2afed82c46ae3bf37cba022acdca1bb"}}, {"rule": 2, "type": "equivalent", "target": "9b1eafd982ad52573adf6f2d6ae70703", "evidence": {"same_day": true, "patch_ids": ["16e4d7f7cb99380bcadbeb1a4c45eac4"], "statement_hash": "42e2acf7dbacc3d12e55dc8cc3dc23c6a2afed82c46ae3bf37cba022acdca1bb"}}, {"rule": 2, "type": "equivalent", "target": "cf7417da3f5aaff52ed6398652b5cefb", "evidence": {"same_day": true, "patch_ids": ["16e4d7f7cb99380bcadbeb1a4c45eac4"], "statement_hash": "42e2acf7dbacc3d12e55dc8cc3dc23c6a2afed82c46ae3bf37cba022acdca1bb"}}]}}, {"id": "18.1-b921a1ea6f2b8ead", "source_entry_id": "18.1/changes/003", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Prevent “unrecognized node type” errors when a SQL/JSON function such as JSON_VALUE has a DEFAULT clause containing a COLLATE expression", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-7345a25f928001c5", "source_entry_id": "17.7/changes/003", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Prevent “unrecognized node type” errors when a SQL/JSON function such as JSON_VALUE has a DEFAULT clause containing a COLLATE expression"}], "entry": {"id": "18.1-b921a1ea6f2b8ead", "cves": [], "html": "Prevent “unrecognized node type” errors when a SQL/JSON function such as JSON_VALUE has a DEFAULT clause containing a COLLATE expression (Jian He) § §
Remove faulty assertion in btree index cleanup (Peter Geoghegan) §
", "text": "Remove faulty assertion in btree index cleanup (Peter Geoghegan) §", "title": "Remove faulty assertion in btree index cleanup", "commits": ["61de81a49"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "59bedcdf0405a0fdb81cbd2d57d7e60036379d06f239428467ffd59ad5ee4756", "section_path": ["Changes"], "commit_groups": [["314004021", "61de81a49", "843e50208", "ae15cebc2", "af302ff6b", "c160fd469", "ca0c93908"]], "identity_text": "Remove faulty assertion in btree index cleanup (Peter Geoghegan)", "commit_aliases": ["314004021", "61de81a49", "843e50208", "ae15cebc2", "af302ff6b", "c160fd469", "ca0c93908"], "source_commits": ["61de81a49"], "source_entry_id": "18.1/changes/008", "db_id": "1a0e9b151c18103e9e44e0d5b065435e", "patch_ids": ["37c608f60096a634457e03ef403861d6"], "statement_hash": "10a7d45ffeb0f11200d10e8732198f5dd91b4ea27bc91850c29a64cd2e8239a1", "relations": [{"rule": 2, "type": "equivalent", "target": "0a57a548c4b77cd7d910727d3c65b3a6", "evidence": {"same_day": true, "patch_ids": ["37c608f60096a634457e03ef403861d6"], "statement_hash": "10a7d45ffeb0f11200d10e8732198f5dd91b4ea27bc91850c29a64cd2e8239a1"}}, {"rule": 2, "type": "equivalent", "target": "3933929e20ae66e9831bcbabb992d203", "evidence": {"same_day": true, "patch_ids": ["37c608f60096a634457e03ef403861d6"], "statement_hash": "10a7d45ffeb0f11200d10e8732198f5dd91b4ea27bc91850c29a64cd2e8239a1"}}, {"rule": 2, "type": "equivalent", "target": "444038cce9bb99031a082f8098e1be72", "evidence": {"same_day": true, "patch_ids": ["37c608f60096a634457e03ef403861d6"], "statement_hash": "10a7d45ffeb0f11200d10e8732198f5dd91b4ea27bc91850c29a64cd2e8239a1"}}, {"rule": 2, "type": "equivalent", "target": "488141078c6f2db091ee11544337a811", "evidence": {"same_day": true, "patch_ids": ["37c608f60096a634457e03ef403861d6"], "statement_hash": "10a7d45ffeb0f11200d10e8732198f5dd91b4ea27bc91850c29a64cd2e8239a1"}}, {"rule": 2, "type": "equivalent", "target": "9e457bb041db2cbeaeaf7995dafca323", "evidence": {"same_day": true, "patch_ids": ["37c608f60096a634457e03ef403861d6"], "statement_hash": "10a7d45ffeb0f11200d10e8732198f5dd91b4ea27bc91850c29a64cd2e8239a1"}}]}}, {"id": "18.1-a00fe3bcec296ab2", "source_entry_id": "18.1/changes/010", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Ensure that BRIN autosummarization provides a snapshot for index expressions that need one", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-a8f10736234e0b39", "source_entry_id": "17.7/changes/012", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Ensure that BRIN autosummarization provides a snapshot for index expressions that need one"}], "entry": {"id": "18.1-a00fe3bcec296ab2", "cves": [], "html": "Ensure that BRIN autosummarization provides a snapshot for index expressions that need one (Álvaro Herrera) § §
\nPreviously, autosummarization would fail for such indexes, and then leave placeholder index tuples behind, causing the index to bloat over time.
", "text": "Ensure that BRIN autosummarization provides a snapshot for index expressions that need one (Álvaro Herrera) § § Previously, autosummarization would fail for such indexes, and then leave placeholder index tuples behind, causing the index to bloat over time.", "title": "Ensure that BRIN autosummarization provides a snapshot for index expressions that need one", "commits": ["419ffde23", "8733f0b54"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "72084de464215059c3d1b5ad06a481c8d136be1b10eac24c155283ac177e3095", "section_path": ["Changes"], "commit_groups": [["0a3d27bfe", "20442cf50", "3b5007347", "65b0d1f74", "8733f0b54", "bcfbd3f74", "ef81697fe"], ["23ddadf68", "3c7b47974", "419ffde23", "6ef33c805", "a95e3d84c", "f0ad41716", "f4b68b033"]], "identity_text": "Ensure that BRIN autosummarization provides a snapshot for index expressions that need one (Álvaro Herrera) Previously, autosummarization would fail for such indexes, and then leave placeholder index tuples behind, causing the index to bloat over time.", "commit_aliases": ["0a3d27bfe", "20442cf50", "23ddadf68", "3b5007347", "3c7b47974", "419ffde23", "65b0d1f74", "6ef33c805", "8733f0b54", "a95e3d84c", "bcfbd3f74", "ef81697fe", "f0ad41716", "f4b68b033"], "source_commits": ["419ffde23", "8733f0b54"], "source_entry_id": "18.1/changes/010", "db_id": "5e3ad415c950ddc874e527c528e4312f", "patch_ids": ["31ad60583179a46f035e6ca49acb5df0", "3fdff7630c20c4073bba1b6676191274"], "statement_hash": "62e341cf9b11ac9a64fec02e85a546e8c1574a3998b12b548653d69ab6270585", "relations": [{"rule": 2, "type": "equivalent", "target": "0cb94d7b769fa6011ab24dd8d4a5182f", "evidence": {"same_day": true, "patch_ids": ["31ad60583179a46f035e6ca49acb5df0", "3fdff7630c20c4073bba1b6676191274"], "statement_hash": "62e341cf9b11ac9a64fec02e85a546e8c1574a3998b12b548653d69ab6270585"}}, {"rule": 2, "type": "equivalent", "target": "0dd09cb0d2d5f7d388110d5f734dee23", "evidence": {"same_day": true, "patch_ids": ["31ad60583179a46f035e6ca49acb5df0", "3fdff7630c20c4073bba1b6676191274"], "statement_hash": "62e341cf9b11ac9a64fec02e85a546e8c1574a3998b12b548653d69ab6270585"}}, {"rule": 2, "type": "equivalent", "target": "3e8741d3d489044f4c55886a02fd1ca6", "evidence": {"same_day": true, "patch_ids": ["31ad60583179a46f035e6ca49acb5df0", "3fdff7630c20c4073bba1b6676191274"], "statement_hash": "62e341cf9b11ac9a64fec02e85a546e8c1574a3998b12b548653d69ab6270585"}}, {"rule": 2, "type": "equivalent", "target": "721aeb1deeff7de3e90db706f730ab11", "evidence": {"same_day": true, "patch_ids": ["31ad60583179a46f035e6ca49acb5df0", "3fdff7630c20c4073bba1b6676191274"], "statement_hash": "62e341cf9b11ac9a64fec02e85a546e8c1574a3998b12b548653d69ab6270585"}}, {"rule": 2, "type": "equivalent", "target": "7f0361a52a096ffc5b14904781aeb0bc", "evidence": {"same_day": true, "patch_ids": ["31ad60583179a46f035e6ca49acb5df0", "3fdff7630c20c4073bba1b6676191274"], "statement_hash": "62e341cf9b11ac9a64fec02e85a546e8c1574a3998b12b548653d69ab6270585"}}]}}, {"id": "18.1-4d75a8abffa08925", "source_entry_id": "18.1/changes/011", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix integer-overflow hazard in BRIN index scans when the table contains close to 232 pages", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-22b81d2b7991be50", "source_entry_id": "17.7/changes/013", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix integer-overflow hazard in BRIN index scans when the table contains close to 232 pages"}], "entry": {"id": "18.1-4d75a8abffa08925", "cves": [], "html": "Fix integer-overflow hazard in BRIN index scans when the table contains close to 232 pages (Sunil S) §
\nThis oversight could result in an infinite loop or scanning of unneeded table pages.
", "text": "Fix integer-overflow hazard in BRIN index scans when the table contains close to 232 pages (Sunil S) § This oversight could result in an infinite loop or scanning of unneeded table pages.", "title": "Fix integer-overflow hazard in BRIN index scans when the table contains close to 232 pages", "commits": ["715983a81"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "a227f200daffb8d9736fdb106e7db525288805f9d039e2aed7b51c500b5e9285", "section_path": ["Changes"], "commit_groups": [["715983a81", "810aaf7f2", "9fd29d7ff", "c28f8ca29", "c4f5a59ab", "eea24eb0a", "ef915bf93"]], "identity_text": "Fix integer-overflow hazard in BRIN index scans when the table contains close to 232 pages (Sunil S) This oversight could result in an infinite loop or scanning of unneeded table pages.", "commit_aliases": ["715983a81", "810aaf7f2", "9fd29d7ff", "c28f8ca29", "c4f5a59ab", "eea24eb0a", "ef915bf93"], "source_commits": ["715983a81"], "source_entry_id": "18.1/changes/011", "db_id": "393a9b7eb2a54302a3bd8b2790808ca8", "patch_ids": ["e15f4df722672d015993ea819e9c3351"], "statement_hash": "45088b42382a6f8a5eb8dc651e95a4c956a04e585cd53f0e8247416c8d6fce3f", "relations": [{"rule": 2, "type": "equivalent", "target": "3eee9fbd93044d08fe7b761285b4eef0", "evidence": {"same_day": true, "patch_ids": ["e15f4df722672d015993ea819e9c3351"], "statement_hash": "45088b42382a6f8a5eb8dc651e95a4c956a04e585cd53f0e8247416c8d6fce3f"}}, {"rule": 2, "type": "equivalent", "target": "41c5c1173ef259c7bb96b3467e9de919", "evidence": {"same_day": true, "patch_ids": ["e15f4df722672d015993ea819e9c3351"], "statement_hash": "45088b42382a6f8a5eb8dc651e95a4c956a04e585cd53f0e8247416c8d6fce3f"}}, {"rule": 2, "type": "equivalent", "target": "c0b6100e40d8b770ece9bacc3084ea91", "evidence": {"same_day": true, "patch_ids": ["e15f4df722672d015993ea819e9c3351"], "statement_hash": "45088b42382a6f8a5eb8dc651e95a4c956a04e585cd53f0e8247416c8d6fce3f"}}, {"rule": 2, "type": "equivalent", "target": "ca0d04f29eca7d84d81b300dc4107221", "evidence": {"same_day": true, "patch_ids": ["e15f4df722672d015993ea819e9c3351"], "statement_hash": "45088b42382a6f8a5eb8dc651e95a4c956a04e585cd53f0e8247416c8d6fce3f"}}, {"rule": 2, "type": "equivalent", "target": "cbb0ef9e07e346b9959c4a482b828973", "evidence": {"same_day": true, "patch_ids": ["e15f4df722672d015993ea819e9c3351"], "statement_hash": "45088b42382a6f8a5eb8dc651e95a4c956a04e585cd53f0e8247416c8d6fce3f"}}]}}, {"id": "18.1-d78511e9b384a86b", "source_entry_id": "18.1/changes/012", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix incorrect zero-extension of stored values in JIT-generated tuple deforming code", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-aa1a9b53c515db45", "source_entry_id": "17.7/changes/014", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix incorrect zero-extension of stored values in JIT-generated tuple deforming code"}], "entry": {"id": "18.1-d78511e9b384a86b", "cves": [], "html": "Fix incorrect zero-extension of stored values in JIT-generated tuple deforming code (David Rowley) §
\nWhen not using JIT, the equivalent code does sign-extension not zero-extension, leading to a different Datum representation of small integer data types. This inconsistency was masked in most cases, but it is known to lead to “could not find memoization table entry” errors when using Memoize plan nodes, and there might be other symptoms.
", "text": "Fix incorrect zero-extension of stored values in JIT-generated tuple deforming code (David Rowley) § When not using JIT, the equivalent code does sign-extension not zero-extension, leading to a different Datum representation of small integer data types. This inconsistency was masked in most cases, but it is known to lead to “could not find memoization table entry” errors when using Memoize plan nodes, and there might be other symptoms.", "title": "Fix incorrect zero-extension of stored values in JIT-generated tuple deforming code", "commits": ["ceb51d09b"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "e82cf8c36ee531c20dbe457691d6d17ef5a6a4de2b92f57fdcfdb5db66d65a3d", "section_path": ["Changes"], "commit_groups": [["10945148e", "3398b0d02", "4afab175b", "6911f8037", "b8ecfbe5a", "ceb51d09b", "e4316ec4d"]], "identity_text": "Fix incorrect zero-extension of stored values in JIT-generated tuple deforming code (David Rowley) When not using JIT, the equivalent code does sign-extension not zero-extension, leading to a different Datum representation of small integer data types. This inconsistency was masked in most cases, but it is known to lead to could not find memoization table entry errors when using Memoize plan nodes, and there might be other symptoms.", "commit_aliases": ["10945148e", "3398b0d02", "4afab175b", "6911f8037", "b8ecfbe5a", "ceb51d09b", "e4316ec4d"], "source_commits": ["ceb51d09b"], "source_entry_id": "18.1/changes/012", "db_id": "de262079624c4f7225fefc1938b4d6c4", "patch_ids": ["55424639c609ad9b211ffd5ac10cc20b"], "statement_hash": "d62bd3e9007f7f090eba935ee43673f57b512e6913d636b18186f3f90712f8fb", "relations": [{"rule": 2, "type": "equivalent", "target": "7c81d67412977edb96996856917b1f9a", "evidence": {"same_day": true, "patch_ids": ["55424639c609ad9b211ffd5ac10cc20b"], "statement_hash": "d62bd3e9007f7f090eba935ee43673f57b512e6913d636b18186f3f90712f8fb"}}, {"rule": 2, "type": "equivalent", "target": "8411046717133be1fc919e915895664b", "evidence": {"same_day": true, "patch_ids": ["55424639c609ad9b211ffd5ac10cc20b"], "statement_hash": "d62bd3e9007f7f090eba935ee43673f57b512e6913d636b18186f3f90712f8fb"}}, {"rule": 2, "type": "equivalent", "target": "9b610d9fca503412ae7e72eddc6e5502", "evidence": {"same_day": true, "patch_ids": ["55424639c609ad9b211ffd5ac10cc20b"], "statement_hash": "d62bd3e9007f7f090eba935ee43673f57b512e6913d636b18186f3f90712f8fb"}}, {"rule": 2, "type": "equivalent", "target": "c520d8534b29d6a33acf98a0e9c4f0ef", "evidence": {"same_day": true, "patch_ids": ["55424639c609ad9b211ffd5ac10cc20b"], "statement_hash": "d62bd3e9007f7f090eba935ee43673f57b512e6913d636b18186f3f90712f8fb"}}, {"rule": 2, "type": "equivalent", "target": "e11c7ac708a333ed4eb5a375fef717d8", "evidence": {"same_day": true, "patch_ids": ["55424639c609ad9b211ffd5ac10cc20b"], "statement_hash": "d62bd3e9007f7f090eba935ee43673f57b512e6913d636b18186f3f90712f8fb"}}]}}, {"id": "18.1-fa17262588de7970", "source_entry_id": "18.1/changes/016", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix incorrect logic for caching result-relation information for triggers", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-6305949a00dd4b54", "source_entry_id": "17.7/changes/015", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix incorrect logic for caching result-relation information for triggers"}], "entry": {"id": "18.1-fa17262588de7970", "cves": [], "html": "Fix incorrect logic for caching result-relation information for triggers (David Rowley, Amit Langote) §
\nIn cases where partitions' column sets aren't physically identical to their parent partitioned tables' column sets, this oversight could lead to crashes.
", "text": "Fix incorrect logic for caching result-relation information for triggers (David Rowley, Amit Langote) § In cases where partitions' column sets aren't physically identical to their parent partitioned tables' column sets, this oversight could lead to crashes.", "title": "Fix incorrect logic for caching result-relation information for triggers", "commits": ["a2387c32f"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "7e6a20eac8e6a679bac5be291d65d4bde10ba300dbe130df9e3bc131f6fe1ef8", "section_path": ["Changes"], "commit_groups": [["0d3074615", "2992b9a07", "39dcfda2d", "a2387c32f", "a546964db"]], "identity_text": "Fix incorrect logic for caching result-relation information for triggers (David Rowley, Amit Langote) In cases where partitions' column sets aren't physically identical to their parent partitioned tables' column sets, this oversight could lead to crashes.", "commit_aliases": ["0d3074615", "2992b9a07", "39dcfda2d", "a2387c32f", "a546964db"], "source_commits": ["a2387c32f"], "source_entry_id": "18.1/changes/016", "db_id": "13af7f30c1a66144a7c4729335ad6c55", "patch_ids": ["aceec90d9a86d1b6d642dda660eebd6f"], "statement_hash": "026782085dea5b1090d57d834e0d4c7d0bc778a784349b74f9ef89ce84fcfaef", "relations": [{"rule": 2, "type": "equivalent", "target": "7ba23c07eaeb399e352fe32a704464e6", "evidence": {"same_day": true, "patch_ids": ["aceec90d9a86d1b6d642dda660eebd6f"], "statement_hash": "026782085dea5b1090d57d834e0d4c7d0bc778a784349b74f9ef89ce84fcfaef"}}, {"rule": 2, "type": "equivalent", "target": "ba3b5897c3d85845178cb5eee8dfba01", "evidence": {"same_day": true, "patch_ids": ["aceec90d9a86d1b6d642dda660eebd6f"], "statement_hash": "026782085dea5b1090d57d834e0d4c7d0bc778a784349b74f9ef89ce84fcfaef"}}, {"rule": 2, "type": "equivalent", "target": "bb7f7a3657690f7a6c75d641dcc65860", "evidence": {"same_day": true, "patch_ids": ["aceec90d9a86d1b6d642dda660eebd6f"], "statement_hash": "026782085dea5b1090d57d834e0d4c7d0bc778a784349b74f9ef89ce84fcfaef"}}]}}, {"id": "18.1-1ad36d259b8c4e29", "source_entry_id": "18.1/changes/018", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix EvalPlanQual handling of foreign or custom joins that do not have an alternative local-join plan prepared for EPQ", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-7d939e96432565c4", "source_entry_id": "17.7/changes/017", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix EvalPlanQual handling of foreign or custom joins that do not have an alternative local-join plan prepared for EPQ"}], "entry": {"id": "18.1-1ad36d259b8c4e29", "cves": [], "html": "Fix EvalPlanQual handling of foreign or custom joins that do not have an alternative local-join plan prepared for EPQ (Masahiko Sawada, Etsuro Fujita) §
\nIn such cases the foreign or custom access method should be invoked normally, but that did not happen, typically leading to a crash.
", "text": "Fix EvalPlanQual handling of foreign or custom joins that do not have an alternative local-join plan prepared for EPQ (Masahiko Sawada, Etsuro Fujita) § In such cases the foreign or custom access method should be invoked normally, but that did not happen, typically leading to a crash.", "title": "Fix EvalPlanQual handling of foreign or custom joins that do not have an alternative local-join plan prepared for EPQ", "commits": ["b14144325"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "68bd82f61fd04a0e7bc6338db072a1418250c1160d5cc3607107def8305a4549", "section_path": ["Changes"], "commit_groups": [["12609fbac", "12b0c0e51", "24e74b962", "2bb84ea7e", "4a08603a2", "5a9af4868", "b14144325"]], "identity_text": "Fix EvalPlanQual handling of foreign or custom joins that do not have an alternative local-join plan prepared for EPQ (Masahiko Sawada, Etsuro Fujita) In such cases the foreign or custom access method should be invoked normally, but that did not happen, typically leading to a crash.", "commit_aliases": ["12609fbac", "12b0c0e51", "24e74b962", "2bb84ea7e", "4a08603a2", "5a9af4868", "b14144325"], "source_commits": ["b14144325"], "source_entry_id": "18.1/changes/018", "db_id": "3a7c71a715168a6fe003c04ad6530b01", "patch_ids": ["4bc4b3eb3e3195a1d0e412e0c9371242"], "statement_hash": "7701ad14c992b95ece421f86b54788df6de9143a62d4e7ff9ea0b08caf2163f5", "relations": [{"rule": 2, "type": "equivalent", "target": "152497e1f56957947f79200f3011a52e", "evidence": {"same_day": true, "patch_ids": ["4bc4b3eb3e3195a1d0e412e0c9371242"], "statement_hash": "7701ad14c992b95ece421f86b54788df6de9143a62d4e7ff9ea0b08caf2163f5"}}, {"rule": 2, "type": "equivalent", "target": "a830cee6374ea38a3cf10eb53388b93d", "evidence": {"same_day": true, "patch_ids": ["4bc4b3eb3e3195a1d0e412e0c9371242"], "statement_hash": "7701ad14c992b95ece421f86b54788df6de9143a62d4e7ff9ea0b08caf2163f5"}}, {"rule": 2, "type": "equivalent", "target": "b4c88efd3c63eeaee70001c500504502", "evidence": {"same_day": true, "patch_ids": ["4bc4b3eb3e3195a1d0e412e0c9371242"], "statement_hash": "7701ad14c992b95ece421f86b54788df6de9143a62d4e7ff9ea0b08caf2163f5"}}, {"rule": 2, "type": "equivalent", "target": "d5c74a3284403534934e2ff5e453332e", "evidence": {"same_day": true, "patch_ids": ["4bc4b3eb3e3195a1d0e412e0c9371242"], "statement_hash": "7701ad14c992b95ece421f86b54788df6de9143a62d4e7ff9ea0b08caf2163f5"}}, {"rule": 2, "type": "equivalent", "target": "f8e7d0fe512da9f5e4221f5173c42a62", "evidence": {"same_day": true, "patch_ids": ["4bc4b3eb3e3195a1d0e412e0c9371242"], "statement_hash": "7701ad14c992b95ece421f86b54788df6de9143a62d4e7ff9ea0b08caf2163f5"}}]}}, {"id": "18.1-570dc654ef6dd9a2", "source_entry_id": "18.1/changes/019", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Avoid duplicating hash partition constraints during DETACH CONCURRENTLY", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-7064942458440619", "source_entry_id": "17.7/changes/018", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Avoid duplicating hash partition constraints during DETACH CONCURRENTLY"}], "entry": {"id": "18.1-570dc654ef6dd9a2", "cves": [], "html": "Avoid duplicating hash partition constraints during DETACH CONCURRENTLY (Haiyang Li) §
ALTER TABLE DETACH PARTITION CONCURRENTLY was written to add a copy of the partitioning constraint to the now-detached partition. This was misguided, partially because non-concurrent DETACH doesn't do that, but mostly because in the case of hash partitioning the constraint expression contains references to the parent table's OID. That causes problems during dump/restore, or if the parent table is dropped after DETACH. In v19 and later, we'll no longer create any such copied constraints at all. In released branches, to minimize the risk of unforeseen consequences, only skip adding a copied constraint if it is for hash partitioning.
Disallow generated columns in partition keys (Jian He, Ashutosh Bapat) §
\nThis was already not allowed, but the check missed some cases, such as where the column reference is implicit in a whole-row reference.
", "text": "Disallow generated columns in partition keys (Jian He, Ashutosh Bapat) § This was already not allowed, but the check missed some cases, such as where the column reference is implicit in a whole-row reference.", "title": "Disallow generated columns in partition keys", "commits": ["ba99c9491"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "c34ef2c7cbe47429ce0a76c1aa2caa7f267cdc4c1707565553f5dc4cd8576ddd", "section_path": ["Changes"], "commit_groups": [["040cc5f3c", "04345d7a4", "0b44f2443", "643a5e96c", "7180d56c5", "7f239c72a", "ba99c9491"]], "identity_text": "Disallow generated columns in partition keys (Jian He, Ashutosh Bapat) This was already not allowed, but the check missed some cases, such as where the column reference is implicit in a whole-row reference.", "commit_aliases": ["040cc5f3c", "04345d7a4", "0b44f2443", "643a5e96c", "7180d56c5", "7f239c72a", "ba99c9491"], "source_commits": ["ba99c9491"], "source_entry_id": "18.1/changes/020", "db_id": "a8595e24703e1deff3ce7b6fe56d02db", "patch_ids": ["26b7dee3d5b5a82dd804a2b2e1ecd780"], "statement_hash": "5dded4849247ab37d7f44a8fd133cdab652ee07cbfab3751bd8d4ffcbdd7e99f", "relations": [{"rule": 2, "type": "equivalent", "target": "300cd459ecbe8f82fbe0665d8d6b47c5", "evidence": {"same_day": true, "patch_ids": ["26b7dee3d5b5a82dd804a2b2e1ecd780"], "statement_hash": "5dded4849247ab37d7f44a8fd133cdab652ee07cbfab3751bd8d4ffcbdd7e99f"}}, {"rule": 2, "type": "equivalent", "target": "525dd26c2bb1d8a0169ce29cab95adac", "evidence": {"same_day": true, "patch_ids": ["26b7dee3d5b5a82dd804a2b2e1ecd780"], "statement_hash": "5dded4849247ab37d7f44a8fd133cdab652ee07cbfab3751bd8d4ffcbdd7e99f"}}, {"rule": 2, "type": "equivalent", "target": "605ca6399f9aae142eb2f308e3d598fd", "evidence": {"same_day": true, "patch_ids": ["26b7dee3d5b5a82dd804a2b2e1ecd780"], "statement_hash": "5dded4849247ab37d7f44a8fd133cdab652ee07cbfab3751bd8d4ffcbdd7e99f"}}, {"rule": 2, "type": "equivalent", "target": "8894dad53381cd45feb93c24e4fb14ba", "evidence": {"same_day": true, "patch_ids": ["26b7dee3d5b5a82dd804a2b2e1ecd780"], "statement_hash": "5dded4849247ab37d7f44a8fd133cdab652ee07cbfab3751bd8d4ffcbdd7e99f"}}, {"rule": 2, "type": "equivalent", "target": "adb9f0cae7cdccc24195248ff3704b74", "evidence": {"same_day": true, "patch_ids": ["26b7dee3d5b5a82dd804a2b2e1ecd780"], "statement_hash": "5dded4849247ab37d7f44a8fd133cdab652ee07cbfab3751bd8d4ffcbdd7e99f"}}]}}, {"id": "18.1-f93c705391287b77", "source_entry_id": "18.1/changes/021", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Disallow generated columns in COPY ... FROM ... WHERE clauses", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-0707cf226664ba13", "source_entry_id": "17.7/changes/020", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Disallow generated columns in COPY ... FROM ... WHERE clauses"}], "entry": {"id": "18.1-f93c705391287b77", "cves": [], "html": "Disallow generated columns in COPY ... FROM ... WHERE clauses (Peter Eisentraut, Jian He) §
Previously, incorrect behavior or an obscure error message resulted from attempting to reference such a column, since generated columns have not yet been computed at the point where WHERE filtering is done.
Avoid potential use-after-free in parallel vacuum (Kevin Oommen Anish) §
\nThis bug seems to have no consequences in standard builds, but it's theoretically a hazard.
", "text": "Avoid potential use-after-free in parallel vacuum (Kevin Oommen Anish) § This bug seems to have no consequences in standard builds, but it's theoretically a hazard.", "title": "Avoid potential use-after-free in parallel vacuum", "commits": ["76613b539"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "794966efecdda80a55b270d172d2da28726e6f70a5a5522d7467b5a2506ac2d1", "section_path": ["Changes"], "commit_groups": [["3549ffb6a", "54ab74865", "76613b539"]], "identity_text": "Avoid potential use-after-free in parallel vacuum (Kevin Oommen Anish) This bug seems to have no consequences in standard builds, but it's theoretically a hazard.", "commit_aliases": ["3549ffb6a", "54ab74865", "76613b539"], "source_commits": ["76613b539"], "source_entry_id": "18.1/changes/023", "db_id": "65b586522e7240dd1f867d7850ea61db", "patch_ids": ["d0dc5f67240a1a53daeb03d7af4ee34b"], "statement_hash": "e224742c5033ba7b9e4b42ddebc1f168038cd08a476019b13fb8d75e3b5bc706", "relations": [{"rule": 2, "type": "equivalent", "target": "f0dbb32056abe3b3dfdd78472b7f273b", "evidence": {"same_day": true, "patch_ids": ["d0dc5f67240a1a53daeb03d7af4ee34b"], "statement_hash": "e224742c5033ba7b9e4b42ddebc1f168038cd08a476019b13fb8d75e3b5bc706"}}]}}, {"id": "18.1-4356f370a232f620", "source_entry_id": "18.1/changes/024", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix visibility checking for statistics objects in pg_temp", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-542a921308709f1a", "source_entry_id": "17.7/changes/022", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix visibility checking for statistics objects in pg_temp"}], "entry": {"id": "18.1-4356f370a232f620", "cves": [], "html": "Fix visibility checking for statistics objects in pg_temp (Noah Misch) §
A statistics object located in a temporary schema cannot be named without schema qualification, but pg_statistics_obj_is_visible() missed that memo and could return “true” regardless. In turn, functions such as pg_describe_object() could fail to schema-qualify the object's name as expected.
Fix minor memory leak during WAL replay of database creation (Nathan Bossart) §
", "text": "Fix minor memory leak during WAL replay of database creation (Nathan Bossart) §", "title": "Fix minor memory leak during WAL replay of database creation", "commits": ["33e7b4a7c"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "a381a6bd43d267b9f76ad047254634c9c95e037e775f93f4d28201deb4381cb1", "section_path": ["Changes"], "commit_groups": [["23b316c36", "33e7b4a7c", "c72b5c536", "f9993ac64", "ff47f9c16"]], "identity_text": "Fix minor memory leak during WAL replay of database creation (Nathan Bossart)", "commit_aliases": ["23b316c36", "33e7b4a7c", "c72b5c536", "f9993ac64", "ff47f9c16"], "source_commits": ["33e7b4a7c"], "source_entry_id": "18.1/changes/025", "db_id": "0e7b5976bd913c25991a5ff549ac5f81", "patch_ids": ["7b3c9562820ec298d794a69d51573920"], "statement_hash": "aaf589db3ca0547c1138682c80ba4c30d7666e77fdcd70b3a9824de7014ad03c", "relations": [{"rule": 2, "type": "equivalent", "target": "07b0f2ed9748f2ad84f75138a8f693ab", "evidence": {"same_day": true, "patch_ids": ["7b3c9562820ec298d794a69d51573920"], "statement_hash": "aaf589db3ca0547c1138682c80ba4c30d7666e77fdcd70b3a9824de7014ad03c"}}, {"rule": 2, "type": "equivalent", "target": "4be639cfbce3dac014c7f3139f4beaa7", "evidence": {"same_day": true, "patch_ids": ["7b3c9562820ec298d794a69d51573920"], "statement_hash": "aaf589db3ca0547c1138682c80ba4c30d7666e77fdcd70b3a9824de7014ad03c"}}, {"rule": 2, "type": "equivalent", "target": "52d97c7cf8fbcce26fef4b0c910e4bf6", "evidence": {"same_day": true, "patch_ids": ["7b3c9562820ec298d794a69d51573920"], "statement_hash": "aaf589db3ca0547c1138682c80ba4c30d7666e77fdcd70b3a9824de7014ad03c"}}]}}, {"id": "18.1-b311e5c7746f8633", "source_entry_id": "18.1/changes/026", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix incorrect reporting of replication lag in pg_stat_replication view", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-fbae455a9f86efab", "source_entry_id": "17.7/changes/031", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix incorrect reporting of replication lag in pg_stat_replication view"}], "entry": {"id": "18.1-b311e5c7746f8633", "cves": [], "html": "Fix incorrect reporting of replication lag in pg_stat_replication view (Fujii Masao) §
If any standby server's replay LSN stopped advancing, the write_lag and flush_lag columns would eventually stop updating.
Avoid duplicative log messages about invalid primary_slot_name settings (Fujii Masao) §
Avoid failures when synchronized_standby_slots references nonexistent replication slots (Shlok Kyal) §
Remove the unfinished slot state file after failing to write a replication slot's state to disk (Michael Paquier) §
\nPreviously, a failure such as out-of-disk-space resulted in leaving a temporary state.tmp file behind. That's problematic because it would block all subsequent attempts to write the state, requiring manual intervention to clean up.
Fix mishandling of lock timeout signals in parallel apply workers for logical replication (Hayato Kuroda) §
\nThe same signal number was being used for both worker shutdown and lock timeout, leading to confusion.
", "text": "Fix mishandling of lock timeout signals in parallel apply workers for logical replication (Hayato Kuroda) § The same signal number was being used for both worker shutdown and lock timeout, leading to confusion.", "title": "Fix mishandling of lock timeout signals in parallel apply workers for logical replication", "commits": ["37fc5de43"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "714e58270e4ca5f91f9e2d91bc61604ea15cf638406700f413135f063d7942c8", "section_path": ["Changes"], "commit_groups": [["2f6e1a490", "37fc5de43", "a54c7a113", "e41d954da"]], "identity_text": "Fix mishandling of lock timeout signals in parallel apply workers for logical replication (Hayato Kuroda) The same signal number was being used for both worker shutdown and lock timeout, leading to confusion.", "commit_aliases": ["2f6e1a490", "37fc5de43", "a54c7a113", "e41d954da"], "source_commits": ["37fc5de43"], "source_entry_id": "18.1/changes/030", "db_id": "943decff2b98c926290fdf650e4a0edc", "patch_ids": ["b3db903786744763190489d6bf47d765"], "statement_hash": "eeca05449e3cc33c400da91c2fe568d3d74ef1488cd64e05a219a1d4578a1575", "relations": [{"rule": 2, "type": "equivalent", "target": "50ee30b81e767311733d723cd36948c0", "evidence": {"same_day": true, "patch_ids": ["b3db903786744763190489d6bf47d765"], "statement_hash": "eeca05449e3cc33c400da91c2fe568d3d74ef1488cd64e05a219a1d4578a1575"}}, {"rule": 2, "type": "equivalent", "target": "b1d5f444628e0aea3eb678b0a2d29dfa", "evidence": {"same_day": true, "patch_ids": ["b3db903786744763190489d6bf47d765"], "statement_hash": "eeca05449e3cc33c400da91c2fe568d3d74ef1488cd64e05a219a1d4578a1575"}}]}}, {"id": "18.1-a20d69b97abaf6de", "source_entry_id": "18.1/changes/031", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Avoid unwanted WAL receiver shutdown when switching from streaming to archive WAL source", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-0a048ec34f6d4d74", "source_entry_id": "17.7/changes/036", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Avoid unwanted WAL receiver shutdown when switching from streaming to archive WAL source"}], "entry": {"id": "18.1-a20d69b97abaf6de", "cves": [], "html": "Avoid unwanted WAL receiver shutdown when switching from streaming to archive WAL source (Xuneng Zhou) §
\nDuring a timeline change, a standby server's WAL receiver should remain alive, waiting for a new WAL streaming start point. Instead it was repeatedly shutting down and immediately getting restarted, which could confuse status monitoring code.
", "text": "Avoid unwanted WAL receiver shutdown when switching from streaming to archive WAL source (Xuneng Zhou) § During a timeline change, a standby server's WAL receiver should remain alive, waiting for a new WAL streaming start point. Instead it was repeatedly shutting down and immediately getting restarted, which could confuse status monitoring code.", "title": "Avoid unwanted WAL receiver shutdown when switching from streaming to archive WAL source", "commits": ["a14201073"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "1e48a276127802a798f2d83743e6434e202fd58ee0a2faa8438270cc38bed7ca", "section_path": ["Changes"], "commit_groups": [["17b2d5ec7", "25b484080", "9b6109607", "a14201073", "a1b8b3b2e", "da5ea6c70", "e7340b484"]], "identity_text": "Avoid unwanted WAL receiver shutdown when switching from streaming to archive WAL source (Xuneng Zhou) During a timeline change, a standby server's WAL receiver should remain alive, waiting for a new WAL streaming start point. Instead it was repeatedly shutting down and immediately getting restarted, which could confuse status monitoring code.", "commit_aliases": ["17b2d5ec7", "25b484080", "9b6109607", "a14201073", "a1b8b3b2e", "da5ea6c70", "e7340b484"], "source_commits": ["a14201073"], "source_entry_id": "18.1/changes/031", "db_id": "5e6622b056fdeebae1797bcd6bab73d8", "patch_ids": ["c329a1ce9ca7c1f3b46341c92f972ea9"], "statement_hash": "94e86829e542dbec362b5314cb0d0420170b66f94aea79d642bd1905c93f5d74", "relations": [{"rule": 2, "type": "equivalent", "target": "186f1aca8e166170a7cedbb47670ed32", "evidence": {"same_day": true, "patch_ids": ["c329a1ce9ca7c1f3b46341c92f972ea9"], "statement_hash": "94e86829e542dbec362b5314cb0d0420170b66f94aea79d642bd1905c93f5d74"}}, {"rule": 2, "type": "equivalent", "target": "74dc0b8668a34ee86a69e81b07977ac3", "evidence": {"same_day": true, "patch_ids": ["c329a1ce9ca7c1f3b46341c92f972ea9"], "statement_hash": "94e86829e542dbec362b5314cb0d0420170b66f94aea79d642bd1905c93f5d74"}}, {"rule": 2, "type": "equivalent", "target": "7e82176acdf9327aca4da62b00d1400a", "evidence": {"same_day": true, "patch_ids": ["c329a1ce9ca7c1f3b46341c92f972ea9"], "statement_hash": "94e86829e542dbec362b5314cb0d0420170b66f94aea79d642bd1905c93f5d74"}}, {"rule": 2, "type": "equivalent", "target": "b76ca1acc7d0e06651b84c05d5298bb5", "evidence": {"same_day": true, "patch_ids": ["c329a1ce9ca7c1f3b46341c92f972ea9"], "statement_hash": "94e86829e542dbec362b5314cb0d0420170b66f94aea79d642bd1905c93f5d74"}}, {"rule": 2, "type": "equivalent", "target": "c392b0b8a9a1720a5f28a1d62993d15b", "evidence": {"same_day": true, "patch_ids": ["c329a1ce9ca7c1f3b46341c92f972ea9"], "statement_hash": "94e86829e542dbec362b5314cb0d0420170b66f94aea79d642bd1905c93f5d74"}}]}}, {"id": "18.1-5ac1192568f3b470", "source_entry_id": "18.1/changes/032", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix use-after-free issue in the relation synchronization cache maintained by the pgoutput logical decoding plugin", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-db1ad25a90aef00e", "source_entry_id": "17.7/changes/038", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix use-after-free issue in the relation synchronization cache maintained by the pgoutput logical decoding plugin"}], "entry": {"id": "18.1-5ac1192568f3b470", "cves": [], "html": "Fix use-after-free issue in the relation synchronization cache maintained by the pgoutput logical decoding plugin (Vignesh C, Masahiko Sawada) §
\nAn error during logical decoding could result in crashes in subsequent logical decoding attempts in the same session. The case is only reachable when pgoutput is invoked via SQL functions.
", "text": "Fix use-after-free issue in the relation synchronization cache maintained by the pgoutput logical decoding plugin (Vignesh C, Masahiko Sawada) § An error during logical decoding could result in crashes in subsequent logical decoding attempts in the same session. The case is only reachable when pgoutput is invoked via SQL functions.", "title": "Fix use-after-free issue in the relation synchronization cache maintained by the pgoutput logical decoding plugin", "commits": ["32b95fc71"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "5e0d3bf538ab0c71063d21857506abb59dbd382251a7f9371a0e85c8a0ca57f3", "section_path": ["Changes"], "commit_groups": [["32b95fc71", "a61592253", "b07682bce", "b46efe904", "c40761759"]], "identity_text": "Fix use-after-free issue in the relation synchronization cache maintained by the pgoutput logical decoding plugin (Vignesh C, Masahiko Sawada) An error during logical decoding could result in crashes in subsequent logical decoding attempts in the same session. The case is only reachable when pgoutput is invoked via SQL functions.", "commit_aliases": ["32b95fc71", "a61592253", "b07682bce", "b46efe904", "c40761759"], "source_commits": ["32b95fc71"], "source_entry_id": "18.1/changes/032", "db_id": "01678f172fb01945bdf37dee98659abb", "patch_ids": ["f0d90b350350451bd966913a51e4879b"], "statement_hash": "a5100d60852834442dddf7c470eb3398c76e0d2de98829a3277bf107f97642fc", "relations": [{"rule": 2, "type": "equivalent", "target": "88eeed6b80c39786442df0b17dadee4a", "evidence": {"same_day": true, "patch_ids": ["f0d90b350350451bd966913a51e4879b"], "statement_hash": "a5100d60852834442dddf7c470eb3398c76e0d2de98829a3277bf107f97642fc"}}, {"rule": 2, "type": "equivalent", "target": "b5c5a46598eb51eef76d3c62dc981396", "evidence": {"same_day": true, "patch_ids": ["f0d90b350350451bd966913a51e4879b"], "statement_hash": "a5100d60852834442dddf7c470eb3398c76e0d2de98829a3277bf107f97642fc"}}, {"rule": 2, "type": "equivalent", "target": "bd8536eb35145d43f731406b08299135", "evidence": {"same_day": true, "patch_ids": ["f0d90b350350451bd966913a51e4879b"], "statement_hash": "a5100d60852834442dddf7c470eb3398c76e0d2de98829a3277bf107f97642fc"}}]}}, {"id": "18.1-11b960ad24efa0be", "source_entry_id": "18.1/changes/033", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Avoid unnecessary invalidation of logical replication slots", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-7503f801e6751f4a", "source_entry_id": "17.7/changes/039", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Avoid unnecessary invalidation of logical replication slots"}], "entry": {"id": "18.1-11b960ad24efa0be", "cves": [], "html": "Avoid unnecessary invalidation of logical replication slots (Bertrand Drouvot) §
", "text": "Avoid unnecessary invalidation of logical replication slots (Bertrand Drouvot) §", "title": "Avoid unnecessary invalidation of logical replication slots", "commits": ["bf3dba508"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "8314a67474fb2faf2aa29f6d4a6461256fd1f4b2de6a62e94ae410489e1838d1", "section_path": ["Changes"], "commit_groups": [["bf3dba508", "d43209468", "e3714dc05", "f3fb6bc9f"]], "identity_text": "Avoid unnecessary invalidation of logical replication slots (Bertrand Drouvot)", "commit_aliases": ["bf3dba508", "d43209468", "e3714dc05", "f3fb6bc9f"], "source_commits": ["bf3dba508"], "source_entry_id": "18.1/changes/033", "db_id": "dbc091f15023788511302d163d035b51", "patch_ids": ["6ea9f1034627e064a66a9993eefe3326"], "statement_hash": "2258d0e5693992de151b50019fd28e9463cd70463c082a7437cf067dd3c0016c", "relations": [{"rule": 2, "type": "equivalent", "target": "cb9ea43000f5f0564c0ad169585ea59f", "evidence": {"same_day": true, "patch_ids": ["6ea9f1034627e064a66a9993eefe3326"], "statement_hash": "2258d0e5693992de151b50019fd28e9463cd70463c082a7437cf067dd3c0016c"}}, {"rule": 2, "type": "equivalent", "target": "d82a9dd65733472f8ceb24aa092ce2c1", "evidence": {"same_day": true, "patch_ids": ["6ea9f1034627e064a66a9993eefe3326"], "statement_hash": "2258d0e5693992de151b50019fd28e9463cd70463c082a7437cf067dd3c0016c"}}]}}, {"id": "18.1-0bab432ae295bddb", "source_entry_id": "18.1/changes/035", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix incorrect printing of messages about failures in checking whether the user has Windows administrator privilege", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-6554bc7b77289e22", "source_entry_id": "17.7/changes/041", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix incorrect printing of messages about failures in checking whether the user has Windows administrator privilege"}], "entry": {"id": "18.1-0bab432ae295bddb", "cves": [], "html": "Fix incorrect printing of messages about failures in checking whether the user has Windows administrator privilege (Bryan Green) §
\nThis code would have crashed or at least printed garbage. No such cases have been reported though, indicating that failure of these system calls is extremely rare.
", "text": "Fix incorrect printing of messages about failures in checking whether the user has Windows administrator privilege (Bryan Green) § This code would have crashed or at least printed garbage. No such cases have been reported though, indicating that failure of these system calls is extremely rare.", "title": "Fix incorrect printing of messages about failures in checking whether the user has Windows administrator privilege", "commits": ["b48ae226e"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "5b3d2f02beb4e4207ef2adb44b13c503bb6ce3715b669e0353ee71a40523866b", "section_path": ["Changes"], "commit_groups": [["03bf7a12c", "4c53519e1", "75a555d61", "9883e3cd1", "b48ae226e", "e91eb4ad6", "f91666c83"]], "identity_text": "Fix incorrect printing of messages about failures in checking whether the user has Windows administrator privilege (Bryan Green) This code would have crashed or at least printed garbage. No such cases have been reported though, indicating that failure of these system calls is extremely rare.", "commit_aliases": ["03bf7a12c", "4c53519e1", "75a555d61", "9883e3cd1", "b48ae226e", "e91eb4ad6", "f91666c83"], "source_commits": ["b48ae226e"], "source_entry_id": "18.1/changes/035", "db_id": "54e06bd3860e1bbda5ac887cf9128e18", "patch_ids": ["d55ac972fc177556ea4a0e974c012182"], "statement_hash": "eaba82bd3ddf1952b1b8d1f5d8eb79c610f601c3b23948c4873ea0e85ca0e1ef", "relations": [{"rule": 2, "type": "equivalent", "target": "1bce0a6531645bd3f70523a4fd591cf3", "evidence": {"same_day": true, "patch_ids": ["d55ac972fc177556ea4a0e974c012182"], "statement_hash": "eaba82bd3ddf1952b1b8d1f5d8eb79c610f601c3b23948c4873ea0e85ca0e1ef"}}, {"rule": 2, "type": "equivalent", "target": "27ca4eb718e79592fec76dc7fda731c1", "evidence": {"same_day": true, "patch_ids": ["d55ac972fc177556ea4a0e974c012182"], "statement_hash": "eaba82bd3ddf1952b1b8d1f5d8eb79c610f601c3b23948c4873ea0e85ca0e1ef"}}, {"rule": 2, "type": "equivalent", "target": "92380498a4385f5ba77ddf5e840497f2", "evidence": {"same_day": true, "patch_ids": ["d55ac972fc177556ea4a0e974c012182"], "statement_hash": "eaba82bd3ddf1952b1b8d1f5d8eb79c610f601c3b23948c4873ea0e85ca0e1ef"}}, {"rule": 2, "type": "equivalent", "target": "bf9e24f2b769f783785421c6c4666a0a", "evidence": {"same_day": true, "patch_ids": ["d55ac972fc177556ea4a0e974c012182"], "statement_hash": "eaba82bd3ddf1952b1b8d1f5d8eb79c610f601c3b23948c4873ea0e85ca0e1ef"}}, {"rule": 2, "type": "equivalent", "target": "fc910ae34d590e376c66274cf6b8087f", "evidence": {"same_day": true, "patch_ids": ["d55ac972fc177556ea4a0e974c012182"], "statement_hash": "eaba82bd3ddf1952b1b8d1f5d8eb79c610f601c3b23948c4873ea0e85ca0e1ef"}}]}}, {"id": "18.1-c00c424726e8c2ba", "source_entry_id": "18.1/changes/036", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Avoid crash when attempting to test PostgreSQL with certain libsanitizer options", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-9ade7eda82977791", "source_entry_id": "17.7/changes/043", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Avoid crash when attempting to test PostgreSQL with certain libsanitizer options"}], "entry": {"id": "18.1-c00c424726e8c2ba", "cves": [], "html": "Avoid crash when attempting to test PostgreSQL with certain libsanitizer options (Emmanuel Sibi, Jacob Champion) §
", "text": "Avoid crash when attempting to test PostgreSQL with certain libsanitizer options (Emmanuel Sibi, Jacob Champion) §", "title": "Avoid crash when attempting to test PostgreSQL with certain libsanitizer options", "commits": ["6d8acb777"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "02b71b367fa5b096a4d78c9500bb07dc328a3f881cd84ef6bb00ab944d1b7821", "section_path": ["Changes"], "commit_groups": [["6d8acb777", "a9515f294", "c775bf048", "d4baa327a"]], "identity_text": "Avoid crash when attempting to test PostgreSQL with certain libsanitizer options (Emmanuel Sibi, Jacob Champion)", "commit_aliases": ["6d8acb777", "a9515f294", "c775bf048", "d4baa327a"], "source_commits": ["6d8acb777"], "source_entry_id": "18.1/changes/036", "db_id": "78099173e39c6c3e78fe3e6dbd3ae346", "patch_ids": ["0aa2e1766b342d485aa4d51817595af8"], "statement_hash": "8083d2803e957ae96e87e94e8d681a4e2bbd775e61d5de91ea925956e3a45ce9", "relations": [{"rule": 2, "type": "equivalent", "target": "1a27f92e7f186016d17a28e80fd6ba2a", "evidence": {"same_day": true, "patch_ids": ["0aa2e1766b342d485aa4d51817595af8"], "statement_hash": "8083d2803e957ae96e87e94e8d681a4e2bbd775e61d5de91ea925956e3a45ce9"}}, {"rule": 2, "type": "equivalent", "target": "3fe9f73cb5b5abb15f5187f203890f07", "evidence": {"same_day": true, "patch_ids": ["0aa2e1766b342d485aa4d51817595af8"], "statement_hash": "8083d2803e957ae96e87e94e8d681a4e2bbd775e61d5de91ea925956e3a45ce9"}}]}}, {"id": "18.1-6ea24c894273b60d", "source_entry_id": "18.1/changes/037", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix false memory-context-checking warnings in debug builds on 64-bit Windows", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-a455f9dd0199fe9d", "source_entry_id": "17.7/changes/044", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix false memory-context-checking warnings in debug builds on 64-bit Windows"}], "entry": {"id": "18.1-6ea24c894273b60d", "cves": [], "html": "Fix false memory-context-checking warnings in debug builds on 64-bit Windows (David Rowley) §
", "text": "Fix false memory-context-checking warnings in debug builds on 64-bit Windows (David Rowley) §", "title": "Fix false memory-context-checking warnings in debug builds on 64-bit Windows", "commits": ["af3a79e08"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "331b95d0ec60c21a82adc672dd67221a36a5f899be5338cdfc4a478771cdb3d1", "section_path": ["Changes"], "commit_groups": [["50eb4e118", "7b955c227", "86bd9497f", "af3a79e08", "bd6f986c9", "cdc04a6c3", "f3420e006"]], "identity_text": "Fix false memory-context-checking warnings in debug builds on 64-bit Windows (David Rowley)", "commit_aliases": ["50eb4e118", "7b955c227", "86bd9497f", "af3a79e08", "bd6f986c9", "cdc04a6c3", "f3420e006"], "source_commits": ["af3a79e08"], "source_entry_id": "18.1/changes/037", "db_id": "8df4cb56b5956e0bcfd2f6b1733b74cc", "patch_ids": ["61b56c5fae6f5e9db534484ddd08ba36"], "statement_hash": "318257c40de6d58edd2102cd728c1f712d4472c110c6470d0b05fd6cea50be8a", "relations": [{"rule": 2, "type": "equivalent", "target": "01aaa14579e082646793b4e27afbf21b", "evidence": {"same_day": true, "patch_ids": ["61b56c5fae6f5e9db534484ddd08ba36"], "statement_hash": "318257c40de6d58edd2102cd728c1f712d4472c110c6470d0b05fd6cea50be8a"}}, {"rule": 2, "type": "equivalent", "target": "0acaf19cbd02c251f9c72a3566ceafd2", "evidence": {"same_day": true, "patch_ids": ["61b56c5fae6f5e9db534484ddd08ba36"], "statement_hash": "318257c40de6d58edd2102cd728c1f712d4472c110c6470d0b05fd6cea50be8a"}}, {"rule": 2, "type": "equivalent", "target": "801cc326322f22aa573edf2c98d1162f", "evidence": {"same_day": true, "patch_ids": ["61b56c5fae6f5e9db534484ddd08ba36"], "statement_hash": "318257c40de6d58edd2102cd728c1f712d4472c110c6470d0b05fd6cea50be8a"}}, {"rule": 2, "type": "equivalent", "target": "84067ed8a3ba1028de01b8a46f2000b9", "evidence": {"same_day": true, "patch_ids": ["61b56c5fae6f5e9db534484ddd08ba36"], "statement_hash": "318257c40de6d58edd2102cd728c1f712d4472c110c6470d0b05fd6cea50be8a"}}, {"rule": 2, "type": "equivalent", "target": "fc378456b09d8aee7ced8ece43c87341", "evidence": {"same_day": true, "patch_ids": ["61b56c5fae6f5e9db534484ddd08ba36"], "statement_hash": "318257c40de6d58edd2102cd728c1f712d4472c110c6470d0b05fd6cea50be8a"}}]}}, {"id": "18.1-ea24cf69287cae1d", "source_entry_id": "18.1/changes/038", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Correctly handle GROUP BY DISTINCT in PL/pgSQL assignment statements", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-da35b615699d0e38", "source_entry_id": "17.7/changes/045", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Correctly handle GROUP BY DISTINCT in PL/pgSQL assignment statements"}], "entry": {"id": "18.1-ea24cf69287cae1d", "cves": [], "html": "Correctly handle GROUP BY DISTINCT in PL/pgSQL assignment statements (Tom Lane) §
The parser failed to record the DISTINCT option in this context, so that the command would act as if it were plain GROUP BY.
Avoid leaking memory when handling a SQL error within PL/Python (Tom Lane) §
\nThis fixes a session-lifespan memory leak introduced in our previous minor releases.
", "text": "Avoid leaking memory when handling a SQL error within PL/Python (Tom Lane) § This fixes a session-lifespan memory leak introduced in our previous minor releases.", "title": "Avoid leaking memory when handling a SQL error within PL/Python", "commits": ["447a794f6"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "25faaa57d44fc2401c1508fc419ebddb55e64b28ada29d9926422d8ebd635ad6", "section_path": ["Changes"], "commit_groups": [["447a794f6", "4cde73259", "798b19d27", "7fb8c9240", "cbfd4d0f8", "d90c92d1c", "fbc41a145"]], "identity_text": "Avoid leaking memory when handling a SQL error within PL/Python (Tom Lane) This fixes a session-lifespan memory leak introduced in our previous minor releases.", "commit_aliases": ["447a794f6", "4cde73259", "798b19d27", "7fb8c9240", "cbfd4d0f8", "d90c92d1c", "fbc41a145"], "source_commits": ["447a794f6"], "source_entry_id": "18.1/changes/039", "db_id": "8ed8073833432a5a8b59221fab2bfd05", "patch_ids": ["304183406b9fbfa71ce70fb98dd02b07"], "statement_hash": "9ed1c89d3ad5eea0e6de5ada0081665e4f99165f891937f5603d7020851959b0", "relations": [{"rule": 2, "type": "equivalent", "target": "1cc5187c2c4ae41cf3accaadaacb20c6", "evidence": {"same_day": true, "patch_ids": ["304183406b9fbfa71ce70fb98dd02b07"], "statement_hash": "9ed1c89d3ad5eea0e6de5ada0081665e4f99165f891937f5603d7020851959b0"}}, {"rule": 2, "type": "equivalent", "target": "21e26aeb99c1f4efef5ee4d427588817", "evidence": {"same_day": true, "patch_ids": ["304183406b9fbfa71ce70fb98dd02b07"], "statement_hash": "9ed1c89d3ad5eea0e6de5ada0081665e4f99165f891937f5603d7020851959b0"}}, {"rule": 2, "type": "equivalent", "target": "4567a5ad601fcfb6e367a0d5788654f3", "evidence": {"same_day": true, "patch_ids": ["304183406b9fbfa71ce70fb98dd02b07"], "statement_hash": "9ed1c89d3ad5eea0e6de5ada0081665e4f99165f891937f5603d7020851959b0"}}, {"rule": 2, "type": "equivalent", "target": "6e6104594627174dfaa8204ac54cf50d", "evidence": {"same_day": true, "patch_ids": ["304183406b9fbfa71ce70fb98dd02b07"], "statement_hash": "9ed1c89d3ad5eea0e6de5ada0081665e4f99165f891937f5603d7020851959b0"}}, {"rule": 2, "type": "equivalent", "target": "f72d5243e6c8215039615db964cfa0bc", "evidence": {"same_day": true, "patch_ids": ["304183406b9fbfa71ce70fb98dd02b07"], "statement_hash": "9ed1c89d3ad5eea0e6de5ada0081665e4f99165f891937f5603d7020851959b0"}}]}}, {"id": "18.1-476a2e50c1064c29", "source_entry_id": "18.1/changes/040", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix libpq's handling of socket-related errors on Windows within its GSSAPI logic", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-b2fb5b95a8bca3b8", "source_entry_id": "17.7/changes/048", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix libpq's handling of socket-related errors on Windows within its GSSAPI logic"}], "entry": {"id": "18.1-476a2e50c1064c29", "cves": [], "html": "Fix libpq's handling of socket-related errors on Windows within its GSSAPI logic (Ning Wu, Tom Lane) §
\nThe code for encrypting/decrypting transmitted data using GSSAPI did not correctly recognize error conditions on the connection socket, since Windows reports those differently than other platforms. This led to failure to make such connections on Windows.
", "text": "Fix libpq's handling of socket-related errors on Windows within its GSSAPI logic (Ning Wu, Tom Lane) § The code for encrypting/decrypting transmitted data using GSSAPI did not correctly recognize error conditions on the connection socket, since Windows reports those differently than other platforms. This led to failure to make such connections on Windows.", "title": "Fix libpq's handling of socket-related errors on Windows within its GSSAPI logic", "commits": ["d83879a32"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "4e01a398b7a3630fc13c41e6ed53709ed17ec704a2fa09b13e0ea903399baa0b", "section_path": ["Changes"], "commit_groups": [["1c4671f7b", "46c4478db", "771b106d1", "d83879a32", "ea78bd6d5", "f46d77377", "fc287cf3c"]], "identity_text": "Fix libpq's handling of socket-related errors on Windows within its GSSAPI logic (Ning Wu, Tom Lane) The code for encrypting/decrypting transmitted data using GSSAPI did not correctly recognize error conditions on the connection socket, since Windows reports those differently than other platforms. This led to failure to make such connections on Windows.", "commit_aliases": ["1c4671f7b", "46c4478db", "771b106d1", "d83879a32", "ea78bd6d5", "f46d77377", "fc287cf3c"], "source_commits": ["d83879a32"], "source_entry_id": "18.1/changes/040", "db_id": "3832ee9d1af37cef22d9ed22d51db616", "patch_ids": ["f0205fc96ae7aa099587d15ffc5b8b43"], "statement_hash": "a697933e21baa20247c447c1011997c652387adcb7183a91d2cc940f1de7888e", "relations": [{"rule": 2, "type": "equivalent", "target": "8a5e4771e1d3efc837da936303fe3e69", "evidence": {"same_day": true, "patch_ids": ["f0205fc96ae7aa099587d15ffc5b8b43"], "statement_hash": "a697933e21baa20247c447c1011997c652387adcb7183a91d2cc940f1de7888e"}}, {"rule": 2, "type": "equivalent", "target": "8c6a6507bd4112a04aa052cc681036ab", "evidence": {"same_day": true, "patch_ids": ["f0205fc96ae7aa099587d15ffc5b8b43"], "statement_hash": "a697933e21baa20247c447c1011997c652387adcb7183a91d2cc940f1de7888e"}}, {"rule": 2, "type": "equivalent", "target": "9d30ea675f07706c069fc213482c9a49", "evidence": {"same_day": true, "patch_ids": ["f0205fc96ae7aa099587d15ffc5b8b43"], "statement_hash": "a697933e21baa20247c447c1011997c652387adcb7183a91d2cc940f1de7888e"}}, {"rule": 2, "type": "equivalent", "target": "a676ca60cf7c395fb8962ab60a474d3e", "evidence": {"same_day": true, "patch_ids": ["f0205fc96ae7aa099587d15ffc5b8b43"], "statement_hash": "a697933e21baa20247c447c1011997c652387adcb7183a91d2cc940f1de7888e"}}, {"rule": 2, "type": "equivalent", "target": "f5be3f6b8947f88fed54b1476ce5d760", "evidence": {"same_day": true, "patch_ids": ["f0205fc96ae7aa099587d15ffc5b8b43"], "statement_hash": "a697933e21baa20247c447c1011997c652387adcb7183a91d2cc940f1de7888e"}}]}}, {"id": "18.1-3a4e23af29635f95", "source_entry_id": "18.1/changes/041", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix dumping of non-inherited not-null constraints on inherited table columns", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-ea1ba6103ffdb14f", "source_entry_id": "17.7/changes/049", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix dumping of non-inherited not-null constraints on inherited table columns"}], "entry": {"id": "18.1-3a4e23af29635f95", "cves": [], "html": "Fix dumping of non-inherited not-null constraints on inherited table columns (Dilip Kumar) §
\npg_dump failed to preserve such constraints when dumping from a pre-v18 server.
", "text": "Fix dumping of non-inherited not-null constraints on inherited table columns (Dilip Kumar) § pg_dump failed to preserve such constraints when dumping from a pre-v18 server.", "title": "Fix dumping of non-inherited not-null constraints on inherited table columns", "commits": ["0fe07fa11"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "04f06ec63a25c2d1bf641d23a4aebcbc0991f4c4683b5a54880fd018960bbe46", "section_path": ["Changes"], "commit_groups": [["0fe07fa11", "615ff828e", "c945b06d5"]], "identity_text": "Fix dumping of non-inherited not-null constraints on inherited table columns (Dilip Kumar) pg_dump failed to preserve such constraints when dumping from a pre-v18 server.", "commit_aliases": ["0fe07fa11", "615ff828e", "c945b06d5"], "source_commits": ["0fe07fa11"], "source_entry_id": "18.1/changes/041", "db_id": "85612db122ce32a9a8151af8dbfda6f6", "patch_ids": ["db74f7b93632cf3feac193a4a7cb92b1"], "statement_hash": "d1c264837bf2a17f1e917f30c81224f49f46e1a8e41803a62145abbe33b00e90", "relations": [{"rule": 2, "type": "equivalent", "target": "093d5c7edafa8bd73b4b72cdfe2bb656", "evidence": {"same_day": true, "patch_ids": ["db74f7b93632cf3feac193a4a7cb92b1"], "statement_hash": "d1c264837bf2a17f1e917f30c81224f49f46e1a8e41803a62145abbe33b00e90"}}]}}, {"id": "18.1-596e4425a92cbba4", "source_entry_id": "18.1/changes/042", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix pg_dump's sorting of foreign key constraints", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-6339fccd8bd64678", "source_entry_id": "17.7/changes/051", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix pg_dump's sorting of default ACLs and foreign key constraints"}], "entry": {"id": "18.1-596e4425a92cbba4", "cves": [], "html": "Fix pg_dump's sorting of foreign key constraints (Álvaro Herrera) §
\nEnsure consistent ordering of these database objects, as was already done for other object types.
", "text": "Fix pg_dump's sorting of foreign key constraints (Álvaro Herrera) § Ensure consistent ordering of these database objects, as was already done for other object types.", "title": "Fix pg_dump's sorting of foreign key constraints", "commits": ["162e70ea0"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "00384e1f4ea3ef405d77d3d12ab30dfec35e04c99d3980730024aa6c0aeda8f8", "section_path": ["Changes"], "commit_groups": [["06c1ee6b7", "162e70ea0", "4921a5972", "4cc3b4445", "6062c3db3", "7419c99a2", "d20df9590"]], "identity_text": "Fix pg_dump's sorting of foreign key constraints (Álvaro Herrera) Ensure consistent ordering of these database objects, as was already done for other object types.", "commit_aliases": ["06c1ee6b7", "162e70ea0", "4921a5972", "4cc3b4445", "6062c3db3", "7419c99a2", "d20df9590"], "source_commits": ["162e70ea0"], "source_entry_id": "18.1/changes/042", "db_id": "0e30416d744287728e67dfa91ecd903e", "patch_ids": ["754d79e483197bda5a8bed16ebe180ac"], "statement_hash": "cdf4d041c1de8192b2513985b95aa43b724c20b0cabb65a8b86c1a98ee9fa82c", "relations": [{"rule": 2, "type": "related", "target": "5d051ea674aeb3f3b326a89ded32901f", "evidence": {"same_day": true, "patch_ids": ["754d79e483197bda5a8bed16ebe180ac"]}}, {"rule": 2, "type": "related", "target": "5d200915f65582fc2484f8ef24cc008e", "evidence": {"same_day": true, "patch_ids": ["754d79e483197bda5a8bed16ebe180ac"]}}, {"rule": 2, "type": "related", "target": "9bedf67fa0860d232401ec8b1b5b9bf5", "evidence": {"same_day": true, "patch_ids": ["754d79e483197bda5a8bed16ebe180ac"]}}, {"rule": 2, "type": "related", "target": "9fe254aca98ebddd5297b74ffc1dfbb8", "evidence": {"same_day": true, "patch_ids": ["754d79e483197bda5a8bed16ebe180ac"]}}, {"rule": 2, "type": "related", "target": "c1d4d17be6dfafe4eaeda5f8c6d009ad", "evidence": {"same_day": true, "patch_ids": ["754d79e483197bda5a8bed16ebe180ac"]}}]}}, {"id": "18.1-939176032400286d", "source_entry_id": "18.1/changes/043", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix assorted errors in the data compression logic in pg_dump and pg_restore", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-2c512121eb50a880", "source_entry_id": "17.7/changes/054", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix assorted errors in the data compression logic in pg_dump and pg_restore"}], "entry": {"id": "18.1-939176032400286d", "cves": [], "html": "Fix assorted errors in the data compression logic in pg_dump and pg_restore (Daniel Gustafsson, Tom Lane) § § §
\nError checking was missing or incorrect in several places, and there were also portability issues that would manifest on big-endian hardware. These problems had been missed because this code is only used to read compressed TOC files within directory-format dumps. pg_dump never produces such a dump; the case can be reached only by manually compressing the TOC file after the fact, which is a supported thing to do but very uncommon.
", "text": "Fix assorted errors in the data compression logic in pg_dump and pg_restore (Daniel Gustafsson, Tom Lane) § § § Error checking was missing or incorrect in several places, and there were also portability issues that would manifest on big-endian hardware. These problems had been missed because this code is only used to read compressed TOC files within directory-format dumps. pg_dump never produces such a dump; the case can be reached only by manually compressing the TOC file after the fact, which is a supported thing to do but very uncommon.", "title": "Fix assorted errors in the data compression logic in pg_dump and pg_restore", "commits": ["6a4009747", "8980c724b", "aa1fcd087"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "00493561410c0849a110c594a3ee4af2d87a29dcfdfa2c25d12df8526aad92c2", "section_path": ["Changes"], "commit_groups": [["1518b7d76", "6a4009747", "a239c4a0c", "bf18e9bd7"], ["277dec651", "2efca1633", "33276cd02", "40dc710a6", "8b9924bce", "aa1fcd087", "c865f5b9f"], ["8980c724b", "92268b35d", "e686010c5", "ec017a305"]], "identity_text": "Fix assorted errors in the data compression logic in pg_dump and pg_restore (Daniel Gustafsson, Tom Lane) Error checking was missing or incorrect in several places, and there were also portability issues that would manifest on big-endian hardware. These problems had been missed because this code is only used to read compressed TOC files within directory-format dumps. pg_dump never produces such a dump; the case can be reached only by manually compressing the TOC file after the fact, which is a supported thing to do but very uncommon.", "commit_aliases": ["1518b7d76", "277dec651", "2efca1633", "33276cd02", "40dc710a6", "6a4009747", "8980c724b", "8b9924bce", "92268b35d", "a239c4a0c", "aa1fcd087", "bf18e9bd7", "c865f5b9f", "e686010c5", "ec017a305"], "source_commits": ["6a4009747", "8980c724b", "aa1fcd087"], "source_entry_id": "18.1/changes/043", "db_id": "db9de757f72a73bd069a8b786f5b8120", "patch_ids": ["34d09b07f99c29b50cf53cc13100ea10", "4eef07986dd4d4d15a60a29e5a15998d", "c6e514b9bc3c0e05d2b6d2fc63af7a54"], "statement_hash": "e1d5e819c74cee28f2154059267d12fd8e6cfc4c9d5affbaf9861a9f4788798c", "relations": [{"rule": 2, "type": "equivalent", "target": "12b4dd9512e147889a0b739f2bbf5ade", "evidence": {"same_day": true, "patch_ids": ["34d09b07f99c29b50cf53cc13100ea10", "4eef07986dd4d4d15a60a29e5a15998d", "c6e514b9bc3c0e05d2b6d2fc63af7a54"], "statement_hash": "e1d5e819c74cee28f2154059267d12fd8e6cfc4c9d5affbaf9861a9f4788798c"}}, {"rule": 2, "type": "equivalent", "target": "2cc366c16ddf487970d4c1a069ddef4d", "evidence": {"same_day": true, "patch_ids": ["34d09b07f99c29b50cf53cc13100ea10", "4eef07986dd4d4d15a60a29e5a15998d", "c6e514b9bc3c0e05d2b6d2fc63af7a54"], "statement_hash": "e1d5e819c74cee28f2154059267d12fd8e6cfc4c9d5affbaf9861a9f4788798c"}}, {"rule": 2, "type": "equivalent", "target": "94448a696df6dbc1fc249f870067647a", "evidence": {"same_day": true, "patch_ids": ["34d09b07f99c29b50cf53cc13100ea10", "4eef07986dd4d4d15a60a29e5a15998d", "c6e514b9bc3c0e05d2b6d2fc63af7a54"], "statement_hash": "e1d5e819c74cee28f2154059267d12fd8e6cfc4c9d5affbaf9861a9f4788798c"}}, {"rule": 2, "type": "equivalent", "target": "d6f9f1f62ddef6d134088a2d74e99a56", "evidence": {"same_day": true, "patch_ids": ["34d09b07f99c29b50cf53cc13100ea10", "4eef07986dd4d4d15a60a29e5a15998d", "c6e514b9bc3c0e05d2b6d2fc63af7a54"], "statement_hash": "e1d5e819c74cee28f2154059267d12fd8e6cfc4c9d5affbaf9861a9f4788798c"}}, {"rule": 2, "type": "equivalent", "target": "f2020f100f9176ff2a2e8a154fa90714", "evidence": {"same_day": true, "patch_ids": ["34d09b07f99c29b50cf53cc13100ea10", "4eef07986dd4d4d15a60a29e5a15998d", "c6e514b9bc3c0e05d2b6d2fc63af7a54"], "statement_hash": "e1d5e819c74cee28f2154059267d12fd8e6cfc4c9d5affbaf9861a9f4788798c"}}]}}, {"id": "18.1-cccbae91c7612842", "source_entry_id": "18.1/changes/044", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix pgbench to error out cleanly if a COPY operation is started", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-be37552c2ac3a78e", "source_entry_id": "17.7/changes/055", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix pgbench to error out cleanly if a COPY operation is started"}], "entry": {"id": "18.1-cccbae91c7612842", "cves": [], "html": "Fix pgbench to error out cleanly if a COPY operation is started (Anthonin Bonnefoy) §
pgbench doesn't intend to support this case, but previously it went into an infinite loop.
", "text": "Fix pgbench to error out cleanly if a COPY operation is started (Anthonin Bonnefoy) § pgbench doesn't intend to support this case, but previously it went into an infinite loop.", "title": "Fix pgbench to error out cleanly if a COPY operation is started", "commits": ["c00637b5f"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "aaf3614d26baed6713030ff063ec3b445c7c4ca96d13485a346fe73062aa4547", "section_path": ["Changes"], "commit_groups": [["640590bb4", "902c08887", "9b3beb7c6", "b5cefc197", "c00637b5f", "de6de069d", "f1a2f3a0c"]], "identity_text": "Fix pgbench to error out cleanly if a COPY operation is started (Anthonin Bonnefoy) pgbench doesn't intend to support this case, but previously it went into an infinite loop.", "commit_aliases": ["640590bb4", "902c08887", "9b3beb7c6", "b5cefc197", "c00637b5f", "de6de069d", "f1a2f3a0c"], "source_commits": ["c00637b5f"], "source_entry_id": "18.1/changes/044", "db_id": "9a22121acd6baa6a9fb3c0a600e6f745", "patch_ids": ["1d095caebd3e91308930c0f046a8615d"], "statement_hash": "b9c6e08e4a0d18e06d97c410e1ac9358f7012ae1718e6db0cee8ee8626b7d2eb", "relations": [{"rule": 2, "type": "equivalent", "target": "0ab8c685f0a9c83205700ee9f16ec69d", "evidence": {"same_day": true, "patch_ids": ["1d095caebd3e91308930c0f046a8615d"], "statement_hash": "b9c6e08e4a0d18e06d97c410e1ac9358f7012ae1718e6db0cee8ee8626b7d2eb"}}, {"rule": 2, "type": "equivalent", "target": "37f3a4ecb0a18fd8795547a2f62aa746", "evidence": {"same_day": true, "patch_ids": ["1d095caebd3e91308930c0f046a8615d"], "statement_hash": "b9c6e08e4a0d18e06d97c410e1ac9358f7012ae1718e6db0cee8ee8626b7d2eb"}}, {"rule": 2, "type": "equivalent", "target": "4fdb075299b2c8dbb29b9dd63ffefa18", "evidence": {"same_day": true, "patch_ids": ["1d095caebd3e91308930c0f046a8615d"], "statement_hash": "b9c6e08e4a0d18e06d97c410e1ac9358f7012ae1718e6db0cee8ee8626b7d2eb"}}, {"rule": 2, "type": "equivalent", "target": "5e3a31a811c1f52525f624d8ce076894", "evidence": {"same_day": true, "patch_ids": ["1d095caebd3e91308930c0f046a8615d"], "statement_hash": "b9c6e08e4a0d18e06d97c410e1ac9358f7012ae1718e6db0cee8ee8626b7d2eb"}}, {"rule": 2, "type": "equivalent", "target": "69889021274de78f6f31d01dd2b4ab62", "evidence": {"same_day": true, "patch_ids": ["1d095caebd3e91308930c0f046a8615d"], "statement_hash": "b9c6e08e4a0d18e06d97c410e1ac9358f7012ae1718e6db0cee8ee8626b7d2eb"}}]}}, {"id": "18.1-1b36133d506932f3", "source_entry_id": "18.1/changes/045", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix pgbench's reporting of multiple errors", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-180d8349ffb479b3", "source_entry_id": "17.7/changes/056", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix pgbench's reporting of multiple errors"}], "entry": {"id": "18.1-1b36133d506932f3", "cves": [], "html": "Fix pgbench's reporting of multiple errors (Yugo Nagata) §
\nIn cases where two successive PQgetResult calls both fail, pgbench might report the wrong error message.
In pgbench, fix faulty assertion about errors in pipeline mode (Yugo Nagata) §
", "text": "In pgbench, fix faulty assertion about errors in pipeline mode (Yugo Nagata) §", "title": "In pgbench, fix faulty assertion about errors in pipeline mode", "commits": ["c736808e0"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "77b36d627e09dac6cd7488622db7fe44901325044109792211e10a5388426f46", "section_path": ["Changes"], "commit_groups": [["704f51771", "8b2e290bd", "8bb174295", "c736808e0", "f39d9164b"]], "identity_text": "In pgbench, fix faulty assertion about errors in pipeline mode (Yugo Nagata)", "commit_aliases": ["704f51771", "8b2e290bd", "8bb174295", "c736808e0", "f39d9164b"], "source_commits": ["c736808e0"], "source_entry_id": "18.1/changes/046", "db_id": "43ed98fa322ca8711e3dbbd5e9dc0db8", "patch_ids": ["f0e6502c068cd0b05ad542efb11a232c"], "statement_hash": "c50d603a6fb129cae06cebd4c235fac3d99cea47d3329930dbc75796a0ec35f9", "relations": [{"rule": 2, "type": "equivalent", "target": "8c4b9756ea8e54675c2636e769219add", "evidence": {"same_day": true, "patch_ids": ["f0e6502c068cd0b05ad542efb11a232c"], "statement_hash": "c50d603a6fb129cae06cebd4c235fac3d99cea47d3329930dbc75796a0ec35f9"}}, {"rule": 2, "type": "equivalent", "target": "c29def4a30c507bcae5d3354625ab08e", "evidence": {"same_day": true, "patch_ids": ["f0e6502c068cd0b05ad542efb11a232c"], "statement_hash": "c50d603a6fb129cae06cebd4c235fac3d99cea47d3329930dbc75796a0ec35f9"}}, {"rule": 2, "type": "equivalent", "target": "fd360afbc940d89de171ce1ab0838f25", "evidence": {"same_day": true, "patch_ids": ["f0e6502c068cd0b05ad542efb11a232c"], "statement_hash": "c50d603a6fb129cae06cebd4c235fac3d99cea47d3329930dbc75796a0ec35f9"}}]}}, {"id": "18.1-e9df74682a19abe9", "source_entry_id": "18.1/changes/047", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix per-file memory leakage in pg_combinebackup", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-b1cf6e244790fd85", "source_entry_id": "17.7/changes/058", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix per-file memory leakage in pg_combinebackup"}], "entry": {"id": "18.1-e9df74682a19abe9", "cves": [], "html": "Fix per-file memory leakage in pg_combinebackup (Tom Lane) §
", "text": "Fix per-file memory leakage in pg_combinebackup (Tom Lane) §", "title": "Fix per-file memory leakage in pg_combinebackup", "commits": ["e2072b47b"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "4beb5cc1ed2c64b638cb70a8db3931edfbd458d919a6d4634c21202e7b74ec70", "section_path": ["Changes"], "commit_groups": [["4eb6992af", "9224c3025", "e2072b47b"]], "identity_text": "Fix per-file memory leakage in pg_combinebackup (Tom Lane)", "commit_aliases": ["4eb6992af", "9224c3025", "e2072b47b"], "source_commits": ["e2072b47b"], "source_entry_id": "18.1/changes/047", "db_id": "7e8fa99b0b4955f6b3cb8bd43181225f", "patch_ids": ["4adc1ba9937db7990ee1e4b0eed20095"], "statement_hash": "cfb0b2884d442379e85fa76d1328a0c95c85939f1727ad5b8efc4d89d3dd1b86", "relations": [{"rule": 2, "type": "equivalent", "target": "027928a265dc472699b9bfa81f7bcb4c", "evidence": {"same_day": true, "patch_ids": ["4adc1ba9937db7990ee1e4b0eed20095"], "statement_hash": "cfb0b2884d442379e85fa76d1328a0c95c85939f1727ad5b8efc4d89d3dd1b86"}}]}}, {"id": "18.1-1f106ef831d50ecf", "source_entry_id": "18.1/changes/048", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Ensure that contrib/pg_buffercache functions can be canceled", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-f96cf4298c654962", "source_entry_id": "17.7/changes/059", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Ensure that contrib/pg_buffercache functions can be canceled"}], "entry": {"id": "18.1-1f106ef831d50ecf", "cves": [], "html": "Ensure that contrib/pg_buffercache functions can be canceled (Satyanarayana Narlapuram, Yuhang Qiu) § §
Some code paths were capable of running for a long time without checking for interrupts.
", "text": "Ensure that contrib/pg_buffercache functions can be canceled (Satyanarayana Narlapuram, Yuhang Qiu) § § Some code paths were capable of running for a long time without checking for interrupts.", "title": "Ensure that contrib/pg_buffercache functions can be canceled", "commits": ["0beb7e933", "71aa2e114"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "c599c52708a4edefe8f956e7bf25970113653d3e96118a198d838931b6795ad9", "section_path": ["Changes"], "commit_groups": [["0beb7e933", "79643105a", "7d8d36289", "815fcfb20", "b6090ed96", "eab9e4e27", "eb9ee4d18"], ["71aa2e114", "8ae0f6a0c"]], "identity_text": "Ensure that contrib/pg_buffercache functions can be canceled (Satyanarayana Narlapuram, Yuhang Qiu) Some code paths were capable of running for a long time without checking for interrupts.", "commit_aliases": ["0beb7e933", "71aa2e114", "79643105a", "7d8d36289", "815fcfb20", "8ae0f6a0c", "b6090ed96", "eab9e4e27", "eb9ee4d18"], "source_commits": ["0beb7e933", "71aa2e114"], "source_entry_id": "18.1/changes/048", "db_id": "23b0ca06794cbfef601b73e5a2401894", "patch_ids": ["d2b70a45c15a7f7e00e59b3284c07ad6", "f86d6a1c7709338528c20336c0252405"], "statement_hash": "344e018da37d95afbc286749fed1e20d7328753b9e73f81484fee0e1e4996dc5", "relations": [{"rule": 2, "type": "equivalent", "target": "3caee2c365e58c61931cc0a6fb332c39", "evidence": {"same_day": true, "patch_ids": ["d2b70a45c15a7f7e00e59b3284c07ad6", "f86d6a1c7709338528c20336c0252405"], "statement_hash": "344e018da37d95afbc286749fed1e20d7328753b9e73f81484fee0e1e4996dc5"}}, {"rule": 2, "type": "equivalent", "target": "7400b4918533b966fb90032b2caf5c76", "evidence": {"same_day": true, "patch_ids": ["d2b70a45c15a7f7e00e59b3284c07ad6", "f86d6a1c7709338528c20336c0252405"], "statement_hash": "344e018da37d95afbc286749fed1e20d7328753b9e73f81484fee0e1e4996dc5"}}, {"rule": 2, "type": "equivalent", "target": "79d155685a49b3acf32f431174e9c679", "evidence": {"same_day": true, "patch_ids": ["d2b70a45c15a7f7e00e59b3284c07ad6", "f86d6a1c7709338528c20336c0252405"], "statement_hash": "344e018da37d95afbc286749fed1e20d7328753b9e73f81484fee0e1e4996dc5"}}, {"rule": 2, "type": "equivalent", "target": "b091d219fb5bea6297016707e7154f0e", "evidence": {"same_day": true, "patch_ids": ["d2b70a45c15a7f7e00e59b3284c07ad6", "f86d6a1c7709338528c20336c0252405"], "statement_hash": "344e018da37d95afbc286749fed1e20d7328753b9e73f81484fee0e1e4996dc5"}}, {"rule": 2, "type": "equivalent", "target": "ee81b22deb19121826702e15ee5489ea", "evidence": {"same_day": true, "patch_ids": ["d2b70a45c15a7f7e00e59b3284c07ad6", "f86d6a1c7709338528c20336c0252405"], "statement_hash": "344e018da37d95afbc286749fed1e20d7328753b9e73f81484fee0e1e4996dc5"}}]}}, {"id": "18.1-f8e1ff87a5a4083e", "source_entry_id": "18.1/changes/049", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Fix contrib/pg_prewarm's privilege checks for indexes", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-56eb4d27523e9522", "source_entry_id": "17.7/changes/060", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Fix contrib/pg_prewarm's privilege checks for indexes"}], "entry": {"id": "18.1-f8e1ff87a5a4083e", "cves": [], "html": "Fix contrib/pg_prewarm's privilege checks for indexes (Ayush Vatsa, Nathan Bossart) § §
pg_prewarm() requires SELECT privilege on relations to be prewarmed. However, since indexes have no SQL privileges of their own, this resulted in non-superusers being unable to prewarm indexes. Instead, check for SELECT privilege on the index's table.
Make contrib/pgstattuple more robust about empty or invalid index pages (Nitin Motiani) §
Count all-zero pages as free space, and ignore pages that are invalid according to a check of the page's special-space size. The code for btree indexes already counted all-zero pages as free, but the hash and gist code would error out, which has been found to be much less user-friendly. Similarly, make all three cases agree on ignoring corrupted pages rather than throwing errors.
", "text": "Make contrib/pgstattuple more robust about empty or invalid index pages (Nitin Motiani) § Count all-zero pages as free space, and ignore pages that are invalid according to a check of the page's special-space size. The code for btree indexes already counted all-zero pages as free, but the hash and gist code would error out, which has been found to be much less user-friendly. Similarly, make all three cases agree on ignoring corrupted pages rather than throwing errors.", "title": "Make contrib/pgstattuple more robust about empty or invalid index pages", "commits": ["fc295beb7"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "source_hash": "4a9c9202864842215eaa32a776e7fc7fc5d43dfb49b5a9dedc863dc9a43b240b", "section_path": ["Changes"], "commit_groups": [["036decbba", "49b5f0b53", "684a745f5", "c0f9fe877", "c207bf473", "ee2dbcad0", "fc295beb7"]], "identity_text": "Make contrib/pgstattuple more robust about empty or invalid index pages (Nitin Motiani) Count all-zero pages as free space, and ignore pages that are invalid according to a check of the page's special-space size. The code for btree indexes already counted all-zero pages as free, but the hash and gist code would error out, which has been found to be much less user-friendly. Similarly, make all three cases agree on ignoring corrupted pages rather than throwing errors.", "commit_aliases": ["036decbba", "49b5f0b53", "684a745f5", "c0f9fe877", "c207bf473", "ee2dbcad0", "fc295beb7"], "source_commits": ["fc295beb7"], "source_entry_id": "18.1/changes/051", "db_id": "7cf5a3928b0125574395c382ed52c5b1", "patch_ids": ["1ec2ccb4b684e5f57590aab9c7c2a444"], "statement_hash": "c02e1d95147e0120948e2eb5839f7964fb935bba934375858d2457ca4e09c98d", "relations": [{"rule": 2, "type": "equivalent", "target": "3be631a7028f49faa7a328c190d249c2", "evidence": {"same_day": true, "patch_ids": ["1ec2ccb4b684e5f57590aab9c7c2a444"], "statement_hash": "c02e1d95147e0120948e2eb5839f7964fb935bba934375858d2457ca4e09c98d"}}, {"rule": 2, "type": "equivalent", "target": "a6ec20ccdb529fbc57070c204bf73a7c", "evidence": {"same_day": true, "patch_ids": ["1ec2ccb4b684e5f57590aab9c7c2a444"], "statement_hash": "c02e1d95147e0120948e2eb5839f7964fb935bba934375858d2457ca4e09c98d"}}, {"rule": 2, "type": "equivalent", "target": "bd4e2931635023fef1578e6a6ef3185b", "evidence": {"same_day": true, "patch_ids": ["1ec2ccb4b684e5f57590aab9c7c2a444"], "statement_hash": "c02e1d95147e0120948e2eb5839f7964fb935bba934375858d2457ca4e09c98d"}}, {"rule": 2, "type": "equivalent", "target": "dbdca19037730dda97abc3c0ca87e248", "evidence": {"same_day": true, "patch_ids": ["1ec2ccb4b684e5f57590aab9c7c2a444"], "statement_hash": "c02e1d95147e0120948e2eb5839f7964fb935bba934375858d2457ca4e09c98d"}}, {"rule": 2, "type": "equivalent", "target": "e2d3ae73f7d42937b9fa7746740e86a5", "evidence": {"same_day": true, "patch_ids": ["1ec2ccb4b684e5f57590aab9c7c2a444"], "statement_hash": "c02e1d95147e0120948e2eb5839f7964fb935bba934375858d2457ca4e09c98d"}}]}}, {"id": "18.1-01cf9fc9542209e8", "source_entry_id": "18.1/changes/052", "version": "18.1", "source_url": "/docs/release/18.1/#RELEASE-18-1-CHANGES", "title": "Harden our read and write barrier macros to satisfy Clang", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.7-a358469faddcaf65", "source_entry_id": "17.7/changes/062", "version": "17.7", "source_url": "/docs/release/17.7/#RELEASE-17-7-CHANGES", "title": "Harden our read and write barrier macros to satisfy Clang"}], "entry": {"id": "18.1-01cf9fc9542209e8", "cves": [], "html": "Harden our read and write barrier macros to satisfy Clang (Thomas Munro) §
\nWe supposed that __atomic_thread_fence() is a sufficient barrier to prevent the C compiler from re-ordering memory accesses around it, but it appears that that's not true for Clang, allowing it to generate incorrect code for at least RISC-V, MIPS, and LoongArch machines. Add explicit compiler barriers to fix that.
Fix PGXS build infrastructure to support building NLS po files for extensions (Ryo Matsumura) §
Guard against unexpected dimensions of oidvector/int2vector (Tom Lane) §
These data types are expected to be 1-dimensional arrays containing no nulls, but there are cast pathways that permit violating those expectations. Add checks to some functions that were depending on those expectations without verifying them, and could misbehave in consequence.
\nThe PostgreSQL Project thanks Altan Birler for reporting this problem. (CVE-2026-2003)
", "text": "Guard against unexpected dimensions of oidvector/int2vector (Tom Lane) § These data types are expected to be 1-dimensional arrays containing no nulls, but there are cast pathways that permit violating those expectations. Add checks to some functions that were depending on those expectations without verifying them, and could misbehave in consequence. The PostgreSQL Project thanks Altan Birler for reporting this problem. (CVE-2026-2003)", "title": "Guard against unexpected dimensions of oidvector/int2vector", "commits": ["3b6588cd9"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "fe994475fb9f99a34b9728f5a5e7ac9315c8f8a27bd6204ddfa72d82ab2f7d91", "section_path": ["Changes"], "commit_groups": [["3b6588cd9", "3d160401b", "429aeaebd", "595956fc7", "60e7ae41a", "b39d38139"]], "identity_text": "Guard against unexpected dimensions of oidvector/int2vector (Tom Lane) These data types are expected to be 1-dimensional arrays containing no nulls, but there are cast pathways that permit violating those expectations. Add checks to some functions that were depending on those expectations without verifying them, and could misbehave in consequence. The PostgreSQL Project thanks Altan Birler for reporting this problem. (CVE-2026-2003)", "commit_aliases": ["3b6588cd9", "3d160401b", "429aeaebd", "595956fc7", "60e7ae41a", "b39d38139"], "source_commits": ["3b6588cd9"], "source_entry_id": "18.2/changes/001", "db_id": "020aec6d98ff35dcd4eca87ecb7d21fd", "patch_ids": ["e625ea93052fd4dfb5ad354c3e4c3569"], "statement_hash": "ce3b678bc249d2400e6f33b017d19a152d1f885b7690423e0e17ba0530a55787", "relations": [{"rule": 2, "type": "equivalent", "target": "8db55cd2cacfbefb7d8380baee0440a5", "evidence": {"same_day": true, "patch_ids": ["e625ea93052fd4dfb5ad354c3e4c3569"], "statement_hash": "ce3b678bc249d2400e6f33b017d19a152d1f885b7690423e0e17ba0530a55787"}}, {"rule": 2, "type": "equivalent", "target": "93680dc2fc005fc9bc0a92b7d80ee23b", "evidence": {"same_day": true, "patch_ids": ["e625ea93052fd4dfb5ad354c3e4c3569"], "statement_hash": "ce3b678bc249d2400e6f33b017d19a152d1f885b7690423e0e17ba0530a55787"}}, {"rule": 2, "type": "equivalent", "target": "d474cd2cf9a4505bba396d502fe366fe", "evidence": {"same_day": true, "patch_ids": ["e625ea93052fd4dfb5ad354c3e4c3569"], "statement_hash": "ce3b678bc249d2400e6f33b017d19a152d1f885b7690423e0e17ba0530a55787"}}, {"rule": 2, "type": "equivalent", "target": "dadfe1bd35a127e4b2350a876ce5f39d", "evidence": {"same_day": true, "patch_ids": ["e625ea93052fd4dfb5ad354c3e4c3569"], "statement_hash": "ce3b678bc249d2400e6f33b017d19a152d1f885b7690423e0e17ba0530a55787"}}]}}, {"id": "18.2-0a3add9d9f709ebd", "source_entry_id": "18.2/changes/002", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Harden selectivity estimators against being attached to operators that accept unexpected data types", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-66e960e22441cfaa", "source_entry_id": "17.8/changes/002", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Harden selectivity estimators against being attached to operators that accept unexpected data types"}], "entry": {"id": "18.2-0a3add9d9f709ebd", "cves": ["CVE-2026-2004"], "html": "Harden selectivity estimators against being attached to operators that accept unexpected data types (Tom Lane) § §
\ncontrib/intarray contained a selectivity estimation function that could be abused for arbitrary code execution, because it did not check that its input was of the expected data type. Third-party extensions should check for similar hazards and add defenses using the technique intarray now uses. Since such extension fixes will take time, we now require superuser privilege to attach a non-built-in selectivity estimator to an operator.
The PostgreSQL Project thanks Daniel Firer, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2004)
", "text": "Harden selectivity estimators against being attached to operators that accept unexpected data types (Tom Lane) § § contrib/intarray contained a selectivity estimation function that could be abused for arbitrary code execution, because it did not check that its input was of the expected data type. Third-party extensions should check for similar hazards and add defenses using the technique intarray now uses. Since such extension fixes will take time, we now require superuser privilege to attach a non-built-in selectivity estimator to an operator. The PostgreSQL Project thanks Daniel Firer, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2004)", "title": "Harden selectivity estimators against being attached to operators that accept unexpected data types", "commits": ["66ddac698", "b69af3dda"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "5f2877c96b4d6a2170fba3c7e8bcac2815e78cd423e2e9f62e69ec8dee5ebdaa", "section_path": ["Changes"], "commit_groups": [["3ecc84cce", "9fa38c572", "d484bc260", "dbb09fd8e"], ["66ddac698", "841d42cc4", "91d7c0bfd", "b764b26f2", "bbf5bcf58", "ea3bf3498"], ["7e82d9a04", "8ebdf41c2", "b69af3dda", "c0887b39d", "dd3ad2a4d", "deb464a40"]], "identity_text": "Harden selectivity estimators against being attached to operators that accept unexpected data types (Tom Lane) contrib/intarray contained a selectivity estimation function that could be abused for arbitrary code execution, because it did not check that its input was of the expected data type. Third-party extensions should check for similar hazards and add defenses using the technique intarray now uses. Since such extension fixes will take time, we now require superuser privilege to attach a non-built-in selectivity estimator to an operator. The PostgreSQL Project thanks Daniel Firer, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2004)", "commit_aliases": ["3ecc84cce", "66ddac698", "7e82d9a04", "841d42cc4", "8ebdf41c2", "91d7c0bfd", "9fa38c572", "b69af3dda", "b764b26f2", "bbf5bcf58", "c0887b39d", "d484bc260", "dbb09fd8e", "dd3ad2a4d", "deb464a40", "ea3bf3498"], "source_commits": ["66ddac698", "b69af3dda", "dbb09fd8e"], "source_entry_id": "18.2/changes/002", "db_id": "853a0accddf2290afda1b4c5d74207ed", "patch_ids": ["2f2e483656bae2dbe55158c3365123bd", "356a9ce59861f3c9318ff0c7fe53f540", "4bc40137a21f6b104cb7a2aaf123c445"], "statement_hash": "bf854d211c57f15bce3aa7bbb099f8690284afbf8188626b5fdf9bd083214cc4", "relations": [{"rule": 2, "type": "equivalent", "target": "184452363a4be8fbad69f06eb60df539", "evidence": {"same_day": true, "patch_ids": ["2f2e483656bae2dbe55158c3365123bd", "356a9ce59861f3c9318ff0c7fe53f540", "4bc40137a21f6b104cb7a2aaf123c445"], "statement_hash": "bf854d211c57f15bce3aa7bbb099f8690284afbf8188626b5fdf9bd083214cc4"}}, {"rule": 2, "type": "equivalent", "target": "3cfe051a6ace1086d9ff67af367a40f4", "evidence": {"same_day": true, "patch_ids": ["2f2e483656bae2dbe55158c3365123bd", "356a9ce59861f3c9318ff0c7fe53f540", "4bc40137a21f6b104cb7a2aaf123c445"], "statement_hash": "bf854d211c57f15bce3aa7bbb099f8690284afbf8188626b5fdf9bd083214cc4"}}, {"rule": 2, "type": "equivalent", "target": "b368f952921e7f029d36869bd2860743", "evidence": {"same_day": true, "patch_ids": ["2f2e483656bae2dbe55158c3365123bd", "356a9ce59861f3c9318ff0c7fe53f540", "4bc40137a21f6b104cb7a2aaf123c445"], "statement_hash": "bf854d211c57f15bce3aa7bbb099f8690284afbf8188626b5fdf9bd083214cc4"}}, {"rule": 2, "type": "equivalent", "target": "eb75ba70d74784578edba6ea18a6aaf9", "evidence": {"same_day": true, "patch_ids": ["2f2e483656bae2dbe55158c3365123bd", "356a9ce59861f3c9318ff0c7fe53f540", "4bc40137a21f6b104cb7a2aaf123c445"], "statement_hash": "bf854d211c57f15bce3aa7bbb099f8690284afbf8188626b5fdf9bd083214cc4"}}]}}, {"id": "18.2-c6669984145bd55c", "source_entry_id": "18.2/changes/003", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix buffer overrun in contrib/pgcrypto's PGP decryption functions", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-ad02898fb1831e36", "source_entry_id": "17.8/changes/003", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix buffer overrun in contrib/pgcrypto's PGP decryption functions"}], "entry": {"id": "18.2-c6669984145bd55c", "cves": ["CVE-2026-2005"], "html": "Fix buffer overrun in contrib/pgcrypto's PGP decryption functions (Michael Paquier) §
Decrypting a crafted message with an overlength session key caused a buffer overrun, with consequences as bad as arbitrary code execution.
\nThe PostgreSQL Project thanks Team Xint Code, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2005)
", "text": "Fix buffer overrun in contrib/pgcrypto's PGP decryption functions (Michael Paquier) § Decrypting a crafted message with an overlength session key caused a buffer overrun, with consequences as bad as arbitrary code execution. The PostgreSQL Project thanks Team Xint Code, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2005)", "title": "Fix buffer overrun in contrib/pgcrypto's PGP decryption functions", "commits": ["209f387b8"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "791a96f3e49adc249c0a775ab7d8472cdeebaadf676276ed6cf8345c0921e5fc", "section_path": ["Changes"], "commit_groups": [["01de2e32d", "209f387b8", "379695d3c", "527b730f4", "7a7d9693c", "9a9982ec6"]], "identity_text": "Fix buffer overrun in contrib/pgcrypto's PGP decryption functions (Michael Paquier) Decrypting a crafted message with an overlength session key caused a buffer overrun, with consequences as bad as arbitrary code execution. The PostgreSQL Project thanks Team Xint Code, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2005)", "commit_aliases": ["01de2e32d", "209f387b8", "379695d3c", "527b730f4", "7a7d9693c", "9a9982ec6"], "source_commits": ["209f387b8"], "source_entry_id": "18.2/changes/003", "db_id": "ef4c4d388861428d41d8694448d1ec90", "patch_ids": ["8812c5ce4844c4609945e75b3dad003d"], "statement_hash": "643330e49824e6c84ee06b67cc1febd73b94c839951a2861efc8c384a23e8307", "relations": [{"rule": 2, "type": "equivalent", "target": "bdd4104dfc3659a38e0f0389ee19b847", "evidence": {"same_day": true, "patch_ids": ["8812c5ce4844c4609945e75b3dad003d"], "statement_hash": "643330e49824e6c84ee06b67cc1febd73b94c839951a2861efc8c384a23e8307"}}, {"rule": 2, "type": "equivalent", "target": "d0b0ce25a07e9ad598056180477520b6", "evidence": {"same_day": true, "patch_ids": ["8812c5ce4844c4609945e75b3dad003d"], "statement_hash": "643330e49824e6c84ee06b67cc1febd73b94c839951a2861efc8c384a23e8307"}}, {"rule": 2, "type": "equivalent", "target": "e4dd47f240a98be34ae099044d8a2b56", "evidence": {"same_day": true, "patch_ids": ["8812c5ce4844c4609945e75b3dad003d"], "statement_hash": "643330e49824e6c84ee06b67cc1febd73b94c839951a2861efc8c384a23e8307"}}, {"rule": 2, "type": "equivalent", "target": "e7bf20473d33d5835462a40fa9fd5552", "evidence": {"same_day": true, "patch_ids": ["8812c5ce4844c4609945e75b3dad003d"], "statement_hash": "643330e49824e6c84ee06b67cc1febd73b94c839951a2861efc8c384a23e8307"}}]}}, {"id": "18.2-b28dc0bb7dc6b053", "source_entry_id": "18.2/changes/004", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix inadequate validation of multibyte character lengths", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-0378679c62701a5e", "source_entry_id": "17.8/changes/004", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix inadequate validation of multibyte character lengths"}], "entry": {"id": "18.2-b28dc0bb7dc6b053", "cves": ["CVE-2026-2006"], "html": "Fix inadequate validation of multibyte character lengths (Thomas Munro, Noah Misch) § § § § § §
\nAssorted bugs allowed an attacker able to issue crafted SQL to overrun string buffers, with consequences as bad as arbitrary code execution. After these fixes, applications may observe “invalid byte sequence for encoding” errors when string functions process invalid text that has been stored in the database.
\nThe PostgreSQL Project thanks Paul Gerste and Moritz Sanft, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2006)
", "text": "Fix inadequate validation of multibyte character lengths (Thomas Munro, Noah Misch) § § § § § § Assorted bugs allowed an attacker able to issue crafted SQL to overrun string buffers, with consequences as bad as arbitrary code execution. After these fixes, applications may observe “invalid byte sequence for encoding” errors when string functions process invalid text that has been stored in the database. The PostgreSQL Project thanks Paul Gerste and Moritz Sanft, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2006)", "title": "Fix inadequate validation of multibyte character lengths", "commits": ["4543b02af", "7b5fc85be", "b0f5d25bc", "b42709194", "df0852fe0", "efef05ba9"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "d557f73b34b4644693c2136f42999479e3bf11299615ca496ccfc56912747e88", "section_path": ["Changes"], "commit_groups": [["0c33d5608", "8373ed094", "8f8b1ffac", "b42709194", "d536aee55", "dc072a09a"], ["10ebc4bd6", "4c08960d9", "757bf8145", "b0f5d25bc", "c67bef3f3", "e7591254c"], ["1e7fe06c1", "319e8a644", "7b5fc85be", "cecedb912", "d837fb029", "fd82ddb67"], ["2a53db21e", "70ff9ede5", "838248b1b", "af79c30dc", "b2c81ac86", "df0852fe0"], ["4543b02af", "5301b2b7d", "6f741bcb6", "763671b74", "955433ebd", "c5dc75479"], ["50863be0b", "6ed116046", "74ee636cc", "7a522039f", "b0e3f5cf9", "efef05ba9"]], "identity_text": "Fix inadequate validation of multibyte character lengths (Thomas Munro, Noah Misch) Assorted bugs allowed an attacker able to issue crafted SQL to overrun string buffers, with consequences as bad as arbitrary code execution. After these fixes, applications may observe invalid byte sequence for encoding errors when string functions process invalid text that has been stored in the database. The PostgreSQL Project thanks Paul Gerste and Moritz Sanft, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2006)", "commit_aliases": ["0c33d5608", "10ebc4bd6", "1e7fe06c1", "2a53db21e", "319e8a644", "4543b02af", "4c08960d9", "50863be0b", "5301b2b7d", "6ed116046", "6f741bcb6", "70ff9ede5", "74ee636cc", "757bf8145", "763671b74", "7a522039f", "7b5fc85be", "8373ed094", "838248b1b", "8f8b1ffac", "955433ebd", "af79c30dc", "b0e3f5cf9", "b0f5d25bc", "b2c81ac86", "b42709194", "c5dc75479", "c67bef3f3", "cecedb912", "d536aee55", "d837fb029", "dc072a09a", "df0852fe0", "e7591254c", "efef05ba9", "fd82ddb67"], "source_commits": ["4543b02af", "7b5fc85be", "b0f5d25bc", "b42709194", "df0852fe0", "efef05ba9"], "source_entry_id": "18.2/changes/004", "db_id": "66ef8e4bb930ff6d7fb76f1509e60bdb", "patch_ids": ["495ed616c5c9d01200b34ff986191d76", "8b94976f553df832eb256817e06f6e8e", "a8ccf4d965aea8d430069f2b4025b384", "b98e99e748716baf094e4d11553e19ae", "e1e546efb1e21ef2c167c052b7fc2c27", "ef48875931b707685e95ea56147ddbe5"], "statement_hash": "6c6e0d081c08625c5f6ce833f7e79f2bb277ec939453acd9d359f724272d34eb", "relations": [{"rule": 2, "type": "equivalent", "target": "25b98554e64d0842a180907318bd502a", "evidence": {"same_day": true, "patch_ids": ["495ed616c5c9d01200b34ff986191d76", "8b94976f553df832eb256817e06f6e8e", "a8ccf4d965aea8d430069f2b4025b384", "b98e99e748716baf094e4d11553e19ae", "e1e546efb1e21ef2c167c052b7fc2c27", "ef48875931b707685e95ea56147ddbe5"], "statement_hash": "6c6e0d081c08625c5f6ce833f7e79f2bb277ec939453acd9d359f724272d34eb"}}, {"rule": 2, "type": "equivalent", "target": "2fee65050d60d6944038f5de1fd6e77f", "evidence": {"same_day": true, "patch_ids": ["495ed616c5c9d01200b34ff986191d76", "8b94976f553df832eb256817e06f6e8e", "a8ccf4d965aea8d430069f2b4025b384", "b98e99e748716baf094e4d11553e19ae", "e1e546efb1e21ef2c167c052b7fc2c27", "ef48875931b707685e95ea56147ddbe5"], "statement_hash": "6c6e0d081c08625c5f6ce833f7e79f2bb277ec939453acd9d359f724272d34eb"}}, {"rule": 2, "type": "equivalent", "target": "c7f1c767af36d148849ecf12abc7b39c", "evidence": {"same_day": true, "patch_ids": ["495ed616c5c9d01200b34ff986191d76", "8b94976f553df832eb256817e06f6e8e", "a8ccf4d965aea8d430069f2b4025b384", "b98e99e748716baf094e4d11553e19ae", "e1e546efb1e21ef2c167c052b7fc2c27", "ef48875931b707685e95ea56147ddbe5"], "statement_hash": "6c6e0d081c08625c5f6ce833f7e79f2bb277ec939453acd9d359f724272d34eb"}}, {"rule": 2, "type": "equivalent", "target": "e5c2b929807dffd0fc80d18ac5ef27da", "evidence": {"same_day": true, "patch_ids": ["495ed616c5c9d01200b34ff986191d76", "8b94976f553df832eb256817e06f6e8e", "a8ccf4d965aea8d430069f2b4025b384", "b98e99e748716baf094e4d11553e19ae", "e1e546efb1e21ef2c167c052b7fc2c27", "ef48875931b707685e95ea56147ddbe5"], "statement_hash": "6c6e0d081c08625c5f6ce833f7e79f2bb277ec939453acd9d359f724272d34eb"}}]}}, {"id": "18.2-d6f0ddb2f2597bb2", "source_entry_id": "18.2/changes/008", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Don't allow CTE references in sub-selects to determine semantic levels of aggregate functions", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-69605b7e08548aa0", "source_entry_id": "17.8/changes/005", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Don't allow CTE references in sub-selects to determine semantic levels of aggregate functions"}], "entry": {"id": "18.2-d6f0ddb2f2597bb2", "cves": [], "html": "Don't allow CTE references in sub-selects to determine semantic levels of aggregate functions (Tom Lane) §
\nThis change undoes a change made two minor releases ago, instead throwing an error if a sub-select references a CTE that's below the semantic level that standard SQL rules would assign to the aggregate based on contained column references and aggregates. The attempted fix turned out to cause problems of its own, and it's unclear what to do instead. Since sub-selects within aggregates are disallowed altogether by the SQL standard, treating such cases as errors seems sufficient.
", "text": "Don't allow CTE references in sub-selects to determine semantic levels of aggregate functions (Tom Lane) § This change undoes a change made two minor releases ago, instead throwing an error if a sub-select references a CTE that's below the semantic level that standard SQL rules would assign to the aggregate based on contained column references and aggregates. The attempted fix turned out to cause problems of its own, and it's unclear what to do instead. Since sub-selects within aggregates are disallowed altogether by the SQL standard, treating such cases as errors seems sufficient.", "title": "Don't allow CTE references in sub-selects to determine semantic levels of aggregate functions", "commits": ["12bc32917"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "7441d1eca0c2bfb6db24f0e89519196554b2eb9ff55fca9d77f788145bc59a02", "section_path": ["Changes"], "commit_groups": [["075a763e2", "12bc32917", "1c8c3206f", "35b5c62c3", "9f5a58aac", "b85397481"]], "identity_text": "Don't allow CTE references in sub-selects to determine semantic levels of aggregate functions (Tom Lane) This change undoes a change made two minor releases ago, instead throwing an error if a sub-select references a CTE that's below the semantic level that standard SQL rules would assign to the aggregate based on contained column references and aggregates. The attempted fix turned out to cause problems of its own, and it's unclear what to do instead. Since sub-selects within aggregates are disallowed altogether by the SQL standard, treating such cases as errors seems sufficient.", "commit_aliases": ["075a763e2", "12bc32917", "1c8c3206f", "35b5c62c3", "9f5a58aac", "b85397481"], "source_commits": ["12bc32917"], "source_entry_id": "18.2/changes/008", "db_id": "968c190ce539c030cfe3824a0cddc761", "patch_ids": ["b900772ffaf16070ad5c6f3ee9476799"], "statement_hash": "aca5184caeda78eb5d5b9152a6295b4c451d3d7324fcbaae36c120961950e059", "relations": [{"rule": 2, "type": "equivalent", "target": "128a16829eb01aeea2a683fa84040725", "evidence": {"same_day": true, "patch_ids": ["b900772ffaf16070ad5c6f3ee9476799"], "statement_hash": "aca5184caeda78eb5d5b9152a6295b4c451d3d7324fcbaae36c120961950e059"}}, {"rule": 2, "type": "equivalent", "target": "4864352d8953061a7f3e2f942fd405e2", "evidence": {"same_day": true, "patch_ids": ["b900772ffaf16070ad5c6f3ee9476799"], "statement_hash": "aca5184caeda78eb5d5b9152a6295b4c451d3d7324fcbaae36c120961950e059"}}, {"rule": 2, "type": "equivalent", "target": "cc9e6465c86b962c0dda27e8afcac193", "evidence": {"same_day": true, "patch_ids": ["b900772ffaf16070ad5c6f3ee9476799"], "statement_hash": "aca5184caeda78eb5d5b9152a6295b4c451d3d7324fcbaae36c120961950e059"}}, {"rule": 2, "type": "equivalent", "target": "dcc6e6d85b35d0422b8e17422a731c4a", "evidence": {"same_day": true, "patch_ids": ["b900772ffaf16070ad5c6f3ee9476799"], "statement_hash": "aca5184caeda78eb5d5b9152a6295b4c451d3d7324fcbaae36c120961950e059"}}]}}, {"id": "18.2-449ed1ba9b72a08e", "source_entry_id": "18.2/changes/009", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix trigger transition table capture for MERGE in CTE queries", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-a05a36b6df4c6b60", "source_entry_id": "17.8/changes/006", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix trigger transition table capture for MERGE in CTE queries"}], "entry": {"id": "18.2-449ed1ba9b72a08e", "cves": [], "html": "Fix trigger transition table capture for MERGE in CTE queries (Dean Rasheed) §
When executing a data-modifying CTE query containing both a MERGE and another DML operation on a table with statement-level AFTER triggers, the transition tables passed to the triggers would not include the rows affected by the MERGE, only those affected by the other operation(s).
Fix failure when all children of a partitioned target table of an update or delete have been pruned (Amit Langote) §
\nIn such cases, the executor could report “could not find junk ctid column” errors, even though nothing needs to be done.
", "text": "Fix failure when all children of a partitioned target table of an update or delete have been pruned (Amit Langote) § In such cases, the executor could report “could not find junk ctid column” errors, even though nothing needs to be done.", "title": "Fix failure when all children of a partitioned target table of an update or delete have been pruned", "commits": ["9f4b7bfc5"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "ae613928441a2248bf5dcb5b91ec42acf14302127242c9163500608ef0f6674e", "section_path": ["Changes"], "commit_groups": [["687533b39", "6d2fa44d2", "933f67fb6", "9f4b7bfc5", "f9a468c66", "fab386f74"]], "identity_text": "Fix failure when all children of a partitioned target table of an update or delete have been pruned (Amit Langote) In such cases, the executor could report could not find junk ctid column errors, even though nothing needs to be done.", "commit_aliases": ["687533b39", "6d2fa44d2", "933f67fb6", "9f4b7bfc5", "f9a468c66", "fab386f74"], "source_commits": ["9f4b7bfc5"], "source_entry_id": "18.2/changes/011", "db_id": "f4b5a0c770a80f36d1c78eef1f635128", "patch_ids": ["9a0dd248bccac339f799f84ddd7d8025"], "statement_hash": "2d865ce2ec1c605811a5336cc6b79b917602006b9d88ed02a66f1499e94eb2b3", "relations": [{"rule": 2, "type": "equivalent", "target": "179b2113d34cec63f6ed7d3339773014", "evidence": {"same_day": true, "patch_ids": ["9a0dd248bccac339f799f84ddd7d8025"], "statement_hash": "2d865ce2ec1c605811a5336cc6b79b917602006b9d88ed02a66f1499e94eb2b3"}}, {"rule": 2, "type": "equivalent", "target": "4ced629daa2801c0202dec91097dd571", "evidence": {"same_day": true, "patch_ids": ["9a0dd248bccac339f799f84ddd7d8025"], "statement_hash": "2d865ce2ec1c605811a5336cc6b79b917602006b9d88ed02a66f1499e94eb2b3"}}, {"rule": 2, "type": "equivalent", "target": "63da9c3d80fbdcaacf4a6c8e130df7a3", "evidence": {"same_day": true, "patch_ids": ["9a0dd248bccac339f799f84ddd7d8025"], "statement_hash": "2d865ce2ec1c605811a5336cc6b79b917602006b9d88ed02a66f1499e94eb2b3"}}, {"rule": 2, "type": "equivalent", "target": "7a4315af35989c84209f54d435f1bc39", "evidence": {"same_day": true, "patch_ids": ["9a0dd248bccac339f799f84ddd7d8025"], "statement_hash": "2d865ce2ec1c605811a5336cc6b79b917602006b9d88ed02a66f1499e94eb2b3"}}]}}, {"id": "18.2-339f2dc7a8d3edca", "source_entry_id": "18.2/changes/014", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Avoid possible planner failure when a query contains duplicate window function calls", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-a2c5213ddb6acb5c", "source_entry_id": "17.8/changes/008", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Avoid possible planner failure when a query contains duplicate window function calls"}], "entry": {"id": "18.2-339f2dc7a8d3edca", "cves": [], "html": "Avoid possible planner failure when a query contains duplicate window function calls (Meng Zhang, David Rowley) §
\nConfusion over de-duplication of such calls could result in errors like “WindowFunc with winref 2 assigned to WindowAgg with winref 1”.
", "text": "Avoid possible planner failure when a query contains duplicate window function calls (Meng Zhang, David Rowley) § Confusion over de-duplication of such calls could result in errors like “WindowFunc with winref 2 assigned to WindowAgg with winref 1”.", "title": "Avoid possible planner failure when a query contains duplicate window function calls", "commits": ["ccde5be68"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "fc0dae4adf33bc18af8510a13791cb63b3243cb74e0fb7ec0534f349211c5782", "section_path": ["Changes"], "commit_groups": [["4297a3519", "7027dd499", "cae812741", "ccde5be68"]], "identity_text": "Avoid possible planner failure when a query contains duplicate window function calls (Meng Zhang, David Rowley) Confusion over de-duplication of such calls could result in errors like WindowFunc with winref 2 assigned to WindowAgg with winref 1.", "commit_aliases": ["4297a3519", "7027dd499", "cae812741", "ccde5be68"], "source_commits": ["ccde5be68"], "source_entry_id": "18.2/changes/014", "db_id": "4b3957065e21f608944a30199fa8b0a3", "patch_ids": ["fa4bfd3b1304bc4a95cf26b478914aab"], "statement_hash": "392afbf3348f0707bd8555b9a123869d33484aee1e6cef1a77967d81fcb6e73e", "relations": [{"rule": 2, "type": "equivalent", "target": "74b77b8e6ab0ea1bc12ae9243c478255", "evidence": {"same_day": true, "patch_ids": ["fa4bfd3b1304bc4a95cf26b478914aab"], "statement_hash": "392afbf3348f0707bd8555b9a123869d33484aee1e6cef1a77967d81fcb6e73e"}}, {"rule": 2, "type": "equivalent", "target": "7ac52809fbfe8babeb50e09de2f149dc", "evidence": {"same_day": true, "patch_ids": ["fa4bfd3b1304bc4a95cf26b478914aab"], "statement_hash": "392afbf3348f0707bd8555b9a123869d33484aee1e6cef1a77967d81fcb6e73e"}}]}}, {"id": "18.2-61e225cdb2ce1f36", "source_entry_id": "18.2/changes/020", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Allow indexscans on partial hash indexes even when the index's predicate implies the truth of the WHERE clause", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-845083cdcffc5df5", "source_entry_id": "17.8/changes/009", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Allow indexscans on partial hash indexes even when the index's predicate implies the truth of the WHERE clause"}], "entry": {"id": "18.2-61e225cdb2ce1f36", "cves": [], "html": "Allow indexscans on partial hash indexes even when the index's predicate implies the truth of the WHERE clause (Tom Lane) §
\nNormally we drop a WHERE clause that is implied by the predicate, since it's pointless to test it; it must hold for every index entry. However that can prevent creation of an indexscan plan if the index is one that requires a WHERE clause on the leading index key, as hash indexes do. Don't drop implied clauses when considering such an index.
", "text": "Allow indexscans on partial hash indexes even when the index's predicate implies the truth of the WHERE clause (Tom Lane) § Normally we drop a WHERE clause that is implied by the predicate, since it's pointless to test it; it must hold for every index entry. However that can prevent creation of an indexscan plan if the index is one that requires a WHERE clause on the leading index key, as hash indexes do. Don't drop implied clauses when considering such an index.", "title": "Allow indexscans on partial hash indexes even when the index's predicate implies the truth of the WHERE clause", "commits": ["a212877dc"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "940c123fdafbfd46e4011394da6445710439a88097114f626d24be102a557cfb", "section_path": ["Changes"], "commit_groups": [["5528e8d10", "9e77323fc", "a212877dc", "b497766a8", "e79b27662", "f19502f04"]], "identity_text": "Allow indexscans on partial hash indexes even when the index's predicate implies the truth of the WHERE clause (Tom Lane) Normally we drop a WHERE clause that is implied by the predicate, since it's pointless to test it; it must hold for every index entry. However that can prevent creation of an indexscan plan if the index is one that requires a WHERE clause on the leading index key, as hash indexes do. Don't drop implied clauses when considering such an index.", "commit_aliases": ["5528e8d10", "9e77323fc", "a212877dc", "b497766a8", "e79b27662", "f19502f04"], "source_commits": ["a212877dc"], "source_entry_id": "18.2/changes/020", "db_id": "ed2a57d1a47eb0ac687c6d995081429b", "patch_ids": ["371e0fb22b0b4c3ce7000e6e8780d0ab"], "statement_hash": "978f69342e3def3b8ca6380a3dacf1634fda30feb1db7c0f20d33cad5e6b4dac", "relations": [{"rule": 2, "type": "equivalent", "target": "46491fe43c6b06ae0b36463bb9ec508d", "evidence": {"same_day": true, "patch_ids": ["371e0fb22b0b4c3ce7000e6e8780d0ab"], "statement_hash": "978f69342e3def3b8ca6380a3dacf1634fda30feb1db7c0f20d33cad5e6b4dac"}}, {"rule": 2, "type": "equivalent", "target": "b1cd37aac266a35b85d498fbf852a341", "evidence": {"same_day": true, "patch_ids": ["371e0fb22b0b4c3ce7000e6e8780d0ab"], "statement_hash": "978f69342e3def3b8ca6380a3dacf1634fda30feb1db7c0f20d33cad5e6b4dac"}}, {"rule": 2, "type": "equivalent", "target": "be90b044d06ac445fb5ba563113882da", "evidence": {"same_day": true, "patch_ids": ["371e0fb22b0b4c3ce7000e6e8780d0ab"], "statement_hash": "978f69342e3def3b8ca6380a3dacf1634fda30feb1db7c0f20d33cad5e6b4dac"}}, {"rule": 2, "type": "equivalent", "target": "f2b4b6b2c2b28f97888464f6ce6ad3fa", "evidence": {"same_day": true, "patch_ids": ["371e0fb22b0b4c3ce7000e6e8780d0ab"], "statement_hash": "978f69342e3def3b8ca6380a3dacf1634fda30feb1db7c0f20d33cad5e6b4dac"}}]}}, {"id": "18.2-569b26ba06e60ceb", "source_entry_id": "18.2/changes/021", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Do not emit WAL for unlogged BRIN indexes", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-91a20d38e502ab15", "source_entry_id": "17.8/changes/010", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Do not emit WAL for unlogged BRIN indexes"}], "entry": {"id": "18.2-569b26ba06e60ceb", "cves": [], "html": "Do not emit WAL for unlogged BRIN indexes (Kirill Reshke) §
\nOne seldom-taken code path incorrectly emitted a WAL record relating to a BRIN index even if the index was marked unlogged. Crash recovery would then fail to replay that record, complaining that the file already exists.
", "text": "Do not emit WAL for unlogged BRIN indexes (Kirill Reshke) § One seldom-taken code path incorrectly emitted a WAL record relating to a BRIN index even if the index was marked unlogged. Crash recovery would then fail to replay that record, complaining that the file already exists.", "title": "Do not emit WAL for unlogged BRIN indexes", "commits": ["d77a5f981"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "4916ac87639a386a3af9712d074cb0e4c0ef07680859c6be41649e5274b34329", "section_path": ["Changes"], "commit_groups": [["460d97020", "4b6d096a0", "951b60f7a", "a5277700e", "ab4256869", "d77a5f981"]], "identity_text": "Do not emit WAL for unlogged BRIN indexes (Kirill Reshke) One seldom-taken code path incorrectly emitted a WAL record relating to a BRIN index even if the index was marked unlogged. Crash recovery would then fail to replay that record, complaining that the file already exists.", "commit_aliases": ["460d97020", "4b6d096a0", "951b60f7a", "a5277700e", "ab4256869", "d77a5f981"], "source_commits": ["d77a5f981"], "source_entry_id": "18.2/changes/021", "db_id": "0937f4c4aaa8ff37a519ed8e315b4268", "patch_ids": ["548b71793684eb7a3b4dc68f7e774931"], "statement_hash": "14bc5b9ab44a24425a2aaf5ae8e65539cd475fa7e779fdd338932c2bec859e4f", "relations": [{"rule": 2, "type": "equivalent", "target": "293acf13040f24b30864b10bd699a3a0", "evidence": {"same_day": true, "patch_ids": ["548b71793684eb7a3b4dc68f7e774931"], "statement_hash": "14bc5b9ab44a24425a2aaf5ae8e65539cd475fa7e779fdd338932c2bec859e4f"}}, {"rule": 2, "type": "equivalent", "target": "5e595f6d6c44016c34bfdd305d261a1f", "evidence": {"same_day": true, "patch_ids": ["548b71793684eb7a3b4dc68f7e774931"], "statement_hash": "14bc5b9ab44a24425a2aaf5ae8e65539cd475fa7e779fdd338932c2bec859e4f"}}, {"rule": 2, "type": "equivalent", "target": "a7d18f384393c9a111537f87704719de", "evidence": {"same_day": true, "patch_ids": ["548b71793684eb7a3b4dc68f7e774931"], "statement_hash": "14bc5b9ab44a24425a2aaf5ae8e65539cd475fa7e779fdd338932c2bec859e4f"}}, {"rule": 2, "type": "equivalent", "target": "e2905bab9de145b119d05715dee49169", "evidence": {"same_day": true, "patch_ids": ["548b71793684eb7a3b4dc68f7e774931"], "statement_hash": "14bc5b9ab44a24425a2aaf5ae8e65539cd475fa7e779fdd338932c2bec859e4f"}}]}}, {"id": "18.2-0a2a82e68a475c0b", "source_entry_id": "18.2/changes/023", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Prevent truncation of CLOG that is still needed by unread NOTIFY messages", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-4391ac8372980d16", "source_entry_id": "17.8/changes/011", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Prevent truncation of CLOG that is still needed by unread NOTIFY messages"}], "entry": {"id": "18.2-0a2a82e68a475c0b", "cves": [], "html": "Prevent truncation of CLOG that is still needed by unread NOTIFY messages (Joel Jacobson, Heikki Linnakangas) § § §
This fix prevents “could not access status of transaction” errors when a backend is slow to absorb NOTIFY messages.
Escalate errors occurring during NOTIFY message processing to FATAL, i.e. close the connection (Heikki Linnakangas) §
Formerly, if a backend got an error while absorbing a NOTIFY message, it would advance past that message, report the error to the client, and move on. That behavior was fraught with problems though. One big concern is that the client has no good way to know that a notification was lost, and certainly no way to know what was in it. Depending on the application logic, missing a notification could cause the application to get stuck waiting, for example. Also, any remaining messages would not get processed until someone sent a new NOTIFY.
Also, if the connection is idle at the time of receiving a NOTIFY signal, any ERROR would be escalated to FATAL anyway, due to unrelated concerns. Therefore, we've chosen to make that happen in all cases, for consistency and to provide a clear signal to the application that it might have missed some notifications.
Fix erroneous counting of updates in EXPLAIN ANALYZE MERGE with a concurrent update (Dean Rasheed) §
This situation led to an incorrect count of “skipped” tuples in EXPLAIN's output, or to an assertion failure in an assert-enabled build.
Fix bug in following update chain when locking a tuple (Jasper Smit) §
\nThis code path neglected to check the xmin of the first new tuple in the update chain, making it possible to lock an unrelated tuple if the original updater aborted and the space was immediately reclaimed by VACUUM and then re-used. That could cause unexpected transaction delays or deadlocks. Errors associated with having identified the wrong tuple have also been observed.
Fix incorrect handling of incremental backups of large tables (Robert Haas, Oleg Tkachenko) §
\nIf a table exceeding 1GB (or in general, the installation's segment size) is truncated by VACUUM between the base backup and the incremental backup, pg_combinebackup could fail with an error about “truncation block length in excess of segment size”. This prevented restoring the incremental backup.
Fix potential backend process crash at process exit due to trying to release a lock in an already-unmapped shared memory segment (Rahila Syed) §
", "text": "Fix potential backend process crash at process exit due to trying to release a lock in an already-unmapped shared memory segment (Rahila Syed) §", "title": "Fix potential backend process crash at process exit due to trying to release a lock in an already-unmapped shared memory segment", "commits": ["1943ceb38"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "180197e1a61f1d8e7a43fa25597e6fab706a833f5b2345e7c840fbb264d9daf7", "section_path": ["Changes"], "commit_groups": [["1943ceb38", "4071fe900", "980b7c736", "9cbb1d21d", "b926ff137", "f6df78173"]], "identity_text": "Fix potential backend process crash at process exit due to trying to release a lock in an already-unmapped shared memory segment (Rahila Syed)", "commit_aliases": ["1943ceb38", "4071fe900", "980b7c736", "9cbb1d21d", "b926ff137", "f6df78173"], "source_commits": ["1943ceb38"], "source_entry_id": "18.2/changes/029", "db_id": "5ad3db5c0edaa4934f3f9d9b4709c52d", "patch_ids": ["126653f8f3297278586a3928c56e06f3"], "statement_hash": "92dcd4d1c3bd738dad9644948eb1cd6efd94bdefcd3219e424732f890c0bceb3", "relations": [{"rule": 2, "type": "equivalent", "target": "125f7282ee77b2dbf96db553539c22c4", "evidence": {"same_day": true, "patch_ids": ["126653f8f3297278586a3928c56e06f3"], "statement_hash": "92dcd4d1c3bd738dad9644948eb1cd6efd94bdefcd3219e424732f890c0bceb3"}}, {"rule": 2, "type": "equivalent", "target": "45af7190ae2808ef37392b8f701626cf", "evidence": {"same_day": true, "patch_ids": ["126653f8f3297278586a3928c56e06f3"], "statement_hash": "92dcd4d1c3bd738dad9644948eb1cd6efd94bdefcd3219e424732f890c0bceb3"}}, {"rule": 2, "type": "equivalent", "target": "7be6eebc70de0b6a710a45541a4092f0", "evidence": {"same_day": true, "patch_ids": ["126653f8f3297278586a3928c56e06f3"], "statement_hash": "92dcd4d1c3bd738dad9644948eb1cd6efd94bdefcd3219e424732f890c0bceb3"}}, {"rule": 2, "type": "equivalent", "target": "d2811b8c558ee3336f69ce2dee648262", "evidence": {"same_day": true, "patch_ids": ["126653f8f3297278586a3928c56e06f3"], "statement_hash": "92dcd4d1c3bd738dad9644948eb1cd6efd94bdefcd3219e424732f890c0bceb3"}}]}}, {"id": "18.2-8b23c352cad22240", "source_entry_id": "18.2/changes/031", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Guard against incorrect truncation of the multixact log after a crash", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-9e854c237f5aabf9", "source_entry_id": "17.8/changes/018", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Guard against incorrect truncation of the multixact log after a crash"}], "entry": {"id": "18.2-8b23c352cad22240", "cves": [], "html": "Guard against incorrect truncation of the multixact log after a crash (Heikki Linnakangas) §
", "text": "Guard against incorrect truncation of the multixact log after a crash (Heikki Linnakangas) §", "title": "Guard against incorrect truncation of the multixact log after a crash", "commits": ["09532a78b"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "b4d9d073ee0c207fd4db7a4b87e25dfeb96b650630b7eb32cdefaef578df0398", "section_path": ["Changes"], "commit_groups": [["09532a78b", "102bdaa9b", "46be454ca", "a563ac619", "c7946e6f3", "d3ad4cef6"]], "identity_text": "Guard against incorrect truncation of the multixact log after a crash (Heikki Linnakangas)", "commit_aliases": ["09532a78b", "102bdaa9b", "46be454ca", "a563ac619", "c7946e6f3", "d3ad4cef6"], "source_commits": ["09532a78b"], "source_entry_id": "18.2/changes/031", "db_id": "3a7694cde691f1c0a64647d256362d79", "patch_ids": ["67a73a4872f6b3f005ad7fe4e9077027"], "statement_hash": "dfecdaac190eb4e172c44ceae68abad6d5cc283f60c6a947351bcef843a944ad", "relations": [{"rule": 2, "type": "equivalent", "target": "06c8d0231b48925fde45dbbe5447711a", "evidence": {"same_day": true, "patch_ids": ["67a73a4872f6b3f005ad7fe4e9077027"], "statement_hash": "dfecdaac190eb4e172c44ceae68abad6d5cc283f60c6a947351bcef843a944ad"}}, {"rule": 2, "type": "equivalent", "target": "423a226c0afa155ba2f8b3bf4d809b9b", "evidence": {"same_day": true, "patch_ids": ["67a73a4872f6b3f005ad7fe4e9077027"], "statement_hash": "dfecdaac190eb4e172c44ceae68abad6d5cc283f60c6a947351bcef843a944ad"}}, {"rule": 2, "type": "equivalent", "target": "543d98a0d64e54acd061d5327cda0d92", "evidence": {"same_day": true, "patch_ids": ["67a73a4872f6b3f005ad7fe4e9077027"], "statement_hash": "dfecdaac190eb4e172c44ceae68abad6d5cc283f60c6a947351bcef843a944ad"}}, {"rule": 2, "type": "equivalent", "target": "98b43daf45e235647020ad11a022bebb", "evidence": {"same_day": true, "patch_ids": ["67a73a4872f6b3f005ad7fe4e9077027"], "statement_hash": "dfecdaac190eb4e172c44ceae68abad6d5cc283f60c6a947351bcef843a944ad"}}]}}, {"id": "18.2-08c685de487e23d3", "source_entry_id": "18.2/changes/032", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix possibly mis-encoded result of pg_stat_get_backend_activity()", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-5b4587fee1692efc", "source_entry_id": "17.8/changes/019", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix possibly mis-encoded result of pg_stat_get_backend_activity()"}], "entry": {"id": "18.2-08c685de487e23d3", "cves": [], "html": "Fix possibly mis-encoded result of pg_stat_get_backend_activity() (Chao Li) §
The shared-memory buffer holding a session's activity string can end with an incomplete multibyte character. Readers are supposed to truncate off any such incomplete character, but this function failed to do so.
", "text": "Fix possibly mis-encoded result of pg_stat_get_backend_activity() (Chao Li) § The shared-memory buffer holding a session's activity string can end with an incomplete multibyte character. Readers are supposed to truncate off any such incomplete character, but this function failed to do so.", "title": "Fix possibly mis-encoded result of pg_stat_get_backend_activity()", "commits": ["06907e864"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "29530afde8264c142f5ab853dcdea08e713d94dabb80e54bdacfb0c892aafb74", "section_path": ["Changes"], "commit_groups": [["06907e864", "300575fe2", "36b8f4974", "52b27f585", "c48829ed8", "ea3524cff"]], "identity_text": "Fix possibly mis-encoded result of pg_stat_get_backend_activity() (Chao Li) The shared-memory buffer holding a session's activity string can end with an incomplete multibyte character. Readers are supposed to truncate off any such incomplete character, but this function failed to do so.", "commit_aliases": ["06907e864", "300575fe2", "36b8f4974", "52b27f585", "c48829ed8", "ea3524cff"], "source_commits": ["06907e864"], "source_entry_id": "18.2/changes/032", "db_id": "2011af15ea6d97b67e6182e61860c8c7", "patch_ids": ["b809be4e7827182df22fb9f71f25cf1d"], "statement_hash": "18f9c2bfb3fe8f5033800a59729a09db060ed74ea247b46aee7ee09268737178", "relations": [{"rule": 2, "type": "equivalent", "target": "1d61f99b846c4ede8289346c443c6eab", "evidence": {"same_day": true, "patch_ids": ["b809be4e7827182df22fb9f71f25cf1d"], "statement_hash": "18f9c2bfb3fe8f5033800a59729a09db060ed74ea247b46aee7ee09268737178"}}, {"rule": 2, "type": "equivalent", "target": "3fc6fbb291fd58ddb3732e1040a55913", "evidence": {"same_day": true, "patch_ids": ["b809be4e7827182df22fb9f71f25cf1d"], "statement_hash": "18f9c2bfb3fe8f5033800a59729a09db060ed74ea247b46aee7ee09268737178"}}, {"rule": 2, "type": "equivalent", "target": "962171149258cdfb98c25d6f7cda03e4", "evidence": {"same_day": true, "patch_ids": ["b809be4e7827182df22fb9f71f25cf1d"], "statement_hash": "18f9c2bfb3fe8f5033800a59729a09db060ed74ea247b46aee7ee09268737178"}}, {"rule": 2, "type": "equivalent", "target": "c6e97abc5a7f6b7dd2f4f8bbf960d054", "evidence": {"same_day": true, "patch_ids": ["b809be4e7827182df22fb9f71f25cf1d"], "statement_hash": "18f9c2bfb3fe8f5033800a59729a09db060ed74ea247b46aee7ee09268737178"}}]}}, {"id": "18.2-92cabc87c606add7", "source_entry_id": "18.2/changes/033", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Guard against recursive memory context logging", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-a1b611399d727246", "source_entry_id": "17.8/changes/020", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Guard against recursive memory context logging"}], "entry": {"id": "18.2-92cabc87c606add7", "cves": [], "html": "Guard against recursive memory context logging (Fujii Masao) §
\nA constant flow of signals requesting memory context logging could cause recursive execution of the logging code, which in theory could lead to stack overflow.
", "text": "Guard against recursive memory context logging (Fujii Masao) § A constant flow of signals requesting memory context logging could cause recursive execution of the logging code, which in theory could lead to stack overflow.", "title": "Guard against recursive memory context logging", "commits": ["b863d8d87"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "61d8b79df234e3b08f9a7ceddb5eb530fc8c77363e6950b382ec3018c466cec6", "section_path": ["Changes"], "commit_groups": [["0fc2f533a", "1a9a49699", "3853f6168", "699293d27", "b3ccb0a2c", "b863d8d87"]], "identity_text": "Guard against recursive memory context logging (Fujii Masao) A constant flow of signals requesting memory context logging could cause recursive execution of the logging code, which in theory could lead to stack overflow.", "commit_aliases": ["0fc2f533a", "1a9a49699", "3853f6168", "699293d27", "b3ccb0a2c", "b863d8d87"], "source_commits": ["b863d8d87"], "source_entry_id": "18.2/changes/033", "db_id": "e532d3e562a8bcd039083d7610c4fe02", "patch_ids": ["5f2e29ee0f0a335aba7ffbb8c5262c9e"], "statement_hash": "b5c2d3f4f692a615b47c23616523ca27bef0dcd03455868cfc0d756ea0575dd4", "relations": [{"rule": 2, "type": "equivalent", "target": "6911fcfb9b3a10c2cb527c328b7e80dd", "evidence": {"same_day": true, "patch_ids": ["5f2e29ee0f0a335aba7ffbb8c5262c9e"], "statement_hash": "b5c2d3f4f692a615b47c23616523ca27bef0dcd03455868cfc0d756ea0575dd4"}}, {"rule": 2, "type": "equivalent", "target": "69b5630e62f581864e385c3537959829", "evidence": {"same_day": true, "patch_ids": ["5f2e29ee0f0a335aba7ffbb8c5262c9e"], "statement_hash": "b5c2d3f4f692a615b47c23616523ca27bef0dcd03455868cfc0d756ea0575dd4"}}, {"rule": 2, "type": "equivalent", "target": "76d6a4cdde5956fd5fdf83af6a0f6953", "evidence": {"same_day": true, "patch_ids": ["5f2e29ee0f0a335aba7ffbb8c5262c9e"], "statement_hash": "b5c2d3f4f692a615b47c23616523ca27bef0dcd03455868cfc0d756ea0575dd4"}}, {"rule": 2, "type": "equivalent", "target": "cdc054743d9f7923ca54a8a0dd5eba4d", "evidence": {"same_day": true, "patch_ids": ["5f2e29ee0f0a335aba7ffbb8c5262c9e"], "statement_hash": "b5c2d3f4f692a615b47c23616523ca27bef0dcd03455868cfc0d756ea0575dd4"}}]}}, {"id": "18.2-f56daebc6196999a", "source_entry_id": "18.2/changes/034", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix memory context usage when reinitializing a parallel execution context", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-cdcf22c5f5200747", "source_entry_id": "17.8/changes/021", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix memory context usage when reinitializing a parallel execution context"}], "entry": {"id": "18.2-f56daebc6196999a", "cves": [], "html": "Fix memory context usage when reinitializing a parallel execution context (Jakub Wartak, Jeevan Chalke) §
\nThis error could result in a crash due to a subsidiary data structure having a shorter lifespan than the parallel context. The problem is not known to be reachable using only core PostgreSQL, but we have reports of trouble in extensions.
", "text": "Fix memory context usage when reinitializing a parallel execution context (Jakub Wartak, Jeevan Chalke) § This error could result in a crash due to a subsidiary data structure having a shorter lifespan than the parallel context. The problem is not known to be reachable using only core PostgreSQL, but we have reports of trouble in extensions.", "title": "Fix memory context usage when reinitializing a parallel execution context", "commits": ["57df5ab80"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "8b856562e302886b3980dd226fc10bab94afbb0d74beb879683b401621aa77ee", "section_path": ["Changes"], "commit_groups": [["12c2f843c", "1d0fc2499", "1d9f7fbba", "57df5ab80", "bd2726d3e", "f1a6e622b"]], "identity_text": "Fix memory context usage when reinitializing a parallel execution context (Jakub Wartak, Jeevan Chalke) This error could result in a crash due to a subsidiary data structure having a shorter lifespan than the parallel context. The problem is not known to be reachable using only core PostgreSQL, but we have reports of trouble in extensions.", "commit_aliases": ["12c2f843c", "1d0fc2499", "1d9f7fbba", "57df5ab80", "bd2726d3e", "f1a6e622b"], "source_commits": ["57df5ab80"], "source_entry_id": "18.2/changes/034", "db_id": "a0538505db5e86d813d403a8571068b8", "patch_ids": ["4c076010d0ab56e908326be07c1b73c6"], "statement_hash": "b3c3fe87f6d12f96eb766c99214c419b7d35f4a67646f0e2ac1a8abac3576cb0", "relations": [{"rule": 2, "type": "equivalent", "target": "0e538a4d4cac5aac8cab0d86cc46e6d8", "evidence": {"same_day": true, "patch_ids": ["4c076010d0ab56e908326be07c1b73c6"], "statement_hash": "b3c3fe87f6d12f96eb766c99214c419b7d35f4a67646f0e2ac1a8abac3576cb0"}}, {"rule": 2, "type": "equivalent", "target": "770932eb6650d49472c43e2db5c83969", "evidence": {"same_day": true, "patch_ids": ["4c076010d0ab56e908326be07c1b73c6"], "statement_hash": "b3c3fe87f6d12f96eb766c99214c419b7d35f4a67646f0e2ac1a8abac3576cb0"}}, {"rule": 2, "type": "equivalent", "target": "82f0fec30baf25cedac6f47fedd86a1a", "evidence": {"same_day": true, "patch_ids": ["4c076010d0ab56e908326be07c1b73c6"], "statement_hash": "b3c3fe87f6d12f96eb766c99214c419b7d35f4a67646f0e2ac1a8abac3576cb0"}}, {"rule": 2, "type": "equivalent", "target": "c0e0fccdb1ff80df5a7c450903b3c742", "evidence": {"same_day": true, "patch_ids": ["4c076010d0ab56e908326be07c1b73c6"], "statement_hash": "b3c3fe87f6d12f96eb766c99214c419b7d35f4a67646f0e2ac1a8abac3576cb0"}}]}}, {"id": "18.2-0eb611cc5bc18380", "source_entry_id": "18.2/changes/035", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Set next multixid's offset when creating a new multixid, to remove the wait loop that was needed in corner cases", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-351e263e26b0031c", "source_entry_id": "17.8/changes/022", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Set next multixid's offset when creating a new multixid, to remove the wait loop that was needed in corner cases"}], "entry": {"id": "18.2-0eb611cc5bc18380", "cves": [], "html": "Set next multixid's offset when creating a new multixid, to remove the wait loop that was needed in corner cases (Andrey Borodin) § §
\nThe previous logic could get stuck waiting for an update that would never occur.
", "text": "Set next multixid's offset when creating a new multixid, to remove the wait loop that was needed in corner cases (Andrey Borodin) § § The previous logic could get stuck waiting for an update that would never occur.", "title": "Set next multixid's offset when creating a new multixid, to remove the wait loop that was needed in corner cases", "commits": ["02ba5e3be", "e46041fd9"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "14e17e5ba91c9882b49a56627e0b767d34ca9a5f5d8ada7687bd25381c2eb477", "section_path": ["Changes"], "commit_groups": [["02ba5e3be", "489695554", "4d689a176", "4d936c3ff", "b9a02b978", "cad40cec2"], ["635166913", "789d65364", "81416e101", "8ba61bc06", "8cfb174a6", "e46041fd9"]], "identity_text": "Set next multixid's offset when creating a new multixid, to remove the wait loop that was needed in corner cases (Andrey Borodin) The previous logic could get stuck waiting for an update that would never occur.", "commit_aliases": ["02ba5e3be", "489695554", "4d689a176", "4d936c3ff", "635166913", "789d65364", "81416e101", "8ba61bc06", "8cfb174a6", "b9a02b978", "cad40cec2", "e46041fd9"], "source_commits": ["02ba5e3be", "e46041fd9"], "source_entry_id": "18.2/changes/035", "db_id": "9d39be361a73eeb011b1508852d458c4", "patch_ids": ["7a935cadcf10c6b2317e3231e31323b6", "ee608729a6ebedc95a84b653d7e6f795"], "statement_hash": "3820414d3ddce5f6a358db922abd2d2d57a70d8990ca5c41a3b91f78a7e3261d", "relations": [{"rule": 2, "type": "equivalent", "target": "1d8beb2475d7ec3ee5619d442f62f4e4", "evidence": {"same_day": true, "patch_ids": ["7a935cadcf10c6b2317e3231e31323b6", "ee608729a6ebedc95a84b653d7e6f795"], "statement_hash": "3820414d3ddce5f6a358db922abd2d2d57a70d8990ca5c41a3b91f78a7e3261d"}}, {"rule": 2, "type": "equivalent", "target": "2b4c07606e0901ac70bb0fbb4680ebbe", "evidence": {"same_day": true, "patch_ids": ["7a935cadcf10c6b2317e3231e31323b6", "ee608729a6ebedc95a84b653d7e6f795"], "statement_hash": "3820414d3ddce5f6a358db922abd2d2d57a70d8990ca5c41a3b91f78a7e3261d"}}, {"rule": 2, "type": "equivalent", "target": "df073012abdc28126571ebecafb9c308", "evidence": {"same_day": true, "patch_ids": ["7a935cadcf10c6b2317e3231e31323b6", "ee608729a6ebedc95a84b653d7e6f795"], "statement_hash": "3820414d3ddce5f6a358db922abd2d2d57a70d8990ca5c41a3b91f78a7e3261d"}}, {"rule": 2, "type": "equivalent", "target": "fff819d80d05a70e4ebf82ab7f9c951a", "evidence": {"same_day": true, "patch_ids": ["7a935cadcf10c6b2317e3231e31323b6", "ee608729a6ebedc95a84b653d7e6f795"], "statement_hash": "3820414d3ddce5f6a358db922abd2d2d57a70d8990ca5c41a3b91f78a7e3261d"}}]}}, {"id": "18.2-598e6b46a303e445", "source_entry_id": "18.2/changes/036", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Avoid rewriting data-modifying CTEs more than once", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-fed0bc33b201283d", "source_entry_id": "17.8/changes/023", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Avoid rewriting data-modifying CTEs more than once"}], "entry": {"id": "18.2-598e6b46a303e445", "cves": [], "html": "Avoid rewriting data-modifying CTEs more than once (Bernice Southey, Dean Rasheed) §
\nFormerly, when updating an auto-updatable view or a relation with rules, if the original query had any data-modifying CTEs, the rewriter would rewrite those CTEs multiple times due to recursion. This was inefficient and could produce false errors if a CTE included an update of an always-generated column.
", "text": "Avoid rewriting data-modifying CTEs more than once (Bernice Southey, Dean Rasheed) § Formerly, when updating an auto-updatable view or a relation with rules, if the original query had any data-modifying CTEs, the rewriter would rewrite those CTEs multiple times due to recursion. This was inefficient and could produce false errors if a CTE included an update of an always-generated column.", "title": "Avoid rewriting data-modifying CTEs more than once", "commits": ["b880d9a02"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "44ccaf69d17829570c1688499434a08725e7185f58e5fd6536d6717c13cb3725", "section_path": ["Changes"], "commit_groups": [["134a8ee22", "2d5b97b8c", "3881561d7", "4d288e33b", "b880d9a02", "c09096503"]], "identity_text": "Avoid rewriting data-modifying CTEs more than once (Bernice Southey, Dean Rasheed) Formerly, when updating an auto-updatable view or a relation with rules, if the original query had any data-modifying CTEs, the rewriter would rewrite those CTEs multiple times due to recursion. This was inefficient and could produce false errors if a CTE included an update of an always-generated column.", "commit_aliases": ["134a8ee22", "2d5b97b8c", "3881561d7", "4d288e33b", "b880d9a02", "c09096503"], "source_commits": ["b880d9a02"], "source_entry_id": "18.2/changes/036", "db_id": "b1252119d1b5ac0ac5230ba9b7fb844b", "patch_ids": ["e0f79f9c321f69bef485ae997c61c414"], "statement_hash": "45d7e282599aa005c97ba4f77c0f61900b8c96a1633aa3b113857a26515155bb", "relations": [{"rule": 2, "type": "equivalent", "target": "6e6c8a0f6889fba17b9d4ea6308a8d7a", "evidence": {"same_day": true, "patch_ids": ["e0f79f9c321f69bef485ae997c61c414"], "statement_hash": "45d7e282599aa005c97ba4f77c0f61900b8c96a1633aa3b113857a26515155bb"}}, {"rule": 2, "type": "equivalent", "target": "c9710e1b97bbf384a5536e25246c2c1e", "evidence": {"same_day": true, "patch_ids": ["e0f79f9c321f69bef485ae997c61c414"], "statement_hash": "45d7e282599aa005c97ba4f77c0f61900b8c96a1633aa3b113857a26515155bb"}}, {"rule": 2, "type": "equivalent", "target": "f467408bfd650872bf1654f4ee4ec70d", "evidence": {"same_day": true, "patch_ids": ["e0f79f9c321f69bef485ae997c61c414"], "statement_hash": "45d7e282599aa005c97ba4f77c0f61900b8c96a1633aa3b113857a26515155bb"}}, {"rule": 2, "type": "equivalent", "target": "fa9d76713707441eef7a725233377166", "evidence": {"same_day": true, "patch_ids": ["e0f79f9c321f69bef485ae997c61c414"], "statement_hash": "45d7e282599aa005c97ba4f77c0f61900b8c96a1633aa3b113857a26515155bb"}}]}}, {"id": "18.2-44b11be419e13584", "source_entry_id": "18.2/changes/037", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Allow retrying initialization of a DSM registry entry", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-be3128d810d25a5b", "source_entry_id": "17.8/changes/024", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Allow retrying initialization of a DSM registry entry"}], "entry": {"id": "18.2-44b11be419e13584", "cves": [], "html": "Allow retrying initialization of a DSM registry entry (Nathan Bossart) §
\nIf we fail partway through initialization of a dynamic shared memory entry, allow the next attempt to use that entry to retry initialization. Previously the entry was left in a permanently-failed state.
", "text": "Allow retrying initialization of a DSM registry entry (Nathan Bossart) § If we fail partway through initialization of a dynamic shared memory entry, allow the next attempt to use that entry to retry initialization. Previously the entry was left in a permanently-failed state.", "title": "Allow retrying initialization of a DSM registry entry", "commits": ["b83bcc0df"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "1d9998e86e6642435db7d6ef25747b4e039b914ac3ac16e0428251aa6d99ebbb", "section_path": ["Changes"], "commit_groups": [["2fc5c5062", "b83bcc0df", "dbdc717ac"]], "identity_text": "Allow retrying initialization of a DSM registry entry (Nathan Bossart) If we fail partway through initialization of a dynamic shared memory entry, allow the next attempt to use that entry to retry initialization. Previously the entry was left in a permanently-failed state.", "commit_aliases": ["2fc5c5062", "b83bcc0df", "dbdc717ac"], "source_commits": ["b83bcc0df"], "source_entry_id": "18.2/changes/037", "db_id": "35cb139db6fcca1cb726591686762d5e", "patch_ids": ["e358cc1d91845e3da8aaed14c787dcd0"], "statement_hash": "6f8c9dfe61ba11aac117897b8a16e2c125090ad069d80ce5e2ebe812b2891a73", "relations": [{"rule": 2, "type": "equivalent", "target": "5039c49f944e0ea8e42e7eb5859d47f5", "evidence": {"same_day": true, "patch_ids": ["e358cc1d91845e3da8aaed14c787dcd0"], "statement_hash": "6f8c9dfe61ba11aac117897b8a16e2c125090ad069d80ce5e2ebe812b2891a73"}}]}}, {"id": "18.2-48e29718af30085d", "source_entry_id": "18.2/changes/040", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fail recovery if WAL does not exist back to the redo point indicated by the checkpoint record", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-3d4d2474ea729f43", "source_entry_id": "17.8/changes/025", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fail recovery if WAL does not exist back to the redo point indicated by the checkpoint record"}], "entry": {"id": "18.2-48e29718af30085d", "cves": [], "html": "Fail recovery if WAL does not exist back to the redo point indicated by the checkpoint record (Nitin Jadhav) §
\nAdd an explicit check for this before starting recovery, so that no harm is done and a useful error message is provided. Previously, recovery might crash or corrupt the database in this situation.
", "text": "Fail recovery if WAL does not exist back to the redo point indicated by the checkpoint record (Nitin Jadhav) § Add an explicit check for this before starting recovery, so that no harm is done and a useful error message is provided. Previously, recovery might crash or corrupt the database in this situation.", "title": "Fail recovery if WAL does not exist back to the redo point indicated by the checkpoint record", "commits": ["68ebdf2b0"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "a97d834694985c925575808f5404b4fed36f485d77bdb9ddc03de6d8e2eda696", "section_path": ["Changes"], "commit_groups": [["14161bca4", "1aa57e9ed", "68ebdf2b0", "95ef6f490", "dc7c77f82", "f5927da4f"]], "identity_text": "Fail recovery if WAL does not exist back to the redo point indicated by the checkpoint record (Nitin Jadhav) Add an explicit check for this before starting recovery, so that no harm is done and a useful error message is provided. Previously, recovery might crash or corrupt the database in this situation.", "commit_aliases": ["14161bca4", "1aa57e9ed", "68ebdf2b0", "95ef6f490", "dc7c77f82", "f5927da4f"], "source_commits": ["68ebdf2b0"], "source_entry_id": "18.2/changes/040", "db_id": "afebd143b96e516829ea82f80f213765", "patch_ids": ["4b87107464945d5170bed63f81ff3790"], "statement_hash": "3acaee6f8628ca0f43630afaa8799cc5ced91cfb215bf493f91ad515f4af1034", "relations": [{"rule": 2, "type": "equivalent", "target": "011195db7fe270680db938124518987b", "evidence": {"same_day": true, "patch_ids": ["4b87107464945d5170bed63f81ff3790"], "statement_hash": "3acaee6f8628ca0f43630afaa8799cc5ced91cfb215bf493f91ad515f4af1034"}}, {"rule": 2, "type": "equivalent", "target": "3f4035b04c1c0e9ba08acef72e76fc91", "evidence": {"same_day": true, "patch_ids": ["4b87107464945d5170bed63f81ff3790"], "statement_hash": "3acaee6f8628ca0f43630afaa8799cc5ced91cfb215bf493f91ad515f4af1034"}}, {"rule": 2, "type": "equivalent", "target": "7e009c5e3ee2635f5a3f2d6750f1a823", "evidence": {"same_day": true, "patch_ids": ["4b87107464945d5170bed63f81ff3790"], "statement_hash": "3acaee6f8628ca0f43630afaa8799cc5ced91cfb215bf493f91ad515f4af1034"}}, {"rule": 2, "type": "equivalent", "target": "ea5f140766dc7aa68dd175c861036247", "evidence": {"same_day": true, "patch_ids": ["4b87107464945d5170bed63f81ff3790"], "statement_hash": "3acaee6f8628ca0f43630afaa8799cc5ced91cfb215bf493f91ad515f4af1034"}}]}}, {"id": "18.2-4ab1376a3267c027", "source_entry_id": "18.2/changes/041", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Avoid scribbling on the source query tree during ALTER PUBLICATION", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-51768104ffbbb8b1", "source_entry_id": "17.8/changes/026", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Avoid scribbling on the source query tree during ALTER PUBLICATION"}], "entry": {"id": "18.2-4ab1376a3267c027", "cves": [], "html": "Avoid scribbling on the source query tree during ALTER PUBLICATION (Sunil S) §
This error had the visible effect that an event trigger fired for the query would see only the first publish option, even if several had been specified. If such a query were set up as a prepared statement, re-executions would misbehave too.
Pass connection options specified in CREATE SUBSCRIPTION ... CONNECTION to the publisher's walsender (Fujii Masao) §
Before this fix, the options connection option (if any) was ignored, thus for example preventing setting custom server parameter values in the walsender session. It was intended for that to work, and it did work before refactoring in PostgreSQL version 15 broke it, so restore the previous behavior.
Prevent invalidation of newly created or newly synced replication slots (Zhijie Hou) § § §
\nA race condition with a concurrent checkpoint could allow WAL to be removed that is needed by the replication slot, causing the slot to immediately get marked invalid.
", "text": "Prevent invalidation of newly created or newly synced replication slots (Zhijie Hou) § § § A race condition with a concurrent checkpoint could allow WAL to be removed that is needed by the replication slot, causing the slot to immediately get marked invalid.", "title": "Prevent invalidation of newly created or newly synced replication slots", "commits": ["1c60f7236", "919c9fa13", "d3ceb2084"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "88ca5df37ed03978aa067a4d4c868b6246df884c64949b108a4266a212778954", "section_path": ["Changes"], "commit_groups": [["006dd4b2e", "24cce33c3", "3510ebeb0", "7406df605", "aae05622a", "d3ceb2084"], ["1c60f7236", "3a98f989e", "9649f1adf"], ["3243c0177", "851f6649c", "919c9fa13"]], "identity_text": "Prevent invalidation of newly created or newly synced replication slots (Zhijie Hou) A race condition with a concurrent checkpoint could allow WAL to be removed that is needed by the replication slot, causing the slot to immediately get marked invalid.", "commit_aliases": ["006dd4b2e", "1c60f7236", "24cce33c3", "3243c0177", "3510ebeb0", "3a98f989e", "7406df605", "851f6649c", "919c9fa13", "9649f1adf", "aae05622a", "d3ceb2084"], "source_commits": ["1c60f7236", "919c9fa13", "d3ceb2084"], "source_entry_id": "18.2/changes/043", "db_id": "cb75695174eb56fb419b9a98e09580cc", "patch_ids": ["52eeca007f2cc833bd086bea5398b6dd", "e27e8fc7ff675146f1b638a98637021e", "fd534fc2f99acb10d2ff04bf0f822f81"], "statement_hash": "a7634872b97f0a43a006c3dc4f9851bc65d8af6cd588b4009553b843b6ae22d9", "relations": [{"rule": 2, "type": "equivalent", "target": "2e44c2dcd00ca731067ba5c1a7a9a31c", "evidence": {"same_day": true, "patch_ids": ["52eeca007f2cc833bd086bea5398b6dd", "e27e8fc7ff675146f1b638a98637021e", "fd534fc2f99acb10d2ff04bf0f822f81"], "statement_hash": "a7634872b97f0a43a006c3dc4f9851bc65d8af6cd588b4009553b843b6ae22d9"}}, {"rule": 2, "type": "equivalent", "target": "54b2a393bc7cb86ab19eb7c660bb2004", "evidence": {"same_day": true, "patch_ids": ["52eeca007f2cc833bd086bea5398b6dd", "e27e8fc7ff675146f1b638a98637021e", "fd534fc2f99acb10d2ff04bf0f822f81"], "statement_hash": "a7634872b97f0a43a006c3dc4f9851bc65d8af6cd588b4009553b843b6ae22d9"}}, {"rule": 2, "type": "equivalent", "target": "7045b64c3c70e172ffa2ef8c1ae90896", "evidence": {"same_day": true, "patch_ids": ["52eeca007f2cc833bd086bea5398b6dd", "e27e8fc7ff675146f1b638a98637021e", "fd534fc2f99acb10d2ff04bf0f822f81"], "statement_hash": "a7634872b97f0a43a006c3dc4f9851bc65d8af6cd588b4009553b843b6ae22d9"}}, {"rule": 2, "type": "equivalent", "target": "d1a860dc00a9dc81973d46ece96b0748", "evidence": {"same_day": true, "patch_ids": ["52eeca007f2cc833bd086bea5398b6dd", "e27e8fc7ff675146f1b638a98637021e", "fd534fc2f99acb10d2ff04bf0f822f81"], "statement_hash": "a7634872b97f0a43a006c3dc4f9851bc65d8af6cd588b4009553b843b6ae22d9"}}]}}, {"id": "18.2-7907d70dfbb36d36", "source_entry_id": "18.2/changes/044", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix race condition in computing a replication slot's required xmin", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-73bf563728deef29", "source_entry_id": "17.8/changes/029", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix race condition in computing a replication slot's required xmin"}], "entry": {"id": "18.2-7907d70dfbb36d36", "cves": [], "html": "Fix race condition in computing a replication slot's required xmin (Zhijie Hou) §
\nThis could lead to the error “cannot build an initial slot snapshot as oldest safe xid follows snapshot's xmin”.
", "text": "Fix race condition in computing a replication slot's required xmin (Zhijie Hou) § This could lead to the error “cannot build an initial slot snapshot as oldest safe xid follows snapshot's xmin”.", "title": "Fix race condition in computing a replication slot's required xmin", "commits": ["fd7c86cfa"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "5b4375f3820b11314c74407155165bb30cc4d0b1dcf897beef596b8f61a11e84", "section_path": ["Changes"], "commit_groups": [["123b851ab", "2a5225b99", "57048d6e1", "821466722", "fa557d300", "fd7c86cfa"]], "identity_text": "Fix race condition in computing a replication slot's required xmin (Zhijie Hou) This could lead to the error cannot build an initial slot snapshot as oldest safe xid follows snapshot's xmin.", "commit_aliases": ["123b851ab", "2a5225b99", "57048d6e1", "821466722", "fa557d300", "fd7c86cfa"], "source_commits": ["fd7c86cfa"], "source_entry_id": "18.2/changes/044", "db_id": "669fa902ee7eb1553fc960938aa0101f", "patch_ids": ["c967ad30d8508306bc9949d6c7504333"], "statement_hash": "8dd9f0879870a4299a9d543db5674a7348ed2b9228376a7028ea153ac3afb369", "relations": [{"rule": 2, "type": "equivalent", "target": "5b75bdc74484bae30e1e7fdc965c9335", "evidence": {"same_day": true, "patch_ids": ["c967ad30d8508306bc9949d6c7504333"], "statement_hash": "8dd9f0879870a4299a9d543db5674a7348ed2b9228376a7028ea153ac3afb369"}}, {"rule": 2, "type": "equivalent", "target": "8dfd1735c21afd64306b7ba15b0a34a0", "evidence": {"same_day": true, "patch_ids": ["c967ad30d8508306bc9949d6c7504333"], "statement_hash": "8dd9f0879870a4299a9d543db5674a7348ed2b9228376a7028ea153ac3afb369"}}, {"rule": 2, "type": "equivalent", "target": "97d0bb3c79bb34e32cf7ac9c088a6cc5", "evidence": {"same_day": true, "patch_ids": ["c967ad30d8508306bc9949d6c7504333"], "statement_hash": "8dd9f0879870a4299a9d543db5674a7348ed2b9228376a7028ea153ac3afb369"}}, {"rule": 2, "type": "equivalent", "target": "ed4968909e48309a69552757b02c2ad7", "evidence": {"same_day": true, "patch_ids": ["c967ad30d8508306bc9949d6c7504333"], "statement_hash": "8dd9f0879870a4299a9d543db5674a7348ed2b9228376a7028ea153ac3afb369"}}]}}, {"id": "18.2-2de557ccdda45f50", "source_entry_id": "18.2/changes/045", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "During initial synchronization of a logical replication subscription, commit the addition of a pg_replication_origin entry before starting to copy data", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-e95d66b2b17f79c5", "source_entry_id": "17.8/changes/030", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "During initial synchronization of a logical replication subscription, commit the addition of a pg_replication_origin entry before starting to copy data"}], "entry": {"id": "18.2-2de557ccdda45f50", "cves": [], "html": "During initial synchronization of a logical replication subscription, commit the addition of a pg_replication_origin entry before starting to copy data (Zhijie Hou) §
Previously, if the copy step failed, the new pg_replication_origin entry would be lost due to transaction rollback. This led to inconsistent state in shared memory.
Don't advance logical replication progress after a parallel worker apply failure (Zhijie Hou) §
\nThe previous behavior allowed transactions to be lost by a subscriber.
", "text": "Don't advance logical replication progress after a parallel worker apply failure (Zhijie Hou) § The previous behavior allowed transactions to be lost by a subscriber.", "title": "Don't advance logical replication progress after a parallel worker apply failure", "commits": ["2f7ffe124"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "c17ef3ba75ba5fa5aac564f44981db3ee27f8743c1b4e5bfc13e722e0597619e", "section_path": ["Changes"], "commit_groups": [["0ed8f1afb", "1528b0d89", "2f7ffe124", "63a65adf4"]], "identity_text": "Don't advance logical replication progress after a parallel worker apply failure (Zhijie Hou) The previous behavior allowed transactions to be lost by a subscriber.", "commit_aliases": ["0ed8f1afb", "1528b0d89", "2f7ffe124", "63a65adf4"], "source_commits": ["2f7ffe124"], "source_entry_id": "18.2/changes/046", "db_id": "3e82f89211515507e8f8677f313d3799", "patch_ids": ["9d8b1309e987cb63c5164f0ac19628f4"], "statement_hash": "843a95a8685d2abb66e22dcecb3ca218c807c27fb6410d57c5646106423458aa", "relations": [{"rule": 2, "type": "equivalent", "target": "0f5fb8d4e546a502c86c3683cd965e48", "evidence": {"same_day": true, "patch_ids": ["9d8b1309e987cb63c5164f0ac19628f4"], "statement_hash": "843a95a8685d2abb66e22dcecb3ca218c807c27fb6410d57c5646106423458aa"}}, {"rule": 2, "type": "equivalent", "target": "d3f0ce1d0627ffd85c57f5963d822b33", "evidence": {"same_day": true, "patch_ids": ["9d8b1309e987cb63c5164f0ac19628f4"], "statement_hash": "843a95a8685d2abb66e22dcecb3ca218c807c27fb6410d57c5646106423458aa"}}]}}, {"id": "18.2-2a6c1c4c27f67acd", "source_entry_id": "18.2/changes/047", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix logical replication slotsync worker processes to handle LOCK_TIMEOUT signals correctly", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-f2b54a080f4d7fca", "source_entry_id": "17.8/changes/032", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix logical replication slotsync worker processes to handle LOCK_TIMEOUT signals correctly"}], "entry": {"id": "18.2-2a6c1c4c27f67acd", "cves": [], "html": "Fix logical replication slotsync worker processes to handle LOCK_TIMEOUT signals correctly (Zhijie Hou) §
\nPreviously, timeout signals were effectively ignored.
", "text": "Fix logical replication slotsync worker processes to handle LOCK_TIMEOUT signals correctly (Zhijie Hou) § Previously, timeout signals were effectively ignored.", "title": "Fix logical replication slotsync worker processes to handle LOCK_TIMEOUT signals correctly", "commits": ["6c61c69d5"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "017587a58ab5429b97a836037d4a2dcc806817c09eeeafb775bf2d12edd94f1f", "section_path": ["Changes"], "commit_groups": [["04396eacd", "6c61c69d5", "f2818868a"]], "identity_text": "Fix logical replication slotsync worker processes to handle LOCK_TIMEOUT signals correctly (Zhijie Hou) Previously, timeout signals were effectively ignored.", "commit_aliases": ["04396eacd", "6c61c69d5", "f2818868a"], "source_commits": ["6c61c69d5"], "source_entry_id": "18.2/changes/047", "db_id": "b79cdfd53c29fdec5dd1d0dff7f08fee", "patch_ids": ["bdd6c0273fd3cdf835c31867877f6167"], "statement_hash": "f0b98267cefa8d08da7ffcca6c441a22dd2c4323a5763263e96b18dd48ae7fc5", "relations": [{"rule": 2, "type": "equivalent", "target": "516169d81baba61d618e37237bc53276", "evidence": {"same_day": true, "patch_ids": ["bdd6c0273fd3cdf835c31867877f6167"], "statement_hash": "f0b98267cefa8d08da7ffcca6c441a22dd2c4323a5763263e96b18dd48ae7fc5"}}]}}, {"id": "18.2-c52d288613257e1b", "source_entry_id": "18.2/changes/048", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix possible failure with “unexpected data beyond EOF” during restart of a streaming replica server", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-ca1e290b0cb2dd09", "source_entry_id": "17.8/changes/033", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix possible failure with “unexpected data beyond EOF” during restart of a streaming replica server"}], "entry": {"id": "18.2-c52d288613257e1b", "cves": [], "html": "Fix possible failure with “unexpected data beyond EOF” during restart of a streaming replica server (Anthonin Bonnefoy) §
", "text": "Fix possible failure with “unexpected data beyond EOF” during restart of a streaming replica server (Anthonin Bonnefoy) §", "title": "Fix possible failure with “unexpected data beyond EOF” during restart of a streaming replica server", "commits": ["9ed411e08"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "0ac3e36bd9eb803636d4bc335fbd3e6c1cd2c90d25709b74f7c9a37a8a9bdc37", "section_path": ["Changes"], "commit_groups": [["23b25586d", "2514f1c77", "9ed411e08", "a2eeb04f3", "c3770181c", "ef8465588"]], "identity_text": "Fix possible failure with unexpected data beyond EOF during restart of a streaming replica server (Anthonin Bonnefoy)", "commit_aliases": ["23b25586d", "2514f1c77", "9ed411e08", "a2eeb04f3", "c3770181c", "ef8465588"], "source_commits": ["9ed411e08"], "source_entry_id": "18.2/changes/048", "db_id": "06594efa4344da118700b1c48988f5e4", "patch_ids": ["5162c78b0f9af44ee53c5daf07030ba8"], "statement_hash": "6b8e19ac39d2a905a6b06a59a41de464bc6a62cc815b31c6e858ae96438db9ab", "relations": [{"rule": 2, "type": "equivalent", "target": "668c3f03c522a5db8d076f179e064027", "evidence": {"same_day": true, "patch_ids": ["5162c78b0f9af44ee53c5daf07030ba8"], "statement_hash": "6b8e19ac39d2a905a6b06a59a41de464bc6a62cc815b31c6e858ae96438db9ab"}}, {"rule": 2, "type": "equivalent", "target": "8d924571fb5bee478b47c49ff89fa7f5", "evidence": {"same_day": true, "patch_ids": ["5162c78b0f9af44ee53c5daf07030ba8"], "statement_hash": "6b8e19ac39d2a905a6b06a59a41de464bc6a62cc815b31c6e858ae96438db9ab"}}, {"rule": 2, "type": "equivalent", "target": "a321a63cf72d9e7f3afd2ff1e5a2c814", "evidence": {"same_day": true, "patch_ids": ["5162c78b0f9af44ee53c5daf07030ba8"], "statement_hash": "6b8e19ac39d2a905a6b06a59a41de464bc6a62cc815b31c6e858ae96438db9ab"}}, {"rule": 2, "type": "equivalent", "target": "a79b7d220801497e224783e6369f7957", "evidence": {"same_day": true, "patch_ids": ["5162c78b0f9af44ee53c5daf07030ba8"], "statement_hash": "6b8e19ac39d2a905a6b06a59a41de464bc6a62cc815b31c6e858ae96438db9ab"}}]}}, {"id": "18.2-a3a0f5425174a83a", "source_entry_id": "18.2/changes/049", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix error reporting for SQL/JSON path type mismatches", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-2a0ef06d727eafaf", "source_entry_id": "17.8/changes/034", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix error reporting for SQL/JSON path type mismatches"}], "entry": {"id": "18.2-a3a0f5425174a83a", "cves": [], "html": "Fix error reporting for SQL/JSON path type mismatches (Jian He) §
\nThe code could produce a “cache lookup failed for type 0” error instead of the intended complaint about the path expression not being of the right type.
", "text": "Fix error reporting for SQL/JSON path type mismatches (Jian He) § The code could produce a “cache lookup failed for type 0” error instead of the intended complaint about the path expression not being of the right type.", "title": "Fix error reporting for SQL/JSON path type mismatches", "commits": ["15ba0702c"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "2e243fce6b9135a007fbafb79736adc7b43b27bd3e12b89d1e6be0a5b8436842", "section_path": ["Changes"], "commit_groups": [["15ba0702c", "519fa0433", "b5511fed5"]], "identity_text": "Fix error reporting for SQL/JSON path type mismatches (Jian He) The code could produce a cache lookup failed for type 0 error instead of the intended complaint about the path expression not being of the right type.", "commit_aliases": ["15ba0702c", "519fa0433", "b5511fed5"], "source_commits": ["15ba0702c"], "source_entry_id": "18.2/changes/049", "db_id": "54166f9d89f4ebad4b6522ec9d70d5f6", "patch_ids": ["280990af5b3469c06fb7ff61c204b4ef"], "statement_hash": "125204f7b1e9d0130c0fb80a18be78fa7ce15ceea1fb46138ad538ba516556af", "relations": [{"rule": 2, "type": "equivalent", "target": "8483ae615f87a4c8e095a563aecd48c8", "evidence": {"same_day": true, "patch_ids": ["280990af5b3469c06fb7ff61c204b4ef"], "statement_hash": "125204f7b1e9d0130c0fb80a18be78fa7ce15ceea1fb46138ad538ba516556af"}}]}}, {"id": "18.2-3915ae13b44752be", "source_entry_id": "18.2/changes/050", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix erroneous tracking of column position when parsing partition range bounds", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-1ae71997df1c5c19", "source_entry_id": "17.8/changes/035", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix erroneous tracking of column position when parsing partition range bounds"}], "entry": {"id": "18.2-3915ae13b44752be", "cves": [], "html": "Fix erroneous tracking of column position when parsing partition range bounds (myzhen) §
\nThis could, for example, lead to the wrong column name being cited in error messages about casting partition bound values to the column's data type.
", "text": "Fix erroneous tracking of column position when parsing partition range bounds (myzhen) § This could, for example, lead to the wrong column name being cited in error messages about casting partition bound values to the column's data type.", "title": "Fix erroneous tracking of column position when parsing partition range bounds", "commits": ["c35e5dd9a"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "fa85d72517344f820a9769f83967f877f4194c8f595ca694fae0c2e502a1d930", "section_path": ["Changes"], "commit_groups": [["349107537", "3ad05640b", "821c4d27b", "84b787ae6", "a65995947", "c35e5dd9a"]], "identity_text": "Fix erroneous tracking of column position when parsing partition range bounds (myzhen) This could, for example, lead to the wrong column name being cited in error messages about casting partition bound values to the column's data type.", "commit_aliases": ["349107537", "3ad05640b", "821c4d27b", "84b787ae6", "a65995947", "c35e5dd9a"], "source_commits": ["c35e5dd9a"], "source_entry_id": "18.2/changes/050", "db_id": "bcd807761d1a951aa85d661bf8df019c", "patch_ids": ["6f0c6912e975c2e11453b9af7373ff2b"], "statement_hash": "99c55def0f9f50d97f55530e56d1c92347af0e9dedfe788a482bbfd2a5b86232", "relations": [{"rule": 2, "type": "equivalent", "target": "3d999c9c39b345cf00d6c149f77369bc", "evidence": {"same_day": true, "patch_ids": ["6f0c6912e975c2e11453b9af7373ff2b"], "statement_hash": "99c55def0f9f50d97f55530e56d1c92347af0e9dedfe788a482bbfd2a5b86232"}}, {"rule": 2, "type": "equivalent", "target": "775ee6e8b3e233efe9c85fc527d0a5d4", "evidence": {"same_day": true, "patch_ids": ["6f0c6912e975c2e11453b9af7373ff2b"], "statement_hash": "99c55def0f9f50d97f55530e56d1c92347af0e9dedfe788a482bbfd2a5b86232"}}, {"rule": 2, "type": "equivalent", "target": "8da33c76c87cf129799d93a7efd47d96", "evidence": {"same_day": true, "patch_ids": ["6f0c6912e975c2e11453b9af7373ff2b"], "statement_hash": "99c55def0f9f50d97f55530e56d1c92347af0e9dedfe788a482bbfd2a5b86232"}}, {"rule": 2, "type": "equivalent", "target": "bb4e430870bc5f4909df899b3e4e6a47", "evidence": {"same_day": true, "patch_ids": ["6f0c6912e975c2e11453b9af7373ff2b"], "statement_hash": "99c55def0f9f50d97f55530e56d1c92347af0e9dedfe788a482bbfd2a5b86232"}}]}}, {"id": "18.2-2eb9c2c4100a1830", "source_entry_id": "18.2/changes/051", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix assorted minor errors in error messages", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-4eafc20a792cccfc", "source_entry_id": "17.8/changes/036", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix assorted minor errors in error messages"}], "entry": {"id": "18.2-2eb9c2c4100a1830", "cves": [], "html": "Fix assorted minor errors in error messages (Man Zeng, Tianchen Zhang) § § § § §
\nFor example, an error report about mismatched timeline number in a backup manifest showed the starting timeline number where it meant to show the ending timeline number.
", "text": "Fix assorted minor errors in error messages (Man Zeng, Tianchen Zhang) § § § § § For example, an error report about mismatched timeline number in a backup manifest showed the starting timeline number where it meant to show the ending timeline number.", "title": "Fix assorted minor errors in error messages", "commits": ["2ca4464b6", "69ee81932", "ab61f0087", "acfa422c3", "cff2ef984"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "3a2e503ffa840257c48e18ab773638404e85b6cf64ba6cd94646de3511c66bcf", "section_path": ["Changes"], "commit_groups": [["05ef2371a", "69ee81932", "6bca4b50d", "e8fd6c9fd", "f1dc7a5b7", "fbf8df580"], ["1653ce523", "3e7bb39df", "5449fd261", "9dcd0b3de", "a7bdbbada", "cff2ef984"], ["263af458e", "2ca4464b6", "c8ec74713"], ["4ec943f7d", "67ad4387b", "74a116a79", "977a17a3e", "acfa422c3", "d32e17160"], ["5995135f1", "a9afa021e", "ab61f0087"]], "identity_text": "Fix assorted minor errors in error messages (Man Zeng, Tianchen Zhang) For example, an error report about mismatched timeline number in a backup manifest showed the starting timeline number where it meant to show the ending timeline number.", "commit_aliases": ["05ef2371a", "1653ce523", "263af458e", "2ca4464b6", "3e7bb39df", "4ec943f7d", "5449fd261", "5995135f1", "67ad4387b", "69ee81932", "6bca4b50d", "74a116a79", "977a17a3e", "9dcd0b3de", "a7bdbbada", "a9afa021e", "ab61f0087", "acfa422c3", "c8ec74713", "cff2ef984", "d32e17160", "e8fd6c9fd", "f1dc7a5b7", "fbf8df580"], "source_commits": ["2ca4464b6", "69ee81932", "ab61f0087", "acfa422c3", "cff2ef984"], "source_entry_id": "18.2/changes/051", "db_id": "c28d793705797c568ae351065c8bf92d", "patch_ids": ["1b2d3003a616272db51c764aca05446f", "9747f7cd321d1b9a8c5ab680817d174b", "d322434f9f1579628716983e1ddfa411", "dafc2603cafe575939465f2fd551a6ac", "e9fdf560cb4a79421801e80c5b2933b7"], "statement_hash": "1c12bc1b49de92034a5abdd2caee35fcf65ab113a875838de01715e754830737", "relations": [{"rule": 2, "type": "equivalent", "target": "03e8508ea8a410388767d947c24e8eb3", "evidence": {"same_day": true, "patch_ids": ["1b2d3003a616272db51c764aca05446f", "9747f7cd321d1b9a8c5ab680817d174b", "d322434f9f1579628716983e1ddfa411", "dafc2603cafe575939465f2fd551a6ac", "e9fdf560cb4a79421801e80c5b2933b7"], "statement_hash": "1c12bc1b49de92034a5abdd2caee35fcf65ab113a875838de01715e754830737"}}, {"rule": 2, "type": "equivalent", "target": "040254b8395148f9ed2820a7a9e7de75", "evidence": {"same_day": true, "patch_ids": ["1b2d3003a616272db51c764aca05446f", "9747f7cd321d1b9a8c5ab680817d174b", "d322434f9f1579628716983e1ddfa411", "dafc2603cafe575939465f2fd551a6ac", "e9fdf560cb4a79421801e80c5b2933b7"], "statement_hash": "1c12bc1b49de92034a5abdd2caee35fcf65ab113a875838de01715e754830737"}}, {"rule": 2, "type": "equivalent", "target": "6391fdf7551cb6b17994c91b76215a9f", "evidence": {"same_day": true, "patch_ids": ["1b2d3003a616272db51c764aca05446f", "9747f7cd321d1b9a8c5ab680817d174b", "d322434f9f1579628716983e1ddfa411", "dafc2603cafe575939465f2fd551a6ac", "e9fdf560cb4a79421801e80c5b2933b7"], "statement_hash": "1c12bc1b49de92034a5abdd2caee35fcf65ab113a875838de01715e754830737"}}, {"rule": 2, "type": "equivalent", "target": "e4eecf733b283aee3b3d1c824dbc8e27", "evidence": {"same_day": true, "patch_ids": ["1b2d3003a616272db51c764aca05446f", "9747f7cd321d1b9a8c5ab680817d174b", "d322434f9f1579628716983e1ddfa411", "dafc2603cafe575939465f2fd551a6ac", "e9fdf560cb4a79421801e80c5b2933b7"], "statement_hash": "1c12bc1b49de92034a5abdd2caee35fcf65ab113a875838de01715e754830737"}}]}}, {"id": "18.2-53f3b7ffe4f6fe06", "source_entry_id": "18.2/changes/052", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix failure to perform function inlining when doing JIT compilation with LLVM version 17 or later", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-c185802f4eacb2ea", "source_entry_id": "17.8/changes/037", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix failure to perform function inlining when doing JIT compilation with LLVM version 17 or later"}], "entry": {"id": "18.2-53f3b7ffe4f6fe06", "cves": [], "html": "Fix failure to perform function inlining when doing JIT compilation with LLVM version 17 or later (Anthonin Bonnefoy) §
", "text": "Fix failure to perform function inlining when doing JIT compilation with LLVM version 17 or later (Anthonin Bonnefoy) §", "title": "Fix failure to perform function inlining when doing JIT compilation with LLVM version 17 or later", "commits": ["f1c6b153c"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "9981fa0cf79c4c8beef5d9a46dae95989b255aff0b13e70cfe22036f2abce7d8", "section_path": ["Changes"], "commit_groups": [["7600dc79c", "cbdd09ae1", "d0bb0e5b3", "de8081c30", "e5d99b4d9", "f1c6b153c"]], "identity_text": "Fix failure to perform function inlining when doing JIT compilation with LLVM version 17 or later (Anthonin Bonnefoy)", "commit_aliases": ["7600dc79c", "cbdd09ae1", "d0bb0e5b3", "de8081c30", "e5d99b4d9", "f1c6b153c"], "source_commits": ["f1c6b153c"], "source_entry_id": "18.2/changes/052", "db_id": "6c8a23f42fdf36b27a5c63a60ef638ee", "patch_ids": ["5add9e288aea8ead5625b1ab17f4b389"], "statement_hash": "d9b663cb80004c186d8a4f9af93bb5b74dc9a0534dcc279ee72325534d3c24af", "relations": [{"rule": 2, "type": "equivalent", "target": "1d826bf62f1c8707e84a00b08bca6cc2", "evidence": {"same_day": true, "patch_ids": ["5add9e288aea8ead5625b1ab17f4b389"], "statement_hash": "d9b663cb80004c186d8a4f9af93bb5b74dc9a0534dcc279ee72325534d3c24af"}}, {"rule": 2, "type": "equivalent", "target": "23db3b0771d0b80deb078c18239bf311", "evidence": {"same_day": true, "patch_ids": ["5add9e288aea8ead5625b1ab17f4b389"], "statement_hash": "d9b663cb80004c186d8a4f9af93bb5b74dc9a0534dcc279ee72325534d3c24af"}}, {"rule": 2, "type": "equivalent", "target": "41aa0fa812e386b3bf111e16e5ca824b", "evidence": {"same_day": true, "patch_ids": ["5add9e288aea8ead5625b1ab17f4b389"], "statement_hash": "d9b663cb80004c186d8a4f9af93bb5b74dc9a0534dcc279ee72325534d3c24af"}}, {"rule": 2, "type": "equivalent", "target": "da5340b311cf457b0c8052e7119f6c5c", "evidence": {"same_day": true, "patch_ids": ["5add9e288aea8ead5625b1ab17f4b389"], "statement_hash": "d9b663cb80004c186d8a4f9af93bb5b74dc9a0534dcc279ee72325534d3c24af"}}]}}, {"id": "18.2-bf063586f9119b1e", "source_entry_id": "18.2/changes/053", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Adjust our JIT code to work with LLVM 21", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-64e9296142cf419d", "source_entry_id": "17.8/changes/038", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Adjust our JIT code to work with LLVM 21"}], "entry": {"id": "18.2-bf063586f9119b1e", "cves": [], "html": "Adjust our JIT code to work with LLVM 21 (Holger Hoffstätte) §
\nThe previous coding failed to compile on aarch64 machines.
", "text": "Adjust our JIT code to work with LLVM 21 (Holger Hoffstätte) § The previous coding failed to compile on aarch64 machines.", "title": "Adjust our JIT code to work with LLVM 21", "commits": ["912cfa314"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "642123a264bfa926555231fb51c1f55785277efb74e7e05d7068980643cc565b", "section_path": ["Changes"], "commit_groups": [["035a1f5ac", "0dceba21d", "55164852d", "600acd34b", "60215eae7", "912cfa314"]], "identity_text": "Adjust our JIT code to work with LLVM 21 (Holger Hoffstätte) The previous coding failed to compile on aarch64 machines.", "commit_aliases": ["035a1f5ac", "0dceba21d", "55164852d", "600acd34b", "60215eae7", "912cfa314"], "source_commits": ["912cfa314"], "source_entry_id": "18.2/changes/053", "db_id": "e7ed91f4e25921028767eb7d80e59575", "patch_ids": ["66d712c94d1e5df73fed0dd65d77b242"], "statement_hash": "3c6749ca7e34ce305cd7020f2256a99d6e58f6a41cedef18deedef24299c3cdc", "relations": [{"rule": 2, "type": "equivalent", "target": "084e13baf0a1aaa1b6831e50a2e8b014", "evidence": {"same_day": true, "patch_ids": ["66d712c94d1e5df73fed0dd65d77b242"], "statement_hash": "3c6749ca7e34ce305cd7020f2256a99d6e58f6a41cedef18deedef24299c3cdc"}}, {"rule": 2, "type": "equivalent", "target": "51e665bd2f8466b41d80cf0223c7e413", "evidence": {"same_day": true, "patch_ids": ["66d712c94d1e5df73fed0dd65d77b242"], "statement_hash": "3c6749ca7e34ce305cd7020f2256a99d6e58f6a41cedef18deedef24299c3cdc"}}, {"rule": 2, "type": "equivalent", "target": "c7ea32ba825d2c7140b0017b02f1a3ec", "evidence": {"same_day": true, "patch_ids": ["66d712c94d1e5df73fed0dd65d77b242"], "statement_hash": "3c6749ca7e34ce305cd7020f2256a99d6e58f6a41cedef18deedef24299c3cdc"}}, {"rule": 2, "type": "equivalent", "target": "cff57c5be469c947c3ffe128e6ba5e35", "evidence": {"same_day": true, "patch_ids": ["66d712c94d1e5df73fed0dd65d77b242"], "statement_hash": "3c6749ca7e34ce305cd7020f2256a99d6e58f6a41cedef18deedef24299c3cdc"}}]}}, {"id": "18.2-03a42dee6cc753ad", "source_entry_id": "18.2/changes/056", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Add new server parameter file_extend_method to control use of posix_fallocate()", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-3210c07692952f51", "source_entry_id": "17.8/changes/039", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Add new server parameter file_extend_method to control use of posix_fallocate()"}], "entry": {"id": "18.2-03a42dee6cc753ad", "cves": [], "html": "Add new server parameter file_extend_method to control use of posix_fallocate() (Thomas Munro) §
PostgreSQL version 16 and later will use posix_fallocate(), if the platform provides it, to extend relation files. However, this has been reported to interact poorly with some file systems: BTRFS compression is disabled by the use of posix_fallocate(), and XFS could produce spurious ENOSPC errors in older Linux kernel versions. To provide a workaround, introduce this new server parameter. Setting file_extend_method to write_zeros will cause the server to return to the old method of extending files by writing blocks of zeroes.
Honor open()'s O_CLOEXEC flag on Windows (Bryan Green, Thomas Munro) § § §
Make this flag work like it does on POSIX platforms, so that we don't leak file handles into child processes such as COPY TO/FROM PROGRAM. While that leakage hasn't caused many problems, it seems undesirable.
Fix failure to parse long options on the server command line in Solaris executables built with meson (Tom Lane) §
", "text": "Fix failure to parse long options on the server command line in Solaris executables built with meson (Tom Lane) §", "title": "Fix failure to parse long options on the server command line in Solaris executables built with meson", "commits": ["5eac1d68f"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "f1d750e251da7d0c5b6c6b1df9e1accdcbd5f93f3d2ebd78c2af2fe02f60fa7d", "section_path": ["Changes"], "commit_groups": [["59c2f7efa", "5eac1d68f", "7369656fa", "c0bf15729"]], "identity_text": "Fix failure to parse long options on the server command line in Solaris executables built with meson (Tom Lane)", "commit_aliases": ["59c2f7efa", "5eac1d68f", "7369656fa", "c0bf15729"], "source_commits": ["5eac1d68f"], "source_entry_id": "18.2/changes/058", "db_id": "c730bdc0e2bcae412d1b558e6989e803", "patch_ids": ["133a9f9fce49cbd34f1b9ba0b7dee391"], "statement_hash": "5ef581baf9ed7ef45975ff2c7d893c9da8f950d13c68cd98fea4606121f2a7ac", "relations": [{"rule": 2, "type": "equivalent", "target": "563cd6c38790a66a34d7d2cbdab27f36", "evidence": {"same_day": true, "patch_ids": ["133a9f9fce49cbd34f1b9ba0b7dee391"], "statement_hash": "5ef581baf9ed7ef45975ff2c7d893c9da8f950d13c68cd98fea4606121f2a7ac"}}, {"rule": 2, "type": "equivalent", "target": "ae36e9e2da103cf26dac76edbf8412a6", "evidence": {"same_day": true, "patch_ids": ["133a9f9fce49cbd34f1b9ba0b7dee391"], "statement_hash": "5ef581baf9ed7ef45975ff2c7d893c9da8f950d13c68cd98fea4606121f2a7ac"}}]}}, {"id": "18.2-e1336b6079ff8d5b", "source_entry_id": "18.2/changes/059", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Support process title changes on GNU/Hurd", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-3cbfa3eb5e11672e", "source_entry_id": "17.8/changes/042", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Support process title changes on GNU/Hurd"}], "entry": {"id": "18.2-e1336b6079ff8d5b", "cves": [], "html": "Support process title changes on GNU/Hurd (Michael Banck) §
", "text": "Support process title changes on GNU/Hurd (Michael Banck) §", "title": "Support process title changes on GNU/Hurd", "commits": ["bcfca332f"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "3651cd00413e52bb3457a26d79d84c86f9729cad9edaec4ba29371fdb93f26e0", "section_path": ["Changes"], "commit_groups": [["29a3e22f3", "32b236644", "3995e4a9d", "a1407dade", "bcfca332f", "d66a922f9"]], "identity_text": "Support process title changes on GNU/Hurd (Michael Banck)", "commit_aliases": ["29a3e22f3", "32b236644", "3995e4a9d", "a1407dade", "bcfca332f", "d66a922f9"], "source_commits": ["bcfca332f"], "source_entry_id": "18.2/changes/059", "db_id": "92b88e55c652dfa1fcdde3f0953f3285", "patch_ids": ["f27aa5a2659577ffa2455a4c94564743"], "statement_hash": "c996e792f260f0d512b6a6524e3b46eed7769d4f17a4584a012601680f44fc4f", "relations": [{"rule": 2, "type": "equivalent", "target": "45f431c4bd4cad50e4053b47f371bd3f", "evidence": {"same_day": true, "patch_ids": ["f27aa5a2659577ffa2455a4c94564743"], "statement_hash": "c996e792f260f0d512b6a6524e3b46eed7769d4f17a4584a012601680f44fc4f"}}, {"rule": 2, "type": "equivalent", "target": "465d44f8b93dc009feaa8d1fac573196", "evidence": {"same_day": true, "patch_ids": ["f27aa5a2659577ffa2455a4c94564743"], "statement_hash": "c996e792f260f0d512b6a6524e3b46eed7769d4f17a4584a012601680f44fc4f"}}, {"rule": 2, "type": "equivalent", "target": "b14342e6824ed37b82078bd9a6cc21e1", "evidence": {"same_day": true, "patch_ids": ["f27aa5a2659577ffa2455a4c94564743"], "statement_hash": "c996e792f260f0d512b6a6524e3b46eed7769d4f17a4584a012601680f44fc4f"}}, {"rule": 2, "type": "equivalent", "target": "d2f91f9760f28a721378c4e8d76ef619", "evidence": {"same_day": true, "patch_ids": ["f27aa5a2659577ffa2455a4c94564743"], "statement_hash": "c996e792f260f0d512b6a6524e3b46eed7769d4f17a4584a012601680f44fc4f"}}]}}, {"id": "18.2-ee37d4b2b910a503", "source_entry_id": "18.2/changes/064", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Avoid pg_dump assertion failure in binary-upgrade mode", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-fb87d1ddb8333f9e", "source_entry_id": "17.8/changes/043", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Avoid pg_dump assertion failure in binary-upgrade mode"}], "entry": {"id": "18.2-ee37d4b2b910a503", "cves": [], "html": "Avoid pg_dump assertion failure in binary-upgrade mode (Vignesh C) §
\nFailure to handle subscription-relation objects in the object sorting code triggered an assertion, though there were no serious ill effects in production builds.
", "text": "Avoid pg_dump assertion failure in binary-upgrade mode (Vignesh C) § Failure to handle subscription-relation objects in the object sorting code triggered an assertion, though there were no serious ill effects in production builds.", "title": "Avoid pg_dump assertion failure in binary-upgrade mode", "commits": ["573e679a2"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "30e87eaba4d7329f1777ef3c10be9b4eeeb69ede053339decb40edbf95012f34", "section_path": ["Changes"], "commit_groups": [["1cdc07ad5", "573e679a2", "d49936f30"]], "identity_text": "Avoid pg_dump assertion failure in binary-upgrade mode (Vignesh C) Failure to handle subscription-relation objects in the object sorting code triggered an assertion, though there were no serious ill effects in production builds.", "commit_aliases": ["1cdc07ad5", "573e679a2", "d49936f30"], "source_commits": ["573e679a2"], "source_entry_id": "18.2/changes/064", "db_id": "df5cb5704fef8f74897251fa0c3be081", "patch_ids": ["ed0dc1c369ce52f90f050a02c31cfe22"], "statement_hash": "305d4ecb2b90454723cac5826da3903c1efb32bfae398fdc085bfa0cabab291a", "relations": [{"rule": 2, "type": "equivalent", "target": "4494339208c66bea624ef04f8e7162d7", "evidence": {"same_day": true, "patch_ids": ["ed0dc1c369ce52f90f050a02c31cfe22"], "statement_hash": "305d4ecb2b90454723cac5826da3903c1efb32bfae398fdc085bfa0cabab291a"}}]}}, {"id": "18.2-e7bddef1f2dbe17d", "source_entry_id": "18.2/changes/065", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix incorrect error handling in pgbench with multiple \\syncpipeline commands in pipeline mode", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-db3cf1766c83bbad", "source_entry_id": "17.8/changes/044", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix incorrect error handling in pgbench with multiple \\syncpipeline commands in pipeline mode"}], "entry": {"id": "18.2-e7bddef1f2dbe17d", "cves": [], "html": "Fix incorrect error handling in pgbench with multiple \\syncpipeline commands in pipeline mode (Yugo Nagata) §
If multiple \\syncpipeline commands are encountered after a query error, pgbench would report “failed to exit pipeline mode”, or get an assertion failure in an assert-enabled build.
Make pg_resetwal print the updated value when changing OldestXID (Heikki Linnakangas) §
\nIt already did that for every other variable it can change.
", "text": "Make pg_resetwal print the updated value when changing OldestXID (Heikki Linnakangas) § It already did that for every other variable it can change.", "title": "Make pg_resetwal print the updated value when changing OldestXID", "commits": ["19594271c"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "7d0671d0086f58d8e012489b82175ffdaeea54f9aec8617fd497a06c1f4dc1b7", "section_path": ["Changes"], "commit_groups": [["11cc0f452", "19594271c", "7c494072b", "890cc81b6", "d5b4f3a6d", "f2e0ca0af"]], "identity_text": "Make pg_resetwal print the updated value when changing OldestXID (Heikki Linnakangas) It already did that for every other variable it can change.", "commit_aliases": ["11cc0f452", "19594271c", "7c494072b", "890cc81b6", "d5b4f3a6d", "f2e0ca0af"], "source_commits": ["19594271c"], "source_entry_id": "18.2/changes/066", "db_id": "5f928cd7f1a940e12cd51a8ce19d06f6", "patch_ids": ["f29e862445ceccbb303aaae2f778a19b"], "statement_hash": "7e00b6482e7aa0b9a1cb427214f076ddb806bf1fa199c1cf0ab023c54c2dd96a", "relations": [{"rule": 2, "type": "equivalent", "target": "22be50f61755ecf5187af28b01545b41", "evidence": {"same_day": true, "patch_ids": ["f29e862445ceccbb303aaae2f778a19b"], "statement_hash": "7e00b6482e7aa0b9a1cb427214f076ddb806bf1fa199c1cf0ab023c54c2dd96a"}}, {"rule": 2, "type": "equivalent", "target": "47e617ce37a58405cf4c7f033f26b641", "evidence": {"same_day": true, "patch_ids": ["f29e862445ceccbb303aaae2f778a19b"], "statement_hash": "7e00b6482e7aa0b9a1cb427214f076ddb806bf1fa199c1cf0ab023c54c2dd96a"}}, {"rule": 2, "type": "equivalent", "target": "500d9d80888f7caeb4b4801bee95301d", "evidence": {"same_day": true, "patch_ids": ["f29e862445ceccbb303aaae2f778a19b"], "statement_hash": "7e00b6482e7aa0b9a1cb427214f076ddb806bf1fa199c1cf0ab023c54c2dd96a"}}, {"rule": 2, "type": "equivalent", "target": "94c5ea9aed8ffadf4043f33f201ed4e5", "evidence": {"same_day": true, "patch_ids": ["f29e862445ceccbb303aaae2f778a19b"], "statement_hash": "7e00b6482e7aa0b9a1cb427214f076ddb806bf1fa199c1cf0ab023c54c2dd96a"}}]}}, {"id": "18.2-b3adbf7cc127bf87", "source_entry_id": "18.2/changes/067", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Make pg_resetwal allow setting next multixact xid to 0 or next multixact offset to UINT32_MAX", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-6a1deb077e1799c1", "source_entry_id": "17.8/changes/046", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Make pg_resetwal allow setting next multixact xid to 0 or next multixact offset to UINT32_MAX"}], "entry": {"id": "18.2-b3adbf7cc127bf87", "cves": [], "html": "Make pg_resetwal allow setting next multixact xid to 0 or next multixact offset to UINT32_MAX (Maxim Orlov) §
\nThese are valid values, so rejecting them was incorrect. In the worst case, if a pg_upgrade is attempted when exactly at the point of multixact wraparound, the upgrade would fail.
", "text": "Make pg_resetwal allow setting next multixact xid to 0 or next multixact offset to UINT32_MAX (Maxim Orlov) § These are valid values, so rejecting them was incorrect. In the worst case, if a pg_upgrade is attempted when exactly at the point of multixact wraparound, the upgrade would fail.", "title": "Make pg_resetwal allow setting next multixact xid to 0 or next multixact offset to UINT32_MAX", "commits": ["8747b969f"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "19aa11ac03ecd9743883b5b3b7d28a4034c78e536b691f1127ad247cf62f9794", "section_path": ["Changes"], "commit_groups": [["8747b969f", "94939c5f3", "97cd4b65a", "cb2ef0e92", "e039b09f8"]], "identity_text": "Make pg_resetwal allow setting next multixact xid to 0 or next multixact offset to UINT32_MAX (Maxim Orlov) These are valid values, so rejecting them was incorrect. In the worst case, if a pg_upgrade is attempted when exactly at the point of multixact wraparound, the upgrade would fail.", "commit_aliases": ["8747b969f", "94939c5f3", "97cd4b65a", "cb2ef0e92", "e039b09f8"], "source_commits": ["8747b969f"], "source_entry_id": "18.2/changes/067", "db_id": "a4ce7629005a43b316bb9b4fbdb478ad", "patch_ids": ["0f6a9848b48d4b26e3e4691043d1c86b"], "statement_hash": "55f06afcc35f279a01bd7723ea6dc23f0393b803bcd2fbe9ea5c0600d99ed0ea", "relations": [{"rule": 2, "type": "equivalent", "target": "4da7f3aac2517d05e54bea6d3c1ab25e", "evidence": {"same_day": true, "patch_ids": ["0f6a9848b48d4b26e3e4691043d1c86b"], "statement_hash": "55f06afcc35f279a01bd7723ea6dc23f0393b803bcd2fbe9ea5c0600d99ed0ea"}}, {"rule": 2, "type": "equivalent", "target": "89127b250f2abea1a64f754f71c48c77", "evidence": {"same_day": true, "patch_ids": ["0f6a9848b48d4b26e3e4691043d1c86b"], "statement_hash": "55f06afcc35f279a01bd7723ea6dc23f0393b803bcd2fbe9ea5c0600d99ed0ea"}}, {"rule": 2, "type": "equivalent", "target": "ba56a98c48c3c98e929510554c2c7d1f", "evidence": {"same_day": true, "patch_ids": ["0f6a9848b48d4b26e3e4691043d1c86b"], "statement_hash": "55f06afcc35f279a01bd7723ea6dc23f0393b803bcd2fbe9ea5c0600d99ed0ea"}}]}}, {"id": "18.2-bbfcc39776d1a2a4", "source_entry_id": "18.2/changes/068", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "In contrib/amcheck, use the correct snapshot for btree index parent checks", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-ab740b8bd4036a5f", "source_entry_id": "17.8/changes/047", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "In contrib/amcheck, use the correct snapshot for btree index parent checks"}], "entry": {"id": "18.2-bbfcc39776d1a2a4", "cves": [], "html": "In contrib/amcheck, use the correct snapshot for btree index parent checks (Mihail Nikalayeu) § §
The previous coding caused spurious errors when examining indexes created with CREATE INDEX CONCURRENTLY.
Fix contrib/amcheck to handle “half-dead” btree index pages correctly (Heikki Linnakangas) §
amcheck expected such a page to have a parent downlink, but it does not, leading to a false error report about “mismatch between parent key and child high key”.
Fix contrib/amcheck to handle incomplete btree root page splits correctly (Heikki Linnakangas) §
amcheck could report a false error about “block is not true root”.
Fix edge-case integer overflow in contrib/intarray's selectivity estimator for @@ (Chao Li) §
This could cause poor selectivity estimates to be produced for cases involving the maximum integer value.
", "text": "Fix edge-case integer overflow in contrib/intarray's selectivity estimator for @@ (Chao Li) § This could cause poor selectivity estimates to be produced for cases involving the maximum integer value.", "title": "Fix edge-case integer overflow in contrib/intarray's selectivity estimator for @@", "commits": ["07c1c6ec5"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "0406ef3ec261ae8dfc6ed54bf7e8d656476a289a09885f44526d65c22f1e2707", "section_path": ["Changes"], "commit_groups": [["07c1c6ec5", "4f49e4b55", "54f82c4aa", "67a6fd507", "a5f2dc421", "c89510431"]], "identity_text": "Fix edge-case integer overflow in contrib/intarray's selectivity estimator for @@ (Chao Li) This could cause poor selectivity estimates to be produced for cases involving the maximum integer value.", "commit_aliases": ["07c1c6ec5", "4f49e4b55", "54f82c4aa", "67a6fd507", "a5f2dc421", "c89510431"], "source_commits": ["07c1c6ec5"], "source_entry_id": "18.2/changes/072", "db_id": "e129aabe6a0e432884befb054f303449", "patch_ids": ["6827108dafb7fb952c98263cf81bfb12"], "statement_hash": "15b336d5589f6d629fe8bb0549cd193d78524753cdd06cfede921f7dce003daf", "relations": [{"rule": 2, "type": "equivalent", "target": "1285579c66ecba8872eb8b17f3bc4e1b", "evidence": {"same_day": true, "patch_ids": ["6827108dafb7fb952c98263cf81bfb12"], "statement_hash": "15b336d5589f6d629fe8bb0549cd193d78524753cdd06cfede921f7dce003daf"}}, {"rule": 2, "type": "equivalent", "target": "59e2d3bf9637de09505f940988dcd182", "evidence": {"same_day": true, "patch_ids": ["6827108dafb7fb952c98263cf81bfb12"], "statement_hash": "15b336d5589f6d629fe8bb0549cd193d78524753cdd06cfede921f7dce003daf"}}, {"rule": 2, "type": "equivalent", "target": "81dbabd3964ac7d16575fec8b0e775d4", "evidence": {"same_day": true, "patch_ids": ["6827108dafb7fb952c98263cf81bfb12"], "statement_hash": "15b336d5589f6d629fe8bb0549cd193d78524753cdd06cfede921f7dce003daf"}}, {"rule": 2, "type": "equivalent", "target": "8280d414e29b698e7a7b5bdab7d65a67", "evidence": {"same_day": true, "patch_ids": ["6827108dafb7fb952c98263cf81bfb12"], "statement_hash": "15b336d5589f6d629fe8bb0549cd193d78524753cdd06cfede921f7dce003daf"}}]}}, {"id": "18.2-4b1b9fbd0223faf3", "source_entry_id": "18.2/changes/073", "version": "18.2", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "title": "Fix multibyte-encoding issue in contrib/ltree", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.8-cb9f9359b4259ec9", "source_entry_id": "17.8/changes/051", "version": "17.8", "source_url": "/docs/release/17.8/#RELEASE-17-8-CHANGES", "title": "Fix multibyte-encoding issue in contrib/ltree"}], "entry": {"id": "18.2-4b1b9fbd0223faf3", "cves": [], "html": "Fix multibyte-encoding issue in contrib/ltree (Jeff Davis) §
The previous coding could pass an incomplete multibyte character to lower(), probably resulting in incorrect behavior.
Update time zone data files to tzdata release 2025c (Tom Lane) §
\nThe only change is in historical data for pre-1976 timestamps in Baja California.
", "text": "Update time zone data files to tzdata release 2025c (Tom Lane) § The only change is in historical data for pre-1976 timestamps in Baja California.", "title": "Update time zone data files to tzdata release 2025c", "commits": ["6574bee64"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.2/#RELEASE-18-2-CHANGES", "source_hash": "bb2f3728e4b9f6f7fccf237ab4892ab16d5f39075e844a735198a307cb87d00a", "section_path": ["Changes"], "commit_groups": [["00410b76d", "228fe0c3e", "6574bee64", "8bbf28191", "d852d105e", "f87c0b84e"]], "identity_text": "Update time zone data files to tzdata release 2025c (Tom Lane) The only change is in historical data for pre-1976 timestamps in Baja California.", "commit_aliases": ["00410b76d", "228fe0c3e", "6574bee64", "8bbf28191", "d852d105e", "f87c0b84e"], "source_commits": ["6574bee64"], "source_entry_id": "18.2/changes/075", "db_id": "1e212940a15748de8b9d8f9f8a00221c", "patch_ids": ["248cd6c3eee33cd4c82f09ee1d6af621"], "statement_hash": "da0a28a77bd7a205873150e5d6559af4853f986168d43f9537c2dbe1b0158a5b", "relations": [{"rule": 2, "type": "equivalent", "target": "6a2a6f129d457a35195c94f742bac1c7", "evidence": {"same_day": true, "patch_ids": ["248cd6c3eee33cd4c82f09ee1d6af621"], "statement_hash": "da0a28a77bd7a205873150e5d6559af4853f986168d43f9537c2dbe1b0158a5b"}}, {"rule": 2, "type": "equivalent", "target": "8fe4829a60aad3b491b6cf8cc56b6b67", "evidence": {"same_day": true, "patch_ids": ["248cd6c3eee33cd4c82f09ee1d6af621"], "statement_hash": "da0a28a77bd7a205873150e5d6559af4853f986168d43f9537c2dbe1b0158a5b"}}, {"rule": 2, "type": "equivalent", "target": "af6fece6fb7485ca9609d00ddf419b69", "evidence": {"same_day": true, "patch_ids": ["248cd6c3eee33cd4c82f09ee1d6af621"], "statement_hash": "da0a28a77bd7a205873150e5d6559af4853f986168d43f9537c2dbe1b0158a5b"}}, {"rule": 2, "type": "equivalent", "target": "e11e7a4857357ba2a4255391b7eb4033", "evidence": {"same_day": true, "patch_ids": ["248cd6c3eee33cd4c82f09ee1d6af621"], "statement_hash": "da0a28a77bd7a205873150e5d6559af4853f986168d43f9537c2dbe1b0158a5b"}}]}}, {"id": "18.3-ad611cd1e209983f", "source_entry_id": "18.3/changes/001", "version": "18.3", "source_url": "/docs/release/18.3/#RELEASE-18-3-CHANGES", "title": "Fix failure after replaying a multixid truncation record from WAL that was generated by an older minor version", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.9-80ecbcad5117683e", "source_entry_id": "17.9/changes/001", "version": "17.9", "source_url": "/docs/release/17.9/#RELEASE-17-9-CHANGES", "title": "Fix failure after replaying a multixid truncation record from WAL that was generated by an older minor version"}], "entry": {"id": "18.3-ad611cd1e209983f", "cves": [], "html": "Fix failure after replaying a multixid truncation record from WAL that was generated by an older minor version (Heikki Linnakangas) §
\nErroneous logic for coping with the way that previous versions handled multixid wraparound led to replay failure, with messages like “could not access status of transaction”. A typical scenario in which this could occur is a standby server of the latest minor version consuming WAL from a primary server of an older version.
", "text": "Fix failure after replaying a multixid truncation record from WAL that was generated by an older minor version (Heikki Linnakangas) § Erroneous logic for coping with the way that previous versions handled multixid wraparound led to replay failure, with messages like “could not access status of transaction”. A typical scenario in which this could occur is a standby server of the latest minor version consuming WAL from a primary server of an older version.", "title": "Fix failure after replaying a multixid truncation record from WAL that was generated by an older minor version", "commits": ["817f74600"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.3/#RELEASE-18-3-CHANGES", "source_hash": "103f7a064258041866386b1c934b5dc1e6ae4ca6f921231e67b0cb23889c5b2d", "section_path": ["Changes"], "commit_groups": [["23064542f", "4a36c89f1", "547a8aaa7", "817f74600", "899de38d8"]], "identity_text": "Fix failure after replaying a multixid truncation record from WAL that was generated by an older minor version (Heikki Linnakangas) Erroneous logic for coping with the way that previous versions handled multixid wraparound led to replay failure, with messages like could not access status of transaction. A typical scenario in which this could occur is a standby server of the latest minor version consuming WAL from a primary server of an older version.", "commit_aliases": ["23064542f", "4a36c89f1", "547a8aaa7", "817f74600", "899de38d8"], "source_commits": ["817f74600"], "source_entry_id": "18.3/changes/001", "db_id": "6d7df9238b789e2555fe1290d455a61a", "patch_ids": ["e8c592597fe0c522a838714ea94d192e"], "statement_hash": "cf611d327c6efbb05b8c3c3eec25baadc4b81f3015eda12031c5dfd70647d75d", "relations": [{"rule": 2, "type": "equivalent", "target": "269e20cac41b248d80f469e35fb3be04", "evidence": {"same_day": true, "patch_ids": ["e8c592597fe0c522a838714ea94d192e"], "statement_hash": "cf611d327c6efbb05b8c3c3eec25baadc4b81f3015eda12031c5dfd70647d75d"}}, {"rule": 2, "type": "equivalent", "target": "54acee06ad9ee6f00cba048e48dfdadc", "evidence": {"same_day": true, "patch_ids": ["e8c592597fe0c522a838714ea94d192e"], "statement_hash": "cf611d327c6efbb05b8c3c3eec25baadc4b81f3015eda12031c5dfd70647d75d"}}, {"rule": 2, "type": "equivalent", "target": "ac9d069b97f39c99f4c9540523c6dd01", "evidence": {"same_day": true, "patch_ids": ["e8c592597fe0c522a838714ea94d192e"], "statement_hash": "cf611d327c6efbb05b8c3c3eec25baadc4b81f3015eda12031c5dfd70647d75d"}}, {"rule": 2, "type": "equivalent", "target": "bb4c9dfad3173d99906963ab569e5990", "evidence": {"same_day": true, "patch_ids": ["e8c592597fe0c522a838714ea94d192e"], "statement_hash": "cf611d327c6efbb05b8c3c3eec25baadc4b81f3015eda12031c5dfd70647d75d"}}]}}, {"id": "18.3-77113f5b52409590", "source_entry_id": "18.3/changes/002", "version": "18.3", "source_url": "/docs/release/18.3/#RELEASE-18-3-CHANGES", "title": "Avoid incorrect complaint of invalid encoding when substring() is applied to “toasted” data", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.9-24d7e69f6ec0ae9a", "source_entry_id": "17.9/changes/002", "version": "17.9", "source_url": "/docs/release/17.9/#RELEASE-17-9-CHANGES", "title": "Avoid incorrect complaint of invalid encoding when substring() is applied to “toasted” data"}], "entry": {"id": "18.3-77113f5b52409590", "cves": ["CVE-2026-2006"], "html": "Avoid incorrect complaint of invalid encoding when substring() is applied to “toasted” data (Noah Misch) § § §
The fix for CVE-2026-2006 was too aggressive and could raise an error about an incomplete character in cases that are actually valid.
", "text": "Avoid incorrect complaint of invalid encoding when substring() is applied to “toasted” data (Noah Misch) § § § The fix for CVE-2026-2006 was too aggressive and could raise an error about an incomplete character in cases that are actually valid.", "title": "Avoid incorrect complaint of invalid encoding when substring() is applied to “toasted” data", "commits": ["4174e41b9", "6e045e1a6", "d04b34d68"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.3/#RELEASE-18-3-CHANGES", "source_hash": "385042f170395ab48ac62db0063a8cbfa5ec36f5acc462be6ce28d90a0d3e02c", "section_path": ["Changes"], "commit_groups": [["14b1fd617", "5d5232bc3", "6e045e1a6", "9f4fd119b", "a20eb248c", "bdfb37228"], ["2280ab354", "50d361f62", "8cef93d8a", "a0769e74d", "d04b34d68", "ec86152e0"], ["4174e41b9", "44fc85bbf", "45eb47230", "4644f8b23", "5b305ebcc", "8e73530f1"]], "identity_text": "Avoid incorrect complaint of invalid encoding when substring() is applied to toasted data (Noah Misch) The fix for CVE-2026-2006 was too aggressive and could raise an error about an incomplete character in cases that are actually valid.", "commit_aliases": ["14b1fd617", "2280ab354", "4174e41b9", "44fc85bbf", "45eb47230", "4644f8b23", "50d361f62", "5b305ebcc", "5d5232bc3", "6e045e1a6", "8cef93d8a", "8e73530f1", "9f4fd119b", "a0769e74d", "a20eb248c", "bdfb37228", "d04b34d68", "ec86152e0"], "source_commits": ["4174e41b9", "6e045e1a6", "d04b34d68"], "source_entry_id": "18.3/changes/002", "db_id": "9b63cad6030353d772f1330dfd687e9f", "patch_ids": ["924bc2a7b62c922890c6948fec9b1504", "b621552d0483c3fe9118c60e77f297ab", "fe6380c6909ab3efff6be8983b7f18a1"], "statement_hash": "b34aae4222592f29a7ecee54df249e73bebb9346d81b2e5c859347ba8c1ea747", "relations": [{"rule": 2, "type": "equivalent", "target": "2913b28e99dd666bc31951814a799735", "evidence": {"same_day": true, "patch_ids": ["924bc2a7b62c922890c6948fec9b1504", "b621552d0483c3fe9118c60e77f297ab", "fe6380c6909ab3efff6be8983b7f18a1"], "statement_hash": "b34aae4222592f29a7ecee54df249e73bebb9346d81b2e5c859347ba8c1ea747"}}, {"rule": 2, "type": "equivalent", "target": "91516991913d971894a1428891e4772e", "evidence": {"same_day": true, "patch_ids": ["924bc2a7b62c922890c6948fec9b1504", "b621552d0483c3fe9118c60e77f297ab", "fe6380c6909ab3efff6be8983b7f18a1"], "statement_hash": "b34aae4222592f29a7ecee54df249e73bebb9346d81b2e5c859347ba8c1ea747"}}, {"rule": 2, "type": "equivalent", "target": "da9fc04e8b825c72955bd70be9fd53ee", "evidence": {"same_day": true, "patch_ids": ["924bc2a7b62c922890c6948fec9b1504", "b621552d0483c3fe9118c60e77f297ab", "fe6380c6909ab3efff6be8983b7f18a1"], "statement_hash": "b34aae4222592f29a7ecee54df249e73bebb9346d81b2e5c859347ba8c1ea747"}}, {"rule": 2, "type": "equivalent", "target": "fe28a154c085da9085a635db8d9d4460", "evidence": {"same_day": true, "patch_ids": ["924bc2a7b62c922890c6948fec9b1504", "b621552d0483c3fe9118c60e77f297ab", "fe6380c6909ab3efff6be8983b7f18a1"], "statement_hash": "b34aae4222592f29a7ecee54df249e73bebb9346d81b2e5c859347ba8c1ea747"}}]}}, {"id": "18.3-cd0444df0515373f", "source_entry_id": "18.3/changes/005", "version": "18.3", "source_url": "/docs/release/18.3/#RELEASE-18-3-CHANGES", "title": "Fix computation of the set of potentially-nulling outer joins for the output of a LATERAL UNION ALL subquery", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.9-1441e21296f1914d", "source_entry_id": "17.9/changes/003", "version": "17.9", "source_url": "/docs/release/17.9/#RELEASE-17-9-CHANGES", "title": "Fix computation of the set of potentially-nulling outer joins for the output of a LATERAL UNION ALL subquery"}], "entry": {"id": "18.3-cd0444df0515373f", "cves": [], "html": "Fix computation of the set of potentially-nulling outer joins for the output of a LATERAL UNION ALL subquery (Richard Guo) §
This error could lead to skipping NOT NULL tests in the mistaken belief that they were unnecessary, resulting in wrong query output.
Fix pg_stat_get_backend_wait_event() and pg_stat_get_backend_wait_event_type() to report values for auxiliary processes (Heikki Linnakangas) §
Previously these functions returned NULL for auxiliary processes, but that's inconsistent with the pg_stat_activity view.
Fix casting a composite-type variable to a domain type when returning its value from a PL/pgSQL function (Tom Lane) §
\nIf the variable's value is NULL, a “cache lookup failed for type 0” error resulted.
", "text": "Fix casting a composite-type variable to a domain type when returning its value from a PL/pgSQL function (Tom Lane) § If the variable's value is NULL, a “cache lookup failed for type 0” error resulted.", "title": "Fix casting a composite-type variable to a domain type when returning its value from a PL/pgSQL function", "commits": ["ce4b7e3a1"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.3/#RELEASE-18-3-CHANGES", "source_hash": "fbea03cca43c2b95870d7024da9123755c4689d0eebbc20fd8aab766b4475f49", "section_path": ["Changes"], "commit_groups": [["254b15cbf", "2b93d3820", "9863c9075", "c66f4cff1", "ce4b7e3a1", "dfd850980"]], "identity_text": "Fix casting a composite-type variable to a domain type when returning its value from a PL/pgSQL function (Tom Lane) If the variable's value is NULL, a cache lookup failed for type 0 error resulted.", "commit_aliases": ["254b15cbf", "2b93d3820", "9863c9075", "c66f4cff1", "ce4b7e3a1", "dfd850980"], "source_commits": ["ce4b7e3a1"], "source_entry_id": "18.3/changes/008", "db_id": "d7289871637eb477a52d704b8b129dee", "patch_ids": ["4682bfcc99694f6b7bf7c07af3082c2e"], "statement_hash": "257a19cad310234769985e6594cf9f32698b7849a63b72427ee23e58e321e7d5", "relations": [{"rule": 2, "type": "equivalent", "target": "08e9766e078b0f98d664963d7351568a", "evidence": {"same_day": true, "patch_ids": ["4682bfcc99694f6b7bf7c07af3082c2e"], "statement_hash": "257a19cad310234769985e6594cf9f32698b7849a63b72427ee23e58e321e7d5"}}, {"rule": 2, "type": "equivalent", "target": "1f6375c5be0406ebaeab1ddd1281f48a", "evidence": {"same_day": true, "patch_ids": ["4682bfcc99694f6b7bf7c07af3082c2e"], "statement_hash": "257a19cad310234769985e6594cf9f32698b7849a63b72427ee23e58e321e7d5"}}, {"rule": 2, "type": "equivalent", "target": "509c9d18c03750ab5a1af4533e9e3f71", "evidence": {"same_day": true, "patch_ids": ["4682bfcc99694f6b7bf7c07af3082c2e"], "statement_hash": "257a19cad310234769985e6594cf9f32698b7849a63b72427ee23e58e321e7d5"}}, {"rule": 2, "type": "equivalent", "target": "b3e55b2d8440115c6283ddb4434aed5d", "evidence": {"same_day": true, "patch_ids": ["4682bfcc99694f6b7bf7c07af3082c2e"], "statement_hash": "257a19cad310234769985e6594cf9f32698b7849a63b72427ee23e58e321e7d5"}}]}}, {"id": "18.3-72cba4c8d34e077e", "source_entry_id": "18.3/changes/009", "version": "18.3", "source_url": "/docs/release/18.3/#RELEASE-18-3-CHANGES", "title": "Fix potential null pointer dereference in contrib/hstore's binary input function", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.9-09236fba7643dbb2", "source_entry_id": "17.9/changes/006", "version": "17.9", "source_url": "/docs/release/17.9/#RELEASE-17-9-CHANGES", "title": "Fix potential null pointer dereference in contrib/hstore's binary input function"}], "entry": {"id": "18.3-72cba4c8d34e077e", "cves": [], "html": "Fix potential null pointer dereference in contrib/hstore's binary input function (Michael Paquier) §
hstore's receive function crashed on input containing duplicate keys. hstore values generated by Postgres would never contain duplicate keys, so this mistake has gone unnoticed. The crash could be provoked by malicious or corrupted data.
Prevent unbounded recursion while processing startup packets (Michael Paquier) §
\nA malicious client could crash the connected backend by alternating rejected SSL and GSS encryption requests indefinitely.
\nThe PostgreSQL Project thanks Calif.io (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-6479)
", "text": "Prevent unbounded recursion while processing startup packets (Michael Paquier) § A malicious client could crash the connected backend by alternating rejected SSL and GSS encryption requests indefinitely. The PostgreSQL Project thanks Calif.io (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-6479)", "title": "Prevent unbounded recursion while processing startup packets", "commits": ["f7a191f53"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "8eaf08bcf7fecada977588ace5d26a12bbe548a1f16e4ee3c3ef360450230814", "section_path": ["Changes"], "commit_groups": [["14a4a7040", "16fda4df6", "6dffaeb8e", "c2e6ef863"], ["32a4ce55c", "3b4e66739", "3fb66d302", "66cf26b9e", "b63f25bdd", "f7a191f53"]], "identity_text": "Prevent unbounded recursion while processing startup packets (Michael Paquier) A malicious client could crash the connected backend by alternating rejected SSL and GSS encryption requests indefinitely. The PostgreSQL Project thanks Calif.io (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-6479)", "commit_aliases": ["14a4a7040", "16fda4df6", "32a4ce55c", "3b4e66739", "3fb66d302", "66cf26b9e", "6dffaeb8e", "b63f25bdd", "c2e6ef863", "f7a191f53"], "source_commits": ["6dffaeb8e", "f7a191f53"], "source_entry_id": "18.4/changes/001", "db_id": "1ca6ff4a849ed2960fad43a403e2b932", "patch_ids": ["4309351724f2df44d6eb12d700f03a90", "fce882e6fdda4deccb44245cc5966b20"], "statement_hash": "879026f1f07a4d172337b9e457cc300e4ed2d558396bcc627770e4ef108f69d4", "relations": [{"rule": 2, "type": "equivalent", "target": "3d1e0d9f6f6214fb84bb4b9d4f9402aa", "evidence": {"same_day": true, "patch_ids": ["4309351724f2df44d6eb12d700f03a90", "fce882e6fdda4deccb44245cc5966b20"], "statement_hash": "879026f1f07a4d172337b9e457cc300e4ed2d558396bcc627770e4ef108f69d4"}}, {"rule": 2, "type": "equivalent", "target": "473b135d9b59dfa88e1611d1141570ee", "evidence": {"same_day": true, "patch_ids": ["4309351724f2df44d6eb12d700f03a90", "fce882e6fdda4deccb44245cc5966b20"], "statement_hash": "879026f1f07a4d172337b9e457cc300e4ed2d558396bcc627770e4ef108f69d4"}}, {"rule": 2, "type": "equivalent", "target": "91cb80c58929d3256c8543b647d98328", "evidence": {"same_day": true, "patch_ids": ["4309351724f2df44d6eb12d700f03a90", "fce882e6fdda4deccb44245cc5966b20"], "statement_hash": "879026f1f07a4d172337b9e457cc300e4ed2d558396bcc627770e4ef108f69d4"}}, {"rule": 2, "type": "equivalent", "target": "e49a23129f6590195a74fcbcc51115f9", "evidence": {"same_day": true, "patch_ids": ["4309351724f2df44d6eb12d700f03a90", "fce882e6fdda4deccb44245cc5966b20"], "statement_hash": "879026f1f07a4d172337b9e457cc300e4ed2d558396bcc627770e4ef108f69d4"}}]}}, {"id": "18.4-0ecf0348f34312bf", "source_entry_id": "18.4/changes/002", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix assorted integer overflows in memory-allocation calculations", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-a0bf50b47f7c6ba2", "source_entry_id": "17.10/changes/002", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix assorted integer overflows in memory-allocation calculations"}], "entry": {"id": "18.4-0ecf0348f34312bf", "cves": ["CVE-2026-6473"], "html": "Fix assorted integer overflows in memory-allocation calculations (Tom Lane, Nathan Bossart, Heikki Linnakangas) § § § § § § § § §
\nVarious places were incautious about the possibility of integer overflow in calculations of how much memory to allocate. Overflow would lead to allocating a too-small buffer which the caller would then write past the end of. This would at least trigger server crashes, and probably could be exploited for arbitrary code execution. In many but by no means all cases, the hazard exists only in 32-bit builds.
\nThe PostgreSQL Project thanks Xint Code, Bruce Dang, Sven Klemm, and Pavel Kohout for reporting these problems. (CVE-2026-6473)
", "text": "Fix assorted integer overflows in memory-allocation calculations (Tom Lane, Nathan Bossart, Heikki Linnakangas) § § § § § § § § § Various places were incautious about the possibility of integer overflow in calculations of how much memory to allocate. Overflow would lead to allocating a too-small buffer which the caller would then write past the end of. This would at least trigger server crashes, and probably could be exploited for arbitrary code execution. In many but by no means all cases, the hazard exists only in 32-bit builds. The PostgreSQL Project thanks Xint Code, Bruce Dang, Sven Klemm, and Pavel Kohout for reporting these problems. (CVE-2026-6473)", "title": "Fix assorted integer overflows in memory-allocation calculations", "commits": ["01e568b8c", "3fbec9e50", "55328e3a9", "67dd6243d", "8d1489d50", "c7fb9f765", "dd8af778d", "e1c30458a", "f3cee4dc4"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "d24e4f43bca1a58fcfd0d015d99c4bb296a743a14acfd85222c166d23b42b54e", "section_path": ["Changes"], "commit_groups": [["00e243e67", "37842f3dc", "924b3e943", "c7fb9f765", "d75b1dc96"], ["01b5ef7df", "01e568b8c", "4032c9d98", "aff71f87b", "c55cea529", "e31ef0720"], ["066b7b144", "3e0eba196", "8d1489d50", "b11c3eadf", "ebcfa7867", "f20b84081"], ["0dc1fdc75", "39bc8f2ca", "7fdb0907e", "a4f089c79", "e3a2bea41", "f3cee4dc4"], ["137013f60", "32c525eb6", "55328e3a9", "6a985e71e", "87357a606", "986753361"], ["26dd3cac2", "b2869ebc4", "bcfd848e7", "c25973124", "dd8af778d", "fb0bc321d"], ["3c41f5534", "67dd6243d", "6d68fcb28", "8e81995de", "e24fb3247", "e49e9590d"], ["3fbec9e50", "8e909812d", "c3f7dde39", "c9447b8bd", "dc6c85ff4", "e42598a41"], ["46593aea0", "61a9b4b6e", "bfc5cea76", "cfb610eaa", "e1c30458a", "fe2720c45"], ["47dae5e74", "6a423a256", "d106295b6", "e5babf754"]], "identity_text": "Fix assorted integer overflows in memory-allocation calculations (Tom Lane, Nathan Bossart, Heikki Linnakangas) Various places were incautious about the possibility of integer overflow in calculations of how much memory to allocate. Overflow would lead to allocating a too-small buffer which the caller would then write past the end of. This would at least trigger server crashes, and probably could be exploited for arbitrary code execution. In many but by no means all cases, the hazard exists only in 32-bit builds. The PostgreSQL Project thanks Xint Code, Bruce Dang, Sven Klemm, and Pavel Kohout for reporting these problems. (CVE-2026-6473)", "commit_aliases": ["00e243e67", "01b5ef7df", "01e568b8c", "066b7b144", "0dc1fdc75", "137013f60", "26dd3cac2", "32c525eb6", "37842f3dc", "39bc8f2ca", "3c41f5534", "3e0eba196", "3fbec9e50", "4032c9d98", "46593aea0", "47dae5e74", "55328e3a9", "61a9b4b6e", "67dd6243d", "6a423a256", "6a985e71e", "6d68fcb28", "7fdb0907e", "87357a606", "8d1489d50", "8e81995de", "8e909812d", "924b3e943", "986753361", "a4f089c79", "aff71f87b", "b11c3eadf", "b2869ebc4", "bcfd848e7", "bfc5cea76", "c25973124", "c3f7dde39", "c55cea529", "c7fb9f765", "c9447b8bd", "cfb610eaa", "d106295b6", "d75b1dc96", "dc6c85ff4", "dd8af778d", "e1c30458a", "e24fb3247", "e31ef0720", "e3a2bea41", "e42598a41", "e49e9590d", "e5babf754", "ebcfa7867", "f20b84081", "f3cee4dc4", "fb0bc321d", "fe2720c45"], "source_commits": ["01e568b8c", "3fbec9e50", "55328e3a9", "67dd6243d", "8d1489d50", "c7fb9f765", "dd8af778d", "e1c30458a", "e5babf754", "f3cee4dc4"], "source_entry_id": "18.4/changes/002", "db_id": "acba67a334312f97f378ad9d28899a71", "patch_ids": ["0ef31353c016842f07a477e36bffc11a", "18b75605d90ace7a2cf8047352074614", "522ba1e579ed17edbf8f9a554cef9734", "5ee943f19c8b14a26d6f6e850b4c2e4a", "67e33d81b6d11e90e4032802100b1f9a", "722cd5796fd759e519e27c59ed0f5bc7", "8b4c7be6720ec411561a3216285eb5c2", "9be6f17ccc7861ac218a3159257353f5", "9c6a62a34c14fe610b5925191c0d43bf", "ac6798245b6fb47cbaf616c47755bec8"], "statement_hash": "e134dbaa858fe12a3a5fc6391ac874300d57d4269c0f25b416434cdc943690d8", "relations": [{"rule": 2, "type": "equivalent", "target": "2566881ea25d8a61c2245b4b04c49f1a", "evidence": {"same_day": true, "patch_ids": ["0ef31353c016842f07a477e36bffc11a", "18b75605d90ace7a2cf8047352074614", "522ba1e579ed17edbf8f9a554cef9734", "5ee943f19c8b14a26d6f6e850b4c2e4a", "67e33d81b6d11e90e4032802100b1f9a", "722cd5796fd759e519e27c59ed0f5bc7", "8b4c7be6720ec411561a3216285eb5c2", "9be6f17ccc7861ac218a3159257353f5", "9c6a62a34c14fe610b5925191c0d43bf", "ac6798245b6fb47cbaf616c47755bec8"], "statement_hash": "e134dbaa858fe12a3a5fc6391ac874300d57d4269c0f25b416434cdc943690d8"}}, {"rule": 2, "type": "equivalent", "target": "295b1d4dab2d6e770a4f53cf19a7aaa0", "evidence": {"same_day": true, "patch_ids": ["0ef31353c016842f07a477e36bffc11a", "18b75605d90ace7a2cf8047352074614", "522ba1e579ed17edbf8f9a554cef9734", "5ee943f19c8b14a26d6f6e850b4c2e4a", "67e33d81b6d11e90e4032802100b1f9a", "722cd5796fd759e519e27c59ed0f5bc7", "8b4c7be6720ec411561a3216285eb5c2", "9be6f17ccc7861ac218a3159257353f5", "9c6a62a34c14fe610b5925191c0d43bf", "ac6798245b6fb47cbaf616c47755bec8"], "statement_hash": "e134dbaa858fe12a3a5fc6391ac874300d57d4269c0f25b416434cdc943690d8"}}, {"rule": 2, "type": "equivalent", "target": "8efe22f93b8d48d1a299e86b11c402e5", "evidence": {"same_day": true, "patch_ids": ["0ef31353c016842f07a477e36bffc11a", "18b75605d90ace7a2cf8047352074614", "522ba1e579ed17edbf8f9a554cef9734", "5ee943f19c8b14a26d6f6e850b4c2e4a", "67e33d81b6d11e90e4032802100b1f9a", "722cd5796fd759e519e27c59ed0f5bc7", "8b4c7be6720ec411561a3216285eb5c2", "9be6f17ccc7861ac218a3159257353f5", "9c6a62a34c14fe610b5925191c0d43bf", "ac6798245b6fb47cbaf616c47755bec8"], "statement_hash": "e134dbaa858fe12a3a5fc6391ac874300d57d4269c0f25b416434cdc943690d8"}}, {"rule": 2, "type": "equivalent", "target": "f0345a5abb8aa96f05fce3fbd32e6535", "evidence": {"same_day": true, "patch_ids": ["0ef31353c016842f07a477e36bffc11a", "18b75605d90ace7a2cf8047352074614", "522ba1e579ed17edbf8f9a554cef9734", "5ee943f19c8b14a26d6f6e850b4c2e4a", "67e33d81b6d11e90e4032802100b1f9a", "722cd5796fd759e519e27c59ed0f5bc7", "8b4c7be6720ec411561a3216285eb5c2", "9be6f17ccc7861ac218a3159257353f5", "9c6a62a34c14fe610b5925191c0d43bf", "ac6798245b6fb47cbaf616c47755bec8"], "statement_hash": "e134dbaa858fe12a3a5fc6391ac874300d57d4269c0f25b416434cdc943690d8"}}]}}, {"id": "18.4-5bdcbd2e82271018", "source_entry_id": "18.4/changes/003", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Properly quote subscription names in pg_createsubscriber", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-927543ba721f9720", "source_entry_id": "17.10/changes/003", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Properly quote subscription names in pg_createsubscriber"}], "entry": {"id": "18.4-5bdcbd2e82271018", "cves": ["CVE-2026-6476"], "html": "Properly quote subscription names in pg_createsubscriber (Nathan Bossart) §
\nThe given subscription name was inserted into SQL commands without quoting, so that SQL injection could be achieved in the (perhaps unlikely) case that the subscription name comes from an untrusted source.
\nThe PostgreSQL Project thanks Yu Kunpeng for reporting this problem. (CVE-2026-6476)
", "text": "Properly quote subscription names in pg_createsubscriber (Nathan Bossart) § The given subscription name was inserted into SQL commands without quoting, so that SQL injection could be achieved in the (perhaps unlikely) case that the subscription name comes from an untrusted source. The PostgreSQL Project thanks Yu Kunpeng for reporting this problem. (CVE-2026-6476)", "title": "Properly quote subscription names in pg_createsubscriber", "commits": ["c2e44c370"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "17f99eabd06cf32577fabbdc981f5e198df7045ca49ae684e192861912efaed4", "section_path": ["Changes"], "commit_groups": [["c2e44c370", "d389415ff", "d7de7fa84"]], "identity_text": "Properly quote subscription names in pg_createsubscriber (Nathan Bossart) The given subscription name was inserted into SQL commands without quoting, so that SQL injection could be achieved in the (perhaps unlikely) case that the subscription name comes from an untrusted source. The PostgreSQL Project thanks Yu Kunpeng for reporting this problem. (CVE-2026-6476)", "commit_aliases": ["c2e44c370", "d389415ff", "d7de7fa84"], "source_commits": ["c2e44c370"], "source_entry_id": "18.4/changes/003", "db_id": "eda2bad4600ad30b4d662076df8c2604", "patch_ids": ["e720680b86f42b77dffa98182668476a"], "statement_hash": "ab8d616fe93986f065230107e451ba6882c134da9ddc1a51188a772cce10dc27", "relations": [{"rule": 2, "type": "equivalent", "target": "c1016302d421112d19c9bbb963270941", "evidence": {"same_day": true, "patch_ids": ["e720680b86f42b77dffa98182668476a"], "statement_hash": "ab8d616fe93986f065230107e451ba6882c134da9ddc1a51188a772cce10dc27"}}]}}, {"id": "18.4-a09de455386cd30a", "source_entry_id": "18.4/changes/004", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Properly quote object names in logical replication origin checks", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-fdd0ba1867f4cdc1", "source_entry_id": "17.10/changes/004", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Properly quote object names in logical replication origin checks"}], "entry": {"id": "18.4-a09de455386cd30a", "cves": ["CVE-2026-6638"], "html": "Properly quote object names in logical replication origin checks (Pavel Kohout) §
\nALTER SUBSCRIPTION ... REFRESH PUBLICATION interpolated schema and relation names into SQL commands without quoting them, allowing execution of arbitrary SQL on the publisher.
The PostgreSQL Project thanks Pavel Kohout for reporting this problem. (CVE-2026-6638)
", "text": "Properly quote object names in logical replication origin checks (Pavel Kohout) § ALTER SUBSCRIPTION ... REFRESH PUBLICATION interpolated schema and relation names into SQL commands without quoting them, allowing execution of arbitrary SQL on the publisher. The PostgreSQL Project thanks Pavel Kohout for reporting this problem. (CVE-2026-6638)", "title": "Properly quote object names in logical replication origin checks", "commits": ["cb35d7306"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "c82b2de372a07bda2f6f26acdea7a434159414051129759fc5db1e843d3db9d1", "section_path": ["Changes"], "commit_groups": [["248a433cd", "46b4f5c11", "cb35d7306", "f0f59b658"]], "identity_text": "Properly quote object names in logical replication origin checks (Pavel Kohout) ALTER SUBSCRIPTION ... REFRESH PUBLICATION interpolated schema and relation names into SQL commands without quoting them, allowing execution of arbitrary SQL on the publisher. The PostgreSQL Project thanks Pavel Kohout for reporting this problem. (CVE-2026-6638)", "commit_aliases": ["248a433cd", "46b4f5c11", "cb35d7306", "f0f59b658"], "source_commits": ["cb35d7306"], "source_entry_id": "18.4/changes/004", "db_id": "160fa6992f90d49b5edf0769aa32c248", "patch_ids": ["a9b5d94f4021c4259f919029b9984225"], "statement_hash": "13a92db4a9747d0e4148764ace1c5b2427bc1582543dea88fe555dd3a4b24743", "relations": [{"rule": 2, "type": "equivalent", "target": "6b9ad77c2d8c8cf7ed6c43c56746b015", "evidence": {"same_day": true, "patch_ids": ["a9b5d94f4021c4259f919029b9984225"], "statement_hash": "13a92db4a9747d0e4148764ace1c5b2427bc1582543dea88fe555dd3a4b24743"}}, {"rule": 2, "type": "equivalent", "target": "f75aecc1c0c865955094a916f7c78463", "evidence": {"same_day": true, "patch_ids": ["a9b5d94f4021c4259f919029b9984225"], "statement_hash": "13a92db4a9747d0e4148764ace1c5b2427bc1582543dea88fe555dd3a4b24743"}}]}}, {"id": "18.4-2463210164fd4e42", "source_entry_id": "18.4/changes/005", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Reject over-length options in ts_headline()", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-b66b265350df29d2", "source_entry_id": "17.10/changes/005", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Reject over-length options in ts_headline()"}], "entry": {"id": "18.4-2463210164fd4e42", "cves": ["CVE-2026-6473"], "html": "Reject over-length options in ts_headline() (Michael Paquier) §
The StartSel, StopSel and FragmentDelimiter strings must not exceed 32Kb in length, but this was not checked for. An over-length value would typically crash the server.
The PostgreSQL Project thanks Xint Code for reporting this problem. (CVE-2026-6473)
", "text": "Reject over-length options in ts_headline() (Michael Paquier) § The StartSel, StopSel and FragmentDelimiter strings must not exceed 32Kb in length, but this was not checked for. An over-length value would typically crash the server. The PostgreSQL Project thanks Xint Code for reporting this problem. (CVE-2026-6473)", "title": "Reject over-length options in ts_headline()", "commits": ["62ad26266"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "b56e9415b151349836349dbc81e45dce003139337b9aa8a7181363531af7f086", "section_path": ["Changes"], "commit_groups": [["2d267ffc4", "3ed3dbbf4", "5919e0005", "62ad26266", "7fe365693", "d388e1d7f"]], "identity_text": "Reject over-length options in ts_headline() (Michael Paquier) The StartSel, StopSel and FragmentDelimiter strings must not exceed 32Kb in length, but this was not checked for. An over-length value would typically crash the server. The PostgreSQL Project thanks Xint Code for reporting this problem. (CVE-2026-6473)", "commit_aliases": ["2d267ffc4", "3ed3dbbf4", "5919e0005", "62ad26266", "7fe365693", "d388e1d7f"], "source_commits": ["62ad26266"], "source_entry_id": "18.4/changes/005", "db_id": "afe38bbdb09239daec9610fc4bf0002f", "patch_ids": ["8457c408eab825cef1442be8b008d331"], "statement_hash": "fa5b62f6b191298714caf3ad9670542a5ca5106f71c0bcc2d9d2de48ba2a0330", "relations": [{"rule": 2, "type": "equivalent", "target": "0d396ecb6f57179d943c76706100debf", "evidence": {"same_day": true, "patch_ids": ["8457c408eab825cef1442be8b008d331"], "statement_hash": "fa5b62f6b191298714caf3ad9670542a5ca5106f71c0bcc2d9d2de48ba2a0330"}}, {"rule": 2, "type": "equivalent", "target": "4e96017be5ce2c6f1d23bf476a962747", "evidence": {"same_day": true, "patch_ids": ["8457c408eab825cef1442be8b008d331"], "statement_hash": "fa5b62f6b191298714caf3ad9670542a5ca5106f71c0bcc2d9d2de48ba2a0330"}}, {"rule": 2, "type": "equivalent", "target": "c2a972753505f1b0a01bf236c883ccad", "evidence": {"same_day": true, "patch_ids": ["8457c408eab825cef1442be8b008d331"], "statement_hash": "fa5b62f6b191298714caf3ad9670542a5ca5106f71c0bcc2d9d2de48ba2a0330"}}, {"rule": 2, "type": "equivalent", "target": "ca39bd1c4d36eb3d5c6808cd66068408", "evidence": {"same_day": true, "patch_ids": ["8457c408eab825cef1442be8b008d331"], "statement_hash": "fa5b62f6b191298714caf3ad9670542a5ca5106f71c0bcc2d9d2de48ba2a0330"}}]}}, {"id": "18.4-3645e80ffc91fcb0", "source_entry_id": "18.4/changes/007", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Guard against malicious time zone names in timeofday() and pg_strftime()", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-f68835d296474e15", "source_entry_id": "17.10/changes/006", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Guard against malicious time zone names in timeofday() and pg_strftime()"}], "entry": {"id": "18.4-3645e80ffc91fcb0", "cves": ["CVE-2026-6474"], "html": "Guard against malicious time zone names in timeofday() and pg_strftime() (Tom Lane) § §
A crafted time zone setting could pass % sequences to snprintf(), potentially causing crashes or disclosure of server memory. Another path to similar results was to overflow the limited-size output buffer used by pg_strftime().
The PostgreSQL Project thanks Xint Code for reporting this problem. (CVE-2026-6474)
", "text": "Guard against malicious time zone names in timeofday() and pg_strftime() (Tom Lane) § § A crafted time zone setting could pass % sequences to snprintf(), potentially causing crashes or disclosure of server memory. Another path to similar results was to overflow the limited-size output buffer used by pg_strftime(). The PostgreSQL Project thanks Xint Code for reporting this problem. (CVE-2026-6474)", "title": "Guard against malicious time zone names in timeofday() and pg_strftime()", "commits": ["ba27389c2", "c6e7a9ef3"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "42e13a8c73d5ecbda4d68a436b303713cfb25440d6aff65d86f397133aaff833", "section_path": ["Changes"], "commit_groups": [["126a236ba", "24e0e3254", "4197c880c", "76ab76f87", "a50ae8306", "ba27389c2"], ["2c8226f52", "79b7847c7", "a386d14fe", "c3fff3950", "c6e7a9ef3", "ec8ded4b3"]], "identity_text": "Guard against malicious time zone names in timeofday() and pg_strftime() (Tom Lane) A crafted time zone setting could pass % sequences to snprintf(), potentially causing crashes or disclosure of server memory. Another path to similar results was to overflow the limited-size output buffer used by pg_strftime(). The PostgreSQL Project thanks Xint Code for reporting this problem. (CVE-2026-6474)", "commit_aliases": ["126a236ba", "24e0e3254", "2c8226f52", "4197c880c", "76ab76f87", "79b7847c7", "a386d14fe", "a50ae8306", "ba27389c2", "c3fff3950", "c6e7a9ef3", "ec8ded4b3"], "source_commits": ["ba27389c2", "c6e7a9ef3"], "source_entry_id": "18.4/changes/007", "db_id": "2a60ebdc5466fdb8ded5b7dd70ff560e", "patch_ids": ["3f00e8116f67649860ad5a155650db89", "b65bcdf6c5ef035597912c09e793606a"], "statement_hash": "28222af75396ae38d496fb3a6ca7635e107ba94454753d5b681b8db434552806", "relations": [{"rule": 2, "type": "equivalent", "target": "4746c5c97c413c4b367427dcc53d74f9", "evidence": {"same_day": true, "patch_ids": ["3f00e8116f67649860ad5a155650db89", "b65bcdf6c5ef035597912c09e793606a"], "statement_hash": "28222af75396ae38d496fb3a6ca7635e107ba94454753d5b681b8db434552806"}}, {"rule": 2, "type": "equivalent", "target": "943c74b8816c45111e8f6f3e4682a426", "evidence": {"same_day": true, "patch_ids": ["3f00e8116f67649860ad5a155650db89", "b65bcdf6c5ef035597912c09e793606a"], "statement_hash": "28222af75396ae38d496fb3a6ca7635e107ba94454753d5b681b8db434552806"}}, {"rule": 2, "type": "equivalent", "target": "c35bb2a8a5d8d6153139912fa574f1be", "evidence": {"same_day": true, "patch_ids": ["3f00e8116f67649860ad5a155650db89", "b65bcdf6c5ef035597912c09e793606a"], "statement_hash": "28222af75396ae38d496fb3a6ca7635e107ba94454753d5b681b8db434552806"}}, {"rule": 2, "type": "equivalent", "target": "f0c61a3ee0b896c91466e00b431d94ba", "evidence": {"same_day": true, "patch_ids": ["3f00e8116f67649860ad5a155650db89", "b65bcdf6c5ef035597912c09e793606a"], "statement_hash": "28222af75396ae38d496fb3a6ca7635e107ba94454753d5b681b8db434552806"}}]}}, {"id": "18.4-5cd7cd57980a1193", "source_entry_id": "18.4/changes/008", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "When creating a multirange type, ensure the user has CREATE privilege on the schema specified for the multirange type", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-7b894433ca4b5fde", "source_entry_id": "17.10/changes/007", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "When creating a multirange type, ensure the user has CREATE privilege on the schema specified for the multirange type"}], "entry": {"id": "18.4-5cd7cd57980a1193", "cves": ["CVE-2026-6472"], "html": "When creating a multirange type, ensure the user has CREATE privilege on the schema specified for the multirange type (Jelte Fennema-Nio) §
The multirange type can be put into a different schema than its parent range type, but we neglected to apply the required privilege check when doing so.
\nThe PostgreSQL Project thanks Jelte Fennema-Nio for reporting this problem. (CVE-2026-6472)
", "text": "When creating a multirange type, ensure the user has CREATE privilege on the schema specified for the multirange type (Jelte Fennema-Nio) § The multirange type can be put into a different schema than its parent range type, but we neglected to apply the required privilege check when doing so. The PostgreSQL Project thanks Jelte Fennema-Nio for reporting this problem. (CVE-2026-6472)", "title": "When creating a multirange type, ensure the user has CREATE privilege on the schema specified for the multirange type", "commits": ["a44780f41"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "d62318111e6c324435000f823b575ec7304c8e7d730a7361206b709d1236e1d4", "section_path": ["Changes"], "commit_groups": [["08c397b02", "4793fc41f", "8bca85e9f", "a44780f41", "c27ba08cd", "d92852d62"]], "identity_text": "When creating a multirange type, ensure the user has CREATE privilege on the schema specified for the multirange type (Jelte Fennema-Nio) The multirange type can be put into a different schema than its parent range type, but we neglected to apply the required privilege check when doing so. The PostgreSQL Project thanks Jelte Fennema-Nio for reporting this problem. (CVE-2026-6472)", "commit_aliases": ["08c397b02", "4793fc41f", "8bca85e9f", "a44780f41", "c27ba08cd", "d92852d62"], "source_commits": ["a44780f41"], "source_entry_id": "18.4/changes/008", "db_id": "d9b882bba9a59b55e34aa99621e22473", "patch_ids": ["1c201360c1e263b311b7234d83ff89be"], "statement_hash": "d04d5cbb5906b8e6e39e901491618574dca51ad80d7a3a625a786fceaddfddfd", "relations": [{"rule": 2, "type": "equivalent", "target": "482afe166c3411e42aa15c76ef043f3e", "evidence": {"same_day": true, "patch_ids": ["1c201360c1e263b311b7234d83ff89be"], "statement_hash": "d04d5cbb5906b8e6e39e901491618574dca51ad80d7a3a625a786fceaddfddfd"}}, {"rule": 2, "type": "equivalent", "target": "65fdc90a340d7a6f096d34d54ccaf154", "evidence": {"same_day": true, "patch_ids": ["1c201360c1e263b311b7234d83ff89be"], "statement_hash": "d04d5cbb5906b8e6e39e901491618574dca51ad80d7a3a625a786fceaddfddfd"}}, {"rule": 2, "type": "equivalent", "target": "8f0e03a85bb45cde24bbedf7f781a5d5", "evidence": {"same_day": true, "patch_ids": ["1c201360c1e263b311b7234d83ff89be"], "statement_hash": "d04d5cbb5906b8e6e39e901491618574dca51ad80d7a3a625a786fceaddfddfd"}}, {"rule": 2, "type": "equivalent", "target": "c06039568f80f491221fd94687f0285e", "evidence": {"same_day": true, "patch_ids": ["1c201360c1e263b311b7234d83ff89be"], "statement_hash": "d04d5cbb5906b8e6e39e901491618574dca51ad80d7a3a625a786fceaddfddfd"}}]}}, {"id": "18.4-81a3fe71f66e6eb4", "source_entry_id": "18.4/changes/009", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Use timing-safe string comparisons in authentication code", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-61c7a5bccb286bea", "source_entry_id": "17.10/changes/008", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Use timing-safe string comparisons in authentication code"}], "entry": {"id": "18.4-81a3fe71f66e6eb4", "cves": ["CVE-2026-6478"], "html": "Use timing-safe string comparisons in authentication code (Michael Paquier) §
\nUse timingsafe_bcmp() instead of memcmp() or strcmp() when checking passwords, hashes, etc. It is not known whether the data dependency of those functions is usefully exploitable in any of these places, but in the interests of safety, replace them.
The PostgreSQL Project thanks Joe Conway for reporting this problem. (CVE-2026-6478)
", "text": "Use timing-safe string comparisons in authentication code (Michael Paquier) § Use timingsafe_bcmp() instead of memcmp() or strcmp() when checking passwords, hashes, etc. It is not known whether the data dependency of those functions is usefully exploitable in any of these places, but in the interests of safety, replace them. The PostgreSQL Project thanks Joe Conway for reporting this problem. (CVE-2026-6478)", "title": "Use timing-safe string comparisons in authentication code", "commits": ["d93ef4131"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "31ac0fd6ff577a6e44248a0cccbeba45ddd27760609e5b903596b279c704b45d", "section_path": ["Changes"], "commit_groups": [["00e27235e", "4608619a1", "5924e256c", "c4e7435b3", "c95275f18", "d93ef4131"], ["1604939b2", "8e34acfda", "9dcfcb92f", "b282280e9"]], "identity_text": "Use timing-safe string comparisons in authentication code (Michael Paquier) Use timingsafe_bcmp() instead of memcmp() or strcmp() when checking passwords, hashes, etc. It is not known whether the data dependency of those functions is usefully exploitable in any of these places, but in the interests of safety, replace them. The PostgreSQL Project thanks Joe Conway for reporting this problem. (CVE-2026-6478)", "commit_aliases": ["00e27235e", "1604939b2", "4608619a1", "5924e256c", "8e34acfda", "9dcfcb92f", "b282280e9", "c4e7435b3", "c95275f18", "d93ef4131"], "source_commits": ["8e34acfda", "d93ef4131"], "source_entry_id": "18.4/changes/009", "db_id": "c468a98baa6993bf40cb569c73528c72", "patch_ids": ["4f5cfd9b1166f378c5d2d04fe94dad87", "7fbe706dd59ebe4eced7f18fe6cbf482"], "statement_hash": "7b7eca3255c6f7cb268565088cc6e073ca0b27ad15442af2772a39e51cbfd149", "relations": [{"rule": 2, "type": "equivalent", "target": "049d75b9e50ceb48ee3ba2c6a5d0f494", "evidence": {"same_day": true, "patch_ids": ["4f5cfd9b1166f378c5d2d04fe94dad87", "7fbe706dd59ebe4eced7f18fe6cbf482"], "statement_hash": "7b7eca3255c6f7cb268565088cc6e073ca0b27ad15442af2772a39e51cbfd149"}}, {"rule": 2, "type": "equivalent", "target": "0851fa23f0d4449b2336783af8c0b37f", "evidence": {"same_day": true, "patch_ids": ["4f5cfd9b1166f378c5d2d04fe94dad87", "7fbe706dd59ebe4eced7f18fe6cbf482"], "statement_hash": "7b7eca3255c6f7cb268565088cc6e073ca0b27ad15442af2772a39e51cbfd149"}}, {"rule": 2, "type": "equivalent", "target": "15b60135e3ecea3f472e4441792a26d0", "evidence": {"same_day": true, "patch_ids": ["4f5cfd9b1166f378c5d2d04fe94dad87", "7fbe706dd59ebe4eced7f18fe6cbf482"], "statement_hash": "7b7eca3255c6f7cb268565088cc6e073ca0b27ad15442af2772a39e51cbfd149"}}, {"rule": 2, "type": "equivalent", "target": "f4fc92fe7fa973d00f46d80cff768f2c", "evidence": {"same_day": true, "patch_ids": ["4f5cfd9b1166f378c5d2d04fe94dad87", "7fbe706dd59ebe4eced7f18fe6cbf482"], "statement_hash": "7b7eca3255c6f7cb268565088cc6e073ca0b27ad15442af2772a39e51cbfd149"}}]}}, {"id": "18.4-d46d3c9f5a15e9ff", "source_entry_id": "18.4/changes/010", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Mark PQfn() as unsafe, and avoid using it within libpq", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-a3a6ffe2e68f9c70", "source_entry_id": "17.10/changes/009", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Mark PQfn() as unsafe, and avoid using it within libpq"}], "entry": {"id": "18.4-d46d3c9f5a15e9ff", "cves": ["CVE-2026-6477"], "html": "Mark PQfn() as unsafe, and avoid using it within libpq (Nathan Bossart) §
For a non-integral result type, PQfn() is not passed the size of the output buffer, so it cannot check that the data returned by the server will fit. A malicious server could therefore overwrite client memory. This is unfixable without an API change, so mark the function as deprecated. Internally to libpq, use a variant version that can apply the missing check.
The PostgreSQL Project thanks Yu Kunpeng and Martin Heistermann for reporting this problem. (CVE-2026-6477)
", "text": "Mark PQfn() as unsafe, and avoid using it within libpq (Nathan Bossart) § For a non-integral result type, PQfn() is not passed the size of the output buffer, so it cannot check that the data returned by the server will fit. A malicious server could therefore overwrite client memory. This is unfixable without an API change, so mark the function as deprecated. Internally to libpq, use a variant version that can apply the missing check. The PostgreSQL Project thanks Yu Kunpeng and Martin Heistermann for reporting this problem. (CVE-2026-6477)", "title": "Mark PQfn() as unsafe, and avoid using it within libpq", "commits": ["be0136440"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "7fc11295c46055a4824819e76fe0415c3ae41f7901858f49c5c1b096f57994a9", "section_path": ["Changes"], "commit_groups": [["614474996", "8ac723b2b", "bd4811493", "be0136440", "d88c7be15", "e3a1f83ea"]], "identity_text": "Mark PQfn() as unsafe, and avoid using it within libpq (Nathan Bossart) For a non-integral result type, PQfn() is not passed the size of the output buffer, so it cannot check that the data returned by the server will fit. A malicious server could therefore overwrite client memory. This is unfixable without an API change, so mark the function as deprecated. Internally to libpq, use a variant version that can apply the missing check. The PostgreSQL Project thanks Yu Kunpeng and Martin Heistermann for reporting this problem. (CVE-2026-6477)", "commit_aliases": ["614474996", "8ac723b2b", "bd4811493", "be0136440", "d88c7be15", "e3a1f83ea"], "source_commits": ["be0136440"], "source_entry_id": "18.4/changes/010", "db_id": "847daceb397313a24d7c441b2b0558f1", "patch_ids": ["751c917289b90832d6991f8f4911d6cc"], "statement_hash": "1bf9b2e2db6cb6f0cc68cfddc7ca5a446d8e7408a35bce897eda2f59aec7605b", "relations": [{"rule": 2, "type": "equivalent", "target": "4ab9970767b3ef4f9da60c3566967c2b", "evidence": {"same_day": true, "patch_ids": ["751c917289b90832d6991f8f4911d6cc"], "statement_hash": "1bf9b2e2db6cb6f0cc68cfddc7ca5a446d8e7408a35bce897eda2f59aec7605b"}}, {"rule": 2, "type": "equivalent", "target": "5659c5fab9b3c23718775a073679d763", "evidence": {"same_day": true, "patch_ids": ["751c917289b90832d6991f8f4911d6cc"], "statement_hash": "1bf9b2e2db6cb6f0cc68cfddc7ca5a446d8e7408a35bce897eda2f59aec7605b"}}, {"rule": 2, "type": "equivalent", "target": "954548c0ee471a5891175ee04e881030", "evidence": {"same_day": true, "patch_ids": ["751c917289b90832d6991f8f4911d6cc"], "statement_hash": "1bf9b2e2db6cb6f0cc68cfddc7ca5a446d8e7408a35bce897eda2f59aec7605b"}}, {"rule": 2, "type": "equivalent", "target": "fcce310e332c33500cf3c168aae9bd79", "evidence": {"same_day": true, "patch_ids": ["751c917289b90832d6991f8f4911d6cc"], "statement_hash": "1bf9b2e2db6cb6f0cc68cfddc7ca5a446d8e7408a35bce897eda2f59aec7605b"}}]}}, {"id": "18.4-ad40fa4da3cebaa2", "source_entry_id": "18.4/changes/011", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Prevent path traversal in pg_basebackup and pg_rewind", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-91d502adb9e9905a", "source_entry_id": "17.10/changes/010", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Prevent path traversal in pg_basebackup and pg_rewind"}], "entry": {"id": "18.4-ad40fa4da3cebaa2", "cves": ["CVE-2026-6475"], "html": "Prevent path traversal in pg_basebackup and pg_rewind (Michael Paquier) §
\nThese applications failed to validate output file paths read from their input, so that a malicious source could overwrite any file writable by these applications. Constrain where data can be written by rejecting paths that are absolute or contain parent-directory references.
\nThe PostgreSQL Project thanks XlabAI Team of Tencent Xuanwu Lab and Valery Gubanov for reporting this problem. (CVE-2026-6475)
", "text": "Prevent path traversal in pg_basebackup and pg_rewind (Michael Paquier) § These applications failed to validate output file paths read from their input, so that a malicious source could overwrite any file writable by these applications. Constrain where data can be written by rejecting paths that are absolute or contain parent-directory references. The PostgreSQL Project thanks XlabAI Team of Tencent Xuanwu Lab and Valery Gubanov for reporting this problem. (CVE-2026-6475)", "title": "Prevent path traversal in pg_basebackup and pg_rewind", "commits": ["6a67c540a"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "6bc165e3208c831cfd8f34eec3a461fc0569e52e0b5e8ba62286675169fa1d64", "section_path": ["Changes"], "commit_groups": [["0c83fe8e4", "498829dca", "6778af13e", "6a67c540a", "8f881e188", "a1063eece"]], "identity_text": "Prevent path traversal in pg_basebackup and pg_rewind (Michael Paquier) These applications failed to validate output file paths read from their input, so that a malicious source could overwrite any file writable by these applications. Constrain where data can be written by rejecting paths that are absolute or contain parent-directory references. The PostgreSQL Project thanks XlabAI Team of Tencent Xuanwu Lab and Valery Gubanov for reporting this problem. (CVE-2026-6475)", "commit_aliases": ["0c83fe8e4", "498829dca", "6778af13e", "6a67c540a", "8f881e188", "a1063eece"], "source_commits": ["6a67c540a"], "source_entry_id": "18.4/changes/011", "db_id": "4327318e7057209dbe42b98400f9d4be", "patch_ids": ["642e466aa03c3fea1f14f662cc164373"], "statement_hash": "f4e8ae9e638997395a0957d148112ff560c0e68ac13f1311986f81899f914d10", "relations": [{"rule": 2, "type": "equivalent", "target": "4bae8e6eba13d8b7f663721c981765fa", "evidence": {"same_day": true, "patch_ids": ["642e466aa03c3fea1f14f662cc164373"], "statement_hash": "f4e8ae9e638997395a0957d148112ff560c0e68ac13f1311986f81899f914d10"}}, {"rule": 2, "type": "equivalent", "target": "5bc8c04625ad184faa480aea65f22c87", "evidence": {"same_day": true, "patch_ids": ["642e466aa03c3fea1f14f662cc164373"], "statement_hash": "f4e8ae9e638997395a0957d148112ff560c0e68ac13f1311986f81899f914d10"}}, {"rule": 2, "type": "equivalent", "target": "869c70a85bc692a897810d4c6c2c8001", "evidence": {"same_day": true, "patch_ids": ["642e466aa03c3fea1f14f662cc164373"], "statement_hash": "f4e8ae9e638997395a0957d148112ff560c0e68ac13f1311986f81899f914d10"}}, {"rule": 2, "type": "equivalent", "target": "a4a793034a07393a1194f5d901c7e563", "evidence": {"same_day": true, "patch_ids": ["642e466aa03c3fea1f14f662cc164373"], "statement_hash": "f4e8ae9e638997395a0957d148112ff560c0e68ac13f1311986f81899f914d10"}}]}}, {"id": "18.4-2061b554e1b2edfa", "source_entry_id": "18.4/changes/012", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Guard against field overflow within contrib/intarray's query_int type and contrib/ltree's ltxtquery type", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-992f2d3fb9146406", "source_entry_id": "17.10/changes/011", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Guard against field overflow within contrib/intarray's query_int type and contrib/ltree's ltxtquery type"}], "entry": {"id": "18.4-2061b554e1b2edfa", "cves": ["CVE-2026-6473"], "html": "Guard against field overflow within contrib/intarray's query_int type and contrib/ltree's ltxtquery type (Tom Lane) § §
Parsing of these query structures did not check for overflow of 16-bit fields, so that construction of an invalid query tree was possible. This can crash the server when executing the query.
\nThe PostgreSQL Project thanks Xint Code for reporting this problem. (CVE-2026-6473)
", "text": "Guard against field overflow within contrib/intarray's query_int type and contrib/ltree's ltxtquery type (Tom Lane) § § Parsing of these query structures did not check for overflow of 16-bit fields, so that construction of an invalid query tree was possible. This can crash the server when executing the query. The PostgreSQL Project thanks Xint Code for reporting this problem. (CVE-2026-6473)", "title": "Guard against field overflow within contrib/intarray's query_int type and contrib/ltree's ltxtquery type", "commits": ["05e73b5c3", "c5790ec4f"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "c072da4c6c8e8d11286a2d5d62c06b65f9880c2bd66f39eebf44dfba434afe5b", "section_path": ["Changes"], "commit_groups": [["05e73b5c3", "2b429d887", "479823a71", "6f0bff33d", "906ea101d", "fc1fd3d97"], ["074702525", "43451a7a2", "5c1069c35", "84a9f2641", "c4d04cc48", "c5790ec4f"]], "identity_text": "Guard against field overflow within contrib/intarray's query_int type and contrib/ltree's ltxtquery type (Tom Lane) Parsing of these query structures did not check for overflow of 16-bit fields, so that construction of an invalid query tree was possible. This can crash the server when executing the query. The PostgreSQL Project thanks Xint Code for reporting this problem. (CVE-2026-6473)", "commit_aliases": ["05e73b5c3", "074702525", "2b429d887", "43451a7a2", "479823a71", "5c1069c35", "6f0bff33d", "84a9f2641", "906ea101d", "c4d04cc48", "c5790ec4f", "fc1fd3d97"], "source_commits": ["05e73b5c3", "c5790ec4f"], "source_entry_id": "18.4/changes/012", "db_id": "9a6b47b64707d2aaa7ed6ba0484070e5", "patch_ids": ["6f7401152b77a4e4d59e752f19e8486b", "b419665d09a38659e641b360731e56da"], "statement_hash": "eab56845994726033024137f96b0dd1e892a863aae111c3043e8a088bf26c0d7", "relations": [{"rule": 2, "type": "equivalent", "target": "0423b242e381085c16cb62849b04525f", "evidence": {"same_day": true, "patch_ids": ["6f7401152b77a4e4d59e752f19e8486b", "b419665d09a38659e641b360731e56da"], "statement_hash": "eab56845994726033024137f96b0dd1e892a863aae111c3043e8a088bf26c0d7"}}, {"rule": 2, "type": "equivalent", "target": "2ad1fdfa4b929eb7b74591983f7fe071", "evidence": {"same_day": true, "patch_ids": ["6f7401152b77a4e4d59e752f19e8486b", "b419665d09a38659e641b360731e56da"], "statement_hash": "eab56845994726033024137f96b0dd1e892a863aae111c3043e8a088bf26c0d7"}}, {"rule": 2, "type": "equivalent", "target": "9f97314dd0efbba664c1f83e75fb5fa1", "evidence": {"same_day": true, "patch_ids": ["6f7401152b77a4e4d59e752f19e8486b", "b419665d09a38659e641b360731e56da"], "statement_hash": "eab56845994726033024137f96b0dd1e892a863aae111c3043e8a088bf26c0d7"}}, {"rule": 2, "type": "equivalent", "target": "d29898a37787b811ca1a66114dcaa530", "evidence": {"same_day": true, "patch_ids": ["6f7401152b77a4e4d59e752f19e8486b", "b419665d09a38659e641b360731e56da"], "statement_hash": "eab56845994726033024137f96b0dd1e892a863aae111c3043e8a088bf26c0d7"}}]}}, {"id": "18.4-eb36ae972f5e73e4", "source_entry_id": "18.4/changes/013", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Guard against overly long values of contrib/ltree's lquery type", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-ac24cc16660e8737", "source_entry_id": "17.10/changes/012", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Guard against overly long values of contrib/ltree's lquery type"}], "entry": {"id": "18.4-eb36ae972f5e73e4", "cves": ["CVE-2026-6473"], "html": "Guard against overly long values of contrib/ltree's lquery type (Michael Paquier) §
Values with more than 64K items caused internal overflows, potentially resulting in stack smashes or wrong answers.
\nThe PostgreSQL Project thanks Vergissmeinnicht, A1ex, and Jihe Wang for reporting this problem. (CVE-2026-6473)
", "text": "Guard against overly long values of contrib/ltree's lquery type (Michael Paquier) § Values with more than 64K items caused internal overflows, potentially resulting in stack smashes or wrong answers. The PostgreSQL Project thanks Vergissmeinnicht, A1ex, and Jihe Wang for reporting this problem. (CVE-2026-6473)", "title": "Guard against overly long values of contrib/ltree's lquery type", "commits": ["7f019f341"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "c636424e1165ad48a14eaeae8259fc21c63fc45076252ce264efb1a7fef87996", "section_path": ["Changes"], "commit_groups": [["2f1b16e86", "6b6b26fde", "7f019f341", "8c3426110", "9c2fa5b6a", "b545c3787"]], "identity_text": "Guard against overly long values of contrib/ltree's lquery type (Michael Paquier) Values with more than 64K items caused internal overflows, potentially resulting in stack smashes or wrong answers. The PostgreSQL Project thanks Vergissmeinnicht, A1ex, and Jihe Wang for reporting this problem. (CVE-2026-6473)", "commit_aliases": ["2f1b16e86", "6b6b26fde", "7f019f341", "8c3426110", "9c2fa5b6a", "b545c3787"], "source_commits": ["7f019f341"], "source_entry_id": "18.4/changes/013", "db_id": "f1ea7b13a59ce4a556a97a665b13ddd9", "patch_ids": ["82d1afadeb06a657e558ea1b226d290b"], "statement_hash": "0f082737f7f109cba8da33aebd4d21f85a8ca0c9ac333cd92d1eafa83684e6e1", "relations": [{"rule": 2, "type": "equivalent", "target": "6aa8f69f3021e6633c690bc4d069a359", "evidence": {"same_day": true, "patch_ids": ["82d1afadeb06a657e558ea1b226d290b"], "statement_hash": "0f082737f7f109cba8da33aebd4d21f85a8ca0c9ac333cd92d1eafa83684e6e1"}}, {"rule": 2, "type": "equivalent", "target": "abd21d034ac90949aacffcced38f44c8", "evidence": {"same_day": true, "patch_ids": ["82d1afadeb06a657e558ea1b226d290b"], "statement_hash": "0f082737f7f109cba8da33aebd4d21f85a8ca0c9ac333cd92d1eafa83684e6e1"}}, {"rule": 2, "type": "equivalent", "target": "b026af4117fde9e94388242432e381e0", "evidence": {"same_day": true, "patch_ids": ["82d1afadeb06a657e558ea1b226d290b"], "statement_hash": "0f082737f7f109cba8da33aebd4d21f85a8ca0c9ac333cd92d1eafa83684e6e1"}}, {"rule": 2, "type": "equivalent", "target": "e57528b755cb641d030a2490a8ecb83e", "evidence": {"same_day": true, "patch_ids": ["82d1afadeb06a657e558ea1b226d290b"], "statement_hash": "0f082737f7f109cba8da33aebd4d21f85a8ca0c9ac333cd92d1eafa83684e6e1"}}]}}, {"id": "18.4-723bbbf2b375795c", "source_entry_id": "18.4/changes/014", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Prevent SQL injection and buffer overruns in contrib/spi", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-24a0ab68af146f7d", "source_entry_id": "17.10/changes/013", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Prevent SQL injection and buffer overruns in contrib/spi"}], "entry": {"id": "18.4-723bbbf2b375795c", "cves": ["CVE-2026-6637"], "html": "Prevent SQL injection and buffer overruns in contrib/spi (Nathan Bossart) §
check_foreign_key() was insufficiently careful about quoting key values, and also used fixed-length buffers for constructing queries. While this module is only meant as example code, it still shouldn't contain such dangerous errors.
The PostgreSQL Project thanks Nikolay Samokhvalov for reporting this problem. (CVE-2026-6637)
", "text": "Prevent SQL injection and buffer overruns in contrib/spi (Nathan Bossart) § check_foreign_key() was insufficiently careful about quoting key values, and also used fixed-length buffers for constructing queries. While this module is only meant as example code, it still shouldn't contain such dangerous errors. The PostgreSQL Project thanks Nikolay Samokhvalov for reporting this problem. (CVE-2026-6637)", "title": "Prevent SQL injection and buffer overruns in contrib/spi", "commits": ["1ebda7da9"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "d1e23fbdb69b2138879701aaf07def7e140aa1af21e7ee27298e304aed0ca7d2", "section_path": ["Changes"], "commit_groups": [["1ebda7da9", "260e97733", "2b026df29", "2dc64ef28", "710995782", "8053235ab"]], "identity_text": "Prevent SQL injection and buffer overruns in contrib/spi (Nathan Bossart) check_foreign_key() was insufficiently careful about quoting key values, and also used fixed-length buffers for constructing queries. While this module is only meant as example code, it still shouldn't contain such dangerous errors. The PostgreSQL Project thanks Nikolay Samokhvalov for reporting this problem. (CVE-2026-6637)", "commit_aliases": ["1ebda7da9", "260e97733", "2b026df29", "2dc64ef28", "710995782", "8053235ab"], "source_commits": ["1ebda7da9"], "source_entry_id": "18.4/changes/014", "db_id": "7f0c9646c89bca074cd9e0bbd964087f", "patch_ids": ["41547e1e28b3ed62af00bb9fe154772c"], "statement_hash": "7b1c0422aa1716161960ade63e1f312c46555a948c91e3b00a8e5c748e70d047", "relations": [{"rule": 2, "type": "equivalent", "target": "47e292139214a78fca35c140daf58270", "evidence": {"same_day": true, "patch_ids": ["41547e1e28b3ed62af00bb9fe154772c"], "statement_hash": "7b1c0422aa1716161960ade63e1f312c46555a948c91e3b00a8e5c748e70d047"}}, {"rule": 2, "type": "equivalent", "target": "5c27c1f393abf9296bda616730209a61", "evidence": {"same_day": true, "patch_ids": ["41547e1e28b3ed62af00bb9fe154772c"], "statement_hash": "7b1c0422aa1716161960ade63e1f312c46555a948c91e3b00a8e5c748e70d047"}}, {"rule": 2, "type": "equivalent", "target": "80646ad1b79ca8538cfec18dd2e574d7", "evidence": {"same_day": true, "patch_ids": ["41547e1e28b3ed62af00bb9fe154772c"], "statement_hash": "7b1c0422aa1716161960ade63e1f312c46555a948c91e3b00a8e5c748e70d047"}}, {"rule": 2, "type": "equivalent", "target": "b9f0b8c87f7b233c50090282e467d8ed", "evidence": {"same_day": true, "patch_ids": ["41547e1e28b3ed62af00bb9fe154772c"], "statement_hash": "7b1c0422aa1716161960ade63e1f312c46555a948c91e3b00a8e5c748e70d047"}}]}}, {"id": "18.4-984de78400375246", "source_entry_id": "18.4/changes/015", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Check for nondeterministic collations before assuming that an equality condition on a collatable type implies uniqueness", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-3d0256182db9ecf0", "source_entry_id": "17.10/changes/014", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Check for nondeterministic collations before assuming that an equality condition on a collatable type implies uniqueness"}], "entry": {"id": "18.4-984de78400375246", "cves": [], "html": "Check for nondeterministic collations before assuming that an equality condition on a collatable type implies uniqueness (Richard Guo) § § § § §
\nNumerous planner optimizations assume that, for example, at most one table row can satisfy WHERE x = 'abc' if there is a unique index on x. However this conclusion is unsafe in general if the index and the WHERE clause have different collations attached. It is safe when both collations are deterministic, because that property essentially requires that equality of two strings means bitwise equality. But nondeterministic collations don't act that way, so that optimizing on the assumption of unique matches can give wrong query answers if either the WHERE clause or the index has a nondeterministic collation.
Fix incomplete removal of relation references in RestrictInfo structs during join removal (Tom Lane) §
This oversight has been shown to result in planner failures such as unexpected “FULL JOIN is only supported with merge-joinable or hash-joinable join conditions” errors. It may also have caused failure to consider valid plans in other cases.
", "text": "Fix incomplete removal of relation references in RestrictInfo structs during join removal (Tom Lane) § This oversight has been shown to result in planner failures such as unexpected “FULL JOIN is only supported with merge-joinable or hash-joinable join conditions” errors. It may also have caused failure to consider valid plans in other cases.", "title": "Fix incomplete removal of relation references in RestrictInfo structs during join removal", "commits": ["16fb94605"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "7890a55f50302b7ca4e67825cbefbb79c5ca02ec380951e76604a48bda8c0624", "section_path": ["Changes"], "commit_groups": [["16fb94605", "766d40286", "cfcd57111", "d509be4ac"], ["53cb4ec1d", "798dabe83", "f0ac6d494"]], "identity_text": "Fix incomplete removal of relation references in RestrictInfo structs during join removal (Tom Lane) This oversight has been shown to result in planner failures such as unexpected FULL JOIN is only supported with merge-joinable or hash-joinable join conditions errors. It may also have caused failure to consider valid plans in other cases.", "commit_aliases": ["16fb94605", "53cb4ec1d", "766d40286", "798dabe83", "cfcd57111", "d509be4ac", "f0ac6d494"], "source_commits": ["16fb94605", "f0ac6d494"], "source_entry_id": "18.4/changes/016", "db_id": "cbba3da86525413deddd8a183780866b", "patch_ids": ["22c06d077427cb5284041785d0e8cde1", "8989faf5448f269deb8ac79dc2a63860"], "statement_hash": "bbc0a2274d4af257fa49e43eafaf28ca0f12217996c9c00ed63e12bf89b35109", "relations": [{"rule": 2, "type": "equivalent", "target": "0a61b6485e0144413b6e68fbe7763a8f", "evidence": {"same_day": true, "patch_ids": ["22c06d077427cb5284041785d0e8cde1", "8989faf5448f269deb8ac79dc2a63860"], "statement_hash": "bbc0a2274d4af257fa49e43eafaf28ca0f12217996c9c00ed63e12bf89b35109"}}, {"rule": 2, "type": "equivalent", "target": "53d5de052cfe73ed3dbffe04ba42ff12", "evidence": {"same_day": true, "patch_ids": ["22c06d077427cb5284041785d0e8cde1", "8989faf5448f269deb8ac79dc2a63860"], "statement_hash": "bbc0a2274d4af257fa49e43eafaf28ca0f12217996c9c00ed63e12bf89b35109"}}]}}, {"id": "18.4-e3a990357e448509", "source_entry_id": "18.4/changes/021", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix incorrect handling of NEW generated columns in rule actions and rule qualifications", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-5a2d4121326fa353", "source_entry_id": "17.10/changes/016", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix incorrect handling of NEW generated columns in rule actions and rule qualifications"}], "entry": {"id": "18.4-e3a990357e448509", "cves": [], "html": "Fix incorrect handling of NEW generated columns in rule actions and rule qualifications (Richard Guo, Dean Rasheed) §
Previously, such column references would produce NULL in INSERT cases, or be equivalent to the OLD value in UPDATE cases.
Fix spurious “generated columns are not supported in COPY FROM WHERE conditions” errors (Tom Lane) §
\nUse of a system column in a COPY FROM WHERE condition could sometimes incorrectly report this error.
Correctly report a serialization failure when MERGE encounters a concurrently-updated tuple in repeatable-read or serializable mode (Tender Wang) §
Previously, such cases behaved the same as in lower isolation levels.
", "text": "Correctly report a serialization failure when MERGE encounters a concurrently-updated tuple in repeatable-read or serializable mode (Tender Wang) § Previously, such cases behaved the same as in lower isolation levels.", "title": "Correctly report a serialization failure when MERGE encounters a concurrently-updated tuple in repeatable-read or serializable mode", "commits": ["13fab378e"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "8a02358aa03c1255369f0fa3de56d57dc1d5929292b77353d5fb36ce49a717a6", "section_path": ["Changes"], "commit_groups": [["13fab378e", "177037341", "2dcac93c0", "8bfaae6fb", "f6e63d4b8"]], "identity_text": "Correctly report a serialization failure when MERGE encounters a concurrently-updated tuple in repeatable-read or serializable mode (Tender Wang) Previously, such cases behaved the same as in lower isolation levels.", "commit_aliases": ["13fab378e", "177037341", "2dcac93c0", "8bfaae6fb", "f6e63d4b8"], "source_commits": ["13fab378e"], "source_entry_id": "18.4/changes/024", "db_id": "bfb26a4ca22c86d79dfde428bbcc3c24", "patch_ids": ["569476436f6f49fe3fc1c20af4157acf"], "statement_hash": "298c05dfef81a90cfb05f72e7375c2ceb55354d2b8c327b08b686d82ad2857b4", "relations": [{"rule": 2, "type": "equivalent", "target": "3f720165e3e8a599ba151cefd48b97e8", "evidence": {"same_day": true, "patch_ids": ["569476436f6f49fe3fc1c20af4157acf"], "statement_hash": "298c05dfef81a90cfb05f72e7375c2ceb55354d2b8c327b08b686d82ad2857b4"}}, {"rule": 2, "type": "equivalent", "target": "6827747aec40694708ad07aebaf4d3c0", "evidence": {"same_day": true, "patch_ids": ["569476436f6f49fe3fc1c20af4157acf"], "statement_hash": "298c05dfef81a90cfb05f72e7375c2ceb55354d2b8c327b08b686d82ad2857b4"}}, {"rule": 2, "type": "equivalent", "target": "f9969f9244f4ca14ba57359448274286", "evidence": {"same_day": true, "patch_ids": ["569476436f6f49fe3fc1c20af4157acf"], "statement_hash": "298c05dfef81a90cfb05f72e7375c2ceb55354d2b8c327b08b686d82ad2857b4"}}]}}, {"id": "18.4-da4a103ca5dfdddc", "source_entry_id": "18.4/changes/025", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix CREATE TABLE ... LIKE ... INCLUDING STATISTICS for cases where the source table has dropped column(s)", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-b893eef62a42d4d7", "source_entry_id": "17.10/changes/019", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix CREATE TABLE ... LIKE ... INCLUDING STATISTICS for cases where the source table has dropped column(s)"}], "entry": {"id": "18.4-da4a103ca5dfdddc", "cves": [], "html": "Fix CREATE TABLE ... LIKE ... INCLUDING STATISTICS for cases where the source table has dropped column(s) (Julien Tachoires) §
In such cases, extended statistics objects could be copied incorrectly, or the command could give an incorrect error.
", "text": "Fix CREATE TABLE ... LIKE ... INCLUDING STATISTICS for cases where the source table has dropped column(s) (Julien Tachoires) § In such cases, extended statistics objects could be copied incorrectly, or the command could give an incorrect error.", "title": "Fix CREATE TABLE ... LIKE ... INCLUDING STATISTICS for cases where the source table has dropped column(s)", "commits": ["149c875fc"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "ea4e0ec26e93b0117e68bbc15ef5d3f14ae1a23e12f8b9de9a4092a49e7865a7", "section_path": ["Changes"], "commit_groups": [["149c875fc", "6cf49e804", "76d15a7ee", "7bb519635", "81b56b47c", "a0104b447"]], "identity_text": "Fix CREATE TABLE ... LIKE ... INCLUDING STATISTICS for cases where the source table has dropped column(s) (Julien Tachoires) In such cases, extended statistics objects could be copied incorrectly, or the command could give an incorrect error.", "commit_aliases": ["149c875fc", "6cf49e804", "76d15a7ee", "7bb519635", "81b56b47c", "a0104b447"], "source_commits": ["149c875fc"], "source_entry_id": "18.4/changes/025", "db_id": "4b8420c7de509df1179d8ee1c1364ee6", "patch_ids": ["910e6f19667b7b2c274a7cfa4cfbf09c"], "statement_hash": "468cd074434d5b124a2f3ad7e4d4363935368333f67c114d461285e65aadff62", "relations": [{"rule": 2, "type": "equivalent", "target": "259f6916a28a7dd3bbeb72cc130b41a9", "evidence": {"same_day": true, "patch_ids": ["910e6f19667b7b2c274a7cfa4cfbf09c"], "statement_hash": "468cd074434d5b124a2f3ad7e4d4363935368333f67c114d461285e65aadff62"}}, {"rule": 2, "type": "equivalent", "target": "2e2724c6cc505b0329f5a78d83fd96cb", "evidence": {"same_day": true, "patch_ids": ["910e6f19667b7b2c274a7cfa4cfbf09c"], "statement_hash": "468cd074434d5b124a2f3ad7e4d4363935368333f67c114d461285e65aadff62"}}, {"rule": 2, "type": "equivalent", "target": "d68baf1e5d412f66c44df3a681238123", "evidence": {"same_day": true, "patch_ids": ["910e6f19667b7b2c274a7cfa4cfbf09c"], "statement_hash": "468cd074434d5b124a2f3ad7e4d4363935368333f67c114d461285e65aadff62"}}, {"rule": 2, "type": "equivalent", "target": "e7ce3c2946bfdef059fc3d3621ffd79d", "evidence": {"same_day": true, "patch_ids": ["910e6f19667b7b2c274a7cfa4cfbf09c"], "statement_hash": "468cd074434d5b124a2f3ad7e4d4363935368333f67c114d461285e65aadff62"}}]}}, {"id": "18.4-720217f77930b818", "source_entry_id": "18.4/changes/026", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Allow ALTER INDEX ... ATTACH PARTITION to mark the parent index valid if appropriate", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-a232240e214fd3cc", "source_entry_id": "17.10/changes/020", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Allow ALTER INDEX ... ATTACH PARTITION to mark the parent index valid if appropriate"}], "entry": {"id": "18.4-720217f77930b818", "cves": [], "html": "Allow ALTER INDEX ... ATTACH PARTITION to mark the parent index valid if appropriate (Sami Imseih) §
There are edge cases in which a partitioned index might remain marked as invalid even when all its leaf indexes are valid. This change provides a mechanism whereby a user can correct such a situation without resorting to manual catalog updates.
", "text": "Allow ALTER INDEX ... ATTACH PARTITION to mark the parent index valid if appropriate (Sami Imseih) § There are edge cases in which a partitioned index might remain marked as invalid even when all its leaf indexes are valid. This change provides a mechanism whereby a user can correct such a situation without resorting to manual catalog updates.", "title": "Allow ALTER INDEX ... ATTACH PARTITION to mark the parent index valid if appropriate", "commits": ["5713ac248"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "c7fb37f05c0c507003df5df3db21d5e4b480562fdecf037cd46f08d0a5239949", "section_path": ["Changes"], "commit_groups": [["0859000d0", "313355d68", "5713ac248", "9d3e094f1", "becf6d269", "d809b16d1"]], "identity_text": "Allow ALTER INDEX ... ATTACH PARTITION to mark the parent index valid if appropriate (Sami Imseih) There are edge cases in which a partitioned index might remain marked as invalid even when all its leaf indexes are valid. This change provides a mechanism whereby a user can correct such a situation without resorting to manual catalog updates.", "commit_aliases": ["0859000d0", "313355d68", "5713ac248", "9d3e094f1", "becf6d269", "d809b16d1"], "source_commits": ["5713ac248"], "source_entry_id": "18.4/changes/026", "db_id": "9efa82150808ee72d1b174825d7f47d3", "patch_ids": ["6f61faf076a411f9a9c18c51b74befa0"], "statement_hash": "d56280bb59ca7a2079394584e577949d3d1706a31278203bdc18b376a97f5ff5", "relations": [{"rule": 2, "type": "equivalent", "target": "15a0dfb907bce338c1244951e2379584", "evidence": {"same_day": true, "patch_ids": ["6f61faf076a411f9a9c18c51b74befa0"], "statement_hash": "d56280bb59ca7a2079394584e577949d3d1706a31278203bdc18b376a97f5ff5"}}, {"rule": 2, "type": "equivalent", "target": "3b47c18aac1b9d5d839c6ae4de3ae964", "evidence": {"same_day": true, "patch_ids": ["6f61faf076a411f9a9c18c51b74befa0"], "statement_hash": "d56280bb59ca7a2079394584e577949d3d1706a31278203bdc18b376a97f5ff5"}}, {"rule": 2, "type": "equivalent", "target": "73eae229fd96afa624d3ae9343724889", "evidence": {"same_day": true, "patch_ids": ["6f61faf076a411f9a9c18c51b74befa0"], "statement_hash": "d56280bb59ca7a2079394584e577949d3d1706a31278203bdc18b376a97f5ff5"}}, {"rule": 2, "type": "equivalent", "target": "ef8cca025501a2f559a921e005a2df3a", "evidence": {"same_day": true, "patch_ids": ["6f61faf076a411f9a9c18c51b74befa0"], "statement_hash": "d56280bb59ca7a2079394584e577949d3d1706a31278203bdc18b376a97f5ff5"}}]}}, {"id": "18.4-58699ca9b2eb6554", "source_entry_id": "18.4/changes/028", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix ALTER FOREIGN DATA WRAPPER to not drop the wrapper object's dependency on its handler function", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-c4bb8ccc29a46458", "source_entry_id": "17.10/changes/021", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix ALTER FOREIGN DATA WRAPPER to not drop the wrapper object's dependency on its handler function"}], "entry": {"id": "18.4-58699ca9b2eb6554", "cves": [], "html": "Fix ALTER FOREIGN DATA WRAPPER to not drop the wrapper object's dependency on its handler function (Jeff Davis) §
Disallow making a composite type be a member of itself via a multirange (Heikki Linnakangas) §
\nWe already forbade such cases when the intermediate type is a domain, array, composite type, or range; but multiranges were overlooked.
", "text": "Disallow making a composite type be a member of itself via a multirange (Heikki Linnakangas) § We already forbade such cases when the intermediate type is a domain, array, composite type, or range; but multiranges were overlooked.", "title": "Disallow making a composite type be a member of itself via a multirange", "commits": ["ff8f27d6e"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "8cc04a190a027ed7f7331686746174c2996429342f086de4aa3471e8450824e3", "section_path": ["Changes"], "commit_groups": [["06e304524", "34ebeb15c", "54343f6f9", "c7a1d5fc6", "dd4069197", "ff8f27d6e"]], "identity_text": "Disallow making a composite type be a member of itself via a multirange (Heikki Linnakangas) We already forbade such cases when the intermediate type is a domain, array, composite type, or range; but multiranges were overlooked.", "commit_aliases": ["06e304524", "34ebeb15c", "54343f6f9", "c7a1d5fc6", "dd4069197", "ff8f27d6e"], "source_commits": ["ff8f27d6e"], "source_entry_id": "18.4/changes/031", "db_id": "e65839c47b604979321948f58b376888", "patch_ids": ["31c00f6d7ed28a6712dcf1e113075156"], "statement_hash": "6b4527853dd5e8e984500173324ec598d423dfc66e71302f1bdff48a4af1e5d2", "relations": [{"rule": 2, "type": "equivalent", "target": "aaf1253e3301e7ce01966fdecb2168ff", "evidence": {"same_day": true, "patch_ids": ["31c00f6d7ed28a6712dcf1e113075156"], "statement_hash": "6b4527853dd5e8e984500173324ec598d423dfc66e71302f1bdff48a4af1e5d2"}}, {"rule": 2, "type": "equivalent", "target": "db27ce7162c0f5f66e5e36b2b4394be0", "evidence": {"same_day": true, "patch_ids": ["31c00f6d7ed28a6712dcf1e113075156"], "statement_hash": "6b4527853dd5e8e984500173324ec598d423dfc66e71302f1bdff48a4af1e5d2"}}, {"rule": 2, "type": "equivalent", "target": "dbfa0390a811562580299aed6addef7f", "evidence": {"same_day": true, "patch_ids": ["31c00f6d7ed28a6712dcf1e113075156"], "statement_hash": "6b4527853dd5e8e984500173324ec598d423dfc66e71302f1bdff48a4af1e5d2"}}, {"rule": 2, "type": "equivalent", "target": "e0d6011d1ad1750ec99d7b452609aa5c", "evidence": {"same_day": true, "patch_ids": ["31c00f6d7ed28a6712dcf1e113075156"], "statement_hash": "6b4527853dd5e8e984500173324ec598d423dfc66e71302f1bdff48a4af1e5d2"}}]}}, {"id": "18.4-4ed3df97c772ff79", "source_entry_id": "18.4/changes/032", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix datum-image comparisons to be insensitive to sign-extension variations", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-0fb5ea65c461a113", "source_entry_id": "17.10/changes/023", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix datum-image comparisons to be insensitive to sign-extension variations"}], "entry": {"id": "18.4-4ed3df97c772ff79", "cves": [], "html": "Fix datum-image comparisons to be insensitive to sign-extension variations (David Rowley) §
\nThis fixes some situations that previously led to “could not find memoization table entry” errors or wrong query results.
", "text": "Fix datum-image comparisons to be insensitive to sign-extension variations (David Rowley) § This fixes some situations that previously led to “could not find memoization table entry” errors or wrong query results.", "title": "Fix datum-image comparisons to be insensitive to sign-extension variations", "commits": ["49315de0c"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "3de832ddc8bf78b6182f0e1711d3c5ff5baade94f5f8eb4f9d6771b78542be2a", "section_path": ["Changes"], "commit_groups": [["0d866282b", "1bd90c887", "49315de0c", "6b2e091f0", "6ce5c310b", "d29808e35"]], "identity_text": "Fix datum-image comparisons to be insensitive to sign-extension variations (David Rowley) This fixes some situations that previously led to could not find memoization table entry errors or wrong query results.", "commit_aliases": ["0d866282b", "1bd90c887", "49315de0c", "6b2e091f0", "6ce5c310b", "d29808e35"], "source_commits": ["49315de0c"], "source_entry_id": "18.4/changes/032", "db_id": "c5c180d0b102c66e23f3e5c67497661a", "patch_ids": ["8b2152dc84fbefe58a465b0d497fe197"], "statement_hash": "95b38df8932c40bbb6eed0884f5ec817fd4ee7218c45df42545da1f44dd8095a", "relations": [{"rule": 2, "type": "equivalent", "target": "5cabc37ab2a14b9bb0980c3ed400e023", "evidence": {"same_day": true, "patch_ids": ["8b2152dc84fbefe58a465b0d497fe197"], "statement_hash": "95b38df8932c40bbb6eed0884f5ec817fd4ee7218c45df42545da1f44dd8095a"}}, {"rule": 2, "type": "equivalent", "target": "6de901a8850aaba4f6cb4f60757fd10b", "evidence": {"same_day": true, "patch_ids": ["8b2152dc84fbefe58a465b0d497fe197"], "statement_hash": "95b38df8932c40bbb6eed0884f5ec817fd4ee7218c45df42545da1f44dd8095a"}}, {"rule": 2, "type": "equivalent", "target": "e186e88d722a03078d4189e25842fa12", "evidence": {"same_day": true, "patch_ids": ["8b2152dc84fbefe58a465b0d497fe197"], "statement_hash": "95b38df8932c40bbb6eed0884f5ec817fd4ee7218c45df42545da1f44dd8095a"}}, {"rule": 2, "type": "equivalent", "target": "f9a962dc778922758842bad523e4e935", "evidence": {"same_day": true, "patch_ids": ["8b2152dc84fbefe58a465b0d497fe197"], "statement_hash": "95b38df8932c40bbb6eed0884f5ec817fd4ee7218c45df42545da1f44dd8095a"}}]}}, {"id": "18.4-e5344bf8a6d35197", "source_entry_id": "18.4/changes/033", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix incorrect logic for hashed IN/NOT IN with non-strict equality operator", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-c7e5a864f1920ba5", "source_entry_id": "17.10/changes/024", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix incorrect logic for hashed IN/NOT IN with non-strict equality operator"}], "entry": {"id": "18.4-e5344bf8a6d35197", "cves": [], "html": "Fix incorrect logic for hashed IN/NOT IN with non-strict equality operator (Chengpeng Yan) §
The previous coding could crash or give wrong answers. All built-in data types have strict equality operators, so that this issue could only arise with an extension data type.
", "text": "Fix incorrect logic for hashed IN/NOT IN with non-strict equality operator (Chengpeng Yan) § The previous coding could crash or give wrong answers. All built-in data types have strict equality operators, so that this issue could only arise with an extension data type.", "title": "Fix incorrect logic for hashed IN/NOT IN with non-strict equality operator", "commits": ["035c520db"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "ffb794be9437535a124258dc5a5a3054bb11a3db6230d2021690f0e0220a79e0", "section_path": ["Changes"], "commit_groups": [["035c520db", "109de35b7", "3fda3e12f", "622f8b530", "94219a73f", "a2a0060d5"]], "identity_text": "Fix incorrect logic for hashed IN/NOT IN with non-strict equality operator (Chengpeng Yan) The previous coding could crash or give wrong answers. All built-in data types have strict equality operators, so that this issue could only arise with an extension data type.", "commit_aliases": ["035c520db", "109de35b7", "3fda3e12f", "622f8b530", "94219a73f", "a2a0060d5"], "source_commits": ["035c520db"], "source_entry_id": "18.4/changes/033", "db_id": "d1a95a788ffc450fd8a8b393d2c3e55d", "patch_ids": ["73bcd2dbc996c0415640dea74d4f247f"], "statement_hash": "f620e21c617639503e22ec199ea3bdfd888287e95b5e026131bfa74e2fd18e5d", "relations": [{"rule": 2, "type": "equivalent", "target": "2a86497013a318262f46769723449b63", "evidence": {"same_day": true, "patch_ids": ["73bcd2dbc996c0415640dea74d4f247f"], "statement_hash": "f620e21c617639503e22ec199ea3bdfd888287e95b5e026131bfa74e2fd18e5d"}}, {"rule": 2, "type": "equivalent", "target": "450e4329b437178c4c67084a2ce52024", "evidence": {"same_day": true, "patch_ids": ["73bcd2dbc996c0415640dea74d4f247f"], "statement_hash": "f620e21c617639503e22ec199ea3bdfd888287e95b5e026131bfa74e2fd18e5d"}}, {"rule": 2, "type": "equivalent", "target": "6a9e4a1d32172e81ee680d6f0342ca63", "evidence": {"same_day": true, "patch_ids": ["73bcd2dbc996c0415640dea74d4f247f"], "statement_hash": "f620e21c617639503e22ec199ea3bdfd888287e95b5e026131bfa74e2fd18e5d"}}, {"rule": 2, "type": "equivalent", "target": "c26aa4cfe9a48bc8f6b4f3924802efa7", "evidence": {"same_day": true, "patch_ids": ["73bcd2dbc996c0415640dea74d4f247f"], "statement_hash": "f620e21c617639503e22ec199ea3bdfd888287e95b5e026131bfa74e2fd18e5d"}}]}}, {"id": "18.4-695d3a73d2ecfb3e", "source_entry_id": "18.4/changes/034", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Truncate overly-long locale-specific numeric symbols in to_char()", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-ead7a4370e3d50c0", "source_entry_id": "17.10/changes/025", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Truncate overly-long locale-specific numeric symbols in to_char()"}], "entry": {"id": "18.4-695d3a73d2ecfb3e", "cves": [], "html": "Truncate overly-long locale-specific numeric symbols in to_char() (Tom Lane) §
If a locale specified a currency symbol, thousands separator, or decimal or sign symbol more than 8 bytes long, a buffer overrun was possible. No such locales exist in the real world, and it's impractical for an unprivileged attacker to install a malicious locale definition underneath a Postgres server; but for safety's sake check for overlength symbols and truncate if needed.
", "text": "Truncate overly-long locale-specific numeric symbols in to_char() (Tom Lane) § If a locale specified a currency symbol, thousands separator, or decimal or sign symbol more than 8 bytes long, a buffer overrun was possible. No such locales exist in the real world, and it's impractical for an unprivileged attacker to install a malicious locale definition underneath a Postgres server; but for safety's sake check for overlength symbols and truncate if needed.", "title": "Truncate overly-long locale-specific numeric symbols in to_char()", "commits": ["580e7be88"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "70eb34f88d8f608012378c0560ddedc3d3a33faefc96ac07099ec4ab95e051f1", "section_path": ["Changes"], "commit_groups": [["580e7be88", "8a6f08c0c", "a50777680", "c97a28618", "e1e60f148", "f60d25986"]], "identity_text": "Truncate overly-long locale-specific numeric symbols in to_char() (Tom Lane) If a locale specified a currency symbol, thousands separator, or decimal or sign symbol more than 8 bytes long, a buffer overrun was possible. No such locales exist in the real world, and it's impractical for an unprivileged attacker to install a malicious locale definition underneath a Postgres server; but for safety's sake check for overlength symbols and truncate if needed.", "commit_aliases": ["580e7be88", "8a6f08c0c", "a50777680", "c97a28618", "e1e60f148", "f60d25986"], "source_commits": ["580e7be88"], "source_entry_id": "18.4/changes/034", "db_id": "606d4464f34532059b31083c8d4b85db", "patch_ids": ["a55b3cc17f0905d7ae426fd181a6dfc3"], "statement_hash": "faa5531634d9cdfe864f4512cf61a4628efe72bf20a627237eac6e0fc2e723b0", "relations": [{"rule": 2, "type": "equivalent", "target": "07daab7dbccbfcc34db05980b3a74098", "evidence": {"same_day": true, "patch_ids": ["a55b3cc17f0905d7ae426fd181a6dfc3"], "statement_hash": "faa5531634d9cdfe864f4512cf61a4628efe72bf20a627237eac6e0fc2e723b0"}}, {"rule": 2, "type": "equivalent", "target": "29acc0aac3cc6b0ee03ac19b4559887d", "evidence": {"same_day": true, "patch_ids": ["a55b3cc17f0905d7ae426fd181a6dfc3"], "statement_hash": "faa5531634d9cdfe864f4512cf61a4628efe72bf20a627237eac6e0fc2e723b0"}}, {"rule": 2, "type": "equivalent", "target": "7477baaf42cc60c640f8610e0225343b", "evidence": {"same_day": true, "patch_ids": ["a55b3cc17f0905d7ae426fd181a6dfc3"], "statement_hash": "faa5531634d9cdfe864f4512cf61a4628efe72bf20a627237eac6e0fc2e723b0"}}, {"rule": 2, "type": "equivalent", "target": "da89f430482b72634ad3d2f296bb5a93", "evidence": {"same_day": true, "patch_ids": ["a55b3cc17f0905d7ae426fd181a6dfc3"], "statement_hash": "faa5531634d9cdfe864f4512cf61a4628efe72bf20a627237eac6e0fc2e723b0"}}]}}, {"id": "18.4-e6587b3cd0787b2e", "source_entry_id": "18.4/changes/035", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Prevent buffer overruns when parsing an affix file for an Ispell dictionary", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-666b81e0c79b2b28", "source_entry_id": "17.10/changes/026", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Prevent buffer overruns when parsing an affix file for an Ispell dictionary"}], "entry": {"id": "18.4-e6587b3cd0787b2e", "cves": [], "html": "Prevent buffer overruns when parsing an affix file for an Ispell dictionary (Tom Lane) § §
A corrupt or malicious affix file could crash the server. This is not considered a security issue because text search configuration files are presumed trustworthy, but it still seems worth fixing.
", "text": "Prevent buffer overruns when parsing an affix file for an Ispell dictionary (Tom Lane) § § A corrupt or malicious affix file could crash the server. This is not considered a security issue because text search configuration files are presumed trustworthy, but it still seems worth fixing.", "title": "Prevent buffer overruns when parsing an affix file for an Ispell dictionary", "commits": ["00c6e0819", "c2bfeb3bb"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "26b8c98f5f285541175bbe791e9adc08dd729f507c8744e2c34ae51d9dfb43ea", "section_path": ["Changes"], "commit_groups": [["00c6e0819", "0b196d3db", "21a24d709", "42383d32d", "d7970e7e9", "ea5f0d176"], ["17f72e037", "6cae0c2bd", "844bb90d4", "a5426dbf8", "c2bfeb3bb", "f852c9093"]], "identity_text": "Prevent buffer overruns when parsing an affix file for an Ispell dictionary (Tom Lane) A corrupt or malicious affix file could crash the server. This is not considered a security issue because text search configuration files are presumed trustworthy, but it still seems worth fixing.", "commit_aliases": ["00c6e0819", "0b196d3db", "17f72e037", "21a24d709", "42383d32d", "6cae0c2bd", "844bb90d4", "a5426dbf8", "c2bfeb3bb", "d7970e7e9", "ea5f0d176", "f852c9093"], "source_commits": ["00c6e0819", "c2bfeb3bb"], "source_entry_id": "18.4/changes/035", "db_id": "12f322f4feb75f55804ad196b114a9d6", "patch_ids": ["3b2347be1395aa44c1c6ae6a8fa24149", "fb61cc9fc6ef6ecc94c4f87d31a648bd"], "statement_hash": "6442ebdc43f39cc7a336c76cc8f8bcdfb68cc5683190ee35457bd8a1cd9e22d8", "relations": [{"rule": 2, "type": "equivalent", "target": "2b5095497f4832976becc4b644155c51", "evidence": {"same_day": true, "patch_ids": ["3b2347be1395aa44c1c6ae6a8fa24149", "fb61cc9fc6ef6ecc94c4f87d31a648bd"], "statement_hash": "6442ebdc43f39cc7a336c76cc8f8bcdfb68cc5683190ee35457bd8a1cd9e22d8"}}, {"rule": 2, "type": "equivalent", "target": "5f8b6d695a4f9576cfb99b263e2e4ff7", "evidence": {"same_day": true, "patch_ids": ["3b2347be1395aa44c1c6ae6a8fa24149", "fb61cc9fc6ef6ecc94c4f87d31a648bd"], "statement_hash": "6442ebdc43f39cc7a336c76cc8f8bcdfb68cc5683190ee35457bd8a1cd9e22d8"}}, {"rule": 2, "type": "equivalent", "target": "cd403cd225ef88fed48df9f593dd683b", "evidence": {"same_day": true, "patch_ids": ["3b2347be1395aa44c1c6ae6a8fa24149", "fb61cc9fc6ef6ecc94c4f87d31a648bd"], "statement_hash": "6442ebdc43f39cc7a336c76cc8f8bcdfb68cc5683190ee35457bd8a1cd9e22d8"}}, {"rule": 2, "type": "equivalent", "target": "f2129c1b029d4e186640295ff2fd808d", "evidence": {"same_day": true, "patch_ids": ["3b2347be1395aa44c1c6ae6a8fa24149", "fb61cc9fc6ef6ecc94c4f87d31a648bd"], "statement_hash": "6442ebdc43f39cc7a336c76cc8f8bcdfb68cc5683190ee35457bd8a1cd9e22d8"}}]}}, {"id": "18.4-e679f36c64f131bf", "source_entry_id": "18.4/changes/036", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Guard against integer overflow in calculations of frame start and end positions for window aggregates", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-9cc0aae20d353dbd", "source_entry_id": "17.10/changes/027", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Guard against integer overflow in calculations of frame start and end positions for window aggregates"}], "entry": {"id": "18.4-e679f36c64f131bf", "cves": [], "html": "Guard against integer overflow in calculations of frame start and end positions for window aggregates (Richard Guo) §
\nVery large user-specified offsets (close to INT64_MAX) could result in errors or incorrect query results.
", "text": "Guard against integer overflow in calculations of frame start and end positions for window aggregates (Richard Guo) § Very large user-specified offsets (close to INT64_MAX) could result in errors or incorrect query results.", "title": "Guard against integer overflow in calculations of frame start and end positions for window aggregates", "commits": ["bfc7dff26"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "7cc0adb14be7a94e57f2517573a111a3e3ebe1c324a0215381ea483c66ba2a2b", "section_path": ["Changes"], "commit_groups": [["0fe032e6a", "305cf0df0", "4da71fc37", "8b6c89e37", "bfc7dff26", "f8736f8bc"]], "identity_text": "Guard against integer overflow in calculations of frame start and end positions for window aggregates (Richard Guo) Very large user-specified offsets (close to INT64_MAX) could result in errors or incorrect query results.", "commit_aliases": ["0fe032e6a", "305cf0df0", "4da71fc37", "8b6c89e37", "bfc7dff26", "f8736f8bc"], "source_commits": ["bfc7dff26"], "source_entry_id": "18.4/changes/036", "db_id": "511c913495519e0301f1fb895b89e0e3", "patch_ids": ["55f185c77388b5ccf5f79078a7a19b0b"], "statement_hash": "84aa1ad98df37853c6497eff68ec71c4a468e09bd91604bc168bf3a8ad45d544", "relations": [{"rule": 2, "type": "equivalent", "target": "8ad5f4df6d3f1b7115577a0c720eb3e0", "evidence": {"same_day": true, "patch_ids": ["55f185c77388b5ccf5f79078a7a19b0b"], "statement_hash": "84aa1ad98df37853c6497eff68ec71c4a468e09bd91604bc168bf3a8ad45d544"}}, {"rule": 2, "type": "equivalent", "target": "9a742821f3f95e4a90a5c8c342890d50", "evidence": {"same_day": true, "patch_ids": ["55f185c77388b5ccf5f79078a7a19b0b"], "statement_hash": "84aa1ad98df37853c6497eff68ec71c4a468e09bd91604bc168bf3a8ad45d544"}}, {"rule": 2, "type": "equivalent", "target": "cac7bd4fb899dfb735baa61da9c859ec", "evidence": {"same_day": true, "patch_ids": ["55f185c77388b5ccf5f79078a7a19b0b"], "statement_hash": "84aa1ad98df37853c6497eff68ec71c4a468e09bd91604bc168bf3a8ad45d544"}}, {"rule": 2, "type": "equivalent", "target": "f1cd95144d4553602b7e2fbfe36961ad", "evidence": {"same_day": true, "patch_ids": ["55f185c77388b5ccf5f79078a7a19b0b"], "statement_hash": "84aa1ad98df37853c6497eff68ec71c4a468e09bd91604bc168bf3a8ad45d544"}}]}}, {"id": "18.4-468cc4bcd201b1ba", "source_entry_id": "18.4/changes/037", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix array_agg_array_combine() to combine the arrays' null bitmaps correctly", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-62d51a1802de9407", "source_entry_id": "17.10/changes/028", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix array_agg_array_combine() to combine the arrays' null bitmaps correctly"}], "entry": {"id": "18.4-468cc4bcd201b1ba", "cves": [], "html": "Fix array_agg_array_combine() to combine the arrays' null bitmaps correctly (Dmytro Astapov) §
This mistake resulted in sometimes-incorrect output from parallelized array_agg(anyarray) calculations.
Retry sync_file_range() if it returns error code EINTR (DaeMyung Kang) §
Fix incorrect behavior of pg_stat_reset_single_table_counters() on a shared catalog (Chao Li) §
Such cases had a side-effect of resetting the current database's stat_reset_timestamp, which was unintended.
Update activity statistics when a parallel apply worker is idle (Zhijie Hou) §
\nPreviously, statistics from a recently-completed transaction might go unreported for long intervals, particularly if the workload is light.
", "text": "Update activity statistics when a parallel apply worker is idle (Zhijie Hou) § Previously, statistics from a recently-completed transaction might go unreported for long intervals, particularly if the workload is light.", "title": "Update activity statistics when a parallel apply worker is idle", "commits": ["44c8dc280"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "0f38a0c7b2916f63a17b15949ea31d283036437e30490f8550f9eee25b66836c", "section_path": ["Changes"], "commit_groups": [["090c4297e", "44c8dc280", "88d7fdcc9", "d052f6c7d"]], "identity_text": "Update activity statistics when a parallel apply worker is idle (Zhijie Hou) Previously, statistics from a recently-completed transaction might go unreported for long intervals, particularly if the workload is light.", "commit_aliases": ["090c4297e", "44c8dc280", "88d7fdcc9", "d052f6c7d"], "source_commits": ["44c8dc280"], "source_entry_id": "18.4/changes/040", "db_id": "980b17cc0e380660feb5723048978d0c", "patch_ids": ["2d9114e9de0545265b46f9271e79774e"], "statement_hash": "1425951cf41b73475715e34b86444749dadef32d8dd753ca05fb84c5dcab7db0", "relations": [{"rule": 2, "type": "equivalent", "target": "677b87203fcf8da98790d6378484a333", "evidence": {"same_day": true, "patch_ids": ["2d9114e9de0545265b46f9271e79774e"], "statement_hash": "1425951cf41b73475715e34b86444749dadef32d8dd753ca05fb84c5dcab7db0"}}, {"rule": 2, "type": "equivalent", "target": "96a3e2b2d17bbc2072d29a84e39fe9f0", "evidence": {"same_day": true, "patch_ids": ["2d9114e9de0545265b46f9271e79774e"], "statement_hash": "1425951cf41b73475715e34b86444749dadef32d8dd753ca05fb84c5dcab7db0"}}]}}, {"id": "18.4-9a9061bf537ff043", "source_entry_id": "18.4/changes/041", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix “no relation entry for relid 0” failure while estimating array lengths in set operations", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-b34c916fe548b623", "source_entry_id": "17.10/changes/032", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix “no relation entry for relid 0” failure while estimating array lengths in set operations"}], "entry": {"id": "18.4-9a9061bf537ff043", "cves": [], "html": "Fix “no relation entry for relid 0” failure while estimating array lengths in set operations (Tender Wang) §
", "text": "Fix “no relation entry for relid 0” failure while estimating array lengths in set operations (Tender Wang) §", "title": "Fix “no relation entry for relid 0” failure while estimating array lengths in set operations", "commits": ["13e20d1c9"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "ecd4d9794c67edfc061e72cc6ae874e0b3d09d0e7aae0513148948a05a1926a2", "section_path": ["Changes"], "commit_groups": [["13e20d1c9", "77d0e82e5", "93ed18720"]], "identity_text": "Fix no relation entry for relid 0 failure while estimating array lengths in set operations (Tender Wang)", "commit_aliases": ["13e20d1c9", "77d0e82e5", "93ed18720"], "source_commits": ["13e20d1c9"], "source_entry_id": "18.4/changes/041", "db_id": "8b93ba333f257971520839fdfb923dc8", "patch_ids": ["564821c3480587e28f1a951776d143da"], "statement_hash": "79d2c12d4a24236694523bc4108c4ef1ad8487e654635a5140572e534f35ca67", "relations": [{"rule": 2, "type": "equivalent", "target": "767acd748e88add4e0b136661b09348d", "evidence": {"same_day": true, "patch_ids": ["564821c3480587e28f1a951776d143da"], "statement_hash": "79d2c12d4a24236694523bc4108c4ef1ad8487e654635a5140572e534f35ca67"}}]}}, {"id": "18.4-1b7a6be51f8649d8", "source_entry_id": "18.4/changes/042", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix buffer overread when pglz_decompress() receives corrupt input", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-fc2a0ba457a12efa", "source_entry_id": "17.10/changes/033", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix buffer overread when pglz_decompress() receives corrupt input"}], "entry": {"id": "18.4-1b7a6be51f8649d8", "cves": [], "html": "Fix buffer overread when pglz_decompress() receives corrupt input (Andrew Dunstan) §
It was possible to read a few bytes past the end of the input, which in very unlucky cases might cause a crash.
", "text": "Fix buffer overread when pglz_decompress() receives corrupt input (Andrew Dunstan) § It was possible to read a few bytes past the end of the input, which in very unlucky cases might cause a crash.", "title": "Fix buffer overread when pglz_decompress() receives corrupt input", "commits": ["c3e436b1c"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "2622fb1e0384f9134f8addee155a77c817d66d712d29b1d6e4192715763b3594", "section_path": ["Changes"], "commit_groups": [["2b5ba2a0a", "c05c3baf1", "c3e436b1c", "c88ad3a21", "de32a01e7", "e630f65d0"]], "identity_text": "Fix buffer overread when pglz_decompress() receives corrupt input (Andrew Dunstan) It was possible to read a few bytes past the end of the input, which in very unlucky cases might cause a crash.", "commit_aliases": ["2b5ba2a0a", "c05c3baf1", "c3e436b1c", "c88ad3a21", "de32a01e7", "e630f65d0"], "source_commits": ["c3e436b1c"], "source_entry_id": "18.4/changes/042", "db_id": "0ae0f8c53b17ca5f253bbab76a0d9b74", "patch_ids": ["c0bb5d07bdfbe114b7578587383a80fa"], "statement_hash": "bd7b2a40bb8d7d7798cf8ecb76df72f44a9455b09e9d2f6b36769b9fa697b84d", "relations": [{"rule": 2, "type": "equivalent", "target": "31b4e32fc9a04113a1aeaa4d2e794a7e", "evidence": {"same_day": true, "patch_ids": ["c0bb5d07bdfbe114b7578587383a80fa"], "statement_hash": "bd7b2a40bb8d7d7798cf8ecb76df72f44a9455b09e9d2f6b36769b9fa697b84d"}}, {"rule": 2, "type": "equivalent", "target": "7d77c3cf4d2df5b2b05bab302e7d6447", "evidence": {"same_day": true, "patch_ids": ["c0bb5d07bdfbe114b7578587383a80fa"], "statement_hash": "bd7b2a40bb8d7d7798cf8ecb76df72f44a9455b09e9d2f6b36769b9fa697b84d"}}, {"rule": 2, "type": "equivalent", "target": "8f0710244d42d6ab314f2ef4a78fa91d", "evidence": {"same_day": true, "patch_ids": ["c0bb5d07bdfbe114b7578587383a80fa"], "statement_hash": "bd7b2a40bb8d7d7798cf8ecb76df72f44a9455b09e9d2f6b36769b9fa697b84d"}}, {"rule": 2, "type": "equivalent", "target": "f313199e743d40f3a6df92ac0387bcfa", "evidence": {"same_day": true, "patch_ids": ["c0bb5d07bdfbe114b7578587383a80fa"], "statement_hash": "bd7b2a40bb8d7d7798cf8ecb76df72f44a9455b09e9d2f6b36769b9fa697b84d"}}]}}, {"id": "18.4-dd2acc7c0ea39340", "source_entry_id": "18.4/changes/043", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix incremental JSON parser's handling of numeric tokens that cross input buffer boundaries", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-4d205143d096f8a7", "source_entry_id": "17.10/changes/034", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix incremental JSON parser's handling of numeric tokens that cross input buffer boundaries"}], "entry": {"id": "18.4-dd2acc7c0ea39340", "cves": [], "html": "Fix incremental JSON parser's handling of numeric tokens that cross input buffer boundaries (Andrew Dunstan) §
\nIt was possible to accept an incorrectly-formatted number, leading to failures later.
", "text": "Fix incremental JSON parser's handling of numeric tokens that cross input buffer boundaries (Andrew Dunstan) § It was possible to accept an incorrectly-formatted number, leading to failures later.", "title": "Fix incremental JSON parser's handling of numeric tokens that cross input buffer boundaries", "commits": ["3e4955630"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "7f354a831bb7d2c88088a9e7dbc4aedf98fa61903915939d634cc0d68b63f18c", "section_path": ["Changes"], "commit_groups": [["2478bd5db", "2e373785e", "3e4955630"]], "identity_text": "Fix incremental JSON parser's handling of numeric tokens that cross input buffer boundaries (Andrew Dunstan) It was possible to accept an incorrectly-formatted number, leading to failures later.", "commit_aliases": ["2478bd5db", "2e373785e", "3e4955630"], "source_commits": ["3e4955630"], "source_entry_id": "18.4/changes/043", "db_id": "19c77cbe8cf7f7f6073b8df365b35790", "patch_ids": ["3a87b59bc06c42cccbaad53a59170a0f"], "statement_hash": "e510b6a330131e0a9e306a9599eda0558466f19ce69118716f8d3a5ac91b7463", "relations": [{"rule": 2, "type": "equivalent", "target": "56aacc58e4b3c19869652bc7bccc257f", "evidence": {"same_day": true, "patch_ids": ["3a87b59bc06c42cccbaad53a59170a0f"], "statement_hash": "e510b6a330131e0a9e306a9599eda0558466f19ce69118716f8d3a5ac91b7463"}}]}}, {"id": "18.4-7eaea7144baecfd7", "source_entry_id": "18.4/changes/044", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Prevent bloating relation visibility maps during restore of an incremental backup", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-1a6869f33820ce4a", "source_entry_id": "17.10/changes/035", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Prevent bloating relation visibility maps during restore of an incremental backup"}], "entry": {"id": "18.4-7eaea7144baecfd7", "cves": [], "html": "Prevent bloating relation visibility maps during restore of an incremental backup (Robert Haas) §
\nRestore could append many blocks of zeroes to a visibility map, due to incorrect computation of the expected file length. This does not result in data corruption, but it could waste a substantial amount of disk space.
", "text": "Prevent bloating relation visibility maps during restore of an incremental backup (Robert Haas) § Restore could append many blocks of zeroes to a visibility map, due to incorrect computation of the expected file length. This does not result in data corruption, but it could waste a substantial amount of disk space.", "title": "Prevent bloating relation visibility maps during restore of an incremental backup", "commits": ["9540c0e5d"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "a2095c132a2c13d2446246bda6509150086aa1af77f74a38e9c9a8a7a9001a44", "section_path": ["Changes"], "commit_groups": [["076bc57fa", "9540c0e5d", "ffc226ab6"]], "identity_text": "Prevent bloating relation visibility maps during restore of an incremental backup (Robert Haas) Restore could append many blocks of zeroes to a visibility map, due to incorrect computation of the expected file length. This does not result in data corruption, but it could waste a substantial amount of disk space.", "commit_aliases": ["076bc57fa", "9540c0e5d", "ffc226ab6"], "source_commits": ["9540c0e5d"], "source_entry_id": "18.4/changes/044", "db_id": "53b7f65c3e08f9341b47945f095569e8", "patch_ids": ["738fd594a90796c809e728fbc5651d22"], "statement_hash": "8be561d5ad13698eca7d90b5fd9fbde1028f705a3031ab9e786774f2c9f7b3a2", "relations": [{"rule": 2, "type": "equivalent", "target": "8d78dd5d30d4094d87fbfc3de7307fc9", "evidence": {"same_day": true, "patch_ids": ["738fd594a90796c809e728fbc5651d22"], "statement_hash": "8be561d5ad13698eca7d90b5fd9fbde1028f705a3031ab9e786774f2c9f7b3a2"}}]}}, {"id": "18.4-3a216fc3a56d1f2e", "source_entry_id": "18.4/changes/045", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Use C collation, not the database's default collation, in catalog cache lookups on text columns", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-a4c0aebef3a26164", "source_entry_id": "17.10/changes/036", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Use C collation, not the database's default collation, in catalog cache lookups on text columns"}], "entry": {"id": "18.4-3a216fc3a56d1f2e", "cves": [], "html": "Use C collation, not the database's default collation, in catalog cache lookups on text columns (Jeff Davis) §
\nThis avoids failures in edge cases such as physical replication startup, where there is no identified database so that a default collation cannot be determined.
", "text": "Use C collation, not the database's default collation, in catalog cache lookups on text columns (Jeff Davis) § This avoids failures in edge cases such as physical replication startup, where there is no identified database so that a default collation cannot be determined.", "title": "Use C collation, not the database's default collation, in catalog cache lookups on text columns", "commits": ["03c4f243e"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "ca6290e5a73104a965da328f8ab392537a5d88f2b104870bd144639e79684eee", "section_path": ["Changes"], "commit_groups": [["03c4f243e", "9dda30dd3", "dbf217c1c"]], "identity_text": "Use C collation, not the database's default collation, in catalog cache lookups on text columns (Jeff Davis) This avoids failures in edge cases such as physical replication startup, where there is no identified database so that a default collation cannot be determined.", "commit_aliases": ["03c4f243e", "9dda30dd3", "dbf217c1c"], "source_commits": ["03c4f243e"], "source_entry_id": "18.4/changes/045", "db_id": "eedc842000f52b63d80fc16df2a3a7fa", "patch_ids": ["1a030429f091c1d56d52205c2930f3cc"], "statement_hash": "c93618f8a7ca56819cbbb9cf9df80953c6fe150819de3e1e7fad58e879a5f52f", "relations": [{"rule": 2, "type": "equivalent", "target": "b4e242e2dfdaddd1a84c10f08ab6fdb6", "evidence": {"same_day": true, "patch_ids": ["1a030429f091c1d56d52205c2930f3cc"], "statement_hash": "c93618f8a7ca56819cbbb9cf9df80953c6fe150819de3e1e7fad58e879a5f52f"}}]}}, {"id": "18.4-401593c891e36279", "source_entry_id": "18.4/changes/046", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Prevent stuck slotsync worker processes from blocking promotion of a standby server", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-f9ca5e51b9e70665", "source_entry_id": "17.10/changes/037", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Prevent stuck slotsync worker processes from blocking promotion of a standby server"}], "entry": {"id": "18.4-401593c891e36279", "cves": [], "html": "Prevent stuck slotsync worker processes from blocking promotion of a standby server (Nisha Moond, Ajin Cherian) § § §
\nA worker process that was vainly waiting for a response from the primary would delay promotion for an unreasonable amount of time.
", "text": "Prevent stuck slotsync worker processes from blocking promotion of a standby server (Nisha Moond, Ajin Cherian) § § § A worker process that was vainly waiting for a response from the primary would delay promotion for an unreasonable amount of time.", "title": "Prevent stuck slotsync worker processes from blocking promotion of a standby server", "commits": ["58c1188a3", "94efd308b", "acf49bfed"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "aaebffec95e506635382bd0e94196d1f16aaf5d2ac954c07ff39f53f2221a160", "section_path": ["Changes"], "commit_groups": [["1362bc33e", "4bed04d39", "94efd308b"], ["15910b1c3", "58c1188a3", "db93032a7"], ["586f4266f", "acf49bfed"]], "identity_text": "Prevent stuck slotsync worker processes from blocking promotion of a standby server (Nisha Moond, Ajin Cherian) A worker process that was vainly waiting for a response from the primary would delay promotion for an unreasonable amount of time.", "commit_aliases": ["1362bc33e", "15910b1c3", "4bed04d39", "586f4266f", "58c1188a3", "94efd308b", "acf49bfed", "db93032a7"], "source_commits": ["58c1188a3", "94efd308b", "acf49bfed"], "source_entry_id": "18.4/changes/046", "db_id": "e197fe7e68af6fc16360be64080650fb", "patch_ids": ["0631393988a6e439ca6c21edde5e08d0", "d9eacc799b9f25f84495940918c9855b", "f0a73f0938081885d684993c67dca652"], "statement_hash": "86bf0b738194ea614f01e7178f35891e27741d55257e8b4157bf2182cf0b6509", "relations": [{"rule": 2, "type": "equivalent", "target": "299696a41fbafef0ba66bb25a5daba56", "evidence": {"same_day": true, "patch_ids": ["0631393988a6e439ca6c21edde5e08d0", "d9eacc799b9f25f84495940918c9855b", "f0a73f0938081885d684993c67dca652"], "statement_hash": "86bf0b738194ea614f01e7178f35891e27741d55257e8b4157bf2182cf0b6509"}}]}}, {"id": "18.4-59479740d5b1c42c", "source_entry_id": "18.4/changes/047", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix excessive log output from idle slotsync worker processes", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-f979cb3196409f3b", "source_entry_id": "17.10/changes/038", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix excessive log output from idle slotsync worker processes"}], "entry": {"id": "18.4-59479740d5b1c42c", "cves": [], "html": "Fix excessive log output from idle slotsync worker processes (Zhijie Hou) §
", "text": "Fix excessive log output from idle slotsync worker processes (Zhijie Hou) §", "title": "Fix excessive log output from idle slotsync worker processes", "commits": ["540fe8fb5"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "56513a1c633ce8a47b2cb0bde6139eca65a3e5251dbaeea476d9f7cd3c3265ca", "section_path": ["Changes"], "commit_groups": [["540fe8fb5", "85c17f612", "91741b7cb"]], "identity_text": "Fix excessive log output from idle slotsync worker processes (Zhijie Hou)", "commit_aliases": ["540fe8fb5", "85c17f612", "91741b7cb"], "source_commits": ["540fe8fb5"], "source_entry_id": "18.4/changes/047", "db_id": "695bd513323417fe3250f7a82dc60ff8", "patch_ids": ["fc452e68c97468e4711e1e83f06f17af"], "statement_hash": "2a2af3205a99361da43475c5da46b1c66376f789f13a1c2ee0f23624cbb849a4", "relations": [{"rule": 2, "type": "equivalent", "target": "823fb36d471b0ef6060bc9363c89e12c", "evidence": {"same_day": true, "patch_ids": ["fc452e68c97468e4711e1e83f06f17af"], "statement_hash": "2a2af3205a99361da43475c5da46b1c66376f789f13a1c2ee0f23624cbb849a4"}}]}}, {"id": "18.4-2024d132beedef06", "source_entry_id": "18.4/changes/048", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Ensure that tuplestore data structures are internally consistent even after an error", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-c10485892a0cc1b6", "source_entry_id": "17.10/changes/039", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Ensure that tuplestore data structures are internally consistent even after an error"}], "entry": {"id": "18.4-2024d132beedef06", "cves": [], "html": "Ensure that tuplestore data structures are internally consistent even after an error (Tom Lane) §
\nThe code was previously careless about this, which is fine most of the time but is problematic for the tuplestore backing a WITH HOLD cursor. In v15 and before this leads to easily-reproducible crashes; later branches are not known to be vulnerable, but it seems best to preserve consistency in all.
Fix premature NULL lag reporting in pg_stat_replication (Shinya Kato) §
The lag columns frequently read as NULL even while replication activity was happening.
", "text": "Fix premature NULL lag reporting in pg_stat_replication (Shinya Kato) § The lag columns frequently read as NULL even while replication activity was happening.", "title": "Fix premature NULL lag reporting in pg_stat_replication", "commits": ["98e96e579"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "eaaba4794adf71b00e0e8b48b6411961a27dddf2c7f6f550898554fd54f50dad", "section_path": ["Changes"], "commit_groups": [["246c296f0", "98e96e579", "bf7ecf353", "eef1ba704", "f42105001", "fdce5de55"]], "identity_text": "Fix premature NULL lag reporting in pg_stat_replication (Shinya Kato) The lag columns frequently read as NULL even while replication activity was happening.", "commit_aliases": ["246c296f0", "98e96e579", "bf7ecf353", "eef1ba704", "f42105001", "fdce5de55"], "source_commits": ["98e96e579"], "source_entry_id": "18.4/changes/050", "db_id": "bf6218705be170d40b881423fbe0391f", "patch_ids": ["7704c6b94c92f272f76de1954c53eb5b"], "statement_hash": "bcd10a6c1d43f2b961925210744b26778b15baa46851120a0a4df4d6146ed920", "relations": [{"rule": 2, "type": "equivalent", "target": "5851dbb38f0eb77c8633d934a8c81fbc", "evidence": {"same_day": true, "patch_ids": ["7704c6b94c92f272f76de1954c53eb5b"], "statement_hash": "bcd10a6c1d43f2b961925210744b26778b15baa46851120a0a4df4d6146ed920"}}, {"rule": 2, "type": "equivalent", "target": "65eb4d53da31a74e1d2b5ae72a4b3f98", "evidence": {"same_day": true, "patch_ids": ["7704c6b94c92f272f76de1954c53eb5b"], "statement_hash": "bcd10a6c1d43f2b961925210744b26778b15baa46851120a0a4df4d6146ed920"}}, {"rule": 2, "type": "equivalent", "target": "8f5d9efb9934b105d69fddf797f34e0b", "evidence": {"same_day": true, "patch_ids": ["7704c6b94c92f272f76de1954c53eb5b"], "statement_hash": "bcd10a6c1d43f2b961925210744b26778b15baa46851120a0a4df4d6146ed920"}}, {"rule": 2, "type": "equivalent", "target": "915ec8a085b4d90eb64720a431768f9b", "evidence": {"same_day": true, "patch_ids": ["7704c6b94c92f272f76de1954c53eb5b"], "statement_hash": "bcd10a6c1d43f2b961925210744b26778b15baa46851120a0a4df4d6146ed920"}}]}}, {"id": "18.4-7270a57d5bd56fee", "source_entry_id": "18.4/changes/052", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Avoid rare flush failure when working with non-WAL-logged GiST indexes", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-81df83553a9e021a", "source_entry_id": "17.10/changes/041", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Avoid rare flush failure when working with non-WAL-logged GiST indexes"}], "entry": {"id": "18.4-7270a57d5bd56fee", "cves": [], "html": "Avoid rare flush failure when working with non-WAL-logged GiST indexes (Tomas Vondra) §
\nA non-logged GiST index could nonetheless sometimes produce “xlog flush request n/nnnn is not satisfied” errors, due to incorrect selection of a “fake LSN” to represent an insertion point.
Fix underestimate of required size of DSA page maps for odd-size segments (Paul Bunn) §
\nThis miscalculation led to out-of-bounds accesses and hence server crashes.
", "text": "Fix underestimate of required size of DSA page maps for odd-size segments (Paul Bunn) § This miscalculation led to out-of-bounds accesses and hence server crashes.", "title": "Fix underestimate of required size of DSA page maps for odd-size segments", "commits": ["a0f38604d"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "7634c8ba8f8ffc038896e0b72ea3fe2175a1d44ae6d57fd144afb296e0dc066d", "section_path": ["Changes"], "commit_groups": [["0af5e64e9", "2543b9ea9", "46c93b705", "4da2afd01", "a0f38604d", "eb11d7a91"]], "identity_text": "Fix underestimate of required size of DSA page maps for odd-size segments (Paul Bunn) This miscalculation led to out-of-bounds accesses and hence server crashes.", "commit_aliases": ["0af5e64e9", "2543b9ea9", "46c93b705", "4da2afd01", "a0f38604d", "eb11d7a91"], "source_commits": ["a0f38604d"], "source_entry_id": "18.4/changes/053", "db_id": "c0162fa5c8bd731ee869a6a910d5a618", "patch_ids": ["51396541ad50c671641591d5c032f25c"], "statement_hash": "b77594e65c1a09137763e6965f04edfa079771b8c115cc6bbea72232ff10e97e", "relations": [{"rule": 2, "type": "equivalent", "target": "132eccad33a03f9808709ff243633e21", "evidence": {"same_day": true, "patch_ids": ["51396541ad50c671641591d5c032f25c"], "statement_hash": "b77594e65c1a09137763e6965f04edfa079771b8c115cc6bbea72232ff10e97e"}}, {"rule": 2, "type": "equivalent", "target": "6c9b24cf6c2959b6e084b0f1468cc147", "evidence": {"same_day": true, "patch_ids": ["51396541ad50c671641591d5c032f25c"], "statement_hash": "b77594e65c1a09137763e6965f04edfa079771b8c115cc6bbea72232ff10e97e"}}, {"rule": 2, "type": "equivalent", "target": "d358ff7daadf000c76becae39274dcc8", "evidence": {"same_day": true, "patch_ids": ["51396541ad50c671641591d5c032f25c"], "statement_hash": "b77594e65c1a09137763e6965f04edfa079771b8c115cc6bbea72232ff10e97e"}}, {"rule": 2, "type": "equivalent", "target": "feb50a4056ee0c9561081c3bd1a5fd94", "evidence": {"same_day": true, "patch_ids": ["51396541ad50c671641591d5c032f25c"], "statement_hash": "b77594e65c1a09137763e6965f04edfa079771b8c115cc6bbea72232ff10e97e"}}]}}, {"id": "18.4-d3cfc20eaff1d676", "source_entry_id": "18.4/changes/054", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix indexing of oldest-multixact arrays in shared memory", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-cfa55dcb71d57c12", "source_entry_id": "17.10/changes/043", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix indexing of oldest-multixact arrays in shared memory"}], "entry": {"id": "18.4-d3cfc20eaff1d676", "cves": [], "html": "Fix indexing of oldest-multixact arrays in shared memory (Yura Sokolov) § §
\nThis mistake could cause a prepared-but-not-yet-committed transaction's row locks to appear invisible to other sessions, or other visibility issues for the results of such a transaction. With a very small max_connections setting, memory stomps were also possible.
", "text": "Fix indexing of oldest-multixact arrays in shared memory (Yura Sokolov) § § This mistake could cause a prepared-but-not-yet-committed transaction's row locks to appear invisible to other sessions, or other visibility issues for the results of such a transaction. With a very small max_connections setting, memory stomps were also possible.", "title": "Fix indexing of oldest-multixact arrays in shared memory", "commits": ["0a50ef094", "fa3b328e6"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "585061295c9c5bfba8ea8450d973ee3ffcd66eca2322f3d514fcddf1dd3b7dbb", "section_path": ["Changes"], "commit_groups": [["0a50ef094", "ccae90abd", "dcd9c06a4"], ["969576dab", "fa3b328e6", "fe08113ae"]], "identity_text": "Fix indexing of oldest-multixact arrays in shared memory (Yura Sokolov) This mistake could cause a prepared-but-not-yet-committed transaction's row locks to appear invisible to other sessions, or other visibility issues for the results of such a transaction. With a very small max_connections setting, memory stomps were also possible.", "commit_aliases": ["0a50ef094", "969576dab", "ccae90abd", "dcd9c06a4", "fa3b328e6", "fe08113ae"], "source_commits": ["0a50ef094", "fa3b328e6"], "source_entry_id": "18.4/changes/054", "db_id": "257e52645de77966b485d158daff2049", "patch_ids": ["9f4b51556384588dee12dabbaa9a5068", "c295c29115de3784af1baea84dd9ddfc"], "statement_hash": "e8c1956b7f46db612ff4602b13580b3f19536358ea0d47bc73cf87584e556dac", "relations": [{"rule": 2, "type": "equivalent", "target": "440f1367bcb7bd58aa010daa1ed5105b", "evidence": {"same_day": true, "patch_ids": ["9f4b51556384588dee12dabbaa9a5068", "c295c29115de3784af1baea84dd9ddfc"], "statement_hash": "e8c1956b7f46db612ff4602b13580b3f19536358ea0d47bc73cf87584e556dac"}}]}}, {"id": "18.4-d17ff570c253e2a4", "source_entry_id": "18.4/changes/056", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix possible server crash when processing extended statistics on expressions of extension data types", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-55b28f30732d7db3", "source_entry_id": "17.10/changes/044", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix possible server crash when processing extended statistics on expressions of extension data types"}], "entry": {"id": "18.4-d17ff570c253e2a4", "cves": [], "html": "Fix possible server crash when processing extended statistics on expressions of extension data types (Michael Paquier) §
\nNULL pointer dereferences were possible if the data type's typanalyze function does not compute any useful statistics. No in-core typanalyze function behaves that way, but extensions could.
", "text": "Fix possible server crash when processing extended statistics on expressions of extension data types (Michael Paquier) § NULL pointer dereferences were possible if the data type's typanalyze function does not compute any useful statistics. No in-core typanalyze function behaves that way, but extensions could.", "title": "Fix possible server crash when processing extended statistics on expressions of extension data types", "commits": ["83671c0da"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "a6d6eda1706575777e401b70e6374c60ef40a88f3a736b35ba170dbddb62cf83", "section_path": ["Changes"], "commit_groups": [["038c7d4a3", "04745ba9c", "3b7a6fa15", "530b6b02f", "83671c0da", "f033abc6c"]], "identity_text": "Fix possible server crash when processing extended statistics on expressions of extension data types (Michael Paquier) NULL pointer dereferences were possible if the data type's typanalyze function does not compute any useful statistics. No in-core typanalyze function behaves that way, but extensions could.", "commit_aliases": ["038c7d4a3", "04745ba9c", "3b7a6fa15", "530b6b02f", "83671c0da", "f033abc6c"], "source_commits": ["83671c0da"], "source_entry_id": "18.4/changes/056", "db_id": "e3fcd13894196d38b7fdafd82a39872b", "patch_ids": ["57808080730ecfb17eedfbeb01bceb92"], "statement_hash": "0b6cefc1fdc0c8f91af788bfe5a8b6d0b6b4059af142c8779ab898a1590a8d8a", "relations": [{"rule": 2, "type": "equivalent", "target": "11bb9497f3c67aace227015bc936b98e", "evidence": {"same_day": true, "patch_ids": ["57808080730ecfb17eedfbeb01bceb92"], "statement_hash": "0b6cefc1fdc0c8f91af788bfe5a8b6d0b6b4059af142c8779ab898a1590a8d8a"}}, {"rule": 2, "type": "equivalent", "target": "1c1afd4ac22d6baac4a29928c824292c", "evidence": {"same_day": true, "patch_ids": ["57808080730ecfb17eedfbeb01bceb92"], "statement_hash": "0b6cefc1fdc0c8f91af788bfe5a8b6d0b6b4059af142c8779ab898a1590a8d8a"}}, {"rule": 2, "type": "equivalent", "target": "7060172e893faabd38e47a052f25c75c", "evidence": {"same_day": true, "patch_ids": ["57808080730ecfb17eedfbeb01bceb92"], "statement_hash": "0b6cefc1fdc0c8f91af788bfe5a8b6d0b6b4059af142c8779ab898a1590a8d8a"}}, {"rule": 2, "type": "equivalent", "target": "80939c27c6a18cbd33af67b54738ffbb", "evidence": {"same_day": true, "patch_ids": ["57808080730ecfb17eedfbeb01bceb92"], "statement_hash": "0b6cefc1fdc0c8f91af788bfe5a8b6d0b6b4059af142c8779ab898a1590a8d8a"}}]}}, {"id": "18.4-d03de691fc9de456", "source_entry_id": "18.4/changes/058", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix minor memory leaks in ICU-based string processing", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-e802516615666acf", "source_entry_id": "17.10/changes/045", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix minor memory leaks in ICU-based string processing"}], "entry": {"id": "18.4-d03de691fc9de456", "cves": [], "html": "Fix minor memory leaks in ICU-based string processing (Jeff Davis) §
", "text": "Fix minor memory leaks in ICU-based string processing (Jeff Davis) §", "title": "Fix minor memory leaks in ICU-based string processing", "commits": ["4abf63c62"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "a9e224936921e1963331dad335fbb68b989592f871716dc81f6ad82e7c37ac94", "section_path": ["Changes"], "commit_groups": [["4761f2eee", "4abf63c62", "a4515c9b4", "d942511f0"]], "identity_text": "Fix minor memory leaks in ICU-based string processing (Jeff Davis)", "commit_aliases": ["4761f2eee", "4abf63c62", "a4515c9b4", "d942511f0"], "source_commits": ["4abf63c62"], "source_entry_id": "18.4/changes/058", "db_id": "837bd67b8c3f6368b3c27a6551f80927", "patch_ids": ["6d9d38d08dbad42448b9071321caaf61"], "statement_hash": "b7a1562c011305e92a0b8937cd9fca1c2e7a7555c23e50eef91b5ced9490aa97", "relations": [{"rule": 2, "type": "equivalent", "target": "50b72add33aaee1a9925c87cbf7716b3", "evidence": {"same_day": true, "patch_ids": ["6d9d38d08dbad42448b9071321caaf61"], "statement_hash": "b7a1562c011305e92a0b8937cd9fca1c2e7a7555c23e50eef91b5ced9490aa97"}}, {"rule": 2, "type": "equivalent", "target": "bd584e4f7982ffc4b076ab2f17b9df9c", "evidence": {"same_day": true, "patch_ids": ["6d9d38d08dbad42448b9071321caaf61"], "statement_hash": "b7a1562c011305e92a0b8937cd9fca1c2e7a7555c23e50eef91b5ced9490aa97"}}]}}, {"id": "18.4-fbb8a60e8a0fb7fa", "source_entry_id": "18.4/changes/059", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "If the startup process fails, properly shut down other child processes before exiting the postmaster", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-ae6a8b961252ec16", "source_entry_id": "17.10/changes/046", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "If the startup process fails, properly shut down other child processes before exiting the postmaster"}], "entry": {"id": "18.4-fbb8a60e8a0fb7fa", "cves": [], "html": "If the startup process fails, properly shut down other child processes before exiting the postmaster (Ayush Tiwari) §
\nThe handling of this situation relied on a long-obsolete assumption that no other postmaster children exist while the startup process is running, so that immediate postmaster exit is acceptable. Orphaned children would eventually notice the postmaster's death and exit on their own, but a cleaner shutdown procedure is desirable.
", "text": "If the startup process fails, properly shut down other child processes before exiting the postmaster (Ayush Tiwari) § The handling of this situation relied on a long-obsolete assumption that no other postmaster children exist while the startup process is running, so that immediate postmaster exit is acceptable. Orphaned children would eventually notice the postmaster's death and exit on their own, but a cleaner shutdown procedure is desirable.", "title": "If the startup process fails, properly shut down other child processes before exiting the postmaster", "commits": ["affdb2dd5"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "68c31c19230ddadd1bb75689080bdcd9d4f19cfe5d82a6547e023d3812aca964", "section_path": ["Changes"], "commit_groups": [["23cebf672", "2d347f2cd", "9b43e6793", "affdb2dd5", "e381843cf"]], "identity_text": "If the startup process fails, properly shut down other child processes before exiting the postmaster (Ayush Tiwari) The handling of this situation relied on a long-obsolete assumption that no other postmaster children exist while the startup process is running, so that immediate postmaster exit is acceptable. Orphaned children would eventually notice the postmaster's death and exit on their own, but a cleaner shutdown procedure is desirable.", "commit_aliases": ["23cebf672", "2d347f2cd", "9b43e6793", "affdb2dd5", "e381843cf"], "source_commits": ["affdb2dd5"], "source_entry_id": "18.4/changes/059", "db_id": "60187dd7a7a6b60a0c3449316b65aa78", "patch_ids": ["336655f61a8e613f6d655ff5a808f10d"], "statement_hash": "cb4e5d59e127aafd8bb2c9e2c73437dd551d9591dd8c7309ec60a48a3299d4f5", "relations": [{"rule": 2, "type": "equivalent", "target": "1258e1d70ad8d20566f8bef565afb542", "evidence": {"same_day": true, "patch_ids": ["336655f61a8e613f6d655ff5a808f10d"], "statement_hash": "cb4e5d59e127aafd8bb2c9e2c73437dd551d9591dd8c7309ec60a48a3299d4f5"}}, {"rule": 2, "type": "equivalent", "target": "2a31a83d114004ec62a45d4511e6eea8", "evidence": {"same_day": true, "patch_ids": ["336655f61a8e613f6d655ff5a808f10d"], "statement_hash": "cb4e5d59e127aafd8bb2c9e2c73437dd551d9591dd8c7309ec60a48a3299d4f5"}}, {"rule": 2, "type": "equivalent", "target": "35889e010982e213ace67b19129690cc", "evidence": {"same_day": true, "patch_ids": ["336655f61a8e613f6d655ff5a808f10d"], "statement_hash": "cb4e5d59e127aafd8bb2c9e2c73437dd551d9591dd8c7309ec60a48a3299d4f5"}}]}}, {"id": "18.4-b95009e302c19df6", "source_entry_id": "18.4/changes/060", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix race condition between WAL replay of checkpoints and multixact ID creations", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-b851403e0c059925", "source_entry_id": "17.10/changes/047", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix race condition between WAL replay of checkpoints and multixact ID creations"}], "entry": {"id": "18.4-b95009e302c19df6", "cves": [], "html": "Fix race condition between WAL replay of checkpoints and multixact ID creations (Heikki Linnakangas) §
\nA standby server following WAL from a primary of an older minor version could get into a crash-and-restart loop complaining about “could not access status of transaction”.
", "text": "Fix race condition between WAL replay of checkpoints and multixact ID creations (Heikki Linnakangas) § A standby server following WAL from a primary of an older minor version could get into a crash-and-restart loop complaining about “could not access status of transaction”.", "title": "Fix race condition between WAL replay of checkpoints and multixact ID creations", "commits": ["0852643e1"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "ac547c6f2c5e79a65589bd908f8df4b0b44a2c86fdb6cad890d325cd54b6e41d", "section_path": ["Changes"], "commit_groups": [["0852643e1", "1ca385032", "77dff5d93", "a5f412107", "e35e466f6"]], "identity_text": "Fix race condition between WAL replay of checkpoints and multixact ID creations (Heikki Linnakangas) A standby server following WAL from a primary of an older minor version could get into a crash-and-restart loop complaining about could not access status of transaction.", "commit_aliases": ["0852643e1", "1ca385032", "77dff5d93", "a5f412107", "e35e466f6"], "source_commits": ["0852643e1"], "source_entry_id": "18.4/changes/060", "db_id": "2dd877a931aebbb79cf02748fddc6985", "patch_ids": ["bc2293c8457ac75a2ee41b1da5cae860"], "statement_hash": "966d18f3bd64c03cfe6fcbf5ad572276df81e74e4f0e0228686357c47c7ba192", "relations": [{"rule": 2, "type": "equivalent", "target": "61f30ae9ddadfa030207bdea7cb12e70", "evidence": {"same_day": true, "patch_ids": ["bc2293c8457ac75a2ee41b1da5cae860"], "statement_hash": "966d18f3bd64c03cfe6fcbf5ad572276df81e74e4f0e0228686357c47c7ba192"}}, {"rule": 2, "type": "equivalent", "target": "7656c6c266fb5f623679c473e6534cb4", "evidence": {"same_day": true, "patch_ids": ["bc2293c8457ac75a2ee41b1da5cae860"], "statement_hash": "966d18f3bd64c03cfe6fcbf5ad572276df81e74e4f0e0228686357c47c7ba192"}}, {"rule": 2, "type": "equivalent", "target": "85b276d385b6533daa45fb10a83fcdc6", "evidence": {"same_day": true, "patch_ids": ["bc2293c8457ac75a2ee41b1da5cae860"], "statement_hash": "966d18f3bd64c03cfe6fcbf5ad572276df81e74e4f0e0228686357c47c7ba192"}}, {"rule": 2, "type": "equivalent", "target": "bdf695af62de33084d77c352623dcee3", "evidence": {"same_day": true, "patch_ids": ["bc2293c8457ac75a2ee41b1da5cae860"], "statement_hash": "966d18f3bd64c03cfe6fcbf5ad572276df81e74e4f0e0228686357c47c7ba192"}}]}}, {"id": "18.4-a9cb192589c0f7aa", "source_entry_id": "18.4/changes/061", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Prevent indefinite wait in shutdown of a walsender process", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-3ccf02812257acd0", "source_entry_id": "17.10/changes/048", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Prevent indefinite wait in shutdown of a walsender process"}], "entry": {"id": "18.4-a9cb192589c0f7aa", "cves": [], "html": "Prevent indefinite wait in shutdown of a walsender process (Anthonin Bonnefoy) § §
\nAt shutdown of a cluster that is publishing logical replication data, the walsender waits for all pending WAL to be written out. But it did not correctly request that to happen, so that in some cases this could become an indefinite wait.
", "text": "Prevent indefinite wait in shutdown of a walsender process (Anthonin Bonnefoy) § § At shutdown of a cluster that is publishing logical replication data, the walsender waits for all pending WAL to be written out. But it did not correctly request that to happen, so that in some cases this could become an indefinite wait.", "title": "Prevent indefinite wait in shutdown of a walsender process", "commits": ["3eb2fecdb", "980498138"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "30e21260db1c3d5b99950ec0f5dc2e6fdbfa011ede52349a41454054360e4a6e", "section_path": ["Changes"], "commit_groups": [["3bf6f22ce", "3eb2fecdb", "42734f296", "6eedb2a5f", "82935467a", "bbbc0888b"], ["8ee536c89", "980498138", "d927b4bd9", "da21ecf57", "f15471464", "fa9f2e317"]], "identity_text": "Prevent indefinite wait in shutdown of a walsender process (Anthonin Bonnefoy) At shutdown of a cluster that is publishing logical replication data, the walsender waits for all pending WAL to be written out. But it did not correctly request that to happen, so that in some cases this could become an indefinite wait.", "commit_aliases": ["3bf6f22ce", "3eb2fecdb", "42734f296", "6eedb2a5f", "82935467a", "8ee536c89", "980498138", "bbbc0888b", "d927b4bd9", "da21ecf57", "f15471464", "fa9f2e317"], "source_commits": ["3eb2fecdb", "980498138"], "source_entry_id": "18.4/changes/061", "db_id": "dd2e9c6da8c31f99c801d2fd16385b3c", "patch_ids": ["472a5975808282fa6bd581c79c39f9ea", "76b367fc789f138e1eeabf0d364392af"], "statement_hash": "82e19a553da5241f427aaa49312a19ba9fb5200bffa8a85355d78e7c64e1a530", "relations": [{"rule": 2, "type": "equivalent", "target": "45420fcd1c11fe55a25c2e6f51f48363", "evidence": {"same_day": true, "patch_ids": ["472a5975808282fa6bd581c79c39f9ea", "76b367fc789f138e1eeabf0d364392af"], "statement_hash": "82e19a553da5241f427aaa49312a19ba9fb5200bffa8a85355d78e7c64e1a530"}}, {"rule": 2, "type": "equivalent", "target": "58a67f2d4d7fff6342315f22db6849a6", "evidence": {"same_day": true, "patch_ids": ["472a5975808282fa6bd581c79c39f9ea", "76b367fc789f138e1eeabf0d364392af"], "statement_hash": "82e19a553da5241f427aaa49312a19ba9fb5200bffa8a85355d78e7c64e1a530"}}, {"rule": 2, "type": "equivalent", "target": "a7b932fcfa614135f399c6d16936a3ee", "evidence": {"same_day": true, "patch_ids": ["472a5975808282fa6bd581c79c39f9ea", "76b367fc789f138e1eeabf0d364392af"], "statement_hash": "82e19a553da5241f427aaa49312a19ba9fb5200bffa8a85355d78e7c64e1a530"}}, {"rule": 2, "type": "equivalent", "target": "f5dd9be5d5ba1e08ae8e1a43cf926484", "evidence": {"same_day": true, "patch_ids": ["472a5975808282fa6bd581c79c39f9ea", "76b367fc789f138e1eeabf0d364392af"], "statement_hash": "82e19a553da5241f427aaa49312a19ba9fb5200bffa8a85355d78e7c64e1a530"}}]}}, {"id": "18.4-97e2910c41fa9a19", "source_entry_id": "18.4/changes/062", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Ensure that changes to tables' free space maps are persisted during recovery", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-fe407982706e6121", "source_entry_id": "17.10/changes/049", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Ensure that changes to tables' free space maps are persisted during recovery"}], "entry": {"id": "18.4-97e2910c41fa9a19", "cves": [], "html": "Ensure that changes to tables' free space maps are persisted during recovery (Alexey Makhmutov) §
\nPreviously, while WAL replay did update the free space map while replaying operations that should change it, the map page buffer did not get marked dirty if checksums are enabled, so that the changes might never get written out. On a standby server, over time this would result in a map wildly at variance with the table's actual contents. While the map is only used as a hint, this condition could cause significant performance degradation for some period of time after the standby server is promoted to be active, until most of the map has been repaired by updates.
", "text": "Ensure that changes to tables' free space maps are persisted during recovery (Alexey Makhmutov) § Previously, while WAL replay did update the free space map while replaying operations that should change it, the map page buffer did not get marked dirty if checksums are enabled, so that the changes might never get written out. On a standby server, over time this would result in a map wildly at variance with the table's actual contents. While the map is only used as a hint, this condition could cause significant performance degradation for some period of time after the standby server is promoted to be active, until most of the map has been repaired by updates.", "title": "Ensure that changes to tables' free space maps are persisted during recovery", "commits": ["ac3b97db3"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "b4c7ae8e1632b5ecf778d21be35386e9777e6a942b825bd1a420c044b7e3cc4e", "section_path": ["Changes"], "commit_groups": [["1cf010f21", "54537de35", "ac3b97db3", "c06d1a4ba", "ca259b084", "f5d1038d9"]], "identity_text": "Ensure that changes to tables' free space maps are persisted during recovery (Alexey Makhmutov) Previously, while WAL replay did update the free space map while replaying operations that should change it, the map page buffer did not get marked dirty if checksums are enabled, so that the changes might never get written out. On a standby server, over time this would result in a map wildly at variance with the table's actual contents. While the map is only used as a hint, this condition could cause significant performance degradation for some period of time after the standby server is promoted to be active, until most of the map has been repaired by updates.", "commit_aliases": ["1cf010f21", "54537de35", "ac3b97db3", "c06d1a4ba", "ca259b084", "f5d1038d9"], "source_commits": ["ac3b97db3"], "source_entry_id": "18.4/changes/062", "db_id": "0ab544ccf54b9ef9d9a67d11e0edd7e6", "patch_ids": ["290b85a9a01972ea333ff078f1b803bd"], "statement_hash": "94dbd19b3ba5c2d1d6d0c3e547d4c2b99593a3f783f7d830b8bd54b62553c5ba", "relations": [{"rule": 2, "type": "equivalent", "target": "0a850a82a0e101c371b76446a16834eb", "evidence": {"same_day": true, "patch_ids": ["290b85a9a01972ea333ff078f1b803bd"], "statement_hash": "94dbd19b3ba5c2d1d6d0c3e547d4c2b99593a3f783f7d830b8bd54b62553c5ba"}}, {"rule": 2, "type": "equivalent", "target": "5d55832b6f7b480606ba52039c22d06e", "evidence": {"same_day": true, "patch_ids": ["290b85a9a01972ea333ff078f1b803bd"], "statement_hash": "94dbd19b3ba5c2d1d6d0c3e547d4c2b99593a3f783f7d830b8bd54b62553c5ba"}}, {"rule": 2, "type": "equivalent", "target": "d0b2b7eb40b300341a738f0c8f9b9486", "evidence": {"same_day": true, "patch_ids": ["290b85a9a01972ea333ff078f1b803bd"], "statement_hash": "94dbd19b3ba5c2d1d6d0c3e547d4c2b99593a3f783f7d830b8bd54b62553c5ba"}}, {"rule": 2, "type": "equivalent", "target": "ef79709e772e43cd7f13cd40fd54ce08", "evidence": {"same_day": true, "patch_ids": ["290b85a9a01972ea333ff078f1b803bd"], "statement_hash": "94dbd19b3ba5c2d1d6d0c3e547d4c2b99593a3f783f7d830b8bd54b62553c5ba"}}]}}, {"id": "18.4-7aa817666dd07903", "source_entry_id": "18.4/changes/063", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix crashes in some ecpg functions when called without any established connection", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-4e8f75e7518f8860", "source_entry_id": "17.10/changes/050", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix crashes in some ecpg functions when called without any established connection"}], "entry": {"id": "18.4-7aa817666dd07903", "cves": [], "html": "Fix crashes in some ecpg functions when called without any established connection (Shruthi Gowda) §
", "text": "Fix crashes in some ecpg functions when called without any established connection (Shruthi Gowda) §", "title": "Fix crashes in some ecpg functions when called without any established connection", "commits": ["e2688ea5e"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "dcf26468595d7c78f1807708270b114aa22c165d1ec52d8150a311fceec78d91", "section_path": ["Changes"], "commit_groups": [["5d67549d9", "6916f4410", "7e4c871f4", "c34a280c8", "e2688ea5e", "f0e3f9732"]], "identity_text": "Fix crashes in some ecpg functions when called without any established connection (Shruthi Gowda)", "commit_aliases": ["5d67549d9", "6916f4410", "7e4c871f4", "c34a280c8", "e2688ea5e", "f0e3f9732"], "source_commits": ["e2688ea5e"], "source_entry_id": "18.4/changes/063", "db_id": "c0c7dfbc8d8c6bcae16ae7205d190917", "patch_ids": ["c7a6bafc62f4feae4e980b1e35da2b80"], "statement_hash": "d082bcf56e345df427e58be27130fd3aa6a1679e210b9c2dac559e63adb7e00a", "relations": [{"rule": 2, "type": "equivalent", "target": "7907242716f81b2600bf11b638097726", "evidence": {"same_day": true, "patch_ids": ["c7a6bafc62f4feae4e980b1e35da2b80"], "statement_hash": "d082bcf56e345df427e58be27130fd3aa6a1679e210b9c2dac559e63adb7e00a"}}, {"rule": 2, "type": "equivalent", "target": "80c1fd60cd9f0d7c266d99b227c860c1", "evidence": {"same_day": true, "patch_ids": ["c7a6bafc62f4feae4e980b1e35da2b80"], "statement_hash": "d082bcf56e345df427e58be27130fd3aa6a1679e210b9c2dac559e63adb7e00a"}}, {"rule": 2, "type": "equivalent", "target": "bdf9527e3b31fa7d5ae8f9823d072d3d", "evidence": {"same_day": true, "patch_ids": ["c7a6bafc62f4feae4e980b1e35da2b80"], "statement_hash": "d082bcf56e345df427e58be27130fd3aa6a1679e210b9c2dac559e63adb7e00a"}}, {"rule": 2, "type": "equivalent", "target": "feefd46320fbb1731e40ec3e06323dbb", "evidence": {"same_day": true, "patch_ids": ["c7a6bafc62f4feae4e980b1e35da2b80"], "statement_hash": "d082bcf56e345df427e58be27130fd3aa6a1679e210b9c2dac559e63adb7e00a"}}]}}, {"id": "18.4-3efb2ed246686260", "source_entry_id": "18.4/changes/065", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Fix assorted bugs in backup decompression and tar-parsing code", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-608dfcd402c79cc9", "source_entry_id": "17.10/changes/051", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Fix assorted bugs in backup decompression and tar-parsing code"}], "entry": {"id": "18.4-3efb2ed246686260", "cves": [], "html": "Fix assorted bugs in backup decompression and tar-parsing code (Andrew Dunstan, Tom Lane, Chao Li) § § §
\nThe decompression and tar-file reading code used in pg_basebackup and pg_verifybackup mishandled tar-file padding data, could corrupt LZ4-compressed data in edge cases, failed to check for some unusual error conditions, failed to exit after compression/decompression errors (leading to cascading error reports), and leaked memory.
", "text": "Fix assorted bugs in backup decompression and tar-parsing code (Andrew Dunstan, Tom Lane, Chao Li) § § § The decompression and tar-file reading code used in pg_basebackup and pg_verifybackup mishandled tar-file padding data, could corrupt LZ4-compressed data in edge cases, failed to check for some unusual error conditions, failed to exit after compression/decompression errors (leading to cascading error reports), and leaked memory.", "title": "Fix assorted bugs in backup decompression and tar-parsing code", "commits": ["5095f3f4a", "78dc9a808", "a01a592b1"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "cb9c6be5fd1ed810aed5121907e9abee1c0eb6f0b0eaa2df4feb45d2fd127cc8", "section_path": ["Changes"], "commit_groups": [["01d58d7e3", "1590723f0", "5095f3f4a", "d3bb7841b", "f1298a4c2"], ["2640c5ba7", "415cc943f", "4548e8746", "78dc9a808", "c70f6dc6b"], ["8b198b093", "9a42888a3", "a01a592b1", "ac0accafd", "cce939c71"]], "identity_text": "Fix assorted bugs in backup decompression and tar-parsing code (Andrew Dunstan, Tom Lane, Chao Li) The decompression and tar-file reading code used in pg_basebackup and pg_verifybackup mishandled tar-file padding data, could corrupt LZ4-compressed data in edge cases, failed to check for some unusual error conditions, failed to exit after compression/decompression errors (leading to cascading error reports), and leaked memory.", "commit_aliases": ["01d58d7e3", "1590723f0", "2640c5ba7", "415cc943f", "4548e8746", "5095f3f4a", "78dc9a808", "8b198b093", "9a42888a3", "a01a592b1", "ac0accafd", "c70f6dc6b", "cce939c71", "d3bb7841b", "f1298a4c2"], "source_commits": ["5095f3f4a", "78dc9a808", "a01a592b1"], "source_entry_id": "18.4/changes/065", "db_id": "2c1767e33fbd2c5b0ad76b3984a83f2d", "patch_ids": ["776d5a67dae4e90312023436a1a121e4", "a09bdaf76ce8e50fc1ed232d629496d1", "e611dc8dc55e1b7e28e7918dce0a5440"], "statement_hash": "14975a7d452ebd245adc06195cb53e296e97faf277282e3324587b2fcb641829", "relations": [{"rule": 2, "type": "equivalent", "target": "212902cab1e6fcee0bcc358f8fa492ef", "evidence": {"same_day": true, "patch_ids": ["776d5a67dae4e90312023436a1a121e4", "a09bdaf76ce8e50fc1ed232d629496d1", "e611dc8dc55e1b7e28e7918dce0a5440"], "statement_hash": "14975a7d452ebd245adc06195cb53e296e97faf277282e3324587b2fcb641829"}}, {"rule": 2, "type": "equivalent", "target": "34c5828614b646d0ee1635c733748049", "evidence": {"same_day": true, "patch_ids": ["776d5a67dae4e90312023436a1a121e4", "a09bdaf76ce8e50fc1ed232d629496d1", "e611dc8dc55e1b7e28e7918dce0a5440"], "statement_hash": "14975a7d452ebd245adc06195cb53e296e97faf277282e3324587b2fcb641829"}}, {"rule": 2, "type": "equivalent", "target": "bb9e0889e1a5adbf796ceaf3f2bba54a", "evidence": {"same_day": true, "patch_ids": ["776d5a67dae4e90312023436a1a121e4", "a09bdaf76ce8e50fc1ed232d629496d1", "e611dc8dc55e1b7e28e7918dce0a5440"], "statement_hash": "14975a7d452ebd245adc06195cb53e296e97faf277282e3324587b2fcb641829"}}]}}, {"id": "18.4-4c4f381190f9d053", "source_entry_id": "18.4/changes/067", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "In pg_dumpall, don't skip role GRANTs with dangling grantor OIDs", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-abb35676e2703512", "source_entry_id": "17.10/changes/052", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "In pg_dumpall, don't skip role GRANTs with dangling grantor OIDs"}], "entry": {"id": "18.4-4c4f381190f9d053", "cves": [], "html": "In pg_dumpall, don't skip role GRANTs with dangling grantor OIDs (Tom Lane) §
Instead, handle such cases by emitting GRANT without any GRANTED BY clause, as we did before v16. This avoids losing the grant in foreseeable cases, since pre-v16 servers didn't prevent dropping the grantor role. Continue to emit a warning about the missing grantor, but only if the source server is v16 or later.
In pg_upgrade, take care to use the correct protocol version when connecting to older source servers (Jacob Champion) §
\nThis could be problematic when attempting to upgrade from a pre-2018 server.
", "text": "In pg_upgrade, take care to use the correct protocol version when connecting to older source servers (Jacob Champion) § This could be problematic when attempting to upgrade from a pre-2018 server.", "title": "In pg_upgrade, take care to use the correct protocol version when connecting to older source servers", "commits": ["1b2773179"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "8350e1a25becbe288b1e0328484e7d60dd9277a9456f597a98cff73be40b3694", "section_path": ["Changes"], "commit_groups": [["1b2773179", "a38ed212f", "a60a10338", "ad7fc3f1f", "c47744ede", "e726620d2"]], "identity_text": "In pg_upgrade, take care to use the correct protocol version when connecting to older source servers (Jacob Champion) This could be problematic when attempting to upgrade from a pre-2018 server.", "commit_aliases": ["1b2773179", "a38ed212f", "a60a10338", "ad7fc3f1f", "c47744ede", "e726620d2"], "source_commits": ["1b2773179"], "source_entry_id": "18.4/changes/068", "db_id": "b441ea3af4b648902039f9d5d3831785", "patch_ids": ["566020049e5cf4849b3dd9a9935a3aba"], "statement_hash": "6ea9a20b0f199ebe33de09e3497f924a73ae542c7d6af134326d0792ad8e087c", "relations": [{"rule": 2, "type": "equivalent", "target": "29ee5ab07783ca431d54fc60a7a68ac6", "evidence": {"same_day": true, "patch_ids": ["566020049e5cf4849b3dd9a9935a3aba"], "statement_hash": "6ea9a20b0f199ebe33de09e3497f924a73ae542c7d6af134326d0792ad8e087c"}}, {"rule": 2, "type": "equivalent", "target": "330e067151809e2b5b18a2ce11b3f4a8", "evidence": {"same_day": true, "patch_ids": ["566020049e5cf4849b3dd9a9935a3aba"], "statement_hash": "6ea9a20b0f199ebe33de09e3497f924a73ae542c7d6af134326d0792ad8e087c"}}, {"rule": 2, "type": "equivalent", "target": "6e7bc01c77ad0b62b80fffc021e1f621", "evidence": {"same_day": true, "patch_ids": ["566020049e5cf4849b3dd9a9935a3aba"], "statement_hash": "6ea9a20b0f199ebe33de09e3497f924a73ae542c7d6af134326d0792ad8e087c"}}, {"rule": 2, "type": "equivalent", "target": "df5ddbd0c6e2f445b5c35f53b9f74046", "evidence": {"same_day": true, "patch_ids": ["566020049e5cf4849b3dd9a9935a3aba"], "statement_hash": "6ea9a20b0f199ebe33de09e3497f924a73ae542c7d6af134326d0792ad8e087c"}}]}}, {"id": "18.4-ab15ea8c2f16b1a1", "source_entry_id": "18.4/changes/069", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "In contrib/basic_archive, allow the archive directory to be missing at startup", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-760c43569faae613", "source_entry_id": "17.10/changes/054", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "In contrib/basic_archive, allow the archive directory to be missing at startup"}], "entry": {"id": "18.4-ab15ea8c2f16b1a1", "cves": [], "html": "In contrib/basic_archive, allow the archive directory to be missing at startup (Nathan Bossart) §
Previously, the setting of basic_archive.archive_directory was rejected if it didn't point to an existing directory. This is undesirable because archiving will be stuck indefinitely, even if the directory appears later.
Fix contrib/ltree to cope when case-folding changes a string's byte length (Jeff Davis) § §
Previously, lquery patterns specifying case-insensitive matching might fail to match labels they should match.
In contrib/pg_stat_statements, don't leak memory if an error occurs while parsing the pgss_query_texts.stat file (Heikki Linnakangas) §
In contrib/postgres_fdw, avoid crash due to premature cleanup of a failed connection (Etsuro Fujita) §
If a remote connection fails abort cleanup, we can't use it any longer. But delay closing the connection object until end of transaction, because there might still be references to it within data structures such as open cursors.
", "text": "In contrib/postgres_fdw, avoid crash due to premature cleanup of a failed connection (Etsuro Fujita) § If a remote connection fails abort cleanup, we can't use it any longer. But delay closing the connection object until end of transaction, because there might still be references to it within data structures such as open cursors.", "title": "In contrib/postgres_fdw, avoid crash due to premature cleanup of a failed connection", "commits": ["c318777da"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "source_hash": "7370c1e27b16e5685bf55cf6357a6c058a35c4df678be5bec75d4a3d13b7d645", "section_path": ["Changes"], "commit_groups": [["1352651c2", "34c18a225", "648818ba3", "af8f9248f", "c318777da", "fd5b36ab1"]], "identity_text": "In contrib/postgres_fdw, avoid crash due to premature cleanup of a failed connection (Etsuro Fujita) If a remote connection fails abort cleanup, we can't use it any longer. But delay closing the connection object until end of transaction, because there might still be references to it within data structures such as open cursors.", "commit_aliases": ["1352651c2", "34c18a225", "648818ba3", "af8f9248f", "c318777da", "fd5b36ab1"], "source_commits": ["c318777da"], "source_entry_id": "18.4/changes/073", "db_id": "5debbdff219f6645c34f0afc23c6c9a8", "patch_ids": ["73eecb88ff1f4197b1eb6900521746ca"], "statement_hash": "c7e9961353a3aad5643e55ab0c89f89d4bd050418724e45b79a4a1fb13cd1c48", "relations": [{"rule": 2, "type": "equivalent", "target": "701d8322decc496c951bc0d7ecfdd513", "evidence": {"same_day": true, "patch_ids": ["73eecb88ff1f4197b1eb6900521746ca"], "statement_hash": "c7e9961353a3aad5643e55ab0c89f89d4bd050418724e45b79a4a1fb13cd1c48"}}, {"rule": 2, "type": "equivalent", "target": "8c8ea6b283a201d99cb3d8c9f57cd142", "evidence": {"same_day": true, "patch_ids": ["73eecb88ff1f4197b1eb6900521746ca"], "statement_hash": "c7e9961353a3aad5643e55ab0c89f89d4bd050418724e45b79a4a1fb13cd1c48"}}, {"rule": 2, "type": "equivalent", "target": "9bcb1c284d9f8abb68fce372f4df9301", "evidence": {"same_day": true, "patch_ids": ["73eecb88ff1f4197b1eb6900521746ca"], "statement_hash": "c7e9961353a3aad5643e55ab0c89f89d4bd050418724e45b79a4a1fb13cd1c48"}}, {"rule": 2, "type": "equivalent", "target": "b0783885375212755fb05950c3052a4a", "evidence": {"same_day": true, "patch_ids": ["73eecb88ff1f4197b1eb6900521746ca"], "statement_hash": "c7e9961353a3aad5643e55ab0c89f89d4bd050418724e45b79a4a1fb13cd1c48"}}]}}, {"id": "18.4-a78c59e453b0788d", "source_entry_id": "18.4/changes/074", "version": "18.4", "source_url": "/docs/release/18.4/#RELEASE-18-4-CHANGES", "title": "Update time zone data files to tzdata release 2026b", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.10-1e6fcd0fa95c5ce6", "source_entry_id": "17.10/changes/058", "version": "17.10", "source_url": "/docs/release/17.10/#RELEASE-17-10-CHANGES", "title": "Update time zone data files to tzdata release 2026b"}], "entry": {"id": "18.4-a78c59e453b0788d", "cves": [], "html": "Update time zone data files to tzdata release 2026b (Tom Lane) §
\nBritish Columbia (America/Vancouver) will be on year-round UTC-07 (effectively, permanent DST) beginning in November 2026. This release assumes that their TZ abbreviation will be MST from that time forward. That seems likely to change, but it's unclear what new abbreviation will be used. Also a historical correction for Moldova: they have followed EU DST transition times since 2022.
Restrict logical decoding output plugins to the set specified by a new server parameter output_plugin_libraries (Jacob Champion) § §
Previously, a replication user could select any loadable library for logical decoding, allowing exploits of various sorts. To allow locking this down without breaking setups that worked before, introduce a whitelist of allowed output plugins.
\nBy default, only the output plugins shipped as part of PostgreSQL (pgoutput and test_decoding) are included in output_plugin_libraries. Installations that rely on other output plugins must add them after updating the server, for example
output_plugin_libraries = 'pgoutput, test_decoding, my_trusted_decoder'\n\n
Additionally, pg_upgrade --check will fail if the output_plugin_libraries parameter on the new cluster does not permit the plugins of logical replication slots on the old cluster, when migrating from versions 17 and later. Make necessary additions to the new cluster's setting before performing pg_upgrade.
The PostgreSQL Project thanks Vladimir Tokarev and Yu Kunpeng for reporting this problem. (CVE-2026-6471)
", "text": "Restrict logical decoding output plugins to the set specified by a new server parameter output_plugin_libraries (Jacob Champion) § § Previously, a replication user could select any loadable library for logical decoding, allowing exploits of various sorts. To allow locking this down without breaking setups that worked before, introduce a whitelist of allowed output plugins. By default, only the output plugins shipped as part of PostgreSQL (pgoutput and test_decoding) are included in output_plugin_libraries. Installations that rely on other output plugins must add them after updating the server, for example output_plugin_libraries = 'pgoutput, test_decoding, my_trusted_decoder' Additionally, pg_upgrade --check will fail if the output_plugin_libraries parameter on the new cluster does not permit the plugins of logical replication slots on the old cluster, when migrating from versions 17 and later. Make necessary additions to the new cluster's setting before performing pg_upgrade. The PostgreSQL Project thanks Vladimir Tokarev and Yu Kunpeng for reporting this problem. (CVE-2026-6471)", "title": "Restrict logical decoding output plugins to the set specified by a new server parameter output_plugin_libraries", "commits": ["2a29b607d", "82fd68801"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "bb65fe803bf799ec945db22c8446c25a0fc57bc240545380b027bcf4cff5e000", "section_path": ["Changes"], "commit_groups": [["01992176e", "226e49cbe", "2a29b607d", "4e1252ee5", "5d47df21e", "99f205407", "bf3842a64"], ["20e9dcefd", "4fcccea97", "7082ce248", "82fd68801"]], "identity_text": "Restrict logical decoding output plugins to the set specified by a new server parameter output_plugin_libraries (Jacob Champion) Previously, a replication user could select any loadable library for logical decoding, allowing exploits of various sorts. To allow locking this down without breaking setups that worked before, introduce a whitelist of allowed output plugins. By default, only the output plugins shipped as part of PostgreSQL (pgoutput and test_decoding) are included in output_plugin_libraries. Installations that rely on other output plugins must add them after updating the server, for example output_plugin_libraries = 'pgoutput, test_decoding, my_trusted_decoder' Additionally, pg_upgrade --check will fail if the output_plugin_libraries parameter on the new cluster does not permit the plugins of logical replication slots on the old cluster, when migrating from versions 17 and later. Make necessary additions to the new cluster's setting before performing pg_upgrade. The PostgreSQL Project thanks Vladimir Tokarev and Yu Kunpeng for reporting this problem. (CVE-2026-6471)", "commit_aliases": ["01992176e", "20e9dcefd", "226e49cbe", "2a29b607d", "4e1252ee5", "4fcccea97", "5d47df21e", "7082ce248", "82fd68801", "99f205407", "bf3842a64"], "source_commits": ["2a29b607d", "82fd68801"], "source_entry_id": "18.6/changes/001", "db_id": "2ed41f6adf451dd977da156f72190023", "patch_ids": ["29a8e1db1536ed40c71312e7d2015c9e", "bcbaedd0455bfc84b87ba56b7f4aba2c"], "statement_hash": "66cffd63e622afc809ffcea154c77acb7025871176da7689b08b6db15ff40212", "relations": [{"rule": 2, "type": "equivalent", "target": "549fb97375289bbc21d70209d1e5e9a8", "evidence": {"same_day": true, "patch_ids": ["29a8e1db1536ed40c71312e7d2015c9e", "bcbaedd0455bfc84b87ba56b7f4aba2c"], "statement_hash": "66cffd63e622afc809ffcea154c77acb7025871176da7689b08b6db15ff40212"}}, {"rule": 2, "type": "equivalent", "target": "7007806ed1d8192364b7ef102e45e7ef", "evidence": {"same_day": true, "patch_ids": ["29a8e1db1536ed40c71312e7d2015c9e", "bcbaedd0455bfc84b87ba56b7f4aba2c"], "statement_hash": "66cffd63e622afc809ffcea154c77acb7025871176da7689b08b6db15ff40212"}}, {"rule": 2, "type": "equivalent", "target": "b5e7e2e2c6e0c744c28da7990822970a", "evidence": {"same_day": true, "patch_ids": ["29a8e1db1536ed40c71312e7d2015c9e", "bcbaedd0455bfc84b87ba56b7f4aba2c"], "statement_hash": "66cffd63e622afc809ffcea154c77acb7025871176da7689b08b6db15ff40212"}}, {"rule": 2, "type": "equivalent", "target": "bbf53e61656864929954589e1f777019", "evidence": {"same_day": true, "patch_ids": ["29a8e1db1536ed40c71312e7d2015c9e", "bcbaedd0455bfc84b87ba56b7f4aba2c"], "statement_hash": "66cffd63e622afc809ffcea154c77acb7025871176da7689b08b6db15ff40212"}}]}}, {"id": "18.6-bfaa3421904d3a41", "source_entry_id": "18.6/changes/002", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix contrib/pgcrypto's PGP encryption to detect unsupported ciphers", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-165fa935d28df7f1", "source_entry_id": "17.11/changes/002", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix contrib/pgcrypto's PGP encryption to detect unsupported ciphers"}], "entry": {"id": "18.6-bfaa3421904d3a41", "cves": ["CVE-2026-14663"], "html": "Fix contrib/pgcrypto's PGP encryption to detect unsupported ciphers (Daniel Gustafsson) § §
Previously, if OpenSSL rejected the requested cipher (for example, because it is running in FIPS mode, or the legacy provider hasn't been loaded), pgcrypto failed to notice the failure and simply XOR'd the non-encrypted block with the plaintext, rendering the “encryption” trivially breakable. This will typically occur with deprecated or non-FIPS cipher algorithms (cipher-algo=blowfish/bf, twofish, cast5, or 3des).
\nBy default, pgcrypto will now fail to decrypt any messages that were affected in this way. To allow retrieval of such data, a new option ignore-cipher-failure has been added to pgp_pub_decrypt() and pgp_sym_decrypt(). Setting ignore-cipher-failure=1 will restore their previous behavior, allowing the faulty encryption wrapper to be stripped off:
pgp_sym_decrypt(encrypted_column, any key, 'ignore-cipher-failure=1')\n\nOnce the affected messages are identified and stripped of their wrappers, they can then be re-encrypted with a modern algorithm. It is important however that the behavior of OpenSSL be the same as it was when the faulty messages were created: if the set of unsupported algorithms is not the same, this approach will not work. See the documentation for ignore-cipher-failure.
The PostgreSQL Project thanks Shishir Sharma for reporting this problem. (CVE-2026-14663)
", "text": "Fix contrib/pgcrypto's PGP encryption to detect unsupported ciphers (Daniel Gustafsson) § § Previously, if OpenSSL rejected the requested cipher (for example, because it is running in FIPS mode, or the legacy provider hasn't been loaded), pgcrypto failed to notice the failure and simply XOR'd the non-encrypted block with the plaintext, rendering the “encryption” trivially breakable. This will typically occur with deprecated or non-FIPS cipher algorithms (cipher-algo=blowfish/bf, twofish, cast5, or 3des). By default, pgcrypto will now fail to decrypt any messages that were affected in this way. To allow retrieval of such data, a new option ignore-cipher-failure has been added to pgp_pub_decrypt() and pgp_sym_decrypt(). Setting ignore-cipher-failure=1 will restore their previous behavior, allowing the faulty encryption wrapper to be stripped off: pgp_sym_decrypt(encrypted_column, any key, 'ignore-cipher-failure=1') Once the affected messages are identified and stripped of their wrappers, they can then be re-encrypted with a modern algorithm. It is important however that the behavior of OpenSSL be the same as it was when the faulty messages were created: if the set of unsupported algorithms is not the same, this approach will not work. See the documentation for ignore-cipher-failure. The PostgreSQL Project thanks Shishir Sharma for reporting this problem. (CVE-2026-14663)", "title": "Fix contrib/pgcrypto's PGP encryption to detect unsupported ciphers", "commits": ["4c5128ca0", "fe32b10fc"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "76c381bb98f96b0d13869dcbf838806af637da86790488eefb0781524c9bb11c", "section_path": ["Changes"], "commit_groups": [["472ef7e4a", "6ca6023ca", "7e29eb6f4", "b05cfc693", "ba207f58f", "d0ecee6de", "fe32b10fc"], ["49e795414", "4c5128ca0", "7eed42aa8", "953be116c", "ba2a63faf", "d97b3f58c", "e2c48c81f"]], "identity_text": "Fix contrib/pgcrypto's PGP encryption to detect unsupported ciphers (Daniel Gustafsson) Previously, if OpenSSL rejected the requested cipher (for example, because it is running in FIPS mode, or the legacy provider hasn't been loaded), pgcrypto failed to notice the failure and simply XOR'd the non-encrypted block with the plaintext, rendering the encryption trivially breakable. This will typically occur with deprecated or non-FIPS cipher algorithms (cipher-algo=blowfish/bf, twofish, cast5, or 3des). By default, pgcrypto will now fail to decrypt any messages that were affected in this way. To allow retrieval of such data, a new option ignore-cipher-failure has been added to pgp_pub_decrypt() and pgp_sym_decrypt(). Setting ignore-cipher-failure=1 will restore their previous behavior, allowing the faulty encryption wrapper to be stripped off: pgp_sym_decrypt(encrypted_column, any key, 'ignore-cipher-failure=1') Once the affected messages are identified and stripped of their wrappers, they can then be re-encrypted with a modern algorithm. It is important however that the behavior of OpenSSL be the same as it was when the faulty messages were created: if the set of unsupported algorithms is not the same, this approach will not work. See the documentation for ignore-cipher-failure. The PostgreSQL Project thanks Shishir Sharma for reporting this problem. (CVE-2026-14663)", "commit_aliases": ["472ef7e4a", "49e795414", "4c5128ca0", "6ca6023ca", "7e29eb6f4", "7eed42aa8", "953be116c", "b05cfc693", "ba207f58f", "ba2a63faf", "d0ecee6de", "d97b3f58c", "e2c48c81f", "fe32b10fc"], "source_commits": ["4c5128ca0", "fe32b10fc"], "source_entry_id": "18.6/changes/002", "db_id": "e8d5337224696bc194016b8a5269940d", "patch_ids": ["0c0f3075fa6d42cb4f237a14111f3f86", "94579ce6ea64094f97312d8046fcb082"], "statement_hash": "f9b50dfe772a85830e7ce5570ba2e751618ceca0e1ebf0653490632965de190f", "relations": [{"rule": 2, "type": "equivalent", "target": "28125c4ed11f62e12267d5aa58f29ab4", "evidence": {"same_day": true, "patch_ids": ["0c0f3075fa6d42cb4f237a14111f3f86", "94579ce6ea64094f97312d8046fcb082"], "statement_hash": "f9b50dfe772a85830e7ce5570ba2e751618ceca0e1ebf0653490632965de190f"}}, {"rule": 2, "type": "equivalent", "target": "379745809d65e827e6739e3818394675", "evidence": {"same_day": true, "patch_ids": ["0c0f3075fa6d42cb4f237a14111f3f86", "94579ce6ea64094f97312d8046fcb082"], "statement_hash": "f9b50dfe772a85830e7ce5570ba2e751618ceca0e1ebf0653490632965de190f"}}, {"rule": 2, "type": "equivalent", "target": "5487cefec946cc3b492ec90f8407bbc0", "evidence": {"same_day": true, "patch_ids": ["0c0f3075fa6d42cb4f237a14111f3f86", "94579ce6ea64094f97312d8046fcb082"], "statement_hash": "f9b50dfe772a85830e7ce5570ba2e751618ceca0e1ebf0653490632965de190f"}}, {"rule": 2, "type": "equivalent", "target": "a686eb51b6b69a27a6ba670a1473120d", "evidence": {"same_day": true, "patch_ids": ["0c0f3075fa6d42cb4f237a14111f3f86", "94579ce6ea64094f97312d8046fcb082"], "statement_hash": "f9b50dfe772a85830e7ce5570ba2e751618ceca0e1ebf0653490632965de190f"}}]}}, {"id": "18.6-7711e8f6ad16c5dd", "source_entry_id": "18.6/changes/003", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix psql to skip in-line data following a scripted COPY ... FROM STDIN command, even if the COPY fails before sending PGRES_COPY_IN", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-8dd81897faaffe37", "source_entry_id": "17.11/changes/003", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix psql to skip in-line data following a scripted COPY ... FROM STDIN command, even if the COPY fails before sending PGRES_COPY_IN"}], "entry": {"id": "18.6-7711e8f6ad16c5dd", "cves": ["CVE-2026-6464"], "html": "Fix psql to skip in-line data following a scripted COPY ... FROM STDIN command, even if the COPY fails before sending PGRES_COPY_IN (Tom Lane) § §
Previously, if a COPY command failed at startup (for instance, because the target table doesn't exist) psql would not realize that and would proceed to read the following in-line data as SQL commands. In the best case that's wrong and in the worst case it's a SQL-injection hazard. Teach psql to recognize syntactically-valid COPY ... FROM STDIN commands and to skip data on its own authority if the server doesn't respond with PGRES_COPY_IN.
While this fix is unlikely to affect any production SQL scripts, test scripts might intentionally exercise failing COPY ... FROM STDIN commands. Those will need to gain a \\. data terminator line after each such command.
The PostgreSQL Project thanks Alexander Lakhin for reporting this problem. (CVE-2026-6464)
", "text": "Fix psql to skip in-line data following a scripted COPY ... FROM STDIN command, even if the COPY fails before sending PGRES_COPY_IN (Tom Lane) § § Previously, if a COPY command failed at startup (for instance, because the target table doesn't exist) psql would not realize that and would proceed to read the following in-line data as SQL commands. In the best case that's wrong and in the worst case it's a SQL-injection hazard. Teach psql to recognize syntactically-valid COPY ... FROM STDIN commands and to skip data on its own authority if the server doesn't respond with PGRES_COPY_IN. While this fix is unlikely to affect any production SQL scripts, test scripts might intentionally exercise failing COPY ... FROM STDIN commands. Those will need to gain a \\. data terminator line after each such command. The PostgreSQL Project thanks Alexander Lakhin for reporting this problem. (CVE-2026-6464)", "title": "Fix psql to skip in-line data following a scripted COPY ... FROM STDIN command, even if the COPY fails before sending PGRES_COPY_IN", "commits": ["29921259e", "900894d35"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "eecc14b4909d681329da93aaa4d3c4b6db68b34d0fbfa27af7599af1e496d5aa", "section_path": ["Changes"], "commit_groups": [["29921259e", "2bdfd5cdc", "3045a25ba", "3fdcfa8f7", "46fa1f6f3", "5c51ae455", "d6ab88d37"], ["7215c7e96", "8cdbabea7", "8cf01e213", "900894d35", "cf754f741", "db96e87f9", "dca6627de"]], "identity_text": "Fix psql to skip in-line data following a scripted COPY ... FROM STDIN command, even if the COPY fails before sending PGRES_COPY_IN (Tom Lane) Previously, if a COPY command failed at startup (for instance, because the target table doesn't exist) psql would not realize that and would proceed to read the following in-line data as SQL commands. In the best case that's wrong and in the worst case it's a SQL-injection hazard. Teach psql to recognize syntactically-valid COPY ... FROM STDIN commands and to skip data on its own authority if the server doesn't respond with PGRES_COPY_IN. While this fix is unlikely to affect any production SQL scripts, test scripts might intentionally exercise failing COPY ... FROM STDIN commands. Those will need to gain a \\. data terminator line after each such command. The PostgreSQL Project thanks Alexander Lakhin for reporting this problem. (CVE-2026-6464)", "commit_aliases": ["29921259e", "2bdfd5cdc", "3045a25ba", "3fdcfa8f7", "46fa1f6f3", "5c51ae455", "7215c7e96", "8cdbabea7", "8cf01e213", "900894d35", "cf754f741", "d6ab88d37", "db96e87f9", "dca6627de"], "source_commits": ["29921259e", "900894d35"], "source_entry_id": "18.6/changes/003", "db_id": "3c7601286aa0c9239f3cd6933eeddc1f", "patch_ids": ["bb5ab12243a3045680f47ff1cb2c8480", "ecf5b4358ac3d55d48e5c5a6cf618bc5"], "statement_hash": "76e8147c7ad5a98f52d6ef02172b79adbee8009366c00ae89f0a205215b4b225", "relations": [{"rule": 2, "type": "equivalent", "target": "3fc8822e02c16e254582e2877b732705", "evidence": {"same_day": true, "patch_ids": ["bb5ab12243a3045680f47ff1cb2c8480", "ecf5b4358ac3d55d48e5c5a6cf618bc5"], "statement_hash": "76e8147c7ad5a98f52d6ef02172b79adbee8009366c00ae89f0a205215b4b225"}}, {"rule": 2, "type": "equivalent", "target": "a4c84c6885a3a330efb43a5e79c7eeca", "evidence": {"same_day": true, "patch_ids": ["bb5ab12243a3045680f47ff1cb2c8480", "ecf5b4358ac3d55d48e5c5a6cf618bc5"], "statement_hash": "76e8147c7ad5a98f52d6ef02172b79adbee8009366c00ae89f0a205215b4b225"}}, {"rule": 2, "type": "equivalent", "target": "df55d2444f4fc088a4a59341aed77733", "evidence": {"same_day": true, "patch_ids": ["bb5ab12243a3045680f47ff1cb2c8480", "ecf5b4358ac3d55d48e5c5a6cf618bc5"], "statement_hash": "76e8147c7ad5a98f52d6ef02172b79adbee8009366c00ae89f0a205215b4b225"}}, {"rule": 2, "type": "equivalent", "target": "ea96c547a98f3910bcd150ec7a9bb871", "evidence": {"same_day": true, "patch_ids": ["bb5ab12243a3045680f47ff1cb2c8480", "ecf5b4358ac3d55d48e5c5a6cf618bc5"], "statement_hash": "76e8147c7ad5a98f52d6ef02172b79adbee8009366c00ae89f0a205215b4b225"}}]}}, {"id": "18.6-cdf902a8952d780f", "source_entry_id": "18.6/changes/004", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Cross-check the output row type of a portal running EXECUTE or FETCH", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-b9a0ccf8cc602cca", "source_entry_id": "17.11/changes/004", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Cross-check the output row type of a portal running EXECUTE or FETCH"}], "entry": {"id": "18.6-cdf902a8952d780f", "cves": ["CVE-2026-16239"], "html": "Cross-check the output row type of a portal running EXECUTE or FETCH (Robert Haas) §
EXECUTE and FETCH use two portals: an outer one for the statement itself, and an inner one running the query being executed on its behalf. It was previously possible to make the declared row types of the two portals diverge, leading to server memory disclosure and arbitrary code execution.
The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) and Peter Geoghegan for reporting this problem. (CVE-2026-16239)
", "text": "Cross-check the output row type of a portal running EXECUTE or FETCH (Robert Haas) § EXECUTE and FETCH use two portals: an outer one for the statement itself, and an inner one running the query being executed on its behalf. It was previously possible to make the declared row types of the two portals diverge, leading to server memory disclosure and arbitrary code execution. The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) and Peter Geoghegan for reporting this problem. (CVE-2026-16239)", "title": "Cross-check the output row type of a portal running EXECUTE or FETCH", "commits": ["37b8f3b0e"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "7787b5a3c11e14e37ef4fc1d99970faa5faa1f486bc292127f6a786ec1cc8f4c", "section_path": ["Changes"], "commit_groups": [["1f49beef2", "37b8f3b0e", "60887d348", "64a65ead1", "7d150b5c9", "9e02e2e18", "fc933ce00"]], "identity_text": "Cross-check the output row type of a portal running EXECUTE or FETCH (Robert Haas) EXECUTE and FETCH use two portals: an outer one for the statement itself, and an inner one running the query being executed on its behalf. It was previously possible to make the declared row types of the two portals diverge, leading to server memory disclosure and arbitrary code execution. The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) and Peter Geoghegan for reporting this problem. (CVE-2026-16239)", "commit_aliases": ["1f49beef2", "37b8f3b0e", "60887d348", "64a65ead1", "7d150b5c9", "9e02e2e18", "fc933ce00"], "source_commits": ["37b8f3b0e"], "source_entry_id": "18.6/changes/004", "db_id": "5b8818230400246029db8b181a69938c", "patch_ids": ["bca9a8aea055bf40b974631f891c3459"], "statement_hash": "6bfdff724b157ff6ff7a59fd5879e05c524cc0a5a96ac58a33fa9750cc2db073", "relations": [{"rule": 2, "type": "equivalent", "target": "35f9a631aba647241e1c1fe3a3c4c269", "evidence": {"same_day": true, "patch_ids": ["bca9a8aea055bf40b974631f891c3459"], "statement_hash": "6bfdff724b157ff6ff7a59fd5879e05c524cc0a5a96ac58a33fa9750cc2db073"}}, {"rule": 2, "type": "equivalent", "target": "3ec84f87545930ce1036d071dad3e665", "evidence": {"same_day": true, "patch_ids": ["bca9a8aea055bf40b974631f891c3459"], "statement_hash": "6bfdff724b157ff6ff7a59fd5879e05c524cc0a5a96ac58a33fa9750cc2db073"}}, {"rule": 2, "type": "equivalent", "target": "e2286cb0c701bb465fa540c1d4a45071", "evidence": {"same_day": true, "patch_ids": ["bca9a8aea055bf40b974631f891c3459"], "statement_hash": "6bfdff724b157ff6ff7a59fd5879e05c524cc0a5a96ac58a33fa9750cc2db073"}}, {"rule": 2, "type": "equivalent", "target": "e9fc65bf1c23945887e9b1904d08b935", "evidence": {"same_day": true, "patch_ids": ["bca9a8aea055bf40b974631f891c3459"], "statement_hash": "6bfdff724b157ff6ff7a59fd5879e05c524cc0a5a96ac58a33fa9750cc2db073"}}]}}, {"id": "18.6-251aba36d837c523", "source_entry_id": "18.6/changes/005", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix buffer overrun with long time zone abbreviation in to_char()", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-9aaf551ddc6d8e1b", "source_entry_id": "17.11/changes/005", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix buffer overrun with long time zone abbreviation in to_char()"}], "entry": {"id": "18.6-251aba36d837c523", "cves": ["CVE-2026-14669"], "html": "Fix buffer overrun with long time zone abbreviation in to_char() (Tom Lane) §
This can easily crash the server, and exploits leading to arbitrary code execution have been reported.
\nThe PostgreSQL Project thanks Hcamael, Amjad Shahzad, Tan Zhen of AntAISecurityLab, Tomer Fichman, Zheng Yu, Amy Burnett (OpenAI Codex Security), Rick de Jager, Heewon Song, Sylvie Mayer, Aleksander Alekseev, and Hillai Ben Sasson for reporting this problem. (CVE-2026-14669)
", "text": "Fix buffer overrun with long time zone abbreviation in to_char() (Tom Lane) § This can easily crash the server, and exploits leading to arbitrary code execution have been reported. The PostgreSQL Project thanks Hcamael, Amjad Shahzad, Tan Zhen of AntAISecurityLab, Tomer Fichman, Zheng Yu, Amy Burnett (OpenAI Codex Security), Rick de Jager, Heewon Song, Sylvie Mayer, Aleksander Alekseev, and Hillai Ben Sasson for reporting this problem. (CVE-2026-14669)", "title": "Fix buffer overrun with long time zone abbreviation in to_char()", "commits": ["4fafe2380"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "08e4bf2c18b6cd512f8d32024d63b2eb56f09338fc780ac9e5dea9a2d705627b", "section_path": ["Changes"], "commit_groups": [["12a620686", "3294ab839", "3d724bf4f", "4fafe2380"], ["2cf28d1b9", "331016322", "5dbeb69bc", "5fb3c6389", "8f64cc83f", "b614de487", "bef46aed3"]], "identity_text": "Fix buffer overrun with long time zone abbreviation in to_char() (Tom Lane) This can easily crash the server, and exploits leading to arbitrary code execution have been reported. The PostgreSQL Project thanks Hcamael, Amjad Shahzad, Tan Zhen of AntAISecurityLab, Tomer Fichman, Zheng Yu, Amy Burnett (OpenAI Codex Security), Rick de Jager, Heewon Song, Sylvie Mayer, Aleksander Alekseev, and Hillai Ben Sasson for reporting this problem. (CVE-2026-14669)", "commit_aliases": ["12a620686", "2cf28d1b9", "3294ab839", "331016322", "3d724bf4f", "4fafe2380", "5dbeb69bc", "5fb3c6389", "8f64cc83f", "b614de487", "bef46aed3"], "source_commits": ["4fafe2380", "5dbeb69bc"], "source_entry_id": "18.6/changes/005", "db_id": "1b34d3e2b18d75096fd2914d3673446c", "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9", "f6e281e04c97bcdc5fa29a25f60517ca"], "statement_hash": "07a38d896c94ef2711ebb1c7c66bf1537f00d81b7488271a922229ab5b8f1962", "relations": [{"rule": 2, "type": "equivalent", "target": "027ccc17f71deb2b38e14fc8cc82dccd", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9", "f6e281e04c97bcdc5fa29a25f60517ca"], "statement_hash": "07a38d896c94ef2711ebb1c7c66bf1537f00d81b7488271a922229ab5b8f1962", "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "related", "target": "1ba572e4a9f5584ecce320e293d4b258", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "equivalent", "target": "70897dba323af27792543b2311799668", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9", "f6e281e04c97bcdc5fa29a25f60517ca"], "statement_hash": "07a38d896c94ef2711ebb1c7c66bf1537f00d81b7488271a922229ab5b8f1962", "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "related", "target": "771fa954f9b22168a0764dc12074dadb", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "related", "target": "b17ef22f538327cabf0726e1b3f902cc", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "equivalent", "target": "bf82a2510c4dfe4309435e9bce0ab3a4", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9", "f6e281e04c97bcdc5fa29a25f60517ca"], "statement_hash": "07a38d896c94ef2711ebb1c7c66bf1537f00d81b7488271a922229ab5b8f1962", "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "related", "target": "bfa74492dd2c8ed5f4b0a4321cb63c85", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "equivalent", "target": "bfa88fa3d381bbc9b7ee7a8614ea363c", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9", "f6e281e04c97bcdc5fa29a25f60517ca"], "statement_hash": "07a38d896c94ef2711ebb1c7c66bf1537f00d81b7488271a922229ab5b8f1962", "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "related", "target": "ea24770278021c00f25a8b13bceb2a2c", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}]}}, {"id": "18.6-94204615ddc5390c", "source_entry_id": "18.6/changes/006", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix buffer overrun in regexp match/split functions", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-cb1b743a0208c3c0", "source_entry_id": "17.11/changes/006", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix buffer overrun in regexp match/split functions"}], "entry": {"id": "18.6-94204615ddc5390c", "cves": ["CVE-2026-14664"], "html": "Fix buffer overrun in regexp match/split functions (Masahiko Sawada) §
\nIf passed invalidly-encoded data, these functions could write past the end of their conversion buffer.
\nThe PostgreSQL Project thanks Francesco Verardi for reporting this problem. (CVE-2026-14664)
", "text": "Fix buffer overrun in regexp match/split functions (Masahiko Sawada) § If passed invalidly-encoded data, these functions could write past the end of their conversion buffer. The PostgreSQL Project thanks Francesco Verardi for reporting this problem. (CVE-2026-14664)", "title": "Fix buffer overrun in regexp match/split functions", "commits": ["b7e5c3f63"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "656802ae623d28a3a12751de94a467f10ff76c8f7d87e4aee4c2fe8b1bee118d", "section_path": ["Changes"], "commit_groups": [["127a0673f", "3179253c2", "343aabf1d", "7df2aa8ef", "890327639", "b7e5c3f63", "e91dcfcca"]], "identity_text": "Fix buffer overrun in regexp match/split functions (Masahiko Sawada) If passed invalidly-encoded data, these functions could write past the end of their conversion buffer. The PostgreSQL Project thanks Francesco Verardi for reporting this problem. (CVE-2026-14664)", "commit_aliases": ["127a0673f", "3179253c2", "343aabf1d", "7df2aa8ef", "890327639", "b7e5c3f63", "e91dcfcca"], "source_commits": ["b7e5c3f63"], "source_entry_id": "18.6/changes/006", "db_id": "31c6d0327b9be4008171a2064e268f6c", "patch_ids": ["0cfa785ead8bfc886613fffe5a36e1bc"], "statement_hash": "966f554e1e936775481250a24075b22027e89685eec1e0c08a9bfd4f761ad444", "relations": [{"rule": 2, "type": "equivalent", "target": "2dff40febce19283ae38aa647816cd73", "evidence": {"same_day": true, "patch_ids": ["0cfa785ead8bfc886613fffe5a36e1bc"], "statement_hash": "966f554e1e936775481250a24075b22027e89685eec1e0c08a9bfd4f761ad444"}}, {"rule": 2, "type": "equivalent", "target": "8e5a5f5c59f91019e7f4f9160ae97951", "evidence": {"same_day": true, "patch_ids": ["0cfa785ead8bfc886613fffe5a36e1bc"], "statement_hash": "966f554e1e936775481250a24075b22027e89685eec1e0c08a9bfd4f761ad444"}}, {"rule": 2, "type": "equivalent", "target": "ee22496a80ac478c7a0e734782b86377", "evidence": {"same_day": true, "patch_ids": ["0cfa785ead8bfc886613fffe5a36e1bc"], "statement_hash": "966f554e1e936775481250a24075b22027e89685eec1e0c08a9bfd4f761ad444"}}, {"rule": 2, "type": "equivalent", "target": "ee60c1b700f965a0913e70294c9927f5", "evidence": {"same_day": true, "patch_ids": ["0cfa785ead8bfc886613fffe5a36e1bc"], "statement_hash": "966f554e1e936775481250a24075b22027e89685eec1e0c08a9bfd4f761ad444"}}]}}, {"id": "18.6-4a45e658fb69cefb", "source_entry_id": "18.6/changes/007", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Harden the ascii() function against invalid input", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-e6de3d1ea5ee5a52", "source_entry_id": "17.11/changes/007", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Harden the ascii() function against invalid input"}], "entry": {"id": "18.6-4a45e658fb69cefb", "cves": ["CVE-2026-18024"], "html": "Harden the ascii() function against invalid input (Michael Paquier) §
By supplying invalidly-encoded input, this function could be coaxed to read and return a few bytes of data that it shouldn't. In assert-enabled builds, its assertions could be triggered too.
\nThe PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-18024)
", "text": "Harden the ascii() function against invalid input (Michael Paquier) § By supplying invalidly-encoded input, this function could be coaxed to read and return a few bytes of data that it shouldn't. In assert-enabled builds, its assertions could be triggered too. The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-18024)", "title": "Harden the ascii() function against invalid input", "commits": ["08e812c02"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "5049ae9ce81738348074ae45e06e63cd9b97bc4cbabd39fbfb981007af3e98b9", "section_path": ["Changes"], "commit_groups": [["08e812c02", "3b925133b", "42d333a78", "80ce920a5", "849da8210", "a16c31d39", "ac450853d"]], "identity_text": "Harden the ascii() function against invalid input (Michael Paquier) By supplying invalidly-encoded input, this function could be coaxed to read and return a few bytes of data that it shouldn't. In assert-enabled builds, its assertions could be triggered too. The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-18024)", "commit_aliases": ["08e812c02", "3b925133b", "42d333a78", "80ce920a5", "849da8210", "a16c31d39", "ac450853d"], "source_commits": ["08e812c02"], "source_entry_id": "18.6/changes/007", "db_id": "28116a0caca0f02980e6eaa33ad62878", "patch_ids": ["55b264296776b9b13ab6e5f986e375f2"], "statement_hash": "30f93fe9d01d5c3e7f51b7ee86b38f0ddd66109774cc7f5bd732db874c26c1a3", "relations": [{"rule": 2, "type": "equivalent", "target": "12383fa89e42b03b68791e4222af5d42", "evidence": {"same_day": true, "patch_ids": ["55b264296776b9b13ab6e5f986e375f2"], "statement_hash": "30f93fe9d01d5c3e7f51b7ee86b38f0ddd66109774cc7f5bd732db874c26c1a3"}}, {"rule": 2, "type": "equivalent", "target": "3fcea79a14fe4f9b97afbae1d619ffdf", "evidence": {"same_day": true, "patch_ids": ["55b264296776b9b13ab6e5f986e375f2"], "statement_hash": "30f93fe9d01d5c3e7f51b7ee86b38f0ddd66109774cc7f5bd732db874c26c1a3"}}, {"rule": 2, "type": "equivalent", "target": "5a7d1cc5fb2e41a7a2acbb0c59894992", "evidence": {"same_day": true, "patch_ids": ["55b264296776b9b13ab6e5f986e375f2"], "statement_hash": "30f93fe9d01d5c3e7f51b7ee86b38f0ddd66109774cc7f5bd732db874c26c1a3"}}, {"rule": 2, "type": "equivalent", "target": "776c34393ca8da3ea9c128e3d7219ad3", "evidence": {"same_day": true, "patch_ids": ["55b264296776b9b13ab6e5f986e375f2"], "statement_hash": "30f93fe9d01d5c3e7f51b7ee86b38f0ddd66109774cc7f5bd732db874c26c1a3"}}]}}, {"id": "18.6-61ef917ba36ebc0f", "source_entry_id": "18.6/changes/008", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix multirange type handling in pg_restore_attribute_stats()", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-ba8cb69723cdb335", "source_entry_id": "17.11/changes/008", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix multirange type handling in pg_restore_attribute_stats()"}], "entry": {"id": "18.6-61ef917ba36ebc0f", "cves": ["CVE-2026-16238"], "html": "Fix multirange type handling in pg_restore_attribute_stats() (OpenAI Security Research Team) § §
pg_restore_attribute_stats() treated multirange types just like their underlying range type. This works correctly for the bounds histogram, but it was wrong for all the other statistics kinds.
The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-16238)
", "text": "Fix multirange type handling in pg_restore_attribute_stats() (OpenAI Security Research Team) § § pg_restore_attribute_stats() treated multirange types just like their underlying range type. This works correctly for the bounds histogram, but it was wrong for all the other statistics kinds. The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-16238)", "title": "Fix multirange type handling in pg_restore_attribute_stats()", "commits": ["08454e8b2", "8d428c6e6"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "2d778012b54a32e71ae2020cc0542b1f6f274071aca48245105476b79eaf8788", "section_path": ["Changes"], "commit_groups": [["08454e8b2", "57835938f", "b3d9262bb"], ["8d428c6e6"]], "identity_text": "Fix multirange type handling in pg_restore_attribute_stats() (OpenAI Security Research Team) pg_restore_attribute_stats() treated multirange types just like their underlying range type. This works correctly for the bounds histogram, but it was wrong for all the other statistics kinds. The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-16238)", "commit_aliases": ["08454e8b2", "57835938f", "8d428c6e6", "b3d9262bb"], "source_commits": ["08454e8b2", "8d428c6e6"], "source_entry_id": "18.6/changes/008", "db_id": "b73333feb74980fc954bc5f235124549", "patch_ids": ["d27616df77f838ec6d65ceac3dab4d29", "e919d719afc48bf0f48ebde0e7586d45"], "statement_hash": "6c702ad16b71228cee81cbc85de20c25fe06c4ec29202dc0be958c9f409a702d", "relations": [{"rule": 2, "type": "equivalent", "target": "23063a48b3c2ddae3e3c1623fd1552b5", "evidence": {"same_day": true, "patch_ids": ["d27616df77f838ec6d65ceac3dab4d29", "e919d719afc48bf0f48ebde0e7586d45"], "statement_hash": "6c702ad16b71228cee81cbc85de20c25fe06c4ec29202dc0be958c9f409a702d"}}, {"rule": 2, "type": "equivalent", "target": "7cdf19717697008d9621e1145ea725cc", "evidence": {"same_day": true, "patch_ids": ["d27616df77f838ec6d65ceac3dab4d29", "e919d719afc48bf0f48ebde0e7586d45"], "statement_hash": "6c702ad16b71228cee81cbc85de20c25fe06c4ec29202dc0be958c9f409a702d"}}, {"rule": 2, "type": "equivalent", "target": "c02d2730726a9bba001c3dcad007a406", "evidence": {"same_day": true, "patch_ids": ["d27616df77f838ec6d65ceac3dab4d29", "e919d719afc48bf0f48ebde0e7586d45"], "statement_hash": "6c702ad16b71228cee81cbc85de20c25fe06c4ec29202dc0be958c9f409a702d"}}, {"rule": 2, "type": "equivalent", "target": "e8b2ed03b7135b067945fe6134a48d0c", "evidence": {"same_day": true, "patch_ids": ["d27616df77f838ec6d65ceac3dab4d29", "e919d719afc48bf0f48ebde0e7586d45"], "statement_hash": "6c702ad16b71228cee81cbc85de20c25fe06c4ec29202dc0be958c9f409a702d"}}]}}, {"id": "18.6-d63d1269e786113b", "source_entry_id": "18.6/changes/009", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Make scalarineqsel() check that a constant it expects to be of type tid actually is", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-3000fb5c37bacd7b", "source_entry_id": "17.11/changes/009", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Make scalarineqsel() check that a constant it expects to be of type tid actually is"}], "entry": {"id": "18.6-d63d1269e786113b", "cves": ["CVE-2026-14668"], "html": "Make scalarineqsel() check that a constant it expects to be of type tid actually is (Tom Lane) §
This expectation will hold for all the built-in operators that use this estimator, but a maliciously-constructed operator could violate it, leading to a crash or server memory disclosure.
\nThe PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14668)
", "text": "Make scalarineqsel() check that a constant it expects to be of type tid actually is (Tom Lane) § This expectation will hold for all the built-in operators that use this estimator, but a maliciously-constructed operator could violate it, leading to a crash or server memory disclosure. The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14668)", "title": "Make scalarineqsel() check that a constant it expects to be of type tid actually is", "commits": ["a2cb5a1cf"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "71a628120eaf5daa06fcc85e23c772587ad03074850944dabf62f1513a399b0b", "section_path": ["Changes"], "commit_groups": [["005ffaa7f", "0d60ee717", "0ebf896f4", "591192e2e", "59205c7e9", "8f0c3d2fe", "a2cb5a1cf"]], "identity_text": "Make scalarineqsel() check that a constant it expects to be of type tid actually is (Tom Lane) This expectation will hold for all the built-in operators that use this estimator, but a maliciously-constructed operator could violate it, leading to a crash or server memory disclosure. The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14668)", "commit_aliases": ["005ffaa7f", "0d60ee717", "0ebf896f4", "591192e2e", "59205c7e9", "8f0c3d2fe", "a2cb5a1cf"], "source_commits": ["a2cb5a1cf"], "source_entry_id": "18.6/changes/009", "db_id": "97ac47be877760addc2f5b0afd4a077b", "patch_ids": ["de7610ed8a59864556ff1fc7a996e26b"], "statement_hash": "9af3f49dfa69a353a456c0aa2751b844ae492634dd94bd7ac2ae7a38d22121ba", "relations": [{"rule": 2, "type": "equivalent", "target": "0c4b36600df59cbe54ae892784279e12", "evidence": {"same_day": true, "patch_ids": ["de7610ed8a59864556ff1fc7a996e26b"], "statement_hash": "9af3f49dfa69a353a456c0aa2751b844ae492634dd94bd7ac2ae7a38d22121ba"}}, {"rule": 2, "type": "equivalent", "target": "7cbf7cb5e5571e3fde38e116219b7ff1", "evidence": {"same_day": true, "patch_ids": ["de7610ed8a59864556ff1fc7a996e26b"], "statement_hash": "9af3f49dfa69a353a456c0aa2751b844ae492634dd94bd7ac2ae7a38d22121ba"}}, {"rule": 2, "type": "equivalent", "target": "8e21096b01a0beb228febdc9d9b21e1a", "evidence": {"same_day": true, "patch_ids": ["de7610ed8a59864556ff1fc7a996e26b"], "statement_hash": "9af3f49dfa69a353a456c0aa2751b844ae492634dd94bd7ac2ae7a38d22121ba"}}, {"rule": 2, "type": "equivalent", "target": "9bd6480c825dec4b7dd7e98d8eca9b8f", "evidence": {"same_day": true, "patch_ids": ["de7610ed8a59864556ff1fc7a996e26b"], "statement_hash": "9af3f49dfa69a353a456c0aa2751b844ae492634dd94bd7ac2ae7a38d22121ba"}}]}}, {"id": "18.6-774bcf033add5976", "source_entry_id": "18.6/changes/010", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Harden tsvector and tsquery code against overly long values (both individual lexemes and total vector/query length)", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-730aec962ef92894", "source_entry_id": "17.11/changes/010", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Harden tsvector and tsquery code against overly long values (both individual lexemes and total vector/query length)"}], "entry": {"id": "18.6-774bcf033add5976", "cves": ["CVE-2026-14662"], "html": "Harden tsvector and tsquery code against overly long values (both individual lexemes and total vector/query length) (Tom Lane) § §
The documented limits were not enforced in all code paths.
\nThe PostgreSQL Project thanks Yuhang Wu, Zhenpeng Lin, Zheng Yu, and Hcamael for reporting these problems. (CVE-2026-14662)
", "text": "Harden tsvector and tsquery code against overly long values (both individual lexemes and total vector/query length) (Tom Lane) § § The documented limits were not enforced in all code paths. The PostgreSQL Project thanks Yuhang Wu, Zhenpeng Lin, Zheng Yu, and Hcamael for reporting these problems. (CVE-2026-14662)", "title": "Harden tsvector and tsquery code against overly long values (both individual lexemes and total vector/query length)", "commits": ["dddc8a69f", "e25135057"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "9634a8c9c802cecb1686784102c75528a5294d81c7a5ed66b0e5c5818f24b1c3", "section_path": ["Changes"], "commit_groups": [["1e3014f37", "3b2238fbe", "4f8b37b6b", "84b6a7a06", "8e87bd473", "90649b6f8", "dddc8a69f"], ["23d9ad771", "7c1a8805a", "7c2ba321d", "cb947ca31", "e25135057", "f443d0a0a", "fe0b5bd6d"]], "identity_text": "Harden tsvector and tsquery code against overly long values (both individual lexemes and total vector/query length) (Tom Lane) The documented limits were not enforced in all code paths. The PostgreSQL Project thanks Yuhang Wu, Zhenpeng Lin, Zheng Yu, and Hcamael for reporting these problems. (CVE-2026-14662)", "commit_aliases": ["1e3014f37", "23d9ad771", "3b2238fbe", "4f8b37b6b", "7c1a8805a", "7c2ba321d", "84b6a7a06", "8e87bd473", "90649b6f8", "cb947ca31", "dddc8a69f", "e25135057", "f443d0a0a", "fe0b5bd6d"], "source_commits": ["dddc8a69f", "e25135057"], "source_entry_id": "18.6/changes/010", "db_id": "e8daa5e986b5139aa334ffb65fe716c9", "patch_ids": ["5d937de349e172af32f322b84994627c", "8594911de53a70a64ff7a92a7e2e7410"], "statement_hash": "58ee7f5cd2b407484897fe1a7e956c16ce0212b7ffe535ead9c50c21ba819c1e", "relations": [{"rule": 2, "type": "equivalent", "target": "3d26273adc446717f1dd7040f0311025", "evidence": {"same_day": true, "patch_ids": ["5d937de349e172af32f322b84994627c", "8594911de53a70a64ff7a92a7e2e7410"], "statement_hash": "58ee7f5cd2b407484897fe1a7e956c16ce0212b7ffe535ead9c50c21ba819c1e"}}, {"rule": 2, "type": "equivalent", "target": "728b5628883585075c121bd29db0affe", "evidence": {"same_day": true, "patch_ids": ["5d937de349e172af32f322b84994627c", "8594911de53a70a64ff7a92a7e2e7410"], "statement_hash": "58ee7f5cd2b407484897fe1a7e956c16ce0212b7ffe535ead9c50c21ba819c1e"}}, {"rule": 2, "type": "equivalent", "target": "aa4dcca3c56a82ca052b2bdbc7e68c1b", "evidence": {"same_day": true, "patch_ids": ["5d937de349e172af32f322b84994627c", "8594911de53a70a64ff7a92a7e2e7410"], "statement_hash": "58ee7f5cd2b407484897fe1a7e956c16ce0212b7ffe535ead9c50c21ba819c1e"}}, {"rule": 2, "type": "equivalent", "target": "f4f98b5e09530fc0d9eabe85409d03ef", "evidence": {"same_day": true, "patch_ids": ["5d937de349e172af32f322b84994627c", "8594911de53a70a64ff7a92a7e2e7410"], "statement_hash": "58ee7f5cd2b407484897fe1a7e956c16ce0212b7ffe535ead9c50c21ba819c1e"}}]}}, {"id": "18.6-fe89a6f688a29e60", "source_entry_id": "18.6/changes/011", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix various places that mistakenly assumed they would not have to deal with more than FUNC_MAX_ARGS function arguments", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-dd9a429d3ce13500", "source_entry_id": "17.11/changes/011", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix various places that mistakenly assumed they would not have to deal with more than FUNC_MAX_ARGS function arguments"}], "entry": {"id": "18.6-fe89a6f688a29e60", "cves": ["CVE-2026-14679"], "html": "Fix various places that mistakenly assumed they would not have to deal with more than FUNC_MAX_ARGS function arguments (Tom Lane) § §
Notably, the server's actual limit on the number of arguments to an aggregate function is FUNC_MAX_ARGS - 1, but the parser failed to enforce that, creating hazards downstream.
The PostgreSQL Project thanks Zheng Yu, ylwangtju, and Masahiko Sawada for reporting these problems. (CVE-2026-14679)
", "text": "Fix various places that mistakenly assumed they would not have to deal with more than FUNC_MAX_ARGS function arguments (Tom Lane) § § Notably, the server's actual limit on the number of arguments to an aggregate function is FUNC_MAX_ARGS - 1, but the parser failed to enforce that, creating hazards downstream. The PostgreSQL Project thanks Zheng Yu, ylwangtju, and Masahiko Sawada for reporting these problems. (CVE-2026-14679)", "title": "Fix various places that mistakenly assumed they would not have to deal with more than FUNC_MAX_ARGS function arguments", "commits": ["2a03f21da", "7f0e1aac7"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "78336166a7234ad10b84a1249d4b43d09a265825e59787c04f3fc43d58a86256", "section_path": ["Changes"], "commit_groups": [["2a03f21da", "32e0d25d4", "42d9749b7", "60e7329b9", "8a40f4b09", "c7f462838", "eb2fa2704"], ["797e3cc4c", "7bd56f7a3", "7f0e1aac7", "8c67c4cf5", "92972e815", "b417744a7", "cf44ff5e6"]], "identity_text": "Fix various places that mistakenly assumed they would not have to deal with more than FUNC_MAX_ARGS function arguments (Tom Lane) Notably, the server's actual limit on the number of arguments to an aggregate function is FUNC_MAX_ARGS - 1, but the parser failed to enforce that, creating hazards downstream. The PostgreSQL Project thanks Zheng Yu, ylwangtju, and Masahiko Sawada for reporting these problems. (CVE-2026-14679)", "commit_aliases": ["2a03f21da", "32e0d25d4", "42d9749b7", "60e7329b9", "797e3cc4c", "7bd56f7a3", "7f0e1aac7", "8a40f4b09", "8c67c4cf5", "92972e815", "b417744a7", "c7f462838", "cf44ff5e6", "eb2fa2704"], "source_commits": ["2a03f21da", "7f0e1aac7"], "source_entry_id": "18.6/changes/011", "db_id": "4a55b4d9f252330dd0f0f94102631952", "patch_ids": ["9c4aca692d373e760403997525c9e073", "ea0a783b3715942dc32c661399220cb1"], "statement_hash": "41c4e79daa1ea65508b91d04fa5138fb9c313606a4ceade697072cb89843941f", "relations": [{"rule": 2, "type": "equivalent", "target": "349adc6ad9cc12d1c04aad6e3d659917", "evidence": {"same_day": true, "patch_ids": ["9c4aca692d373e760403997525c9e073", "ea0a783b3715942dc32c661399220cb1"], "statement_hash": "41c4e79daa1ea65508b91d04fa5138fb9c313606a4ceade697072cb89843941f"}}, {"rule": 2, "type": "equivalent", "target": "41c6f110168cdb7324811a04a2654cf2", "evidence": {"same_day": true, "patch_ids": ["9c4aca692d373e760403997525c9e073", "ea0a783b3715942dc32c661399220cb1"], "statement_hash": "41c4e79daa1ea65508b91d04fa5138fb9c313606a4ceade697072cb89843941f"}}, {"rule": 2, "type": "equivalent", "target": "b48c4a1b729ca10627402a86238f5a19", "evidence": {"same_day": true, "patch_ids": ["9c4aca692d373e760403997525c9e073", "ea0a783b3715942dc32c661399220cb1"], "statement_hash": "41c4e79daa1ea65508b91d04fa5138fb9c313606a4ceade697072cb89843941f"}}, {"rule": 2, "type": "equivalent", "target": "bea7e191e30a8a238690f6d536666b13", "evidence": {"same_day": true, "patch_ids": ["9c4aca692d373e760403997525c9e073", "ea0a783b3715942dc32c661399220cb1"], "statement_hash": "41c4e79daa1ea65508b91d04fa5138fb9c313606a4ceade697072cb89843941f"}}]}}, {"id": "18.6-a8d1f97d70d85295", "source_entry_id": "18.6/changes/012", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Reject calls from SQL to functions that take or return type internal", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-ea70ef62a58da283", "source_entry_id": "17.11/changes/012", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Reject calls from SQL to functions that take or return type internal"}], "entry": {"id": "18.6-a8d1f97d70d85295", "cves": ["CVE-2026-14680"], "html": "Reject calls from SQL to functions that take or return type internal (Tom Lane) § §
The existing defenses against doing this have been shown to be insufficient, so add more explicit checks.
\nThe PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-14680)
", "text": "Reject calls from SQL to functions that take or return type internal (Tom Lane) § § The existing defenses against doing this have been shown to be insufficient, so add more explicit checks. The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-14680)", "title": "Reject calls from SQL to functions that take or return type internal", "commits": ["54649de65", "722695db1"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "9fc338e9d48ea9fb35714275ed0d3331db14eb450da43f5cebbd900436553e52", "section_path": ["Changes"], "commit_groups": [["155dacbc5", "21a00de43", "4c0c1b2cd", "54649de65", "8f7e35b08", "e926a9aac", "eb9e55297"], ["1aa601b4f", "21d8cfb18", "722695db1", "7f308dd7c", "83d0a083f", "913fe0c31", "d6e861e19"]], "identity_text": "Reject calls from SQL to functions that take or return type internal (Tom Lane) The existing defenses against doing this have been shown to be insufficient, so add more explicit checks. The PostgreSQL Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-14680)", "commit_aliases": ["155dacbc5", "1aa601b4f", "21a00de43", "21d8cfb18", "4c0c1b2cd", "54649de65", "722695db1", "7f308dd7c", "83d0a083f", "8f7e35b08", "913fe0c31", "d6e861e19", "e926a9aac", "eb9e55297"], "source_commits": ["54649de65", "722695db1"], "source_entry_id": "18.6/changes/012", "db_id": "02bb5a11139923dd7f170a94556495c3", "patch_ids": ["8b623dad3bf883bcb9bd41023fc8f168", "b94f9935e7be4a2be88c49eae8a6ae70"], "statement_hash": "713f97bceae2187dec2f42b397097077fb7eec20b6eddb9a6fb32f8878d44f9f", "relations": [{"rule": 2, "type": "equivalent", "target": "42aa2e3353b4536c48a5271f47f0eb90", "evidence": {"same_day": true, "patch_ids": ["8b623dad3bf883bcb9bd41023fc8f168", "b94f9935e7be4a2be88c49eae8a6ae70"], "statement_hash": "713f97bceae2187dec2f42b397097077fb7eec20b6eddb9a6fb32f8878d44f9f"}}, {"rule": 2, "type": "equivalent", "target": "97ff2029068cd51a1802927b5b54f2d3", "evidence": {"same_day": true, "patch_ids": ["8b623dad3bf883bcb9bd41023fc8f168", "b94f9935e7be4a2be88c49eae8a6ae70"], "statement_hash": "713f97bceae2187dec2f42b397097077fb7eec20b6eddb9a6fb32f8878d44f9f"}}, {"rule": 2, "type": "equivalent", "target": "b56373871b3aaa929aaba36a65e4eb45", "evidence": {"same_day": true, "patch_ids": ["8b623dad3bf883bcb9bd41023fc8f168", "b94f9935e7be4a2be88c49eae8a6ae70"], "statement_hash": "713f97bceae2187dec2f42b397097077fb7eec20b6eddb9a6fb32f8878d44f9f"}}, {"rule": 2, "type": "equivalent", "target": "e54c1abdbc2feb1d5c81f31cc4a073f8", "evidence": {"same_day": true, "patch_ids": ["8b623dad3bf883bcb9bd41023fc8f168", "b94f9935e7be4a2be88c49eae8a6ae70"], "statement_hash": "713f97bceae2187dec2f42b397097077fb7eec20b6eddb9a6fb32f8878d44f9f"}}]}}, {"id": "18.6-c42539c16ee68f2f", "source_entry_id": "18.6/changes/013", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Preserve the ownership of extended statistics objects when they are rebuilt by ALTER TABLE", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-50a00c5a01592c04", "source_entry_id": "17.11/changes/013", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Preserve the ownership of extended statistics objects when they are rebuilt by ALTER TABLE"}], "entry": {"id": "18.6-c42539c16ee68f2f", "cves": ["CVE-2026-6469"], "html": "Preserve the ownership of extended statistics objects when they are rebuilt by ALTER TABLE (Masahiko Sawada) §
Previously, the role running ALTER TABLE gained ownership of such objects, but that seems inappropriate.
The PostgreSQL Project thanks Noah Misch for reporting this problem. (CVE-2026-6469)
", "text": "Preserve the ownership of extended statistics objects when they are rebuilt by ALTER TABLE (Masahiko Sawada) § Previously, the role running ALTER TABLE gained ownership of such objects, but that seems inappropriate. The PostgreSQL Project thanks Noah Misch for reporting this problem. (CVE-2026-6469)", "title": "Preserve the ownership of extended statistics objects when they are rebuilt by ALTER TABLE", "commits": ["a1fa24127"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "24663e30aeab6ad754d8132d106fe4a7a7973900d0381b17c6a730bc4a47640c", "section_path": ["Changes"], "commit_groups": [["6713a6e04", "70a3b4e18", "75a03c569", "7c3367ab5", "93b93f28f", "a1fa24127", "fb6d1ca8d"]], "identity_text": "Preserve the ownership of extended statistics objects when they are rebuilt by ALTER TABLE (Masahiko Sawada) Previously, the role running ALTER TABLE gained ownership of such objects, but that seems inappropriate. The PostgreSQL Project thanks Noah Misch for reporting this problem. (CVE-2026-6469)", "commit_aliases": ["6713a6e04", "70a3b4e18", "75a03c569", "7c3367ab5", "93b93f28f", "a1fa24127", "fb6d1ca8d"], "source_commits": ["a1fa24127"], "source_entry_id": "18.6/changes/013", "db_id": "4ce18d2a1cf23ef6c7ff55c667d59eae", "patch_ids": ["c847f131eaad282f5fa724ff040f1fc2"], "statement_hash": "855872db5602ac9ec63e8c9b362b906eef0f29c2ae3da9a0473220149fc815a6", "relations": [{"rule": 2, "type": "equivalent", "target": "a45d7275fb35413aaeeb017f13dfbf83", "evidence": {"same_day": true, "patch_ids": ["c847f131eaad282f5fa724ff040f1fc2"], "statement_hash": "855872db5602ac9ec63e8c9b362b906eef0f29c2ae3da9a0473220149fc815a6"}}, {"rule": 2, "type": "equivalent", "target": "a511c71fb1c56e7bba21699bf176d02f", "evidence": {"same_day": true, "patch_ids": ["c847f131eaad282f5fa724ff040f1fc2"], "statement_hash": "855872db5602ac9ec63e8c9b362b906eef0f29c2ae3da9a0473220149fc815a6"}}, {"rule": 2, "type": "equivalent", "target": "ddb05610c858789527b1369d30b4bb1c", "evidence": {"same_day": true, "patch_ids": ["c847f131eaad282f5fa724ff040f1fc2"], "statement_hash": "855872db5602ac9ec63e8c9b362b906eef0f29c2ae3da9a0473220149fc815a6"}}, {"rule": 2, "type": "equivalent", "target": "f73abeba4ef827229ec4b724b2dbde1b", "evidence": {"same_day": true, "patch_ids": ["c847f131eaad282f5fa724ff040f1fc2"], "statement_hash": "855872db5602ac9ec63e8c9b362b906eef0f29c2ae3da9a0473220149fc815a6"}}]}}, {"id": "18.6-323a1fc7b03b6859", "source_entry_id": "18.6/changes/014", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "When deparsing an EXTRACT() function call, quote the field name if needed", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-2bafbd49437d6dde", "source_entry_id": "17.11/changes/014", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "When deparsing an EXTRACT() function call, quote the field name if needed"}], "entry": {"id": "18.6-323a1fc7b03b6859", "cves": ["CVE-2026-15741"], "html": "When deparsing an EXTRACT() function call, quote the field name if needed (Nathan Bossart) §
The parser accepts any string literal as a field name in EXTRACT(), deferring validation to execution. If the call is stored and deparsed (for example during pg_dump), the string body was regurgitated verbatim, allowing SQL injection.
The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15741)
", "text": "When deparsing an EXTRACT() function call, quote the field name if needed (Nathan Bossart) § The parser accepts any string literal as a field name in EXTRACT(), deferring validation to execution. If the call is stored and deparsed (for example during pg_dump), the string body was regurgitated verbatim, allowing SQL injection. The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15741)", "title": "When deparsing an EXTRACT() function call, quote the field name if needed", "commits": ["0ddd9098a"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "b0f3b42c30940539f07658c95026fe3f58860d297a362ca19ea132415bd9848d", "section_path": ["Changes"], "commit_groups": [["0ddd9098a", "44ea6764b", "5981fe370", "5e5ea74e3", "967acab87", "a3832a757", "f9729b507"]], "identity_text": "When deparsing an EXTRACT() function call, quote the field name if needed (Nathan Bossart) The parser accepts any string literal as a field name in EXTRACT(), deferring validation to execution. If the call is stored and deparsed (for example during pg_dump), the string body was regurgitated verbatim, allowing SQL injection. The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15741)", "commit_aliases": ["0ddd9098a", "44ea6764b", "5981fe370", "5e5ea74e3", "967acab87", "a3832a757", "f9729b507"], "source_commits": ["0ddd9098a"], "source_entry_id": "18.6/changes/014", "db_id": "57a69063ff0b7f44b253f158536bbc64", "patch_ids": ["f0b1d31c8ffb5349b650b0e3b88706ad"], "statement_hash": "8fb62033eeb6ede7911fce4b990d20a94bf88226d146867552627bcce9f533ef", "relations": [{"rule": 2, "type": "equivalent", "target": "0b6c8ce7fe6e116e2bb99be5e53dff29", "evidence": {"same_day": true, "patch_ids": ["f0b1d31c8ffb5349b650b0e3b88706ad"], "statement_hash": "8fb62033eeb6ede7911fce4b990d20a94bf88226d146867552627bcce9f533ef"}}, {"rule": 2, "type": "equivalent", "target": "46e3e259f29471b862d3a1eeaae97525", "evidence": {"same_day": true, "patch_ids": ["f0b1d31c8ffb5349b650b0e3b88706ad"], "statement_hash": "8fb62033eeb6ede7911fce4b990d20a94bf88226d146867552627bcce9f533ef"}}, {"rule": 2, "type": "equivalent", "target": "7c6c8c33a06891c077c2444b81e229fb", "evidence": {"same_day": true, "patch_ids": ["f0b1d31c8ffb5349b650b0e3b88706ad"], "statement_hash": "8fb62033eeb6ede7911fce4b990d20a94bf88226d146867552627bcce9f533ef"}}, {"rule": 2, "type": "equivalent", "target": "9677e1d0e314b1250191bf908cc27099", "evidence": {"same_day": true, "patch_ids": ["f0b1d31c8ffb5349b650b0e3b88706ad"], "statement_hash": "8fb62033eeb6ede7911fce4b990d20a94bf88226d146867552627bcce9f533ef"}}]}}, {"id": "18.6-0b5cda175039a2c3", "source_entry_id": "18.6/changes/015", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Check for USAGE privilege on data types in places that formerly failed to check that", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-575634f97737603c", "source_entry_id": "17.11/changes/015", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Check for USAGE privilege on data types in places that formerly failed to check that"}], "entry": {"id": "18.6-0b5cda175039a2c3", "cves": ["CVE-2026-6470"], "html": "Check for USAGE privilege on data types in places that formerly failed to check that (Nathan Bossart) § § §
CREATE TYPE AS RANGE did not check, nor did ALTER TABLE OF, nor did commands that create stored expressions. These omissions allowed roles without USAGE privilege to nonetheless create objects depending on the type, possibly blocking the type's owner from changing the type later.
The PostgreSQL Project thanks Jingzhou Fu for reporting this problem. (CVE-2026-6470)
", "text": "Check for USAGE privilege on data types in places that formerly failed to check that (Nathan Bossart) § § § CREATE TYPE AS RANGE did not check, nor did ALTER TABLE OF, nor did commands that create stored expressions. These omissions allowed roles without USAGE privilege to nonetheless create objects depending on the type, possibly blocking the type's owner from changing the type later. The PostgreSQL Project thanks Jingzhou Fu for reporting this problem. (CVE-2026-6470)", "title": "Check for USAGE privilege on data types in places that formerly failed to check that", "commits": ["278053843", "2e91f8548", "57f59ca1d"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "75e3a152860bf6489cdbd50ff6c57c8551e228583eb60e84a8b6068bf59b58c6", "section_path": ["Changes"], "commit_groups": [["1a358b8f2", "278053843", "424fb7160", "4fac4c108", "6dbedd48b", "7ce056b17", "d1c8aa0b0"], ["24855357c", "2e91f8548", "323af0a4e", "97e277402", "a9f6e768a", "efdb26072", "fd6d3e7e9"], ["53ed5ebd8", "57f59ca1d", "671359605", "7a761fe40", "b6e45b4f8", "bb1bc525d", "c062734cd"]], "identity_text": "Check for USAGE privilege on data types in places that formerly failed to check that (Nathan Bossart) CREATE TYPE AS RANGE did not check, nor did ALTER TABLE OF, nor did commands that create stored expressions. These omissions allowed roles without USAGE privilege to nonetheless create objects depending on the type, possibly blocking the type's owner from changing the type later. The PostgreSQL Project thanks Jingzhou Fu for reporting this problem. (CVE-2026-6470)", "commit_aliases": ["1a358b8f2", "24855357c", "278053843", "2e91f8548", "323af0a4e", "424fb7160", "4fac4c108", "53ed5ebd8", "57f59ca1d", "671359605", "6dbedd48b", "7a761fe40", "7ce056b17", "97e277402", "a9f6e768a", "b6e45b4f8", "bb1bc525d", "c062734cd", "d1c8aa0b0", "efdb26072", "fd6d3e7e9"], "source_commits": ["278053843", "2e91f8548", "57f59ca1d"], "source_entry_id": "18.6/changes/015", "db_id": "56232d6e6345f5c09340b72ed581eb4d", "patch_ids": ["2470df146b9201b14de19f772c90d867", "2de75ceea92e216f0b0f3ec035342d7e", "76d1b8b6ad0cee83e43cc4a88d123867"], "statement_hash": "f6ec51b2de1a066951596511e998a5e51ac29a83e3c8e018df4d6e981ebe7068", "relations": [{"rule": 2, "type": "equivalent", "target": "8c93b6ddad829461b98126755a87488f", "evidence": {"same_day": true, "patch_ids": ["2470df146b9201b14de19f772c90d867", "2de75ceea92e216f0b0f3ec035342d7e", "76d1b8b6ad0cee83e43cc4a88d123867"], "statement_hash": "f6ec51b2de1a066951596511e998a5e51ac29a83e3c8e018df4d6e981ebe7068"}}, {"rule": 2, "type": "equivalent", "target": "e50027af5564cb33c0ec80ab0f86e1a9", "evidence": {"same_day": true, "patch_ids": ["2470df146b9201b14de19f772c90d867", "2de75ceea92e216f0b0f3ec035342d7e", "76d1b8b6ad0cee83e43cc4a88d123867"], "statement_hash": "f6ec51b2de1a066951596511e998a5e51ac29a83e3c8e018df4d6e981ebe7068"}}, {"rule": 2, "type": "equivalent", "target": "f2f63cd272a4e4c0c968eacb6779415b", "evidence": {"same_day": true, "patch_ids": ["2470df146b9201b14de19f772c90d867", "2de75ceea92e216f0b0f3ec035342d7e", "76d1b8b6ad0cee83e43cc4a88d123867"], "statement_hash": "f6ec51b2de1a066951596511e998a5e51ac29a83e3c8e018df4d6e981ebe7068"}}, {"rule": 2, "type": "equivalent", "target": "f44708d4a1d626e3b8656335ae598c69", "evidence": {"same_day": true, "patch_ids": ["2470df146b9201b14de19f772c90d867", "2de75ceea92e216f0b0f3ec035342d7e", "76d1b8b6ad0cee83e43cc4a88d123867"], "statement_hash": "f6ec51b2de1a066951596511e998a5e51ac29a83e3c8e018df4d6e981ebe7068"}}]}}, {"id": "18.6-ad01030c7fc964f1", "source_entry_id": "18.6/changes/016", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Invalidate role-dependent cached plans after role changes", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-43977a837123cada", "source_entry_id": "17.11/changes/016", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Invalidate role-dependent cached plans after role changes"}], "entry": {"id": "18.6-ad01030c7fc964f1", "cves": ["CVE-2026-14666"], "html": "Invalidate role-dependent cached plans after role changes (Ilya Staroverov, Shinya Kato, Nathan Bossart) §
\nRole membership, role attribute, and database ownership changes may impact the expected behavior of row-level security policies, but previously we'd continue to use cached plans that were made according to the old state of affairs.
\nThe PostgreSQL Project thanks Ilya Staroverov and Shinya Kato for reporting this problem. (CVE-2026-14666)
", "text": "Invalidate role-dependent cached plans after role changes (Ilya Staroverov, Shinya Kato, Nathan Bossart) § Role membership, role attribute, and database ownership changes may impact the expected behavior of row-level security policies, but previously we'd continue to use cached plans that were made according to the old state of affairs. The PostgreSQL Project thanks Ilya Staroverov and Shinya Kato for reporting this problem. (CVE-2026-14666)", "title": "Invalidate role-dependent cached plans after role changes", "commits": ["0b12f56bf"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "4b0f6546901b6c865183e9d3201d0ebca911407b1403022f7e39db73d6ef8c30", "section_path": ["Changes"], "commit_groups": [["0b12f56bf", "17b6083db", "1974acf23", "567286b76", "f4174aa84", "f5f2da795", "ffca23839"]], "identity_text": "Invalidate role-dependent cached plans after role changes (Ilya Staroverov, Shinya Kato, Nathan Bossart) Role membership, role attribute, and database ownership changes may impact the expected behavior of row-level security policies, but previously we'd continue to use cached plans that were made according to the old state of affairs. The PostgreSQL Project thanks Ilya Staroverov and Shinya Kato for reporting this problem. (CVE-2026-14666)", "commit_aliases": ["0b12f56bf", "17b6083db", "1974acf23", "567286b76", "f4174aa84", "f5f2da795", "ffca23839"], "source_commits": ["0b12f56bf"], "source_entry_id": "18.6/changes/016", "db_id": "0e200ae2afa3db031ffa07314f2deab2", "patch_ids": ["7a5d6580a542a5467ce64bfd9ad2b724"], "statement_hash": "b27f8aace3b388937c6e28c9f1ede652d42059e6b0a2111846c88a4b39769432", "relations": [{"rule": 2, "type": "equivalent", "target": "043b1e2a717a3c7862402faa9c4b1f91", "evidence": {"same_day": true, "patch_ids": ["7a5d6580a542a5467ce64bfd9ad2b724"], "statement_hash": "b27f8aace3b388937c6e28c9f1ede652d42059e6b0a2111846c88a4b39769432"}}, {"rule": 2, "type": "equivalent", "target": "49941507efa272e723ff0698b2236a6e", "evidence": {"same_day": true, "patch_ids": ["7a5d6580a542a5467ce64bfd9ad2b724"], "statement_hash": "b27f8aace3b388937c6e28c9f1ede652d42059e6b0a2111846c88a4b39769432"}}, {"rule": 2, "type": "equivalent", "target": "652fbbbd4aff8c1d5babff0cde01bc7f", "evidence": {"same_day": true, "patch_ids": ["7a5d6580a542a5467ce64bfd9ad2b724"], "statement_hash": "b27f8aace3b388937c6e28c9f1ede652d42059e6b0a2111846c88a4b39769432"}}, {"rule": 2, "type": "equivalent", "target": "c1425f2f64ac014a0d5ac494fbe66faf", "evidence": {"same_day": true, "patch_ids": ["7a5d6580a542a5467ce64bfd9ad2b724"], "statement_hash": "b27f8aace3b388937c6e28c9f1ede652d42059e6b0a2111846c88a4b39769432"}}]}}, {"id": "18.6-ed40b113af1a65e3", "source_entry_id": "18.6/changes/017", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Reject GSSEncRequest after direct SSL connection", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-1d103f53312d0305", "source_entry_id": "17.11/changes/017", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Reject GSSEncRequest after direct SSL connection"}], "entry": {"id": "18.6-ed40b113af1a65e3", "cves": ["CVE-2026-14681"], "html": "Reject GSSEncRequest after direct SSL connection (Michael Paquier) §
\nAfter establishing a TLS-encrypted connection, the server would still accept a request for GSSAPI encryption. If that succeeded, the connection would proceed using TLS encryption, but it would look like a GSS connection to the pg_hba rules. Thus, a pg_hba policy intending to disallow TLS would not be enforced correctly.
The PostgreSQL Project thanks p4p3r for reporting this problem. (CVE-2026-14681)
", "text": "Reject GSSEncRequest after direct SSL connection (Michael Paquier) § After establishing a TLS-encrypted connection, the server would still accept a request for GSSAPI encryption. If that succeeded, the connection would proceed using TLS encryption, but it would look like a GSS connection to the pg_hba rules. Thus, a pg_hba policy intending to disallow TLS would not be enforced correctly. The PostgreSQL Project thanks p4p3r for reporting this problem. (CVE-2026-14681)", "title": "Reject GSSEncRequest after direct SSL connection", "commits": ["203a48209"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "f4e2864baf55c24b865ce6284f997649fdadecb1671b9173a5b147049484bf3f", "section_path": ["Changes"], "commit_groups": [["067a64d40", "203a48209", "3bf185b4b", "bf1bb7e29"]], "identity_text": "Reject GSSEncRequest after direct SSL connection (Michael Paquier) After establishing a TLS-encrypted connection, the server would still accept a request for GSSAPI encryption. If that succeeded, the connection would proceed using TLS encryption, but it would look like a GSS connection to the pg_hba rules. Thus, a pg_hba policy intending to disallow TLS would not be enforced correctly. The PostgreSQL Project thanks p4p3r for reporting this problem. (CVE-2026-14681)", "commit_aliases": ["067a64d40", "203a48209", "3bf185b4b", "bf1bb7e29"], "source_commits": ["203a48209"], "source_entry_id": "18.6/changes/017", "db_id": "deae128594614e84894b8e7a7062759f", "patch_ids": ["0a86d0c924c70e8b47408f823a77a964"], "statement_hash": "f08040a4f6b5dfe94a4b30090677fd13c199828e108149421fa23eaa60d5f620", "relations": [{"rule": 2, "type": "equivalent", "target": "55da165c3ced2d17689a546cd13a10f8", "evidence": {"same_day": true, "patch_ids": ["0a86d0c924c70e8b47408f823a77a964"], "statement_hash": "f08040a4f6b5dfe94a4b30090677fd13c199828e108149421fa23eaa60d5f620"}}, {"rule": 2, "type": "equivalent", "target": "bdd453999af206604b4ae0c623733bc5", "evidence": {"same_day": true, "patch_ids": ["0a86d0c924c70e8b47408f823a77a964"], "statement_hash": "f08040a4f6b5dfe94a4b30090677fd13c199828e108149421fa23eaa60d5f620"}}, {"rule": 2, "type": "equivalent", "target": "efca948aece74421d5dff07ca459356e", "evidence": {"same_day": true, "patch_ids": ["0a86d0c924c70e8b47408f823a77a964"], "statement_hash": "f08040a4f6b5dfe94a4b30090677fd13c199828e108149421fa23eaa60d5f620"}}, {"rule": 2, "type": "equivalent", "target": "fae551c24851f8412783e17b85987136", "evidence": {"same_day": true, "patch_ids": ["0a86d0c924c70e8b47408f823a77a964"], "statement_hash": "f08040a4f6b5dfe94a4b30090677fd13c199828e108149421fa23eaa60d5f620"}}]}}, {"id": "18.6-bb742148aa1ab70a", "source_entry_id": "18.6/changes/018", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Make mock SCRAM authentication secrets more plausible", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-f319d2c2bdee8718", "source_entry_id": "17.11/changes/018", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Make mock SCRAM authentication secrets more plausible"}], "entry": {"id": "18.6-bb742148aa1ab70a", "cves": ["CVE-2026-14672"], "html": "Make mock SCRAM authentication secrets more plausible (Nathan Bossart) §
\nIf a SCRAM login is attempted against a role that doesn't exist or doesn't have a SCRAM secret, we generate a mock secret and carry out the authentication handshake anyway, to avoid revealing these facts to an attacker. But the mock secret was made with a fixed iteration count, which in itself can be an observable response discrepancy. Use the configuration setting scram_iterations instead, to make the mock secret look more like the installation's real secrets.
The PostgreSQL Project thanks Radim Marek for reporting this problem. (CVE-2026-14672)
", "text": "Make mock SCRAM authentication secrets more plausible (Nathan Bossart) § If a SCRAM login is attempted against a role that doesn't exist or doesn't have a SCRAM secret, we generate a mock secret and carry out the authentication handshake anyway, to avoid revealing these facts to an attacker. But the mock secret was made with a fixed iteration count, which in itself can be an observable response discrepancy. Use the configuration setting scram_iterations instead, to make the mock secret look more like the installation's real secrets. The PostgreSQL Project thanks Radim Marek for reporting this problem. (CVE-2026-14672)", "title": "Make mock SCRAM authentication secrets more plausible", "commits": ["822143c4d"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "b6d6fce5b17052a224535f8883fd14426e8400bcc457f265cd697f4f32c9a224", "section_path": ["Changes"], "commit_groups": [["4d192fa16", "822143c4d", "dec60e8ad", "fadbe882d", "feb8b0182"]], "identity_text": "Make mock SCRAM authentication secrets more plausible (Nathan Bossart) If a SCRAM login is attempted against a role that doesn't exist or doesn't have a SCRAM secret, we generate a mock secret and carry out the authentication handshake anyway, to avoid revealing these facts to an attacker. But the mock secret was made with a fixed iteration count, which in itself can be an observable response discrepancy. Use the configuration setting scram_iterations instead, to make the mock secret look more like the installation's real secrets. The PostgreSQL Project thanks Radim Marek for reporting this problem. (CVE-2026-14672)", "commit_aliases": ["4d192fa16", "822143c4d", "dec60e8ad", "fadbe882d", "feb8b0182"], "source_commits": ["822143c4d"], "source_entry_id": "18.6/changes/018", "db_id": "360618cf2b5023ffb07258f47a407319", "patch_ids": ["b915b0f76ef63e3fd030de3a5e4052c7"], "statement_hash": "76daff375fab06e676eed2c7ce655a806a67e546c22e89cce3f2506387c91178", "relations": [{"rule": 2, "type": "equivalent", "target": "0b4b5a7457f7fbba0ac49362d4205d94", "evidence": {"same_day": true, "patch_ids": ["b915b0f76ef63e3fd030de3a5e4052c7"], "statement_hash": "76daff375fab06e676eed2c7ce655a806a67e546c22e89cce3f2506387c91178"}}, {"rule": 2, "type": "equivalent", "target": "328f985aab0b40a393740fb418be993c", "evidence": {"same_day": true, "patch_ids": ["b915b0f76ef63e3fd030de3a5e4052c7"], "statement_hash": "76daff375fab06e676eed2c7ce655a806a67e546c22e89cce3f2506387c91178"}}, {"rule": 2, "type": "equivalent", "target": "465da641b2ad8e32d9b3eff9044cfd21", "evidence": {"same_day": true, "patch_ids": ["b915b0f76ef63e3fd030de3a5e4052c7"], "statement_hash": "76daff375fab06e676eed2c7ce655a806a67e546c22e89cce3f2506387c91178"}}, {"rule": 2, "type": "equivalent", "target": "adc5092861582d88d34f6a1b1124f2eb", "evidence": {"same_day": true, "patch_ids": ["b915b0f76ef63e3fd030de3a5e4052c7"], "statement_hash": "76daff375fab06e676eed2c7ce655a806a67e546c22e89cce3f2506387c91178"}}]}}, {"id": "18.6-2d9ddb6163eca29a", "source_entry_id": "18.6/changes/019", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix out-of-bounds writes in ecpg applications caused by invalid bytea data received from the server", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-368d04431d80a7fd", "source_entry_id": "17.11/changes/019", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix out-of-bounds writes in ecpg applications caused by invalid bytea data received from the server"}], "entry": {"id": "18.6-2d9ddb6163eca29a", "cves": ["CVE-2026-16241"], "html": "Fix out-of-bounds writes in ecpg applications caused by invalid bytea data received from the server (Michael Paquier) §
ecpg assumed without checking that any bytea value must begin with \\x. A broken or malicious server might send a string shorter than 2 bytes, resulting in memory clobber in the application.
The PostgreSQL Project thanks ylwangtju for reporting this problem. (CVE-2026-16241)
", "text": "Fix out-of-bounds writes in ecpg applications caused by invalid bytea data received from the server (Michael Paquier) § ecpg assumed without checking that any bytea value must begin with \\x. A broken or malicious server might send a string shorter than 2 bytes, resulting in memory clobber in the application. The PostgreSQL Project thanks ylwangtju for reporting this problem. (CVE-2026-16241)", "title": "Fix out-of-bounds writes in ecpg applications caused by invalid bytea data received from the server", "commits": ["a14ba29b1"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "bf6d1d41094210cd2ecc127ceb7d2a543ec1b49bae85d8b91a8b744c663c3bbf", "section_path": ["Changes"], "commit_groups": [["39f855e0e", "457b8737a", "5737110b6", "74c59d062", "a14ba29b1", "c3c830272", "c7da85fec"]], "identity_text": "Fix out-of-bounds writes in ecpg applications caused by invalid bytea data received from the server (Michael Paquier) ecpg assumed without checking that any bytea value must begin with \\x. A broken or malicious server might send a string shorter than 2 bytes, resulting in memory clobber in the application. The PostgreSQL Project thanks ylwangtju for reporting this problem. (CVE-2026-16241)", "commit_aliases": ["39f855e0e", "457b8737a", "5737110b6", "74c59d062", "a14ba29b1", "c3c830272", "c7da85fec"], "source_commits": ["a14ba29b1"], "source_entry_id": "18.6/changes/019", "db_id": "c7e226410c72dad9c39b76d880e2f2a5", "patch_ids": ["eda4e515c03b7210bd33a13cc191c754"], "statement_hash": "ef3db74c8b626f19d33ecc7d3b8e292c1e11cd1089b59edbc38f72bd729fe946", "relations": [{"rule": 2, "type": "equivalent", "target": "18aec69fea13406451ddcbd0d4c23a88", "evidence": {"same_day": true, "patch_ids": ["eda4e515c03b7210bd33a13cc191c754"], "statement_hash": "ef3db74c8b626f19d33ecc7d3b8e292c1e11cd1089b59edbc38f72bd729fe946"}}, {"rule": 2, "type": "equivalent", "target": "4fb7c5910a0436ce3e2bb2ab88b25a87", "evidence": {"same_day": true, "patch_ids": ["eda4e515c03b7210bd33a13cc191c754"], "statement_hash": "ef3db74c8b626f19d33ecc7d3b8e292c1e11cd1089b59edbc38f72bd729fe946"}}, {"rule": 2, "type": "equivalent", "target": "7393e9b24b9abe3400e3f04577d58cba", "evidence": {"same_day": true, "patch_ids": ["eda4e515c03b7210bd33a13cc191c754"], "statement_hash": "ef3db74c8b626f19d33ecc7d3b8e292c1e11cd1089b59edbc38f72bd729fe946"}}, {"rule": 2, "type": "equivalent", "target": "f5473f236236eb170503879999034ecc", "evidence": {"same_day": true, "patch_ids": ["eda4e515c03b7210bd33a13cc191c754"], "statement_hash": "ef3db74c8b626f19d33ecc7d3b8e292c1e11cd1089b59edbc38f72bd729fe946"}}]}}, {"id": "18.6-2227ccac7ef5135c", "source_entry_id": "18.6/changes/020", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Do not do backquote expansion on the argument of psql's \\unrestrict command", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-7f417b32587acff8", "source_entry_id": "17.11/changes/020", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Do not do backquote expansion on the argument of psql's \\unrestrict command"}], "entry": {"id": "18.6-2227ccac7ef5135c", "cves": ["CVE-2025-8714", "CVE-2026-18408"], "html": "Do not do backquote expansion on the argument of psql's \\unrestrict command (Nathan Bossart) §
This oversight in the fix for CVE-2025-8714 allows a malicious server to inject shell commands into plain-text dump output that will be run at restore time on the machine running psql, the exact scenario that CVE-2025-8714 intended to prevent.
\nThe PostgreSQL Project thanks Lucas Velgus, Filip Janus, and Daniel Bakker for reporting this problem. (CVE-2026-18408)
", "text": "Do not do backquote expansion on the argument of psql's \\unrestrict command (Nathan Bossart) § This oversight in the fix for CVE-2025-8714 allows a malicious server to inject shell commands into plain-text dump output that will be run at restore time on the machine running psql, the exact scenario that CVE-2025-8714 intended to prevent. The PostgreSQL Project thanks Lucas Velgus, Filip Janus, and Daniel Bakker for reporting this problem. (CVE-2026-18408)", "title": "Do not do backquote expansion on the argument of psql's \\unrestrict command", "commits": ["71ca694c7"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "70f1f2d332357c2ca128a1dfdb521c31951bc150a0902b355418af50095c6552", "section_path": ["Changes"], "commit_groups": [["0119aa30e", "086f6f176", "0bfac9e1f", "2006fca40", "33d0c63fb", "71ca694c7", "df245c374"]], "identity_text": "Do not do backquote expansion on the argument of psql's \\unrestrict command (Nathan Bossart) This oversight in the fix for CVE-2025-8714 allows a malicious server to inject shell commands into plain-text dump output that will be run at restore time on the machine running psql, the exact scenario that CVE-2025-8714 intended to prevent. The PostgreSQL Project thanks Lucas Velgus, Filip Janus, and Daniel Bakker for reporting this problem. (CVE-2026-18408)", "commit_aliases": ["0119aa30e", "086f6f176", "0bfac9e1f", "2006fca40", "33d0c63fb", "71ca694c7", "df245c374"], "source_commits": ["71ca694c7"], "source_entry_id": "18.6/changes/020", "db_id": "36ccc2b6f4b04376dc6bf74ae3d2f6de", "patch_ids": ["061af71132ccdfb4f1bbeed893be595c"], "statement_hash": "3a14df9ccfd7372d3dac771a23f52e41c3376ea71cf1946e2c9e95f97d2b5d3b", "relations": [{"rule": 2, "type": "equivalent", "target": "49dd1006826cb5f529df97b64194c139", "evidence": {"same_day": true, "patch_ids": ["061af71132ccdfb4f1bbeed893be595c"], "statement_hash": "3a14df9ccfd7372d3dac771a23f52e41c3376ea71cf1946e2c9e95f97d2b5d3b"}}, {"rule": 2, "type": "equivalent", "target": "5221242491685338de78e8922e1f353a", "evidence": {"same_day": true, "patch_ids": ["061af71132ccdfb4f1bbeed893be595c"], "statement_hash": "3a14df9ccfd7372d3dac771a23f52e41c3376ea71cf1946e2c9e95f97d2b5d3b"}}, {"rule": 2, "type": "equivalent", "target": "56ffc2f53e9a050b5de71327d3cef06f", "evidence": {"same_day": true, "patch_ids": ["061af71132ccdfb4f1bbeed893be595c"], "statement_hash": "3a14df9ccfd7372d3dac771a23f52e41c3376ea71cf1946e2c9e95f97d2b5d3b"}}, {"rule": 2, "type": "equivalent", "target": "7a747536f32a440151dcb2b04ac4e968", "evidence": {"same_day": true, "patch_ids": ["061af71132ccdfb4f1bbeed893be595c"], "statement_hash": "3a14df9ccfd7372d3dac771a23f52e41c3376ea71cf1946e2c9e95f97d2b5d3b"}}]}}, {"id": "18.6-d40f8de8e21a4c6f", "source_entry_id": "18.6/changes/021", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Remove pg_dump's assumption that pg_proc.protrftypes cannot have more than FUNC_MAX_ARGS entries", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-f6aaa44b60ea5479", "source_entry_id": "17.11/changes/021", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Remove pg_dump's assumption that pg_proc.protrftypes cannot have more than FUNC_MAX_ARGS entries"}], "entry": {"id": "18.6-d40f8de8e21a4c6f", "cves": ["CVE-2026-19385"], "html": "Remove pg_dump's assumption that pg_proc.protrftypes cannot have more than FUNC_MAX_ARGS entries (Tom Lane) §
Since there could be entries for both input and output arguments, it's feasible for this array's length to exceed FUNC_MAX_ARGS (which constrains only input arguments). Even if that were not so, pg_dump cannot assume that the server was built with the same value of FUNC_MAX_ARGS that it has. An overrun would lead to a memory clobber inside pg_dump.
The PostgreSQL Project thanks Masahiko Sawada for reporting this problem. (CVE-2026-19385)
", "text": "Remove pg_dump's assumption that pg_proc.protrftypes cannot have more than FUNC_MAX_ARGS entries (Tom Lane) § Since there could be entries for both input and output arguments, it's feasible for this array's length to exceed FUNC_MAX_ARGS (which constrains only input arguments). Even if that were not so, pg_dump cannot assume that the server was built with the same value of FUNC_MAX_ARGS that it has. An overrun would lead to a memory clobber inside pg_dump. The PostgreSQL Project thanks Masahiko Sawada for reporting this problem. (CVE-2026-19385)", "title": "Remove pg_dump's assumption that pg_proc.protrftypes cannot have more than FUNC_MAX_ARGS entries", "commits": ["3392cce5c"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "94decd765e88345ccbe70faa6e3a61af2c519c0b307c93e6de8a846e22bcba68", "section_path": ["Changes"], "commit_groups": [["13bb73aeb", "3299c2ba0", "3392cce5c", "57aa21f69", "71ba5705d", "86cd82bf4", "c2b16f5d4"]], "identity_text": "Remove pg_dump's assumption that pg_proc.protrftypes cannot have more than FUNC_MAX_ARGS entries (Tom Lane) Since there could be entries for both input and output arguments, it's feasible for this array's length to exceed FUNC_MAX_ARGS (which constrains only input arguments). Even if that were not so, pg_dump cannot assume that the server was built with the same value of FUNC_MAX_ARGS that it has. An overrun would lead to a memory clobber inside pg_dump. The PostgreSQL Project thanks Masahiko Sawada for reporting this problem. (CVE-2026-19385)", "commit_aliases": ["13bb73aeb", "3299c2ba0", "3392cce5c", "57aa21f69", "71ba5705d", "86cd82bf4", "c2b16f5d4"], "source_commits": ["3392cce5c"], "source_entry_id": "18.6/changes/021", "db_id": "f91d32a8c03492afba6d7ba835690a32", "patch_ids": ["185500373cc27d3d610be991561eb522"], "statement_hash": "0503fb690855a4bf21f955b8b62af71583c422a4e69c4c228faea1f3e3f8b84b", "relations": [{"rule": 2, "type": "equivalent", "target": "5183659937548a24721c52721ce5656b", "evidence": {"same_day": true, "patch_ids": ["185500373cc27d3d610be991561eb522"], "statement_hash": "0503fb690855a4bf21f955b8b62af71583c422a4e69c4c228faea1f3e3f8b84b"}}, {"rule": 2, "type": "equivalent", "target": "63fc39b2fe0a2553fb195650ae6915cb", "evidence": {"same_day": true, "patch_ids": ["185500373cc27d3d610be991561eb522"], "statement_hash": "0503fb690855a4bf21f955b8b62af71583c422a4e69c4c228faea1f3e3f8b84b"}}, {"rule": 2, "type": "equivalent", "target": "6a0f92cad4fbbfe88adb2be733310a9b", "evidence": {"same_day": true, "patch_ids": ["185500373cc27d3d610be991561eb522"], "statement_hash": "0503fb690855a4bf21f955b8b62af71583c422a4e69c4c228faea1f3e3f8b84b"}}, {"rule": 2, "type": "equivalent", "target": "dce6c62e738d4e4801ee4cb45757968f", "evidence": {"same_day": true, "patch_ids": ["185500373cc27d3d610be991561eb522"], "statement_hash": "0503fb690855a4bf21f955b8b62af71583c422a4e69c4c228faea1f3e3f8b84b"}}]}}, {"id": "18.6-6d183d795dd4fadd", "source_entry_id": "18.6/changes/022", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Harden PL/Perl against “tied” Perl arrays and hashes", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-58243a045a5d2555", "source_entry_id": "17.11/changes/022", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Harden PL/Perl against “tied” Perl arrays and hashes"}], "entry": {"id": "18.6-6d183d795dd4fadd", "cves": ["CVE-2026-14670"], "html": "Harden PL/Perl against “tied” Perl arrays and hashes (Tom Lane) §
\nA tied object that doesn't behave like a regular one could lead to memory overwrite, or to constructing a corrupt result array (which would likely cause problems later).
\nThe PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14670)
", "text": "Harden PL/Perl against “tied” Perl arrays and hashes (Tom Lane) § A tied object that doesn't behave like a regular one could lead to memory overwrite, or to constructing a corrupt result array (which would likely cause problems later). The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14670)", "title": "Harden PL/Perl against “tied” Perl arrays and hashes", "commits": ["87c4b8219"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "10b1106372761b89d406fd05bbb2541ae14a0d97192d90e5f7a2298a11c3e1c0", "section_path": ["Changes"], "commit_groups": [["2d78c34f8", "477a6bdb0", "63cb15f40", "87c4b8219", "8c48cd615", "cf4ae7c3b", "d7fcfead3"]], "identity_text": "Harden PL/Perl against tied Perl arrays and hashes (Tom Lane) A tied object that doesn't behave like a regular one could lead to memory overwrite, or to constructing a corrupt result array (which would likely cause problems later). The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14670)", "commit_aliases": ["2d78c34f8", "477a6bdb0", "63cb15f40", "87c4b8219", "8c48cd615", "cf4ae7c3b", "d7fcfead3"], "source_commits": ["87c4b8219"], "source_entry_id": "18.6/changes/022", "db_id": "45822fd5bc04f9bc7cd5310ebd922c61", "patch_ids": ["5749c355b8bd5a5f2a0f8679d48902f9"], "statement_hash": "e681b36f925829491afb4aaf1536bea68f7b5021f6e0ea3fdb126ffd69367fa0", "relations": [{"rule": 2, "type": "equivalent", "target": "0caaa5502645631a657b97dc78add8c0", "evidence": {"same_day": true, "patch_ids": ["5749c355b8bd5a5f2a0f8679d48902f9"], "statement_hash": "e681b36f925829491afb4aaf1536bea68f7b5021f6e0ea3fdb126ffd69367fa0"}}, {"rule": 2, "type": "equivalent", "target": "59a40e9cc2306d6e115d10b26c7b6d9e", "evidence": {"same_day": true, "patch_ids": ["5749c355b8bd5a5f2a0f8679d48902f9"], "statement_hash": "e681b36f925829491afb4aaf1536bea68f7b5021f6e0ea3fdb126ffd69367fa0"}}, {"rule": 2, "type": "equivalent", "target": "bd87bdc33bbf3c2a24631a385372b6ad", "evidence": {"same_day": true, "patch_ids": ["5749c355b8bd5a5f2a0f8679d48902f9"], "statement_hash": "e681b36f925829491afb4aaf1536bea68f7b5021f6e0ea3fdb126ffd69367fa0"}}, {"rule": 2, "type": "equivalent", "target": "f0c1fefb4fd60b97ad1a6420db84a85a", "evidence": {"same_day": true, "patch_ids": ["5749c355b8bd5a5f2a0f8679d48902f9"], "statement_hash": "e681b36f925829491afb4aaf1536bea68f7b5021f6e0ea3fdb126ffd69367fa0"}}]}}, {"id": "18.6-16cede7597f41368", "source_entry_id": "18.6/changes/023", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix integer overflows in memory-allocation calculations in PL/Perl and PL/Tcl", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-7026dc1b76714418", "source_entry_id": "17.11/changes/023", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix integer overflows in memory-allocation calculations in PL/Perl and PL/Tcl"}], "entry": {"id": "18.6-16cede7597f41368", "cves": ["CVE-2026-14677", "CVE-2026-6473"], "html": "Fix integer overflows in memory-allocation calculations in PL/Perl and PL/Tcl (Heikki Linnakangas) §
\nThis is the same type of problem as CVE-2026-6473, just in a different part of the code, and is fixed in the same way.
\nThe PostgreSQL Project thanks the Tulya Project (Team Dhiutsa, Bitecope Technologies Private Ltd) for reporting this problem. (CVE-2026-14677)
", "text": "Fix integer overflows in memory-allocation calculations in PL/Perl and PL/Tcl (Heikki Linnakangas) § This is the same type of problem as CVE-2026-6473, just in a different part of the code, and is fixed in the same way. The PostgreSQL Project thanks the Tulya Project (Team Dhiutsa, Bitecope Technologies Private Ltd) for reporting this problem. (CVE-2026-14677)", "title": "Fix integer overflows in memory-allocation calculations in PL/Perl and PL/Tcl", "commits": ["028ee716a"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "852c6f91848bf90946172edfb621354ea11883c45a93972557c73aaea1ec39d2", "section_path": ["Changes"], "commit_groups": [["028ee716a", "1eb0d5380", "776467301", "8bbdc0540", "a1c1727cb", "aff9dac1c", "b56cc7deb"]], "identity_text": "Fix integer overflows in memory-allocation calculations in PL/Perl and PL/Tcl (Heikki Linnakangas) This is the same type of problem as CVE-2026-6473, just in a different part of the code, and is fixed in the same way. The PostgreSQL Project thanks the Tulya Project (Team Dhiutsa, Bitecope Technologies Private Ltd) for reporting this problem. (CVE-2026-14677)", "commit_aliases": ["028ee716a", "1eb0d5380", "776467301", "8bbdc0540", "a1c1727cb", "aff9dac1c", "b56cc7deb"], "source_commits": ["028ee716a"], "source_entry_id": "18.6/changes/023", "db_id": "238a2ce678961ff0ad08154da3915f04", "patch_ids": ["551a41f04d69f180135194c24f4907fb"], "statement_hash": "b56f55f83d652a2d7354185c8891454536092c27a727aecc0b21ea91949626f4", "relations": [{"rule": 2, "type": "equivalent", "target": "4cc223998ff4d5b7cf50efd21e2284b1", "evidence": {"same_day": true, "patch_ids": ["551a41f04d69f180135194c24f4907fb"], "statement_hash": "b56f55f83d652a2d7354185c8891454536092c27a727aecc0b21ea91949626f4"}}, {"rule": 2, "type": "equivalent", "target": "a110c06ad7fd7a9c4f063b051daf6836", "evidence": {"same_day": true, "patch_ids": ["551a41f04d69f180135194c24f4907fb"], "statement_hash": "b56f55f83d652a2d7354185c8891454536092c27a727aecc0b21ea91949626f4"}}, {"rule": 2, "type": "equivalent", "target": "eaeb89e4752f46002fc91e3a83e9f683", "evidence": {"same_day": true, "patch_ids": ["551a41f04d69f180135194c24f4907fb"], "statement_hash": "b56f55f83d652a2d7354185c8891454536092c27a727aecc0b21ea91949626f4"}}, {"rule": 2, "type": "equivalent", "target": "f5ff50e89bc960e1e5bac3249477b995", "evidence": {"same_day": true, "patch_ids": ["551a41f04d69f180135194c24f4907fb"], "statement_hash": "b56f55f83d652a2d7354185c8891454536092c27a727aecc0b21ea91949626f4"}}]}}, {"id": "18.6-64ea1ee53902ffcc", "source_entry_id": "18.6/changes/024", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Ensure that contrib/amcheck functions restrict search_path before executing index expressions", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-ee34ba8ba8f4fa3d", "source_entry_id": "17.11/changes/024", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Ensure that contrib/amcheck functions restrict search_path before executing index expressions"}], "entry": {"id": "18.6-64ea1ee53902ffcc", "cves": ["CVE-2026-14673"], "html": "Ensure that contrib/amcheck functions restrict search_path before executing index expressions (Noah Misch) §
Because amcheck will run such index expressions as the owner of their tables, a caller could potentially hijack search_path-dependent functions to run arbitrary code as the table owner. By default this is not a vulnerability because only superusers are allowed to call amcheck functions; but if that privilege was granted out, it created a larger hazard than the documentation suggests.
The PostgreSQL Project thanks Yuelin Wang and Jacob Brazeal for reporting this problem. (CVE-2026-14673)
", "text": "Ensure that contrib/amcheck functions restrict search_path before executing index expressions (Noah Misch) § Because amcheck will run such index expressions as the owner of their tables, a caller could potentially hijack search_path-dependent functions to run arbitrary code as the table owner. By default this is not a vulnerability because only superusers are allowed to call amcheck functions; but if that privilege was granted out, it created a larger hazard than the documentation suggests. The PostgreSQL Project thanks Yuelin Wang and Jacob Brazeal for reporting this problem. (CVE-2026-14673)", "title": "Ensure that contrib/amcheck functions restrict search_path before executing index expressions", "commits": ["0a61fcde0"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "7ba5e2ae5e38ee0207d070213a63610b01797ed2acef9003492c19568e51fdd1", "section_path": ["Changes"], "commit_groups": [["0a61fcde0", "0fbf785b1", "2cc147318", "39d792040", "557cc7186", "e41c72aff", "e43e74756"]], "identity_text": "Ensure that contrib/amcheck functions restrict search_path before executing index expressions (Noah Misch) Because amcheck will run such index expressions as the owner of their tables, a caller could potentially hijack search_path-dependent functions to run arbitrary code as the table owner. By default this is not a vulnerability because only superusers are allowed to call amcheck functions; but if that privilege was granted out, it created a larger hazard than the documentation suggests. The PostgreSQL Project thanks Yuelin Wang and Jacob Brazeal for reporting this problem. (CVE-2026-14673)", "commit_aliases": ["0a61fcde0", "0fbf785b1", "2cc147318", "39d792040", "557cc7186", "e41c72aff", "e43e74756"], "source_commits": ["0a61fcde0"], "source_entry_id": "18.6/changes/024", "db_id": "cb5c4637df879fb88877a760ee0058f9", "patch_ids": ["5c909624ee89c6ad2350bdeebaf3e414"], "statement_hash": "659077ecd2d4227788959afddf19d4e415449e3189a19ba0beb867937958bff6", "relations": [{"rule": 2, "type": "equivalent", "target": "2c238928eeda3326738ac133c3580936", "evidence": {"same_day": true, "patch_ids": ["5c909624ee89c6ad2350bdeebaf3e414"], "statement_hash": "659077ecd2d4227788959afddf19d4e415449e3189a19ba0beb867937958bff6"}}, {"rule": 2, "type": "equivalent", "target": "465e8cabac386aa937b2b97c990e0a0f", "evidence": {"same_day": true, "patch_ids": ["5c909624ee89c6ad2350bdeebaf3e414"], "statement_hash": "659077ecd2d4227788959afddf19d4e415449e3189a19ba0beb867937958bff6"}}, {"rule": 2, "type": "equivalent", "target": "9ef4dc62946cbc0407d82f3a9b826f0e", "evidence": {"same_day": true, "patch_ids": ["5c909624ee89c6ad2350bdeebaf3e414"], "statement_hash": "659077ecd2d4227788959afddf19d4e415449e3189a19ba0beb867937958bff6"}}, {"rule": 2, "type": "equivalent", "target": "c016d6a0f320dafa02d0585b20842685", "evidence": {"same_day": true, "patch_ids": ["5c909624ee89c6ad2350bdeebaf3e414"], "statement_hash": "659077ecd2d4227788959afddf19d4e415449e3189a19ba0beb867937958bff6"}}]}}, {"id": "18.6-9f4c551d8e885121", "source_entry_id": "18.6/changes/025", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix integer overflows in contrib/fuzzystrmatch's levenshtein() and levenshtein_less_equal() functions", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-8ee281616fb9fd49", "source_entry_id": "17.11/changes/025", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix integer overflows in contrib/fuzzystrmatch's levenshtein() and levenshtein_less_equal() functions"}], "entry": {"id": "18.6-9f4c551d8e885121", "cves": ["CVE-2026-15742"], "html": "Fix integer overflows in contrib/fuzzystrmatch's levenshtein() and levenshtein_less_equal() functions (Nathan Bossart) §
Passing large cost values to these functions could cause integer overflows, thereby producing nonsensical results, and even causing out-of-bounds writes in some cases.
\nThe PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15742)
", "text": "Fix integer overflows in contrib/fuzzystrmatch's levenshtein() and levenshtein_less_equal() functions (Nathan Bossart) § Passing large cost values to these functions could cause integer overflows, thereby producing nonsensical results, and even causing out-of-bounds writes in some cases. The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15742)", "title": "Fix integer overflows in contrib/fuzzystrmatch's levenshtein() and levenshtein_less_equal() functions", "commits": ["e88eb4e76"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "96c67bb1a9ef0c2604ab626734f8e8097c1f3ebea23560d09c5afbd92e7f9683", "section_path": ["Changes"], "commit_groups": [["61481aa0e", "62c31b490", "74916136f", "918683d12", "9505175f2", "c4d51b627", "e88eb4e76"]], "identity_text": "Fix integer overflows in contrib/fuzzystrmatch's levenshtein() and levenshtein_less_equal() functions (Nathan Bossart) Passing large cost values to these functions could cause integer overflows, thereby producing nonsensical results, and even causing out-of-bounds writes in some cases. The PostgreSQL Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15742)", "commit_aliases": ["61481aa0e", "62c31b490", "74916136f", "918683d12", "9505175f2", "c4d51b627", "e88eb4e76"], "source_commits": ["e88eb4e76"], "source_entry_id": "18.6/changes/025", "db_id": "1e5eda106e8fd11472d74f91bffc2ff0", "patch_ids": ["b6a4ec5efdc01505934fe024a8a4270f"], "statement_hash": "f6379cf73e457381cf432fa9add17bfe91f2d96391011c3fe8081ecbbd13eff5", "relations": [{"rule": 2, "type": "equivalent", "target": "24d49d08ad8dddbb2e9b85283621ee67", "evidence": {"same_day": true, "patch_ids": ["b6a4ec5efdc01505934fe024a8a4270f"], "statement_hash": "f6379cf73e457381cf432fa9add17bfe91f2d96391011c3fe8081ecbbd13eff5"}}, {"rule": 2, "type": "equivalent", "target": "6cca8c3102c334bca04243a3114f48fe", "evidence": {"same_day": true, "patch_ids": ["b6a4ec5efdc01505934fe024a8a4270f"], "statement_hash": "f6379cf73e457381cf432fa9add17bfe91f2d96391011c3fe8081ecbbd13eff5"}}, {"rule": 2, "type": "equivalent", "target": "bc23bdcfa3cae705ffa99474b3b97aae", "evidence": {"same_day": true, "patch_ids": ["b6a4ec5efdc01505934fe024a8a4270f"], "statement_hash": "f6379cf73e457381cf432fa9add17bfe91f2d96391011c3fe8081ecbbd13eff5"}}, {"rule": 2, "type": "equivalent", "target": "f41b59ba5bf8ae6184895fe8e7bb8dc1", "evidence": {"same_day": true, "patch_ids": ["b6a4ec5efdc01505934fe024a8a4270f"], "statement_hash": "f6379cf73e457381cf432fa9add17bfe91f2d96391011c3fe8081ecbbd13eff5"}}]}}, {"id": "18.6-c2bc95cc72b98750", "source_entry_id": "18.6/changes/026", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix buffer overrun in contrib/pg_stat_statements", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-881f882c67a9948d", "source_entry_id": "17.11/changes/026", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix buffer overrun in contrib/pg_stat_statements"}], "entry": {"id": "18.6-c2bc95cc72b98750", "cves": ["CVE-2026-14676"], "html": "Fix buffer overrun in contrib/pg_stat_statements (Álvaro Herrera) §
Query normalization didn't accurately account for the amount of space the normalized string would require.
\nThe PostgreSQL Project thanks Sajeeb Lohani (with TrendAI Zero Day Initiative) and Yuelin Wang for reporting this problem. (CVE-2026-14676)
", "text": "Fix buffer overrun in contrib/pg_stat_statements (Álvaro Herrera) § Query normalization didn't accurately account for the amount of space the normalized string would require. The PostgreSQL Project thanks Sajeeb Lohani (with TrendAI Zero Day Initiative) and Yuelin Wang for reporting this problem. (CVE-2026-14676)", "title": "Fix buffer overrun in contrib/pg_stat_statements", "commits": ["8a31ffc2d"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "d2635f488ff4a3302586cb71fa7ddad74aeebf54da30c6109e0319f3e53df0e9", "section_path": ["Changes"], "commit_groups": [["1e2795dde", "8a31ffc2d", "bb02eba53"]], "identity_text": "Fix buffer overrun in contrib/pg_stat_statements (Álvaro Herrera) Query normalization didn't accurately account for the amount of space the normalized string would require. The PostgreSQL Project thanks Sajeeb Lohani (with TrendAI Zero Day Initiative) and Yuelin Wang for reporting this problem. (CVE-2026-14676)", "commit_aliases": ["1e2795dde", "8a31ffc2d", "bb02eba53"], "source_commits": ["8a31ffc2d"], "source_entry_id": "18.6/changes/026", "db_id": "e84c1b71b1c15bae4e222a2f72d84864", "patch_ids": ["ff92e3cbebc5005b0bef45f9f1d8d30a"], "statement_hash": "9ccd331655eef445554d4bf3ba5a781e3ca80ec62b9fce48b4cf6f7177789b22", "relations": [{"rule": 2, "type": "equivalent", "target": "29895bb80ed2951a21b387b1a32fd0bf", "evidence": {"same_day": true, "patch_ids": ["ff92e3cbebc5005b0bef45f9f1d8d30a"], "statement_hash": "9ccd331655eef445554d4bf3ba5a781e3ca80ec62b9fce48b4cf6f7177789b22"}}, {"rule": 2, "type": "equivalent", "target": "aaa4509a01eb087a7c8dae3d3477599b", "evidence": {"same_day": true, "patch_ids": ["ff92e3cbebc5005b0bef45f9f1d8d30a"], "statement_hash": "9ccd331655eef445554d4bf3ba5a781e3ca80ec62b9fce48b4cf6f7177789b22"}}, {"rule": 2, "type": "equivalent", "target": "d7011cf7f02dec0d6f5320d50f1060d7", "evidence": {"same_day": true, "patch_ids": ["ff92e3cbebc5005b0bef45f9f1d8d30a"], "statement_hash": "9ccd331655eef445554d4bf3ba5a781e3ca80ec62b9fce48b4cf6f7177789b22"}}, {"rule": 2, "type": "equivalent", "target": "d8f3c95effa66c9d7648ed329303a70e", "evidence": {"same_day": true, "patch_ids": ["ff92e3cbebc5005b0bef45f9f1d8d30a"], "statement_hash": "9ccd331655eef445554d4bf3ba5a781e3ca80ec62b9fce48b4cf6f7177789b22"}}]}}, {"id": "18.6-b960de4f8267096f", "source_entry_id": "18.6/changes/027", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix datatype error in contrib/pg_trgm's GiST picksplit function", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-caca197ce0ba4b3f", "source_entry_id": "17.11/changes/027", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix datatype error in contrib/pg_trgm's GiST picksplit function"}], "entry": {"id": "18.6-b960de4f8267096f", "cves": ["CVE-2026-14678"], "html": "Fix datatype error in contrib/pg_trgm's GiST picksplit function (Heikki Linnakangas) §
This mistake resulted in reading past the end of the buffer, typically causing bad split decisions; but a crash could ensue if you're very unlucky.
\nThe PostgreSQL Project thanks Mehmet D. Ince for reporting this problem. (CVE-2026-14678)
", "text": "Fix datatype error in contrib/pg_trgm's GiST picksplit function (Heikki Linnakangas) § This mistake resulted in reading past the end of the buffer, typically causing bad split decisions; but a crash could ensue if you're very unlucky. The PostgreSQL Project thanks Mehmet D. Ince for reporting this problem. (CVE-2026-14678)", "title": "Fix datatype error in contrib/pg_trgm's GiST picksplit function", "commits": ["849019a50"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "80d67ce760ed68d00013270c286690f7d0aa6dd3ecd75d390bacd9e741c74117", "section_path": ["Changes"], "commit_groups": [["1af08af69", "24c88cd39", "66c2dbb20", "849019a50", "a74aa0854", "aa7b5815e", "c7c82a88c"]], "identity_text": "Fix datatype error in contrib/pg_trgm's GiST picksplit function (Heikki Linnakangas) This mistake resulted in reading past the end of the buffer, typically causing bad split decisions; but a crash could ensue if you're very unlucky. The PostgreSQL Project thanks Mehmet D. Ince for reporting this problem. (CVE-2026-14678)", "commit_aliases": ["1af08af69", "24c88cd39", "66c2dbb20", "849019a50", "a74aa0854", "aa7b5815e", "c7c82a88c"], "source_commits": ["849019a50"], "source_entry_id": "18.6/changes/027", "db_id": "0bc10887e786dd035f4571e42ea848b8", "patch_ids": ["e6003b6617841df26303992ba1215f03"], "statement_hash": "b75b9d4c297e71b80fedfe6eeb16417da2cd09f4baa7f5d2b7d3f4d2495f3474", "relations": [{"rule": 2, "type": "equivalent", "target": "007e7b20002c9154a7b78500dad11fde", "evidence": {"same_day": true, "patch_ids": ["e6003b6617841df26303992ba1215f03"], "statement_hash": "b75b9d4c297e71b80fedfe6eeb16417da2cd09f4baa7f5d2b7d3f4d2495f3474"}}, {"rule": 2, "type": "equivalent", "target": "1dcffcddaa3ea6a57ebf8bf560e8c531", "evidence": {"same_day": true, "patch_ids": ["e6003b6617841df26303992ba1215f03"], "statement_hash": "b75b9d4c297e71b80fedfe6eeb16417da2cd09f4baa7f5d2b7d3f4d2495f3474"}}, {"rule": 2, "type": "equivalent", "target": "b9b08968a5deb7a55558cd0e3c3ecb91", "evidence": {"same_day": true, "patch_ids": ["e6003b6617841df26303992ba1215f03"], "statement_hash": "b75b9d4c297e71b80fedfe6eeb16417da2cd09f4baa7f5d2b7d3f4d2495f3474"}}, {"rule": 2, "type": "equivalent", "target": "c1b223f3527ab1382981f7ea6931f7ec", "evidence": {"same_day": true, "patch_ids": ["e6003b6617841df26303992ba1215f03"], "statement_hash": "b75b9d4c297e71b80fedfe6eeb16417da2cd09f4baa7f5d2b7d3f4d2495f3474"}}]}}, {"id": "18.6-2fe39251a9e1874e", "source_entry_id": "18.6/changes/028", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Remove the plan cache in contrib/refint", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-9677b8014f265a17", "source_entry_id": "17.11/changes/028", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Remove the plan cache in contrib/refint"}], "entry": {"id": "18.6-2fe39251a9e1874e", "cves": ["CVE-2026-14671"], "html": "Remove the plan cache in contrib/refint (Ayush Tiwari) §
This caching behavior has several serious bugs, notably that check_foreign_key() embeds the new key values in its cascade-UPDATE queries, so a cached plan reuses the originally-needed values rather than the key values that should be used. The simplest solution is to remove it.
The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14671)
", "text": "Remove the plan cache in contrib/refint (Ayush Tiwari) § This caching behavior has several serious bugs, notably that check_foreign_key() embeds the new key values in its cascade-UPDATE queries, so a cached plan reuses the originally-needed values rather than the key values that should be used. The simplest solution is to remove it. The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14671)", "title": "Remove the plan cache in contrib/refint", "commits": ["79a506228"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "6e1519ab2f6327b36adc78242481530b3c30efd3dfa202b0fc360b4be1b6fa31", "section_path": ["Changes"], "commit_groups": [["1fbe2066d", "5b72d0279", "66a5146dc", "79a506228", "a572dd213", "b7b513d9a"]], "identity_text": "Remove the plan cache in contrib/refint (Ayush Tiwari) This caching behavior has several serious bugs, notably that check_foreign_key() embeds the new key values in its cascade-UPDATE queries, so a cached plan reuses the originally-needed values rather than the key values that should be used. The simplest solution is to remove it. The PostgreSQL Project thanks Hcamael for reporting this problem. (CVE-2026-14671)", "commit_aliases": ["1fbe2066d", "5b72d0279", "66a5146dc", "79a506228", "a572dd213", "b7b513d9a"], "source_commits": ["79a506228"], "source_entry_id": "18.6/changes/028", "db_id": "139a1ada6baf2bae757b6a1a97ee7f41", "patch_ids": ["1a32666836cb434aea5b3cbd8282c9f7"], "statement_hash": "b8e6fe77ce440b33c793882e33b84a13458e57df19432239a74f731dbb6496f9", "relations": [{"rule": 2, "type": "equivalent", "target": "0edf0fe6be4ddcafd5c7d27addaa918f", "evidence": {"same_day": true, "patch_ids": ["1a32666836cb434aea5b3cbd8282c9f7"], "statement_hash": "b8e6fe77ce440b33c793882e33b84a13458e57df19432239a74f731dbb6496f9"}}, {"rule": 2, "type": "equivalent", "target": "7dbe14e2bbf06d93dd90088eae989b60", "evidence": {"same_day": true, "patch_ids": ["1a32666836cb434aea5b3cbd8282c9f7"], "statement_hash": "b8e6fe77ce440b33c793882e33b84a13458e57df19432239a74f731dbb6496f9"}}, {"rule": 2, "type": "equivalent", "target": "aca3bdc694388071f82dcc5eb7deb70d", "evidence": {"same_day": true, "patch_ids": ["1a32666836cb434aea5b3cbd8282c9f7"], "statement_hash": "b8e6fe77ce440b33c793882e33b84a13458e57df19432239a74f731dbb6496f9"}}, {"rule": 2, "type": "equivalent", "target": "ddbe7d30f92efca35dca583745e7a91a", "evidence": {"same_day": true, "patch_ids": ["1a32666836cb434aea5b3cbd8282c9f7"], "statement_hash": "b8e6fe77ce440b33c793882e33b84a13458e57df19432239a74f731dbb6496f9"}}]}}, {"id": "18.6-ac95828b13f18d05", "source_entry_id": "18.6/changes/030", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix mis-handling of asynchronous reads when rescanning an asynchronous Append plan node", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-3e22bb5ab29aa62e", "source_entry_id": "17.11/changes/029", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix mis-handling of asynchronous reads when rescanning an asynchronous Append plan node"}], "entry": {"id": "18.6-ac95828b13f18d05", "cves": [], "html": "Fix mis-handling of asynchronous reads when rescanning an asynchronous Append plan node (Alexander Korotkov, Gleb Kashkin, Etsuro Fujita) §
\nWhen an upper plan node rescans an Append before having read the entire Append output, we need to discard any in-flight requests sent to external servers (by postgres_fdw for example). This was not done correctly in cases where a subplan has parameter changes or is discarded by partition pruning in the next scan. The outcome could be incorrect query results, an infinite loop, or an assertion failure.
Fix error in partition pruning for RANGE-partitioned tables (David Rowley) §
\nIn some cases the DEFAULT partition would be skipped when it should not be, which could lead to rows missing from query results.
", "text": "Fix error in partition pruning for RANGE-partitioned tables (David Rowley) § In some cases the DEFAULT partition would be skipped when it should not be, which could lead to rows missing from query results.", "title": "Fix error in partition pruning for RANGE-partitioned tables", "commits": ["02e69be47"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "3e9800e0665c2e72616be8e9d68eb5b862ff71271140f5fba3d9feac638d1de7", "section_path": ["Changes"], "commit_groups": [["02e69be47", "31f2acde5", "5190732c9", "6098f35f4", "709dfd27f", "9a0cd8e73", "f9282a650"]], "identity_text": "Fix error in partition pruning for RANGE-partitioned tables (David Rowley) In some cases the DEFAULT partition would be skipped when it should not be, which could lead to rows missing from query results.", "commit_aliases": ["02e69be47", "31f2acde5", "5190732c9", "6098f35f4", "709dfd27f", "9a0cd8e73", "f9282a650"], "source_commits": ["02e69be47"], "source_entry_id": "18.6/changes/031", "db_id": "128f5b0ef464d5fb3f9f8de9b62b5b0c", "patch_ids": ["07f80c898c23577b927785baf5699ba6"], "statement_hash": "e3e0e32dc70a802e15316cd723301dfb9165a361cfaaa3eaebb6138320570c23", "relations": [{"rule": 2, "type": "equivalent", "target": "199c05dd5ca242a1207113d841920d91", "evidence": {"same_day": true, "patch_ids": ["07f80c898c23577b927785baf5699ba6"], "statement_hash": "e3e0e32dc70a802e15316cd723301dfb9165a361cfaaa3eaebb6138320570c23"}}, {"rule": 2, "type": "equivalent", "target": "8e616a25980e478e4ba1d40fd43361c9", "evidence": {"same_day": true, "patch_ids": ["07f80c898c23577b927785baf5699ba6"], "statement_hash": "e3e0e32dc70a802e15316cd723301dfb9165a361cfaaa3eaebb6138320570c23"}}, {"rule": 2, "type": "equivalent", "target": "b1408f66d7e290909c80f8c2b9d6a6e6", "evidence": {"same_day": true, "patch_ids": ["07f80c898c23577b927785baf5699ba6"], "statement_hash": "e3e0e32dc70a802e15316cd723301dfb9165a361cfaaa3eaebb6138320570c23"}}, {"rule": 2, "type": "equivalent", "target": "c03487e8eed72def14469f629495faba", "evidence": {"same_day": true, "patch_ids": ["07f80c898c23577b927785baf5699ba6"], "statement_hash": "e3e0e32dc70a802e15316cd723301dfb9165a361cfaaa3eaebb6138320570c23"}}]}}, {"id": "18.6-7f07d942a2dc7fb3", "source_entry_id": "18.6/changes/036", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix planner's nullability and strictness checks for value IN (array) expressions", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-0179d9549f7c629e", "source_entry_id": "17.11/changes/031", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix planner's nullability and strictness checks for value IN (array) expressions"}], "entry": {"id": "18.6-7f07d942a2dc7fb3", "cves": [], "html": "Fix planner's nullability and strictness checks for value IN (array)
These checks should only succeed if the array operand is known to be non-empty, but that consideration was missed, allowing optimizations to be applied that should not be. This could result in wrong query answers if the array actually was empty.
", "text": "Fix planner's nullability and strictness checks for value IN (array) expressions (Ayush Tiwari) § These checks should only succeed if the array operand is known to be non-empty, but that consideration was missed, allowing optimizations to be applied that should not be. This could result in wrong query answers if the array actually was empty.", "title": "Fix planner's nullability and strictness checks for value IN (array) expressions", "commits": ["277122036"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "59acbe1e0d72123c284eb75137c993aa778cc3317be6c39737ab227966226fcc", "section_path": ["Changes"], "commit_groups": [["13b627a3e", "239eabda4", "26d6b7dc9", "277122036", "53470ffba", "6fcee189b", "9740c68ff"]], "identity_text": "Fix planner's nullability and strictness checks for value IN (array) expressions (Ayush Tiwari) These checks should only succeed if the array operand is known to be non-empty, but that consideration was missed, allowing optimizations to be applied that should not be. This could result in wrong query answers if the array actually was empty.", "commit_aliases": ["13b627a3e", "239eabda4", "26d6b7dc9", "277122036", "53470ffba", "6fcee189b", "9740c68ff"], "source_commits": ["277122036"], "source_entry_id": "18.6/changes/036", "db_id": "ad3ee3744d12ed87e41b743df908a973", "patch_ids": ["df435503db83a1e14391340c77582135"], "statement_hash": "2d92bc3cfa84bb56afc5d1f1b3a42de958d5476b1ad5c8eeac46ecc8e878ca25", "relations": [{"rule": 2, "type": "equivalent", "target": "295b1a7da9077453b2e0fd1899e5c7e4", "evidence": {"same_day": true, "patch_ids": ["df435503db83a1e14391340c77582135"], "statement_hash": "2d92bc3cfa84bb56afc5d1f1b3a42de958d5476b1ad5c8eeac46ecc8e878ca25"}}, {"rule": 2, "type": "equivalent", "target": "53fcc801e2a78a55196f6122abbd7a01", "evidence": {"same_day": true, "patch_ids": ["df435503db83a1e14391340c77582135"], "statement_hash": "2d92bc3cfa84bb56afc5d1f1b3a42de958d5476b1ad5c8eeac46ecc8e878ca25"}}, {"rule": 2, "type": "equivalent", "target": "8c22785dc1e64a0a8f07acd08ee8695d", "evidence": {"same_day": true, "patch_ids": ["df435503db83a1e14391340c77582135"], "statement_hash": "2d92bc3cfa84bb56afc5d1f1b3a42de958d5476b1ad5c8eeac46ecc8e878ca25"}}, {"rule": 2, "type": "equivalent", "target": "c4e4aedd211ab9a3cebe71bab9209dff", "evidence": {"same_day": true, "patch_ids": ["df435503db83a1e14391340c77582135"], "statement_hash": "2d92bc3cfa84bb56afc5d1f1b3a42de958d5476b1ad5c8eeac46ecc8e878ca25"}}]}}, {"id": "18.6-8445b59319518d4d", "source_entry_id": "18.6/changes/037", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix incorrect join removal logic", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-8ac984b046b9e22d", "source_entry_id": "17.11/changes/032", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix incorrect join removal logic"}], "entry": {"id": "18.6-8445b59319518d4d", "cves": [], "html": "Fix incorrect join removal logic (Matheus Alcantara, Richard Guo) § §
\nIn edge cases, it was possible for a constant output value coming from within the nullable side of an outer join to not be replaced by NULL when it should be.
", "text": "Fix incorrect join removal logic (Matheus Alcantara, Richard Guo) § § In edge cases, it was possible for a constant output value coming from within the nullable side of an outer join to not be replaced by NULL when it should be.", "title": "Fix incorrect join removal logic", "commits": ["21f5e659e", "9e40d07e1"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "2282060f2cd290842672f0145f4ff5559cbf9d177d487d890edfca94f95af51d", "section_path": ["Changes"], "commit_groups": [["0da71d90d", "72457f1df", "9e40d07e1", "b308eb366", "d610d8e8b"], ["1df9e8d96", "21f5e659e", "3e1fe25e6", "8bc479627", "cdcec567d"]], "identity_text": "Fix incorrect join removal logic (Matheus Alcantara, Richard Guo) In edge cases, it was possible for a constant output value coming from within the nullable side of an outer join to not be replaced by NULL when it should be.", "commit_aliases": ["0da71d90d", "1df9e8d96", "21f5e659e", "3e1fe25e6", "72457f1df", "8bc479627", "9e40d07e1", "b308eb366", "cdcec567d", "d610d8e8b"], "source_commits": ["21f5e659e", "9e40d07e1"], "source_entry_id": "18.6/changes/037", "db_id": "4f181419572dec31c7f8a0612a21f555", "patch_ids": ["1e12745a4a72c22047b3d9e8c13b8fb6", "dabc0be4437bfea2c9473e4b0cbd7ede"], "statement_hash": "66372d30c157ceb2f0f88f6e5275d315accebe006eebab6de4089f55d7597b5d", "relations": [{"rule": 2, "type": "equivalent", "target": "86a9304ee897d487f2f08fdf6cd5a298", "evidence": {"same_day": true, "patch_ids": ["1e12745a4a72c22047b3d9e8c13b8fb6", "dabc0be4437bfea2c9473e4b0cbd7ede"], "statement_hash": "66372d30c157ceb2f0f88f6e5275d315accebe006eebab6de4089f55d7597b5d"}}, {"rule": 2, "type": "equivalent", "target": "d46715d5dbb4902eaecdcfe45967fd74", "evidence": {"same_day": true, "patch_ids": ["1e12745a4a72c22047b3d9e8c13b8fb6", "dabc0be4437bfea2c9473e4b0cbd7ede"], "statement_hash": "66372d30c157ceb2f0f88f6e5275d315accebe006eebab6de4089f55d7597b5d"}}]}}, {"id": "18.6-7bb42265442bdc48", "source_entry_id": "18.6/changes/039", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Add missed checks for hashability of equality comparisons on container datatypes (arrays, composites, ranges)", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-f6f35a5c24f27bf2", "source_entry_id": "17.11/changes/033", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Add missed checks for hashability of equality comparisons on container datatypes (arrays, composites, ranges)"}], "entry": {"id": "18.6-7bb42265442bdc48", "cves": [], "html": "Add missed checks for hashability of equality comparisons on container datatypes (arrays, composites, ranges) (Andrei Lepikhov, Tom Lane) §
\nThe planner must verify hashability of the container's component type(s) before deciding it can use a hash-based plan type. This step was missed in some places, leading to “could not identify a hash function” failures at execution.
", "text": "Add missed checks for hashability of equality comparisons on container datatypes (arrays, composites, ranges) (Andrei Lepikhov, Tom Lane) § The planner must verify hashability of the container's component type(s) before deciding it can use a hash-based plan type. This step was missed in some places, leading to “could not identify a hash function” failures at execution.", "title": "Add missed checks for hashability of equality comparisons on container datatypes (arrays, composites, ranges)", "commits": ["11aed8d19"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "6ad8dd8c985b21b21108124389165bf7327db02422d4aae9a1e764bd8d71d016", "section_path": ["Changes"], "commit_groups": [["06e94eccf", "11aed8d19", "19152e3c2", "64778fac7", "caebac5f1", "cf2bfe073"]], "identity_text": "Add missed checks for hashability of equality comparisons on container datatypes (arrays, composites, ranges) (Andrei Lepikhov, Tom Lane) The planner must verify hashability of the container's component type(s) before deciding it can use a hash-based plan type. This step was missed in some places, leading to could not identify a hash function failures at execution.", "commit_aliases": ["06e94eccf", "11aed8d19", "19152e3c2", "64778fac7", "caebac5f1", "cf2bfe073"], "source_commits": ["11aed8d19"], "source_entry_id": "18.6/changes/039", "db_id": "b401153415d6c7495b085ccde803a0bc", "patch_ids": ["f162e2041e91d006f552b603fcf44b0b"], "statement_hash": "b7a7a5b48bc59370b10583c89b44b2318a828907126bcf1f7993377c9815a9e9", "relations": [{"rule": 2, "type": "equivalent", "target": "4de85f9df67410e6ee11d61a4934c2dd", "evidence": {"same_day": true, "patch_ids": ["f162e2041e91d006f552b603fcf44b0b"], "statement_hash": "b7a7a5b48bc59370b10583c89b44b2318a828907126bcf1f7993377c9815a9e9"}}, {"rule": 2, "type": "equivalent", "target": "8f291081d50c65368eaa75ffccbfb916", "evidence": {"same_day": true, "patch_ids": ["f162e2041e91d006f552b603fcf44b0b"], "statement_hash": "b7a7a5b48bc59370b10583c89b44b2318a828907126bcf1f7993377c9815a9e9"}}, {"rule": 2, "type": "equivalent", "target": "f09d5370fd92cd8394d32a7c6a39f808", "evidence": {"same_day": true, "patch_ids": ["f162e2041e91d006f552b603fcf44b0b"], "statement_hash": "b7a7a5b48bc59370b10583c89b44b2318a828907126bcf1f7993377c9815a9e9"}}, {"rule": 2, "type": "equivalent", "target": "f1ae81ec65ad7eceb75ed5e3e0b2c543", "evidence": {"same_day": true, "patch_ids": ["f162e2041e91d006f552b603fcf44b0b"], "statement_hash": "b7a7a5b48bc59370b10583c89b44b2318a828907126bcf1f7993377c9815a9e9"}}]}}, {"id": "18.6-88417491cf3856e5", "source_entry_id": "18.6/changes/041", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix mis-optimization of COUNT window functions that have an EXCLUDE clause or lack ORDER BY", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-c7bededba93f5fa4", "source_entry_id": "17.11/changes/034", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix mis-optimization of COUNT window functions that have an EXCLUDE clause or lack ORDER BY"}], "entry": {"id": "18.6-88417491cf3856e5", "cves": [], "html": "Fix mis-optimization of COUNT window functions that have an EXCLUDE clause or lack ORDER BY (Chengpeng Yan, David Rowley) §
These window functions were treated as monotonic when they should not be, allowing wrong answers to be computed.
", "text": "Fix mis-optimization of COUNT window functions that have an EXCLUDE clause or lack ORDER BY (Chengpeng Yan, David Rowley) § These window functions were treated as monotonic when they should not be, allowing wrong answers to be computed.", "title": "Fix mis-optimization of COUNT window functions that have an EXCLUDE clause or lack ORDER BY", "commits": ["cf184ec77"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "0ea7c716ea749b5741a7bf87e0ccbd8f8674c2d3136b6c921885dd8bb2d28a2c", "section_path": ["Changes"], "commit_groups": [["842e34efa", "a85732162", "be63b285e", "cf184ec77", "d007800f0", "fcd58c6d9"]], "identity_text": "Fix mis-optimization of COUNT window functions that have an EXCLUDE clause or lack ORDER BY (Chengpeng Yan, David Rowley) These window functions were treated as monotonic when they should not be, allowing wrong answers to be computed.", "commit_aliases": ["842e34efa", "a85732162", "be63b285e", "cf184ec77", "d007800f0", "fcd58c6d9"], "source_commits": ["cf184ec77"], "source_entry_id": "18.6/changes/041", "db_id": "ddf83605232b0de3c591e0caa7a88605", "patch_ids": ["28e51714721f6a824be654de7f6357bc"], "statement_hash": "6285e56236281de47720490e02f655ef1c492df7841c118242cef65b8c828aa3", "relations": [{"rule": 2, "type": "equivalent", "target": "28c2612bebf05e287b83343abb5a649a", "evidence": {"same_day": true, "patch_ids": ["28e51714721f6a824be654de7f6357bc"], "statement_hash": "6285e56236281de47720490e02f655ef1c492df7841c118242cef65b8c828aa3"}}, {"rule": 2, "type": "equivalent", "target": "40a7c9c1b0ba3bb62e973869e4377d48", "evidence": {"same_day": true, "patch_ids": ["28e51714721f6a824be654de7f6357bc"], "statement_hash": "6285e56236281de47720490e02f655ef1c492df7841c118242cef65b8c828aa3"}}, {"rule": 2, "type": "equivalent", "target": "f36b3896971ebb704e9049fa9035f582", "evidence": {"same_day": true, "patch_ids": ["28e51714721f6a824be654de7f6357bc"], "statement_hash": "6285e56236281de47720490e02f655ef1c492df7841c118242cef65b8c828aa3"}}]}}, {"id": "18.6-14a8792e9a6b6b0c", "source_entry_id": "18.6/changes/043", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix ALTER COLUMN ... DROP EXPRESSION to work when there are multiple levels of partitions", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-aa9ce164073e6fc7", "source_entry_id": "17.11/changes/035", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix ALTER COLUMN ... DROP EXPRESSION to work when there are multiple levels of partitions"}], "entry": {"id": "18.6-14a8792e9a6b6b0c", "cves": [], "html": "Fix ALTER COLUMN ... DROP EXPRESSION to work when there are multiple levels of partitions (Alberto Piai) §
Fix attaching partitions of indexes that are exclusion constraints (Japin Li) §
\nNotably, this oversight broke dump/restore of partitioned exclusion constraints.
", "text": "Fix attaching partitions of indexes that are exclusion constraints (Japin Li) § Notably, this oversight broke dump/restore of partitioned exclusion constraints.", "title": "Fix attaching partitions of indexes that are exclusion constraints", "commits": ["19e3aa704"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "e26997d652381c7f0ed9681bc22f8e68776fa5da18d5bc132c86c3b7e545f464", "section_path": ["Changes"], "commit_groups": [["19e3aa704", "1d6c654c8", "2b2c2492c", "d049a31a4"]], "identity_text": "Fix attaching partitions of indexes that are exclusion constraints (Japin Li) Notably, this oversight broke dump/restore of partitioned exclusion constraints.", "commit_aliases": ["19e3aa704", "1d6c654c8", "2b2c2492c", "d049a31a4"], "source_commits": ["19e3aa704"], "source_entry_id": "18.6/changes/044", "db_id": "5c4182efd803f6d6d6537714c7bd42b7", "patch_ids": ["32801b307162bd0744d51d9ca6c96a29"], "statement_hash": "a43e644386fbc7d5b0bbee11dd34413bc9867bd3e1172c28e5ef212327072aab", "relations": [{"rule": 2, "type": "equivalent", "target": "93afcbc160733050810dc157756fa912", "evidence": {"same_day": true, "patch_ids": ["32801b307162bd0744d51d9ca6c96a29"], "statement_hash": "a43e644386fbc7d5b0bbee11dd34413bc9867bd3e1172c28e5ef212327072aab"}}]}}, {"id": "18.6-7007f0ab50735ceb", "source_entry_id": "18.6/changes/046", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Disallow renaming a rule to _RETURN", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-d462466d836ceca5", "source_entry_id": "17.11/changes/037", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Disallow renaming a rule to _RETURN"}], "entry": {"id": "18.6-7007f0ab50735ceb", "cves": [], "html": "Disallow renaming a rule to _RETURN (Tom Lane) §
That name is reserved for a view's ON SELECT rule, but ALTER RULE allowed renaming other rules to _RETURN, causing trouble later.
Fix missing lock release for role membership grants in DROP OWNED BY (Jeff Davis) §
This oversight resulted in a warning message, followed by retaining a lock on the membership grant until the end of the transaction.
", "text": "Fix missing lock release for role membership grants in DROP OWNED BY (Jeff Davis) § This oversight resulted in a warning message, followed by retaining a lock on the membership grant until the end of the transaction.", "title": "Fix missing lock release for role membership grants in DROP OWNED BY", "commits": ["a0daa0b41"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "2aac72ff4aa5ee2955a6053adaa7adbb8f63722691ed0531eec8c26985c5efa3", "section_path": ["Changes"], "commit_groups": [["25e54cec7", "9eccdae22", "a0daa0b41", "b48caa7df", "e61d44fde"]], "identity_text": "Fix missing lock release for role membership grants in DROP OWNED BY (Jeff Davis) This oversight resulted in a warning message, followed by retaining a lock on the membership grant until the end of the transaction.", "commit_aliases": ["25e54cec7", "9eccdae22", "a0daa0b41", "b48caa7df", "e61d44fde"], "source_commits": ["a0daa0b41"], "source_entry_id": "18.6/changes/047", "db_id": "5ac990e6d8ae4f5c9facf9044c23d6c9", "patch_ids": ["366a54c27360ab3839f71c858dc847c7"], "statement_hash": "c3d8dda4db627322e27465f2a355faabf29a98b7c4ddfd870cf46d4fa9b704f9", "relations": [{"rule": 2, "type": "equivalent", "target": "0563a596791449f44372e96193722ea2", "evidence": {"same_day": true, "patch_ids": ["366a54c27360ab3839f71c858dc847c7"], "statement_hash": "c3d8dda4db627322e27465f2a355faabf29a98b7c4ddfd870cf46d4fa9b704f9"}}, {"rule": 2, "type": "equivalent", "target": "f38a9d64af080b972d55091afa2b7167", "evidence": {"same_day": true, "patch_ids": ["366a54c27360ab3839f71c858dc847c7"], "statement_hash": "c3d8dda4db627322e27465f2a355faabf29a98b7c4ddfd870cf46d4fa9b704f9"}}]}}, {"id": "18.6-604b807a12c59a87", "source_entry_id": "18.6/changes/048", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix failure of EXPLAIN when deparsing SQL/JSON aggregates", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-df483e133aa49926", "source_entry_id": "17.11/changes/039", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix failure of EXPLAIN when deparsing SQL/JSON aggregates"}], "entry": {"id": "18.6-604b807a12c59a87", "cves": [], "html": "Fix failure of EXPLAIN when deparsing SQL/JSON aggregates (Richard Guo) §
Some plan structures resulted in “invalid JsonConstructorExpr underlying node type” errors.
", "text": "Fix failure of EXPLAIN when deparsing SQL/JSON aggregates (Richard Guo) § Some plan structures resulted in “invalid JsonConstructorExpr underlying node type” errors.", "title": "Fix failure of EXPLAIN when deparsing SQL/JSON aggregates", "commits": ["45364e496"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "d3a0089d91c98ae5bf10b57ed60f7d442c6dd373660c026c360f1fa30e2703ea", "section_path": ["Changes"], "commit_groups": [["45364e496", "485527190", "96ab9a990", "dcda1f07d", "eaa561fb6"]], "identity_text": "Fix failure of EXPLAIN when deparsing SQL/JSON aggregates (Richard Guo) Some plan structures resulted in invalid JsonConstructorExpr underlying node type errors.", "commit_aliases": ["45364e496", "485527190", "96ab9a990", "dcda1f07d", "eaa561fb6"], "source_commits": ["45364e496"], "source_entry_id": "18.6/changes/048", "db_id": "9bd2c80a3ef9ebab0fa8c15b085cb9d4", "patch_ids": ["60000a6e62ddc3ae0c3b7ef80802ee71"], "statement_hash": "6a7283c8b92d0663e05728d26d406516f01a522c2433821f328a072f69e8d6c2", "relations": [{"rule": 2, "type": "equivalent", "target": "76da1bf58091a36c27ddeecb07c72440", "evidence": {"same_day": true, "patch_ids": ["60000a6e62ddc3ae0c3b7ef80802ee71"], "statement_hash": "6a7283c8b92d0663e05728d26d406516f01a522c2433821f328a072f69e8d6c2"}}, {"rule": 2, "type": "equivalent", "target": "9796917e37d7742de7735ae20dbc9e8c", "evidence": {"same_day": true, "patch_ids": ["60000a6e62ddc3ae0c3b7ef80802ee71"], "statement_hash": "6a7283c8b92d0663e05728d26d406516f01a522c2433821f328a072f69e8d6c2"}}]}}, {"id": "18.6-8283ac4f7a0c7e8e", "source_entry_id": "18.6/changes/049", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix use of REINDEX CONCURRENTLY with a deferred uniqueness constraint", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-5f6921ca5abdfb75", "source_entry_id": "17.11/changes/040", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix use of REINDEX CONCURRENTLY with a deferred uniqueness constraint"}], "entry": {"id": "18.6-8283ac4f7a0c7e8e", "cves": [], "html": "Fix use of REINDEX CONCURRENTLY with a deferred uniqueness constraint (Nitin Motiani) §
The transient index copy created during REINDEX CONCURRENTLY was incorrectly marked as enforcing immediate uniqueness, causing spurious reports of constraint violation.
Fix incorrect NFC recomposition for Hangul U+11A7 (TBASE) (Diego Frias, Michael Paquier) §
\nThis character was treated as a valid T syllable, which it is not, and hence silently swallowed during normalization.
", "text": "Fix incorrect NFC recomposition for Hangul U+11A7 (TBASE) (Diego Frias, Michael Paquier) § This character was treated as a valid T syllable, which it is not, and hence silently swallowed during normalization.", "title": "Fix incorrect NFC recomposition for Hangul U+11A7 (TBASE)", "commits": ["273fe9485"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "12dfc8fb1740739aa2a2241aafbdc5e41621ac922bf07241fb5d6d9f53cabe3d", "section_path": ["Changes"], "commit_groups": [["0c9cbbfb5", "273fe9485", "82116023e", "8bb935d61", "c391375ba", "f2ff15e4c"]], "identity_text": "Fix incorrect NFC recomposition for Hangul U+11A7 (TBASE) (Diego Frias, Michael Paquier) This character was treated as a valid T syllable, which it is not, and hence silently swallowed during normalization.", "commit_aliases": ["0c9cbbfb5", "273fe9485", "82116023e", "8bb935d61", "c391375ba", "f2ff15e4c"], "source_commits": ["273fe9485"], "source_entry_id": "18.6/changes/054", "db_id": "3a6050c2cb2fe8b496eaa4963a657d6a", "patch_ids": ["725250db9eb55dab240d380ece2a835b"], "statement_hash": "0790cf6e3b0bbc225a449fee5cfdf5d70b4c6b23cc6777393156d83479c1c717", "relations": [{"rule": 2, "type": "equivalent", "target": "3ca62c531cc3952831a57b828ba3be6f", "evidence": {"same_day": true, "patch_ids": ["725250db9eb55dab240d380ece2a835b"], "statement_hash": "0790cf6e3b0bbc225a449fee5cfdf5d70b4c6b23cc6777393156d83479c1c717"}}, {"rule": 2, "type": "equivalent", "target": "955b29dab0dd740875781e1df1992bdc", "evidence": {"same_day": true, "patch_ids": ["725250db9eb55dab240d380ece2a835b"], "statement_hash": "0790cf6e3b0bbc225a449fee5cfdf5d70b4c6b23cc6777393156d83479c1c717"}}, {"rule": 2, "type": "equivalent", "target": "aaef9ba320136440f8b0a3ec12c67f23", "evidence": {"same_day": true, "patch_ids": ["725250db9eb55dab240d380ece2a835b"], "statement_hash": "0790cf6e3b0bbc225a449fee5cfdf5d70b4c6b23cc6777393156d83479c1c717"}}, {"rule": 2, "type": "equivalent", "target": "b4da21230a332d29b7fdd0c30e5eb1b0", "evidence": {"same_day": true, "patch_ids": ["725250db9eb55dab240d380ece2a835b"], "statement_hash": "0790cf6e3b0bbc225a449fee5cfdf5d70b4c6b23cc6777393156d83479c1c717"}}]}}, {"id": "18.6-3c978527782bcd11", "source_entry_id": "18.6/changes/055", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Avoid possible truncation of output lexemes in case-insensitive synonym dictionaries", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-a4695342e5fc0fc7", "source_entry_id": "17.11/changes/043", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Avoid possible truncation of output lexemes in case-insensitive synonym dictionaries"}], "entry": {"id": "18.6-3c978527782bcd11", "cves": [], "html": "Avoid possible truncation of output lexemes in case-insensitive synonym dictionaries (Jeff Davis) §
If folding to lower case increased the byte length of a lexeme, it was incorrectly truncated to its original byte length when emitted.
", "text": "Avoid possible truncation of output lexemes in case-insensitive synonym dictionaries (Jeff Davis) § If folding to lower case increased the byte length of a lexeme, it was incorrectly truncated to its original byte length when emitted.", "title": "Avoid possible truncation of output lexemes in case-insensitive synonym dictionaries", "commits": ["89e648498"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "77469b6258132929a06ffd007b2e4038dba19ecf2bf22a1c920ef1c94e3decdd", "section_path": ["Changes"], "commit_groups": [["1e0458172", "3805641cb", "89e648498", "9234e3337", "a7e0e42a2", "b32df590c"]], "identity_text": "Avoid possible truncation of output lexemes in case-insensitive synonym dictionaries (Jeff Davis) If folding to lower case increased the byte length of a lexeme, it was incorrectly truncated to its original byte length when emitted.", "commit_aliases": ["1e0458172", "3805641cb", "89e648498", "9234e3337", "a7e0e42a2", "b32df590c"], "source_commits": ["89e648498"], "source_entry_id": "18.6/changes/055", "db_id": "347d8e16786f9262348eddb4e4ab7132", "patch_ids": ["751e547292fa99c95c843d27d6c9593a"], "statement_hash": "c66911e6e36c7126e1b585143d9e9b87d38db4e29cfb38c6987eff4e2c4f70d3", "relations": [{"rule": 2, "type": "equivalent", "target": "0633548b5897af860062f0da29c48e44", "evidence": {"same_day": true, "patch_ids": ["751e547292fa99c95c843d27d6c9593a"], "statement_hash": "c66911e6e36c7126e1b585143d9e9b87d38db4e29cfb38c6987eff4e2c4f70d3"}}, {"rule": 2, "type": "equivalent", "target": "3af409a2d71c7fbd1a45975cdba31ea0", "evidence": {"same_day": true, "patch_ids": ["751e547292fa99c95c843d27d6c9593a"], "statement_hash": "c66911e6e36c7126e1b585143d9e9b87d38db4e29cfb38c6987eff4e2c4f70d3"}}, {"rule": 2, "type": "equivalent", "target": "a4a88f042e4bc74a3646ee98fc6e3a95", "evidence": {"same_day": true, "patch_ids": ["751e547292fa99c95c843d27d6c9593a"], "statement_hash": "c66911e6e36c7126e1b585143d9e9b87d38db4e29cfb38c6987eff4e2c4f70d3"}}, {"rule": 2, "type": "equivalent", "target": "ae43518b0809db4841928b42a3de5142", "evidence": {"same_day": true, "patch_ids": ["751e547292fa99c95c843d27d6c9593a"], "statement_hash": "c66911e6e36c7126e1b585143d9e9b87d38db4e29cfb38c6987eff4e2c4f70d3"}}]}}, {"id": "18.6-fcede1358593efe6", "source_entry_id": "18.6/changes/056", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Defend against truncated UTF-8 characters in case-conversion logic", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-650fe2adca4c15c7", "source_entry_id": "17.11/changes/044", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Defend against truncated UTF-8 characters in case-conversion logic"}], "entry": {"id": "18.6-fcede1358593efe6", "cves": [], "html": "Defend against truncated UTF-8 characters in case-conversion logic (Jeff Davis) §
", "text": "Defend against truncated UTF-8 characters in case-conversion logic (Jeff Davis) §", "title": "Defend against truncated UTF-8 characters in case-conversion logic", "commits": ["9021c8f3c"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "89b6cc131a56223f184b1fbcb6088e67d57ed12feda80537ab55e794e0c3ac4d", "section_path": ["Changes"], "commit_groups": [["05da336dd", "21ffc271d", "5e78ebca5", "9021c8f3c"]], "identity_text": "Defend against truncated UTF-8 characters in case-conversion logic (Jeff Davis)", "commit_aliases": ["05da336dd", "21ffc271d", "5e78ebca5", "9021c8f3c"], "source_commits": ["9021c8f3c"], "source_entry_id": "18.6/changes/056", "db_id": "fbf07b5b0ddd47273177153e01d4ca58", "patch_ids": ["70ade08782c5c0086629edb156a1a000"], "statement_hash": "b8ea4712aa3d1f59707ea58deb088497b6eb664982552c1833b1fdb40b14fc59", "relations": [{"rule": 2, "type": "equivalent", "target": "6587fa053296846f315df1024b486ffb", "evidence": {"same_day": true, "patch_ids": ["70ade08782c5c0086629edb156a1a000"], "statement_hash": "b8ea4712aa3d1f59707ea58deb088497b6eb664982552c1833b1fdb40b14fc59"}}]}}, {"id": "18.6-07aee184fcf9a835", "source_entry_id": "18.6/changes/057", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix typo in hash_record_extended()", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-f5ccad03da59d5de", "source_entry_id": "17.11/changes/045", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix typo in hash_record_extended()"}], "entry": {"id": "18.6-07aee184fcf9a835", "cves": [], "html": "Fix typo in hash_record_extended() (Man Zeng) §
The code failed to initialize the second isnull argument passed to FunctionCallInvoke(). This is harmless for existing in-core extended hash support functions, which will not examine that value. However, extension-provided hash functions could be affected if they inspect PG_ARGISNULL(1).
Fix pg_get_publication_tables() to not fail if a publishable table is dropped concurrently (Bharath Rupireddy) §
Prevent satisfies_hash_partition() from crashing with VARIADIC NULL (Robert Haas) §
Report invalid-weight errors more cleanly and consistently in tsvector_filter() and allied functions (Ewan Young) §
In particular, report weight characters that are not printable ASCII in octal form (\\), as nnncharout() would render them. This avoids possibly producing an invalidly-encoded error message.
Fix mishandling of namespace nodes in xpath() (Michael Paquier) § §
This fix avoids an unexpected “could not copy node” error.
", "text": "Fix mishandling of namespace nodes in xpath() (Michael Paquier) § § This fix avoids an unexpected “could not copy node” error.", "title": "Fix mishandling of namespace nodes in xpath()", "commits": ["0d145be2c", "4c777d6dd"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "46a1a93cf33ad088d8ce016a48b23002f2c9ca6b8eb39cb5d92df14ea571c8bb", "section_path": ["Changes"], "commit_groups": [["0b74df66f", "0d145be2c", "940916549", "9618e790c", "a17f39aa2", "fac26fd41"], ["174076601", "1d8c72b2e", "41876c8d7", "4c777d6dd", "6c08cbb7a", "8bf257aeb"]], "identity_text": "Fix mishandling of namespace nodes in xpath() (Michael Paquier) This fix avoids an unexpected could not copy node error.", "commit_aliases": ["0b74df66f", "0d145be2c", "174076601", "1d8c72b2e", "41876c8d7", "4c777d6dd", "6c08cbb7a", "8bf257aeb", "940916549", "9618e790c", "a17f39aa2", "fac26fd41"], "source_commits": ["0d145be2c", "4c777d6dd"], "source_entry_id": "18.6/changes/062", "db_id": "9d61a6c023f441c2a3883f44804564ca", "patch_ids": ["702367d070cdeca227ba0e4197a518e9", "7df9ed5e8663765f5ca836c89d33f03d"], "statement_hash": "2ab954d63190bf0ecdc409c287a734a5049667a3d9db9dc5337f82a35275db37", "relations": [{"rule": 2, "type": "equivalent", "target": "a3cd7c73a5609ef9df5a2f2035307742", "evidence": {"same_day": true, "patch_ids": ["702367d070cdeca227ba0e4197a518e9", "7df9ed5e8663765f5ca836c89d33f03d"], "statement_hash": "2ab954d63190bf0ecdc409c287a734a5049667a3d9db9dc5337f82a35275db37"}}, {"rule": 2, "type": "equivalent", "target": "c9299f10a2be68af64d82e072893d1fa", "evidence": {"same_day": true, "patch_ids": ["702367d070cdeca227ba0e4197a518e9", "7df9ed5e8663765f5ca836c89d33f03d"], "statement_hash": "2ab954d63190bf0ecdc409c287a734a5049667a3d9db9dc5337f82a35275db37"}}, {"rule": 2, "type": "equivalent", "target": "d35a51c2f2bcdba360c287240fa92b7a", "evidence": {"same_day": true, "patch_ids": ["702367d070cdeca227ba0e4197a518e9", "7df9ed5e8663765f5ca836c89d33f03d"], "statement_hash": "2ab954d63190bf0ecdc409c287a734a5049667a3d9db9dc5337f82a35275db37"}}, {"rule": 2, "type": "equivalent", "target": "da05c3ee44af186be3d4b5b7c6f0afe4", "evidence": {"same_day": true, "patch_ids": ["702367d070cdeca227ba0e4197a518e9", "7df9ed5e8663765f5ca836c89d33f03d"], "statement_hash": "2ab954d63190bf0ecdc409c287a734a5049667a3d9db9dc5337f82a35275db37"}}]}}, {"id": "18.6-9490e3fbcfd0ff13", "source_entry_id": "18.6/changes/063", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix jsonpath's .decimal method to not throw a hard error for incorrect precision or scale", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-3a52211bf75efb3d", "source_entry_id": "17.11/changes/050", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix jsonpath's .decimal method to not throw a hard error for incorrect precision or scale"}], "entry": {"id": "18.6-9490e3fbcfd0ff13", "cves": [], "html": "Fix jsonpath's .decimal method to not throw a hard error for incorrect precision or scale (Ewan Young) § §
Silent mode should suppress these errors, but failed to.
", "text": "Fix jsonpath's .decimal method to not throw a hard error for incorrect precision or scale (Ewan Young) § § Silent mode should suppress these errors, but failed to.", "title": "Fix jsonpath's .decimal method to not throw a hard error for incorrect precision or scale", "commits": ["84001a04d", "90789900b"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "a24f0d483057c78a7d10cc03aacfc3f8214515bbebcd0c3bd866baab53ff26bf", "section_path": ["Changes"], "commit_groups": [["5bbc9b300", "7b12ae729", "84001a04d", "ab35b8d25"], ["90789900b", "c768637d6"]], "identity_text": "Fix jsonpath's .decimal method to not throw a hard error for incorrect precision or scale (Ewan Young) Silent mode should suppress these errors, but failed to.", "commit_aliases": ["5bbc9b300", "7b12ae729", "84001a04d", "90789900b", "ab35b8d25", "c768637d6"], "source_commits": ["84001a04d", "90789900b"], "source_entry_id": "18.6/changes/063", "db_id": "e2b61ba2f7f1acf6259668e5028c0d3a", "patch_ids": ["154a264168d2701e57e668c30f8c6672", "a933e072e485a711920d54cb328279be"], "statement_hash": "c504d01401e67b15f04b83edbe81331d59a4135c0f6c1aae9aeea83bf5ceb972", "relations": [{"rule": 2, "type": "equivalent", "target": "151967124db1018c14bba6aaa8fb0531", "evidence": {"same_day": true, "patch_ids": ["154a264168d2701e57e668c30f8c6672", "a933e072e485a711920d54cb328279be"], "statement_hash": "c504d01401e67b15f04b83edbe81331d59a4135c0f6c1aae9aeea83bf5ceb972"}}]}}, {"id": "18.6-2abf51fa81b5fec1", "source_entry_id": "18.6/changes/064", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix NULL-pointer crash when IS JSON or similar constructs have an argument that is of string category but lacks a cast to type text", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-b72bd4ebdcd34344", "source_entry_id": "17.11/changes/051", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix NULL-pointer crash when IS JSON or similar constructs have an argument that is of string category but lacks a cast to type text"}], "entry": {"id": "18.6-2abf51fa81b5fec1", "cves": [], "html": "Fix NULL-pointer crash when IS JSON or similar constructs have an argument that is of string category but lacks a cast to type text (Ayush Tiwari) §
There are no such data types in core PostgreSQL, but the problem is reachable with some extension types.
", "text": "Fix NULL-pointer crash when IS JSON or similar constructs have an argument that is of string category but lacks a cast to type text (Ayush Tiwari) § There are no such data types in core PostgreSQL, but the problem is reachable with some extension types.", "title": "Fix NULL-pointer crash when IS JSON or similar constructs have an argument that is of string category but lacks a cast to type text", "commits": ["35d9a6263"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "15c4b6ebef3e976580dd4a81a7bddc91381ff8e797fc936f95505c826d0e418e", "section_path": ["Changes"], "commit_groups": [["35d9a6263", "60abb3c73", "7dd153259", "d0acd2535"]], "identity_text": "Fix NULL-pointer crash when IS JSON or similar constructs have an argument that is of string category but lacks a cast to type text (Ayush Tiwari) There are no such data types in core PostgreSQL, but the problem is reachable with some extension types.", "commit_aliases": ["35d9a6263", "60abb3c73", "7dd153259", "d0acd2535"], "source_commits": ["35d9a6263"], "source_entry_id": "18.6/changes/064", "db_id": "2fbf45f00e42445fcae00d71cbf1f0dc", "patch_ids": ["96b46719db446e88ef3c60d115404730"], "statement_hash": "ea987d289e305c0b161cfa39b9d0169ba382dac0fa72d5593a7a281f289b9a70", "relations": [{"rule": 2, "type": "equivalent", "target": "79cd8a83e8bf1bc35f530164bf6860b4", "evidence": {"same_day": true, "patch_ids": ["96b46719db446e88ef3c60d115404730"], "statement_hash": "ea987d289e305c0b161cfa39b9d0169ba382dac0fa72d5593a7a281f289b9a70"}}, {"rule": 2, "type": "equivalent", "target": "f8921df2d66db8b26d617c27bddf1db2", "evidence": {"same_day": true, "patch_ids": ["96b46719db446e88ef3c60d115404730"], "statement_hash": "ea987d289e305c0b161cfa39b9d0169ba382dac0fa72d5593a7a281f289b9a70"}}]}}, {"id": "18.6-e111e1506709b495", "source_entry_id": "18.6/changes/065", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Ensure that SQL/JSON ON EMPTY / ON ERROR DEFAULT values are coerced to the correct typmod", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-17dc3fca15a1c17a", "source_entry_id": "17.11/changes/052", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Ensure that SQL/JSON ON EMPTY / ON ERROR DEFAULT values are coerced to the correct typmod"}], "entry": {"id": "18.6-e111e1506709b495", "cves": [], "html": "Ensure that SQL/JSON ON EMPTY / ON ERROR DEFAULT values are coerced to the correct typmod (Ewan Young) §
For example, the declared precision and scale of a numeric target column were not applied to the default value.
Avoid machine-dependent behavior when dividing the smallest possible money value by -1 (Andrey Rachitskiy) §
Fix crash after out-of-memory failure partway through creation of a cache entry for a text search dictionary (Tom Lane) §
", "text": "Fix crash after out-of-memory failure partway through creation of a cache entry for a text search dictionary (Tom Lane) §", "title": "Fix crash after out-of-memory failure partway through creation of a cache entry for a text search dictionary", "commits": ["81b1e7916"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "da086036f61c30030e5480df95ebc5320aafce594ba5114ebc8b25742df3e065", "section_path": ["Changes"], "commit_groups": [["025228104", "4e68b7e29", "634a8dcb8", "81b1e7916", "83336e3ed", "dda622edc", "df8407d7d"]], "identity_text": "Fix crash after out-of-memory failure partway through creation of a cache entry for a text search dictionary (Tom Lane)", "commit_aliases": ["025228104", "4e68b7e29", "634a8dcb8", "81b1e7916", "83336e3ed", "dda622edc", "df8407d7d"], "source_commits": ["81b1e7916"], "source_entry_id": "18.6/changes/067", "db_id": "c02824b6af588491530569e4ec99fe1c", "patch_ids": ["3c3b45b5ca2c2212b9a36ad4558d619a"], "statement_hash": "bba5519e5078b4a32c843646cda9fbb9119cc591d67acb786924d35be185c1e2", "relations": [{"rule": 2, "type": "equivalent", "target": "0c1ad5d57b9bccac58da6089309d8ba7", "evidence": {"same_day": true, "patch_ids": ["3c3b45b5ca2c2212b9a36ad4558d619a"], "statement_hash": "bba5519e5078b4a32c843646cda9fbb9119cc591d67acb786924d35be185c1e2"}}, {"rule": 2, "type": "equivalent", "target": "7df44ef8cf990bb0e618cec50c164949", "evidence": {"same_day": true, "patch_ids": ["3c3b45b5ca2c2212b9a36ad4558d619a"], "statement_hash": "bba5519e5078b4a32c843646cda9fbb9119cc591d67acb786924d35be185c1e2"}}, {"rule": 2, "type": "equivalent", "target": "b0c7268f189c5a8d74b8439d4bc7c5d9", "evidence": {"same_day": true, "patch_ids": ["3c3b45b5ca2c2212b9a36ad4558d619a"], "statement_hash": "bba5519e5078b4a32c843646cda9fbb9119cc591d67acb786924d35be185c1e2"}}, {"rule": 2, "type": "equivalent", "target": "b1fc0de5d2d692ed4af6bcafccb53961", "evidence": {"same_day": true, "patch_ids": ["3c3b45b5ca2c2212b9a36ad4558d619a"], "statement_hash": "bba5519e5078b4a32c843646cda9fbb9119cc591d67acb786924d35be185c1e2"}}]}}, {"id": "18.6-df42fd80a3fef364", "source_entry_id": "18.6/changes/068", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix memory-safety bugs in processing of incorrect ispell/hunspell dictionary files", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-ce317c73e36b1b1b", "source_entry_id": "17.11/changes/055", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix memory-safety bugs in processing of incorrect ispell/hunspell dictionary files"}], "entry": {"id": "18.6-df42fd80a3fef364", "cves": [], "html": "Fix memory-safety bugs in processing of incorrect ispell/hunspell dictionary files (Andrey Rachitskiy) §
", "text": "Fix memory-safety bugs in processing of incorrect ispell/hunspell dictionary files (Andrey Rachitskiy) §", "title": "Fix memory-safety bugs in processing of incorrect ispell/hunspell dictionary files", "commits": ["4689ea9ce"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "71d6a8d23076219ae1c5fcc19a9192f7397d430f00d0743090078b3c95433c02", "section_path": ["Changes"], "commit_groups": [["0fb88979b", "330a72052", "3fe4062cc", "444038bb7", "4689ea9ce", "5fdea3aa3", "cfc720ef4"]], "identity_text": "Fix memory-safety bugs in processing of incorrect ispell/hunspell dictionary files (Andrey Rachitskiy)", "commit_aliases": ["0fb88979b", "330a72052", "3fe4062cc", "444038bb7", "4689ea9ce", "5fdea3aa3", "cfc720ef4"], "source_commits": ["4689ea9ce"], "source_entry_id": "18.6/changes/068", "db_id": "704f65f60aac8a5ed9ba34cc041d5717", "patch_ids": ["a2481aa7491246722b292cb1e96c16e2"], "statement_hash": "188f51f4de54b27a68f6be9927610ed299c71a8aed01714563e401acac778944", "relations": [{"rule": 2, "type": "equivalent", "target": "5e12745b9a23fea83bd8ffdb594c44cb", "evidence": {"same_day": true, "patch_ids": ["a2481aa7491246722b292cb1e96c16e2"], "statement_hash": "188f51f4de54b27a68f6be9927610ed299c71a8aed01714563e401acac778944"}}, {"rule": 2, "type": "equivalent", "target": "764e3f0a6b15565637fa481647bae444", "evidence": {"same_day": true, "patch_ids": ["a2481aa7491246722b292cb1e96c16e2"], "statement_hash": "188f51f4de54b27a68f6be9927610ed299c71a8aed01714563e401acac778944"}}, {"rule": 2, "type": "equivalent", "target": "77ab5557c03ca1e42e47d51eb237608a", "evidence": {"same_day": true, "patch_ids": ["a2481aa7491246722b292cb1e96c16e2"], "statement_hash": "188f51f4de54b27a68f6be9927610ed299c71a8aed01714563e401acac778944"}}, {"rule": 2, "type": "equivalent", "target": "bff681fe60683158629758d3a37c8488", "evidence": {"same_day": true, "patch_ids": ["a2481aa7491246722b292cb1e96c16e2"], "statement_hash": "188f51f4de54b27a68f6be9927610ed299c71a8aed01714563e401acac778944"}}]}}, {"id": "18.6-90e78edb7a08a279", "source_entry_id": "18.6/changes/069", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Prevent access to other sessions' temporary tables", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-712f69030e2d06d3", "source_entry_id": "17.11/changes/056", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Prevent access to other sessions' temporary tables"}], "entry": {"id": "18.6-90e78edb7a08a279", "cves": [], "html": "Prevent access to other sessions' temporary tables (Jim Jones, Daniil Davydov, Alexander Korotkov) § §
\nSome code paths failed to prevent this, leading to silently wrong (inconsistent) results.
", "text": "Prevent access to other sessions' temporary tables (Jim Jones, Daniil Davydov, Alexander Korotkov) § § Some code paths failed to prevent this, leading to silently wrong (inconsistent) results.", "title": "Prevent access to other sessions' temporary tables", "commits": ["1b0dd0815", "3aaefe892"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "0cdade44b0c297826d20dc41b61003ae0f4f3817586046a1103471fd0d51fc89", "section_path": ["Changes"], "commit_groups": [["1b0dd0815", "4dfae59a1", "ce146621f"], ["3aaefe892", "4e49f68b7", "8021cdceb", "c40819ebf", "cc3fe7e2a"]], "identity_text": "Prevent access to other sessions' temporary tables (Jim Jones, Daniil Davydov, Alexander Korotkov) Some code paths failed to prevent this, leading to silently wrong (inconsistent) results.", "commit_aliases": ["1b0dd0815", "3aaefe892", "4dfae59a1", "4e49f68b7", "8021cdceb", "c40819ebf", "cc3fe7e2a", "ce146621f"], "source_commits": ["1b0dd0815", "3aaefe892"], "source_entry_id": "18.6/changes/069", "db_id": "2b3bc99c3e3caa8f2f62effa65bfd425", "patch_ids": ["05c640bb8e2093f6ab8c82eace31d407", "78047299bcd9d41b99e91dfc8ff6128f"], "statement_hash": "bfbfb8f49eb1b9a9eeed9932c828c7ac49f313cc1b97070b91d77b3a11bb80b3", "relations": [{"rule": 2, "type": "equivalent", "target": "446bb0cc48d437fdbe5c1c4d4b77a47b", "evidence": {"same_day": true, "patch_ids": ["05c640bb8e2093f6ab8c82eace31d407", "78047299bcd9d41b99e91dfc8ff6128f"], "statement_hash": "bfbfb8f49eb1b9a9eeed9932c828c7ac49f313cc1b97070b91d77b3a11bb80b3"}}, {"rule": 2, "type": "equivalent", "target": "c23432cdcb396cd3d3ed58612faea4e6", "evidence": {"same_day": true, "patch_ids": ["05c640bb8e2093f6ab8c82eace31d407", "78047299bcd9d41b99e91dfc8ff6128f"], "statement_hash": "bfbfb8f49eb1b9a9eeed9932c828c7ac49f313cc1b97070b91d77b3a11bb80b3"}}]}}, {"id": "18.6-8f425dbb364b3d86", "source_entry_id": "18.6/changes/071", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix the order in which autovacuum processes databases", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-e7e74333c130ff46", "source_entry_id": "17.11/changes/057", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix the order in which autovacuum processes databases"}], "entry": {"id": "18.6-8f425dbb364b3d86", "cves": [], "html": "Fix the order in which autovacuum processes databases (Rustam Khamidullin) §
\nIt was unintentionally processing databases from lowest to highest score, when it should be doing the reverse.
", "text": "Fix the order in which autovacuum processes databases (Rustam Khamidullin) § It was unintentionally processing databases from lowest to highest score, when it should be doing the reverse.", "title": "Fix the order in which autovacuum processes databases", "commits": ["4cc49cb70"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "1fd6e0f3d2162dba796e2b1af675ddaa0591b54062dd8f3eae3648a2fcc25a21", "section_path": ["Changes"], "commit_groups": [["288d4e83f", "4cc49cb70", "b3331578b", "baab3268c"]], "identity_text": "Fix the order in which autovacuum processes databases (Rustam Khamidullin) It was unintentionally processing databases from lowest to highest score, when it should be doing the reverse.", "commit_aliases": ["288d4e83f", "4cc49cb70", "b3331578b", "baab3268c"], "source_commits": ["4cc49cb70"], "source_entry_id": "18.6/changes/071", "db_id": "b9d8f2a43e4df58e7a17df3fbade9bf4", "patch_ids": ["42b814ceb732c97aa3c3a526508d3abb"], "statement_hash": "c6cdd05a4bedc5971c267480385958b00c43f204b53e4cc0fe52b1e5bf13ea9d", "relations": [{"rule": 2, "type": "equivalent", "target": "7e5aa2c0c13918b50520756d59c3270c", "evidence": {"same_day": true, "patch_ids": ["42b814ceb732c97aa3c3a526508d3abb"], "statement_hash": "c6cdd05a4bedc5971c267480385958b00c43f204b53e4cc0fe52b1e5bf13ea9d"}}]}}, {"id": "18.6-cf57ab07d77fbdf9", "source_entry_id": "18.6/changes/073", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix memory leak in parallel vacuum worker processes", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-94146e86474835ca", "source_entry_id": "17.11/changes/058", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix memory leak in parallel vacuum worker processes"}], "entry": {"id": "18.6-cf57ab07d77fbdf9", "cves": [], "html": "Fix memory leak in parallel vacuum worker processes (Baji Shaik) §
\nProgress reports from a parallel worker leaked about 1kB per report, with the waste accumulating for the life of the worker process.
", "text": "Fix memory leak in parallel vacuum worker processes (Baji Shaik) § Progress reports from a parallel worker leaked about 1kB per report, with the waste accumulating for the life of the worker process.", "title": "Fix memory leak in parallel vacuum worker processes", "commits": ["4154a1482"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "eeb4d951de8faa7e6593a2a3defcc579409614caa126d11a39645d0152811604", "section_path": ["Changes"], "commit_groups": [["4154a1482", "8ad414831", "b20c952ce"]], "identity_text": "Fix memory leak in parallel vacuum worker processes (Baji Shaik) Progress reports from a parallel worker leaked about 1kB per report, with the waste accumulating for the life of the worker process.", "commit_aliases": ["4154a1482", "8ad414831", "b20c952ce"], "source_commits": ["4154a1482"], "source_entry_id": "18.6/changes/073", "db_id": "7610626b7c4fe5c411f6eaf69975db96", "patch_ids": ["d49aabf7256557adc98b6cb3284f6aaa"], "statement_hash": "568c6bb4288fdf9897eb84891ce83a70e68203e76785f837606ed060e05d9705", "relations": [{"rule": 2, "type": "equivalent", "target": "12d3079ba949a43359b006c455b1a4d0", "evidence": {"same_day": true, "patch_ids": ["d49aabf7256557adc98b6cb3284f6aaa"], "statement_hash": "568c6bb4288fdf9897eb84891ce83a70e68203e76785f837606ed060e05d9705"}}]}}, {"id": "18.6-06642c9e897515be", "source_entry_id": "18.6/changes/074", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Honor query cancel and vacuum delay during GIN index posting-tree cleanup", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-69bd1a00ee81086e", "source_entry_id": "17.11/changes/059", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Honor query cancel and vacuum delay during GIN index posting-tree cleanup"}], "entry": {"id": "18.6-06642c9e897515be", "cves": [], "html": "Honor query cancel and vacuum delay during GIN index posting-tree cleanup (Paul Kim, Alexander Korotkov) §
\nThe posting tree for a common value can be large, so that this missed check could allow vacuum to run for a long time before noticing an interrupt.
", "text": "Honor query cancel and vacuum delay during GIN index posting-tree cleanup (Paul Kim, Alexander Korotkov) § The posting tree for a common value can be large, so that this missed check could allow vacuum to run for a long time before noticing an interrupt.", "title": "Honor query cancel and vacuum delay during GIN index posting-tree cleanup", "commits": ["7becb647d"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "49842de8d396c469f5393f32a3ce7fe07babe095a16356733cf2d10be6590697", "section_path": ["Changes"], "commit_groups": [["006ac761e", "15fd7a3e2", "70dad584e", "7123abab7", "7becb647d", "8a045f760", "ba5e46329"]], "identity_text": "Honor query cancel and vacuum delay during GIN index posting-tree cleanup (Paul Kim, Alexander Korotkov) The posting tree for a common value can be large, so that this missed check could allow vacuum to run for a long time before noticing an interrupt.", "commit_aliases": ["006ac761e", "15fd7a3e2", "70dad584e", "7123abab7", "7becb647d", "8a045f760", "ba5e46329"], "source_commits": ["7becb647d"], "source_entry_id": "18.6/changes/074", "db_id": "5ae3f0e86d0ce40099b20e708d75c4df", "patch_ids": ["5737ead0e5ff1d380903a73cc5289899"], "statement_hash": "dbe0ee194244f00d3dbdcf97c73698ed65ff34b62bead922d8670ce2d3ad820b", "relations": [{"rule": 2, "type": "equivalent", "target": "409fe91bb94144927c72c3c45b46a6de", "evidence": {"same_day": true, "patch_ids": ["5737ead0e5ff1d380903a73cc5289899"], "statement_hash": "dbe0ee194244f00d3dbdcf97c73698ed65ff34b62bead922d8670ce2d3ad820b"}}, {"rule": 2, "type": "equivalent", "target": "49ebdb578d55efc3f72704dda719fc23", "evidence": {"same_day": true, "patch_ids": ["5737ead0e5ff1d380903a73cc5289899"], "statement_hash": "dbe0ee194244f00d3dbdcf97c73698ed65ff34b62bead922d8670ce2d3ad820b"}}, {"rule": 2, "type": "equivalent", "target": "814dbd746257f327d953bc1cef61300f", "evidence": {"same_day": true, "patch_ids": ["5737ead0e5ff1d380903a73cc5289899"], "statement_hash": "dbe0ee194244f00d3dbdcf97c73698ed65ff34b62bead922d8670ce2d3ad820b"}}, {"rule": 2, "type": "equivalent", "target": "95dd23cd66ca5f13741dbc751bd94f78", "evidence": {"same_day": true, "patch_ids": ["5737ead0e5ff1d380903a73cc5289899"], "statement_hash": "dbe0ee194244f00d3dbdcf97c73698ed65ff34b62bead922d8670ce2d3ad820b"}}]}}, {"id": "18.6-5a9e09abedfed179", "source_entry_id": "18.6/changes/075", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix possible mis-decoding of index tuples during GiST and SP-GiST index-only scans", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-7b0787620962198f", "source_entry_id": "17.11/changes/060", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix possible mis-decoding of index tuples during GiST and SP-GiST index-only scans"}], "entry": {"id": "18.6-5a9e09abedfed179", "cves": [], "html": "Fix possible mis-decoding of index tuples during GiST and SP-GiST index-only scans (Peter Geoghegan) §
\nThis error could lead to emitting corrupted data from an index-only scan plan. The only affected core opclass is GiST's range_ops, and it could only fail if the range column were not the first index column.
", "text": "Fix possible mis-decoding of index tuples during GiST and SP-GiST index-only scans (Peter Geoghegan) § This error could lead to emitting corrupted data from an index-only scan plan. The only affected core opclass is GiST's range_ops, and it could only fail if the range column were not the first index column.", "title": "Fix possible mis-decoding of index tuples during GiST and SP-GiST index-only scans", "commits": ["959b7fa2c"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "d7cc314ea76420e257a538b400aafc8307da56ed29c7aec8ff09e69825fdf64a", "section_path": ["Changes"], "commit_groups": [["126141425", "1d4c81ad6", "355faed5a", "959b7fa2c", "c9ea37231", "e4ad22eb0", "e58192546"]], "identity_text": "Fix possible mis-decoding of index tuples during GiST and SP-GiST index-only scans (Peter Geoghegan) This error could lead to emitting corrupted data from an index-only scan plan. The only affected core opclass is GiST's range_ops, and it could only fail if the range column were not the first index column.", "commit_aliases": ["126141425", "1d4c81ad6", "355faed5a", "959b7fa2c", "c9ea37231", "e4ad22eb0", "e58192546"], "source_commits": ["959b7fa2c"], "source_entry_id": "18.6/changes/075", "db_id": "ae38912b977aee6ba812c2a99322b4ad", "patch_ids": ["7ca370d11dfae190ad9f8fa921a2ad3d"], "statement_hash": "9efc8088134be1c1e73efd8706fe30257c8c7003aa683976e4455f175426f7c5", "relations": [{"rule": 2, "type": "equivalent", "target": "14d92270ba44127134ec95d6dc3f7106", "evidence": {"same_day": true, "patch_ids": ["7ca370d11dfae190ad9f8fa921a2ad3d"], "statement_hash": "9efc8088134be1c1e73efd8706fe30257c8c7003aa683976e4455f175426f7c5"}}, {"rule": 2, "type": "equivalent", "target": "65fae97c05ec4b526543f385b077725a", "evidence": {"same_day": true, "patch_ids": ["7ca370d11dfae190ad9f8fa921a2ad3d"], "statement_hash": "9efc8088134be1c1e73efd8706fe30257c8c7003aa683976e4455f175426f7c5"}}, {"rule": 2, "type": "equivalent", "target": "7639c43a8df152827beb0f3c4e7cfc7b", "evidence": {"same_day": true, "patch_ids": ["7ca370d11dfae190ad9f8fa921a2ad3d"], "statement_hash": "9efc8088134be1c1e73efd8706fe30257c8c7003aa683976e4455f175426f7c5"}}, {"rule": 2, "type": "equivalent", "target": "fcb9ed65e8420a852359f3e3f6bd54b4", "evidence": {"same_day": true, "patch_ids": ["7ca370d11dfae190ad9f8fa921a2ad3d"], "statement_hash": "9efc8088134be1c1e73efd8706fe30257c8c7003aa683976e4455f175426f7c5"}}]}}, {"id": "18.6-27ff2778a5384e11", "source_entry_id": "18.6/changes/076", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Ensure that the new last block of a bulk-extended table is added to its free space map promptly", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-3992304d0ec9fe22", "source_entry_id": "17.11/changes/061", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Ensure that the new last block of a bulk-extended table is added to its free space map promptly"}], "entry": {"id": "18.6-27ff2778a5384e11", "cves": [], "html": "Ensure that the new last block of a bulk-extended table is added to its free space map promptly (Jingtang Zhang) §
\nAn off-by-one error caused the last block of a multi-block table extension to not be marked as free in the map. This would eventually get corrected by vacuum, but meanwhile the space wouldn't be used.
", "text": "Ensure that the new last block of a bulk-extended table is added to its free space map promptly (Jingtang Zhang) § An off-by-one error caused the last block of a multi-block table extension to not be marked as free in the map. This would eventually get corrected by vacuum, but meanwhile the space wouldn't be used.", "title": "Ensure that the new last block of a bulk-extended table is added to its free space map promptly", "commits": ["eabc9a9dd"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "00108bc91bf3548e985abaaceb15ffddb576d4b6698d11cc22ebd57764038b7c", "section_path": ["Changes"], "commit_groups": [["0fd5595aa", "768ae083e", "7a103928a", "a2fd8d65a", "eabc9a9dd"]], "identity_text": "Ensure that the new last block of a bulk-extended table is added to its free space map promptly (Jingtang Zhang) An off-by-one error caused the last block of a multi-block table extension to not be marked as free in the map. This would eventually get corrected by vacuum, but meanwhile the space wouldn't be used.", "commit_aliases": ["0fd5595aa", "768ae083e", "7a103928a", "a2fd8d65a", "eabc9a9dd"], "source_commits": ["eabc9a9dd"], "source_entry_id": "18.6/changes/076", "db_id": "edf9c4cb86d4f9c68eb8b2fe8ad0b5d1", "patch_ids": ["a01b2fa451eb1e57f308131966fdbfa3"], "statement_hash": "86a67f4007c63f314fcd3fa59706655774d99e6653a04f11b106c0666d4ea725", "relations": [{"rule": 2, "type": "equivalent", "target": "21d26afc1e7bfcc375bff059f0b216d1", "evidence": {"same_day": true, "patch_ids": ["a01b2fa451eb1e57f308131966fdbfa3"], "statement_hash": "86a67f4007c63f314fcd3fa59706655774d99e6653a04f11b106c0666d4ea725"}}, {"rule": 2, "type": "equivalent", "target": "5a75bdb8448ae2da9b4ee0c1b6cfc0ec", "evidence": {"same_day": true, "patch_ids": ["a01b2fa451eb1e57f308131966fdbfa3"], "statement_hash": "86a67f4007c63f314fcd3fa59706655774d99e6653a04f11b106c0666d4ea725"}}]}}, {"id": "18.6-0c1c452c86d77ab6", "source_entry_id": "18.6/changes/077", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Avoid possible double-free or infinite error recovery loop in resource cleanup during transaction abort", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-bc733642b8318e02", "source_entry_id": "17.11/changes/062", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Avoid possible double-free or infinite error recovery loop in resource cleanup during transaction abort"}], "entry": {"id": "18.6-0c1c452c86d77ab6", "cves": [], "html": "Avoid possible double-free or infinite error recovery loop in resource cleanup during transaction abort (Tom Lane) §
", "text": "Avoid possible double-free or infinite error recovery loop in resource cleanup during transaction abort (Tom Lane) §", "title": "Avoid possible double-free or infinite error recovery loop in resource cleanup during transaction abort", "commits": ["ac6a58a70"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "715f023028128f4013b8cb1d6fda903d37d8e3744cb19b6e61bc48873d3a3f0e", "section_path": ["Changes"], "commit_groups": [["011eedcdc", "ac6a58a70", "ef01ca6db"]], "identity_text": "Avoid possible double-free or infinite error recovery loop in resource cleanup during transaction abort (Tom Lane)", "commit_aliases": ["011eedcdc", "ac6a58a70", "ef01ca6db"], "source_commits": ["ac6a58a70"], "source_entry_id": "18.6/changes/077", "db_id": "1c2d5d9905bd8e6369c82b7ef237290e", "patch_ids": ["952c61c83d0d5caa000ecdb0d8cb575f"], "statement_hash": "0a5717b9df09bcb1cf776219cba662308d08a453587910b5eb52fcd98913cda4", "relations": [{"rule": 2, "type": "equivalent", "target": "c57cf207c2d63b373be8c9b4e51bf8b0", "evidence": {"same_day": true, "patch_ids": ["952c61c83d0d5caa000ecdb0d8cb575f"], "statement_hash": "0a5717b9df09bcb1cf776219cba662308d08a453587910b5eb52fcd98913cda4"}}]}}, {"id": "18.6-67b85199c3f22fc0", "source_entry_id": "18.6/changes/078", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "When creating directories, tolerate concurrent creation of the same directory", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-13269e0439b17ec9", "source_entry_id": "17.11/changes/063", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "When creating directories, tolerate concurrent creation of the same directory"}], "entry": {"id": "18.6-67b85199c3f22fc0", "cves": [], "html": "When creating directories, tolerate concurrent creation of the same directory (Andrew Dunstan, Tom Lane) §
", "text": "When creating directories, tolerate concurrent creation of the same directory (Andrew Dunstan, Tom Lane) §", "title": "When creating directories, tolerate concurrent creation of the same directory", "commits": ["aa80c34c8"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "7f9cbeb061ab70c91f9d3ab57ff63f17ff4e9749996673f6b9e0507628033ac3", "section_path": ["Changes"], "commit_groups": [["4647ac142", "4b3bc6b71", "9951e3d38", "aa80c34c8", "f0a831ef3", "f25a07b2d"]], "identity_text": "When creating directories, tolerate concurrent creation of the same directory (Andrew Dunstan, Tom Lane)", "commit_aliases": ["4647ac142", "4b3bc6b71", "9951e3d38", "aa80c34c8", "f0a831ef3", "f25a07b2d"], "source_commits": ["aa80c34c8"], "source_entry_id": "18.6/changes/078", "db_id": "7b3923b1add1cfb8cc243430e7e7769f", "patch_ids": ["be8272a81c28ebdf12c66d1c6ab05685"], "statement_hash": "abc7e610f491a4ce631c4e62316b1f9bd718c7e9e581a2f07ba12774f5db10eb", "relations": [{"rule": 2, "type": "equivalent", "target": "0c17e02f698dc60a4c3ff762796f0a7f", "evidence": {"same_day": true, "patch_ids": ["be8272a81c28ebdf12c66d1c6ab05685"], "statement_hash": "abc7e610f491a4ce631c4e62316b1f9bd718c7e9e581a2f07ba12774f5db10eb"}}, {"rule": 2, "type": "equivalent", "target": "268b9e4fbdc7682f30cd928e974932c2", "evidence": {"same_day": true, "patch_ids": ["be8272a81c28ebdf12c66d1c6ab05685"], "statement_hash": "abc7e610f491a4ce631c4e62316b1f9bd718c7e9e581a2f07ba12774f5db10eb"}}, {"rule": 2, "type": "equivalent", "target": "467be2f83ba0b7e841b7fca2b8c0a0af", "evidence": {"same_day": true, "patch_ids": ["be8272a81c28ebdf12c66d1c6ab05685"], "statement_hash": "abc7e610f491a4ce631c4e62316b1f9bd718c7e9e581a2f07ba12774f5db10eb"}}, {"rule": 2, "type": "equivalent", "target": "b3f796774144a4fd6c7ec84d799fce9c", "evidence": {"same_day": true, "patch_ids": ["be8272a81c28ebdf12c66d1c6ab05685"], "statement_hash": "abc7e610f491a4ce631c4e62316b1f9bd718c7e9e581a2f07ba12774f5db10eb"}}]}}, {"id": "18.6-04ef095d0d14ee39", "source_entry_id": "18.6/changes/080", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Prevent creation of dangling object dependencies by acquiring a shared lock on any object being depended on", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-3ecac11b2752e81b", "source_entry_id": "17.11/changes/064", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Prevent creation of dangling object dependencies by acquiring a shared lock on any object being depended on"}], "entry": {"id": "18.6-04ef095d0d14ee39", "cves": [], "html": "Prevent creation of dangling object dependencies by acquiring a shared lock on any object being depended on (Bertrand Drouvot) § §
\nThe shared lock will conflict with any attempt to drop the depended-on object, eliminating the race condition that formerly existed. For example, if one session drops a schema (that appears empty to it) concurrently with some other session creating a function in that schema, previously both transactions could commit, leaving an invalid function definition behind. Now, one transaction or the other will fail.
", "text": "Prevent creation of dangling object dependencies by acquiring a shared lock on any object being depended on (Bertrand Drouvot) § § The shared lock will conflict with any attempt to drop the depended-on object, eliminating the race condition that formerly existed. For example, if one session drops a schema (that appears empty to it) concurrently with some other session creating a function in that schema, previously both transactions could commit, leaving an invalid function definition behind. Now, one transaction or the other will fail.", "title": "Prevent creation of dangling object dependencies by acquiring a shared lock on any object being depended on", "commits": ["c8cd3d697", "f9d5a52da"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "8504063374e840b20b0a001143714b29ff53124b6c9ee7ed57542adbbe725847", "section_path": ["Changes"], "commit_groups": [["2fbb21170", "3a9909eda", "5100bdbd3", "5fa137727", "c8cd3d697", "d9bc0d96c"], ["36b6ed260", "c1588f92a", "d44cd4674", "ef3d7b15e", "f9d5a52da", "fd93ee100"]], "identity_text": "Prevent creation of dangling object dependencies by acquiring a shared lock on any object being depended on (Bertrand Drouvot) The shared lock will conflict with any attempt to drop the depended-on object, eliminating the race condition that formerly existed. For example, if one session drops a schema (that appears empty to it) concurrently with some other session creating a function in that schema, previously both transactions could commit, leaving an invalid function definition behind. Now, one transaction or the other will fail.", "commit_aliases": ["2fbb21170", "36b6ed260", "3a9909eda", "5100bdbd3", "5fa137727", "c1588f92a", "c8cd3d697", "d44cd4674", "d9bc0d96c", "ef3d7b15e", "f9d5a52da", "fd93ee100"], "source_commits": ["c8cd3d697", "f9d5a52da"], "source_entry_id": "18.6/changes/080", "db_id": "a34abdf13c3a75b01325176fd494ce54", "patch_ids": ["6536cf91f14cf539ab4bd08602032b89", "aca7f5e76462423a64bce89519f8b4ca"], "statement_hash": "aabd3d9b6b1a0460624c086ca1a5f2223aec25bb342c2883b18a435de52ba98c", "relations": [{"rule": 2, "type": "equivalent", "target": "744925e5c1491a9c1e34c5d45e2c5ffd", "evidence": {"same_day": true, "patch_ids": ["6536cf91f14cf539ab4bd08602032b89", "aca7f5e76462423a64bce89519f8b4ca"], "statement_hash": "aabd3d9b6b1a0460624c086ca1a5f2223aec25bb342c2883b18a435de52ba98c"}}, {"rule": 2, "type": "equivalent", "target": "a9f65b357e29d3c7c477cf734deef532", "evidence": {"same_day": true, "patch_ids": ["6536cf91f14cf539ab4bd08602032b89", "aca7f5e76462423a64bce89519f8b4ca"], "statement_hash": "aabd3d9b6b1a0460624c086ca1a5f2223aec25bb342c2883b18a435de52ba98c"}}, {"rule": 2, "type": "equivalent", "target": "e1119f78a9d166b823f798e0194d35f4", "evidence": {"same_day": true, "patch_ids": ["6536cf91f14cf539ab4bd08602032b89", "aca7f5e76462423a64bce89519f8b4ca"], "statement_hash": "aabd3d9b6b1a0460624c086ca1a5f2223aec25bb342c2883b18a435de52ba98c"}}, {"rule": 2, "type": "equivalent", "target": "e811cff0335c3ca435753578de40cbd3", "evidence": {"same_day": true, "patch_ids": ["6536cf91f14cf539ab4bd08602032b89", "aca7f5e76462423a64bce89519f8b4ca"], "statement_hash": "aabd3d9b6b1a0460624c086ca1a5f2223aec25bb342c2883b18a435de52ba98c"}}]}}, {"id": "18.6-020cfc417a109d87", "source_entry_id": "18.6/changes/081", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix race condition in conflict detection for SERIALIZABLE isolation mode", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-869506b0934d2991", "source_entry_id": "17.11/changes/065", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix race condition in conflict detection for SERIALIZABLE isolation mode"}], "entry": {"id": "18.6-020cfc417a109d87", "cves": [], "html": "Fix race condition in conflict detection for SERIALIZABLE isolation mode (Peter Geoghegan) §
A conflict could be missed when examining an initially-empty btree index, allowing failure of serializability due to improperly allowing conflicting transactions to commit.
", "text": "Fix race condition in conflict detection for SERIALIZABLE isolation mode (Peter Geoghegan) § A conflict could be missed when examining an initially-empty btree index, allowing failure of serializability due to improperly allowing conflicting transactions to commit.", "title": "Fix race condition in conflict detection for SERIALIZABLE isolation mode", "commits": ["d560e730e"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "4935166aff045404d175f6177404bfb76452f17de5687028de3dbd95695df263", "section_path": ["Changes"], "commit_groups": [["2aa3c6d1f", "2fc3e1b44", "5d18105ca", "8434c9385", "ce3f19e26", "d560e730e", "e321faaae"]], "identity_text": "Fix race condition in conflict detection for SERIALIZABLE isolation mode (Peter Geoghegan) A conflict could be missed when examining an initially-empty btree index, allowing failure of serializability due to improperly allowing conflicting transactions to commit.", "commit_aliases": ["2aa3c6d1f", "2fc3e1b44", "5d18105ca", "8434c9385", "ce3f19e26", "d560e730e", "e321faaae"], "source_commits": ["d560e730e"], "source_entry_id": "18.6/changes/081", "db_id": "37ab9407c7a4720c042c3c30e616b840", "patch_ids": ["76d6d81d4ce8e28654632817bbc18838"], "statement_hash": "08b20f0b0cc877fd90cf1664195b8bfe906cd38aa76d41fb6a77cbb2ead17297", "relations": [{"rule": 2, "type": "equivalent", "target": "03ed91689e7472f3e2b40c0668a9efe6", "evidence": {"same_day": true, "patch_ids": ["76d6d81d4ce8e28654632817bbc18838"], "statement_hash": "08b20f0b0cc877fd90cf1664195b8bfe906cd38aa76d41fb6a77cbb2ead17297"}}, {"rule": 2, "type": "equivalent", "target": "06c841c7e97c29498c3c18507b648e43", "evidence": {"same_day": true, "patch_ids": ["76d6d81d4ce8e28654632817bbc18838"], "statement_hash": "08b20f0b0cc877fd90cf1664195b8bfe906cd38aa76d41fb6a77cbb2ead17297"}}, {"rule": 2, "type": "equivalent", "target": "8911cf537e3c81e99f223106f705f385", "evidence": {"same_day": true, "patch_ids": ["76d6d81d4ce8e28654632817bbc18838"], "statement_hash": "08b20f0b0cc877fd90cf1664195b8bfe906cd38aa76d41fb6a77cbb2ead17297"}}, {"rule": 2, "type": "equivalent", "target": "a69025df57e9873eeee634c6a24b5f52", "evidence": {"same_day": true, "patch_ids": ["76d6d81d4ce8e28654632817bbc18838"], "statement_hash": "08b20f0b0cc877fd90cf1664195b8bfe906cd38aa76d41fb6a77cbb2ead17297"}}]}}, {"id": "18.6-814e47a6c0f16883", "source_entry_id": "18.6/changes/082", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix race condition in ProcSignalBarrier code", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-0e94152c02ef540a", "source_entry_id": "17.11/changes/066", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix race condition in ProcSignalBarrier code"}], "entry": {"id": "18.6-814e47a6c0f16883", "cves": [], "html": "Fix race condition in ProcSignalBarrier code (Masahiko Sawada) §
\nThis error could result in processes getting stuck, typically after reporting “still waiting for backend with PID nnnn to accept ProcSignalBarrier”.
Fix race conditions when a set of processes that belong to the same lock group exit at the same time (Vlad Lesin) § §
\nThese errors could lead to PANIC aborts, with messages such as “latch already owned”. The issue does not normally arise in regular parallel query, since the leader won't exit before seeing its workers finish; but some extensions reach the problem.
", "text": "Fix race conditions when a set of processes that belong to the same lock group exit at the same time (Vlad Lesin) § § These errors could lead to PANIC aborts, with messages such as “latch already owned”. The issue does not normally arise in regular parallel query, since the leader won't exit before seeing its workers finish; but some extensions reach the problem.", "title": "Fix race conditions when a set of processes that belong to the same lock group exit at the same time", "commits": ["12c9b8b42", "ae08eb168"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "3690c0e45c50bcba3395861167636f0bbdb986d728039e0ebf6dd25961da24f4", "section_path": ["Changes"], "commit_groups": [["12c9b8b42", "4e8edf53f", "84b9d6bce", "db4d12fc9", "e14b4ea4a", "e786fb5aa"], ["563104523", "65d04df60", "8007d1185", "ae08eb168", "d489c4439", "d5cc6df60"]], "identity_text": "Fix race conditions when a set of processes that belong to the same lock group exit at the same time (Vlad Lesin) These errors could lead to PANIC aborts, with messages such as latch already owned. The issue does not normally arise in regular parallel query, since the leader won't exit before seeing its workers finish; but some extensions reach the problem.", "commit_aliases": ["12c9b8b42", "4e8edf53f", "563104523", "65d04df60", "8007d1185", "84b9d6bce", "ae08eb168", "d489c4439", "d5cc6df60", "db4d12fc9", "e14b4ea4a", "e786fb5aa"], "source_commits": ["12c9b8b42", "ae08eb168"], "source_entry_id": "18.6/changes/083", "db_id": "5b2fc7485dc383d08b3d68f5272b2a11", "patch_ids": ["879e5bd994847bca2264dea6ae8e7636", "deebb0acfe2f0b111568661ecf5bdaeb"], "statement_hash": "8d70122ebcc8b017ec76eed632b4e53a2f4e86497efb77268f99f3855284c592", "relations": [{"rule": 2, "type": "equivalent", "target": "2c46dad30462775a825ad96cfb3ffbdf", "evidence": {"same_day": true, "patch_ids": ["879e5bd994847bca2264dea6ae8e7636", "deebb0acfe2f0b111568661ecf5bdaeb"], "statement_hash": "8d70122ebcc8b017ec76eed632b4e53a2f4e86497efb77268f99f3855284c592"}}, {"rule": 2, "type": "equivalent", "target": "62cbccb23171427808fec1301b0ac804", "evidence": {"same_day": true, "patch_ids": ["879e5bd994847bca2264dea6ae8e7636", "deebb0acfe2f0b111568661ecf5bdaeb"], "statement_hash": "8d70122ebcc8b017ec76eed632b4e53a2f4e86497efb77268f99f3855284c592"}}, {"rule": 2, "type": "equivalent", "target": "edd683109ce0095065cd3a04ab6b5136", "evidence": {"same_day": true, "patch_ids": ["879e5bd994847bca2264dea6ae8e7636", "deebb0acfe2f0b111568661ecf5bdaeb"], "statement_hash": "8d70122ebcc8b017ec76eed632b4e53a2f4e86497efb77268f99f3855284c592"}}, {"rule": 2, "type": "equivalent", "target": "f2fcbfdff352b775c9b16fc62d0649b5", "evidence": {"same_day": true, "patch_ids": ["879e5bd994847bca2264dea6ae8e7636", "deebb0acfe2f0b111568661ecf5bdaeb"], "statement_hash": "8d70122ebcc8b017ec76eed632b4e53a2f4e86497efb77268f99f3855284c592"}}]}}, {"id": "18.6-591cce0db8214715", "source_entry_id": "18.6/changes/084", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix WAL logging of operations that clear bits in tables' visibility maps", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-3f8c2715fb02eef2", "source_entry_id": "17.11/changes/068", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix WAL logging of operations that clear bits in tables' visibility maps"}], "entry": {"id": "18.6-591cce0db8214715", "cves": [], "html": "Fix WAL logging of operations that clear bits in tables' visibility maps (Melanie Plageman, Andres Freund) § § §
\nSuch VM changes were missed by the WAL summarizer, potentially leading to incorrect incremental backups. We also failed to log full-page images of such VM pages when needed, potentially allowing torn page writes to go uncorrected. This could lead to misbehavior later, such as wrong results from index-only scans.
", "text": "Fix WAL logging of operations that clear bits in tables' visibility maps (Melanie Plageman, Andres Freund) § § § Such VM changes were missed by the WAL summarizer, potentially leading to incorrect incremental backups. We also failed to log full-page images of such VM pages when needed, potentially allowing torn page writes to go uncorrected. This could lead to misbehavior later, such as wrong results from index-only scans.", "title": "Fix WAL logging of operations that clear bits in tables' visibility maps", "commits": ["4d7feebfb", "d0fb1da21", "f581fa729"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "b95470ab8772f7064d787af7fca17722a43fdbb85ec0339e7e7f3a0b846c0f87", "section_path": ["Changes"], "commit_groups": [["067213430", "4d7feebfb", "5174d157a", "9171f77db"], ["10911fde0", "56bf5fa5d", "7edec8b57", "d0fb1da21"], ["b01c31eef", "c0d9864f5", "ed62d26ca", "f581fa729"]], "identity_text": "Fix WAL logging of operations that clear bits in tables' visibility maps (Melanie Plageman, Andres Freund) Such VM changes were missed by the WAL summarizer, potentially leading to incorrect incremental backups. We also failed to log full-page images of such VM pages when needed, potentially allowing torn page writes to go uncorrected. This could lead to misbehavior later, such as wrong results from index-only scans.", "commit_aliases": ["067213430", "10911fde0", "4d7feebfb", "5174d157a", "56bf5fa5d", "7edec8b57", "9171f77db", "b01c31eef", "c0d9864f5", "d0fb1da21", "ed62d26ca", "f581fa729"], "source_commits": ["4d7feebfb", "d0fb1da21", "f581fa729"], "source_entry_id": "18.6/changes/084", "db_id": "9fb751cb38bcd179121b328ba031747e", "patch_ids": ["34adf46d69ca32061b06da3d079a7069", "41df06de615aa532015928409cff3d95", "892803f446e66b4cc097d23f3797a918"], "statement_hash": "06aadf1e9f9cee9405150393ea42bc91f00a02570025c6028daa277cee57c7f3", "relations": [{"rule": 2, "type": "equivalent", "target": "4def260cbd8a4182ec017b70a81b56f5", "evidence": {"same_day": true, "patch_ids": ["34adf46d69ca32061b06da3d079a7069", "41df06de615aa532015928409cff3d95", "892803f446e66b4cc097d23f3797a918"], "statement_hash": "06aadf1e9f9cee9405150393ea42bc91f00a02570025c6028daa277cee57c7f3"}}]}}, {"id": "18.6-2ef24f05b5bd445d", "source_entry_id": "18.6/changes/085", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Prevent WAL summarizer process from getting stuck at a timeline switch", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-aa32892bb54c9a4c", "source_entry_id": "17.11/changes/069", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Prevent WAL summarizer process from getting stuck at a timeline switch"}], "entry": {"id": "18.6-2ef24f05b5bd445d", "cves": [], "html": "Prevent WAL summarizer process from getting stuck at a timeline switch (Robert Haas) § §
", "text": "Prevent WAL summarizer process from getting stuck at a timeline switch (Robert Haas) § §", "title": "Prevent WAL summarizer process from getting stuck at a timeline switch", "commits": ["18f0de6b8", "1d299d6ab"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "875094e4fb85ef4bbd5e3a57e55d80654eef573b8dac8966d60c792eb090e8de", "section_path": ["Changes"], "commit_groups": [["18f0de6b8", "3e8a0c1b0", "499d9eabb", "dfb96277d"], ["1d299d6ab", "8767a10cb", "bdcea66f0", "d28cdf46e"]], "identity_text": "Prevent WAL summarizer process from getting stuck at a timeline switch (Robert Haas)", "commit_aliases": ["18f0de6b8", "1d299d6ab", "3e8a0c1b0", "499d9eabb", "8767a10cb", "bdcea66f0", "d28cdf46e", "dfb96277d"], "source_commits": ["18f0de6b8", "1d299d6ab"], "source_entry_id": "18.6/changes/085", "db_id": "3173f4833a6a0aae8a455f45a5a4568e", "patch_ids": ["508495a1aeae90a13092582478007f0c", "99c5fedfb753eda3ff5558c646f420a7"], "statement_hash": "693f186e16744df775e9c612662444e181a78d71562335513f419c84cb3c35b9", "relations": [{"rule": 2, "type": "equivalent", "target": "6c5349d1b6e45948404ea7876a48dcf9", "evidence": {"same_day": true, "patch_ids": ["508495a1aeae90a13092582478007f0c", "99c5fedfb753eda3ff5558c646f420a7"], "statement_hash": "693f186e16744df775e9c612662444e181a78d71562335513f419c84cb3c35b9"}}]}}, {"id": "18.6-c988b88dbd957c88", "source_entry_id": "18.6/changes/086", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix race with timeline selection in logical decoding during standby promotion", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-563becf7bc3e6dcf", "source_entry_id": "17.11/changes/070", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix race with timeline selection in logical decoding during standby promotion"}], "entry": {"id": "18.6-c988b88dbd957c88", "cves": [], "html": "Fix race with timeline selection in logical decoding during standby promotion (Bertrand Drouvot) § §
\nLogical decoding being performed on the standby could fail with a “requested WAL segment has already been removed” error. A repeat attempt would succeed, so there was no permanent problem but there was an availability hazard.
", "text": "Fix race with timeline selection in logical decoding during standby promotion (Bertrand Drouvot) § § Logical decoding being performed on the standby could fail with a “requested WAL segment has already been removed” error. A repeat attempt would succeed, so there was no permanent problem but there was an availability hazard.", "title": "Fix race with timeline selection in logical decoding during standby promotion", "commits": ["4bff3aa51", "b4bd13850"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "4d311a1b067d67a29744f1d9c2b459818b0b24040c0f3c40c4d5b6745dec9501", "section_path": ["Changes"], "commit_groups": [["16b89ff04", "8cd687c44", "b4bd13850", "eb4e7224a"], ["2a04624da", "4bff3aa51", "a8ee70bd5", "ab5334d8b"], ["d9b49e5b4"]], "identity_text": "Fix race with timeline selection in logical decoding during standby promotion (Bertrand Drouvot) Logical decoding being performed on the standby could fail with a requested WAL segment has already been removed error. A repeat attempt would succeed, so there was no permanent problem but there was an availability hazard.", "commit_aliases": ["16b89ff04", "2a04624da", "4bff3aa51", "8cd687c44", "a8ee70bd5", "ab5334d8b", "b4bd13850", "d9b49e5b4", "eb4e7224a"], "source_commits": ["4bff3aa51", "b4bd13850", "d9b49e5b4"], "source_entry_id": "18.6/changes/086", "db_id": "cfd9fb4fa936abb9c7ef216b4854fb3c", "patch_ids": ["0baec0cbb6545813886061f478d7fe09", "1bbd3b28c72161d54ff8850fb5990a90", "afe572d50b5aa93a1a43ac975df96fa6"], "statement_hash": "b5c88f0e08517e3cf00dd9b3461ec817031530e9f8f05c2cde86c91f4ec8fc51", "relations": [{"rule": 2, "type": "equivalent", "target": "7c127c9b86c4ff620059a798b7b8dda9", "evidence": {"same_day": true, "patch_ids": ["0baec0cbb6545813886061f478d7fe09", "1bbd3b28c72161d54ff8850fb5990a90", "afe572d50b5aa93a1a43ac975df96fa6"], "statement_hash": "b5c88f0e08517e3cf00dd9b3461ec817031530e9f8f05c2cde86c91f4ec8fc51"}}, {"rule": 2, "type": "equivalent", "target": "d6f8670170e47d169eec30b65187d2c4", "evidence": {"same_day": true, "patch_ids": ["0baec0cbb6545813886061f478d7fe09", "1bbd3b28c72161d54ff8850fb5990a90", "afe572d50b5aa93a1a43ac975df96fa6"], "statement_hash": "b5c88f0e08517e3cf00dd9b3461ec817031530e9f8f05c2cde86c91f4ec8fc51"}}]}}, {"id": "18.6-afb05b61d5152a3a", "source_entry_id": "18.6/changes/087", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Avoid exposing a WAL receiver's full connection string during timeline jumps", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-1e3e950c5c9035d8", "source_entry_id": "17.11/changes/071", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Avoid exposing a WAL receiver's full connection string during timeline jumps"}], "entry": {"id": "18.6-afb05b61d5152a3a", "cves": [], "html": "Avoid exposing a WAL receiver's full connection string during timeline jumps (Chao Li) §
\nThe pg_stat_wal_receiver view should show a sanitized version of the connection string, without sensitive data. But it transiently showed the full string when we re-use an existing WAL receiver.
Use run-time checks, not just Asserts, to verify the correct number of columns in tuples received during logical replication (Varik Matevosyan) §
\nA malicious or buggy publisher could send inconsistent numbers of columns. While we could not find a scenario in which this would have serious ill effects, extra caution seems warranted.
", "text": "Use run-time checks, not just Asserts, to verify the correct number of columns in tuples received during logical replication (Varik Matevosyan) § A malicious or buggy publisher could send inconsistent numbers of columns. While we could not find a scenario in which this would have serious ill effects, extra caution seems warranted.", "title": "Use run-time checks, not just Asserts, to verify the correct number of columns in tuples received during logical replication", "commits": ["dc3db3a83"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "9f31c202910443cee93755001261c06de77951acb16b3fbaa7604fd58b7fb29f", "section_path": ["Changes"], "commit_groups": [["15f4e3d0c", "510a05f07", "59759e1a5", "871d4f5b6", "bf7d19be9", "dc3db3a83"]], "identity_text": "Use run-time checks, not just Asserts, to verify the correct number of columns in tuples received during logical replication (Varik Matevosyan) A malicious or buggy publisher could send inconsistent numbers of columns. While we could not find a scenario in which this would have serious ill effects, extra caution seems warranted.", "commit_aliases": ["15f4e3d0c", "510a05f07", "59759e1a5", "871d4f5b6", "bf7d19be9", "dc3db3a83"], "source_commits": ["dc3db3a83"], "source_entry_id": "18.6/changes/088", "db_id": "29b7d5b8d289c2e83357b4b3887c6ece", "patch_ids": ["8665f0efb53857b1f65d3aab55fce701"], "statement_hash": "ccb9933f82e897841fcc7799b27c7cb46784658d50590f121d691ba4eb1ab215", "relations": [{"rule": 2, "type": "equivalent", "target": "2bec14054822093ac2f6b8e098cf50ef", "evidence": {"same_day": true, "patch_ids": ["8665f0efb53857b1f65d3aab55fce701"], "statement_hash": "ccb9933f82e897841fcc7799b27c7cb46784658d50590f121d691ba4eb1ab215"}}, {"rule": 2, "type": "equivalent", "target": "3d36fdfc273db605a521f97942cc7c8b", "evidence": {"same_day": true, "patch_ids": ["8665f0efb53857b1f65d3aab55fce701"], "statement_hash": "ccb9933f82e897841fcc7799b27c7cb46784658d50590f121d691ba4eb1ab215"}}, {"rule": 2, "type": "equivalent", "target": "52499b2c374ab99a8520d4e208b224ca", "evidence": {"same_day": true, "patch_ids": ["8665f0efb53857b1f65d3aab55fce701"], "statement_hash": "ccb9933f82e897841fcc7799b27c7cb46784658d50590f121d691ba4eb1ab215"}}, {"rule": 2, "type": "equivalent", "target": "b984d160c74d462df46c0818a7351ddb", "evidence": {"same_day": true, "patch_ids": ["8665f0efb53857b1f65d3aab55fce701"], "statement_hash": "ccb9933f82e897841fcc7799b27c7cb46784658d50590f121d691ba4eb1ab215"}}]}}, {"id": "18.6-9e33f830eed35c6f", "source_entry_id": "18.6/changes/089", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Clean up quoting of string parameters within constructed replication commands", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-f6a7585b485a41e6", "source_entry_id": "17.11/changes/073", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Clean up quoting of string parameters within constructed replication commands"}], "entry": {"id": "18.6-9e33f830eed35c6f", "cves": [], "html": "Clean up quoting of string parameters within constructed replication commands (Tom Lane) §
\nVarious places that generate replication commands were not being adequately careful about quoting replication slot names and other parameters that need to be inserted into those commands. This could result in unexpected syntax errors in those commands. In principle, a crafted replication slot name could result in SQL injection; but such a scenario seems very unlikely to occur in practice, since replication operations can only be invoked by highly-privileged users and there is no reason for them to use a slot name coming from an untrustworthy source.
", "text": "Clean up quoting of string parameters within constructed replication commands (Tom Lane) § Various places that generate replication commands were not being adequately careful about quoting replication slot names and other parameters that need to be inserted into those commands. This could result in unexpected syntax errors in those commands. In principle, a crafted replication slot name could result in SQL injection; but such a scenario seems very unlikely to occur in practice, since replication operations can only be invoked by highly-privileged users and there is no reason for them to use a slot name coming from an untrustworthy source.", "title": "Clean up quoting of string parameters within constructed replication commands", "commits": ["abb582555"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "eff14326812c72ae4f764c7f658e5ae7c0bc9c099d1151414e565b9da16e397f", "section_path": ["Changes"], "commit_groups": [["14810cc0d", "26d6c19d0", "2a00840e8", "819e5b964", "a75bd485b", "abb582555"]], "identity_text": "Clean up quoting of string parameters within constructed replication commands (Tom Lane) Various places that generate replication commands were not being adequately careful about quoting replication slot names and other parameters that need to be inserted into those commands. This could result in unexpected syntax errors in those commands. In principle, a crafted replication slot name could result in SQL injection; but such a scenario seems very unlikely to occur in practice, since replication operations can only be invoked by highly-privileged users and there is no reason for them to use a slot name coming from an untrustworthy source.", "commit_aliases": ["14810cc0d", "26d6c19d0", "2a00840e8", "819e5b964", "a75bd485b", "abb582555"], "source_commits": ["abb582555"], "source_entry_id": "18.6/changes/089", "db_id": "1ef980c1780b85528850bbdd9466fa41", "patch_ids": ["32ecc5c79c988e036daa92766ab9c826"], "statement_hash": "247fbb71eedfaa36fb21d3377adab99beeefb9b4863ba98c464369fe5a6bc0fa", "relations": [{"rule": 2, "type": "equivalent", "target": "492d74031b46a2dbdba89517c2392411", "evidence": {"same_day": true, "patch_ids": ["32ecc5c79c988e036daa92766ab9c826"], "statement_hash": "247fbb71eedfaa36fb21d3377adab99beeefb9b4863ba98c464369fe5a6bc0fa"}}, {"rule": 2, "type": "equivalent", "target": "54ed2b1cad03859f062c5ae13dc62693", "evidence": {"same_day": true, "patch_ids": ["32ecc5c79c988e036daa92766ab9c826"], "statement_hash": "247fbb71eedfaa36fb21d3377adab99beeefb9b4863ba98c464369fe5a6bc0fa"}}, {"rule": 2, "type": "equivalent", "target": "74c4a1b4a808ecb95dfae29020191080", "evidence": {"same_day": true, "patch_ids": ["32ecc5c79c988e036daa92766ab9c826"], "statement_hash": "247fbb71eedfaa36fb21d3377adab99beeefb9b4863ba98c464369fe5a6bc0fa"}}, {"rule": 2, "type": "equivalent", "target": "de678a747a30bf549de927b53ebbc3e7", "evidence": {"same_day": true, "patch_ids": ["32ecc5c79c988e036daa92766ab9c826"], "statement_hash": "247fbb71eedfaa36fb21d3377adab99beeefb9b4863ba98c464369fe5a6bc0fa"}}]}}, {"id": "18.6-9c7f709d1f862457", "source_entry_id": "18.6/changes/090", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix logical decoding of empty prepared transactions", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-4fcd3ca4da51d952", "source_entry_id": "17.11/changes/074", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix logical decoding of empty prepared transactions"}], "entry": {"id": "18.6-9c7f709d1f862457", "cves": [], "html": "Fix logical decoding of empty prepared transactions (Masahiko Sawada) §
\nA prepared transaction that did not cause any decodable updates could result in sending COMMIT/ROLLBACK PREPARED to the output plugin with no preceding PREPARE. For the built-in subscriber this breaks replication, and other plugins will probably not like it either.
Fix corruption of unlogged sequences after standby promotion (Fujii Masao) §
\nPreviously, if an unlogged sequence was created on the primary and replicated to a standby, accessing the sequence after promoting the standby could fail with “bad magic number in sequence” or related errors.
", "text": "Fix corruption of unlogged sequences after standby promotion (Fujii Masao) § Previously, if an unlogged sequence was created on the primary and replicated to a standby, accessing the sequence after promoting the standby could fail with “bad magic number in sequence” or related errors.", "title": "Fix corruption of unlogged sequences after standby promotion", "commits": ["627605713"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "30d41fa84a95a15e9368578cde5b1e576f99f5b28764feb0fded6f9da9b5faa9", "section_path": ["Changes"], "commit_groups": [["22af34b98", "627605713", "8e684ce11", "913d3b610", "a1ed6a9a0", "d2980067b"]], "identity_text": "Fix corruption of unlogged sequences after standby promotion (Fujii Masao) Previously, if an unlogged sequence was created on the primary and replicated to a standby, accessing the sequence after promoting the standby could fail with bad magic number in sequence or related errors.", "commit_aliases": ["22af34b98", "627605713", "8e684ce11", "913d3b610", "a1ed6a9a0", "d2980067b"], "source_commits": ["627605713"], "source_entry_id": "18.6/changes/091", "db_id": "7c75fcad7f434b0760cdb29e86f36c46", "patch_ids": ["0c00c75b81c9cf4e2c7dd727d7f47148"], "statement_hash": "6ef22cc70bed7a3bdbb01c79c02e183283e72e3ea1060f614fc65f0d30467462", "relations": [{"rule": 2, "type": "equivalent", "target": "04e99de2d6b9c7c2dbe0bac4e30b6b62", "evidence": {"same_day": true, "patch_ids": ["0c00c75b81c9cf4e2c7dd727d7f47148"], "statement_hash": "6ef22cc70bed7a3bdbb01c79c02e183283e72e3ea1060f614fc65f0d30467462"}}, {"rule": 2, "type": "equivalent", "target": "1ce08b2128763f685c989c7f545e1b3e", "evidence": {"same_day": true, "patch_ids": ["0c00c75b81c9cf4e2c7dd727d7f47148"], "statement_hash": "6ef22cc70bed7a3bdbb01c79c02e183283e72e3ea1060f614fc65f0d30467462"}}, {"rule": 2, "type": "equivalent", "target": "ecc31612cc8e203d9211831d84c3f264", "evidence": {"same_day": true, "patch_ids": ["0c00c75b81c9cf4e2c7dd727d7f47148"], "statement_hash": "6ef22cc70bed7a3bdbb01c79c02e183283e72e3ea1060f614fc65f0d30467462"}}]}}, {"id": "18.6-e75bd84b8c02b997", "source_entry_id": "18.6/changes/092", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix cascading standby reconnect failure after archive fallback", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-8291f394c20dacdc", "source_entry_id": "17.11/changes/076", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix cascading standby reconnect failure after archive fallback"}], "entry": {"id": "18.6-e75bd84b8c02b997", "cves": [], "html": "Fix cascading standby reconnect failure after archive fallback (Marco Nenciarini) §
\nA cascading standby could fail to reconnect to its upstream standby with “requested starting point ... is ahead of the WAL flush position” after falling back to archive recovery.
", "text": "Fix cascading standby reconnect failure after archive fallback (Marco Nenciarini) § A cascading standby could fail to reconnect to its upstream standby with “requested starting point ... is ahead of the WAL flush position” after falling back to archive recovery.", "title": "Fix cascading standby reconnect failure after archive fallback", "commits": ["331016322"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "5a51be4cd8f245f23d1e5e10bb08538693a17619e15c5a49adfcc92b3d850c4e", "section_path": ["Changes"], "commit_groups": [["2cf28d1b9", "331016322", "5dbeb69bc", "5fb3c6389", "8f64cc83f", "b614de487", "bef46aed3"]], "identity_text": "Fix cascading standby reconnect failure after archive fallback (Marco Nenciarini) A cascading standby could fail to reconnect to its upstream standby with requested starting point ... is ahead of the WAL flush position after falling back to archive recovery.", "commit_aliases": ["2cf28d1b9", "331016322", "5dbeb69bc", "5fb3c6389", "8f64cc83f", "b614de487", "bef46aed3"], "source_commits": ["331016322"], "source_entry_id": "18.6/changes/092", "db_id": "1ba572e4a9f5584ecce320e293d4b258", "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "statement_hash": "fb1d8ff1de50924ae1113199938a0ff6d45296b275bab29a749f5176ddbc64ad", "relations": [{"rule": 2, "type": "related", "target": "027ccc17f71deb2b38e14fc8cc82dccd", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "related", "target": "1b34d3e2b18d75096fd2914d3673446c", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "related", "target": "70897dba323af27792543b2311799668", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "equivalent", "target": "771fa954f9b22168a0764dc12074dadb", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "statement_hash": "fb1d8ff1de50924ae1113199938a0ff6d45296b275bab29a749f5176ddbc64ad", "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "equivalent", "target": "b17ef22f538327cabf0726e1b3f902cc", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "statement_hash": "fb1d8ff1de50924ae1113199938a0ff6d45296b275bab29a749f5176ddbc64ad", "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "related", "target": "bf82a2510c4dfe4309435e9bce0ab3a4", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "equivalent", "target": "bfa74492dd2c8ed5f4b0a4321cb63c85", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "statement_hash": "fb1d8ff1de50924ae1113199938a0ff6d45296b275bab29a749f5176ddbc64ad", "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "related", "target": "bfa88fa3d381bbc9b7ee7a8614ea363c", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}, {"rule": 2, "type": "equivalent", "target": "ea24770278021c00f25a8b13bceb2a2c", "evidence": {"same_day": true, "patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"], "statement_hash": "fb1d8ff1de50924ae1113199938a0ff6d45296b275bab29a749f5176ddbc64ad", "ambiguous_patch_ids": ["8d6dc29f16ca43220ac734ee400f5ee9"]}}]}}, {"id": "18.6-d53aeb4078876f26", "source_entry_id": "18.6/changes/094", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Do not try to clear pg_database.dathasloginevt locally on a standby server", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-4ea3a29628f7f415", "source_entry_id": "17.11/changes/077", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Do not try to clear pg_database.dathasloginevt locally on a standby server"}], "entry": {"id": "18.6-d53aeb4078876f26", "cves": [], "html": "Do not try to clear pg_database.dathasloginevt locally on a standby server (Ayush Tiwari) §
Event trigger cleanup tried to perform that action on standby servers as well as the primary. That can't work on a standby, and there's no need anyway since replay of the primary's database change will soon fix it.
", "text": "Do not try to clear pg_database.dathasloginevt locally on a standby server (Ayush Tiwari) § Event trigger cleanup tried to perform that action on standby servers as well as the primary. That can't work on a standby, and there's no need anyway since replay of the primary's database change will soon fix it.", "title": "Do not try to clear pg_database.dathasloginevt locally on a standby server", "commits": ["97b5c5aaa"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "7dedca87b69ef21715aa2679b45381940636ac8d0716019fb33eca7ea306fdfb", "section_path": ["Changes"], "commit_groups": [["4a375527a", "97b5c5aaa", "bec61f593"]], "identity_text": "Do not try to clear pg_database.dathasloginevt locally on a standby server (Ayush Tiwari) Event trigger cleanup tried to perform that action on standby servers as well as the primary. That can't work on a standby, and there's no need anyway since replay of the primary's database change will soon fix it.", "commit_aliases": ["4a375527a", "97b5c5aaa", "bec61f593"], "source_commits": ["97b5c5aaa"], "source_entry_id": "18.6/changes/094", "db_id": "c7c89eea0ca114afbedbf0cfbae711f9", "patch_ids": ["4ce4f54c8bf735435a0cd83d5e3fd94c"], "statement_hash": "ccdeea440cff75c363fd3daa73d137e4deed890abd48b629fa6387377abac755", "relations": [{"rule": 2, "type": "equivalent", "target": "2652e45990dd9ead74f7cb1a60cd06ae", "evidence": {"same_day": true, "patch_ids": ["4ce4f54c8bf735435a0cd83d5e3fd94c"], "statement_hash": "ccdeea440cff75c363fd3daa73d137e4deed890abd48b629fa6387377abac755"}}]}}, {"id": "18.6-da8598a35476aae4", "source_entry_id": "18.6/changes/095", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Avoid race condition while dropping obsolete replication slots", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-5aeb772ab7b96772", "source_entry_id": "17.11/changes/078", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Avoid race condition while dropping obsolete replication slots"}], "entry": {"id": "18.6-da8598a35476aae4", "cves": [], "html": "Avoid race condition while dropping obsolete replication slots (Xuneng Zhou) §
\nAn incorrect unlock and log message could occur if another session immediately re-used the dropped slot's shared-memory entry.
", "text": "Avoid race condition while dropping obsolete replication slots (Xuneng Zhou) § An incorrect unlock and log message could occur if another session immediately re-used the dropped slot's shared-memory entry.", "title": "Avoid race condition while dropping obsolete replication slots", "commits": ["08458bcae"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "cf6d11cd5580220ca35ddb16dd3a29615a1ef8c87cd71658da7e80f82c77be63", "section_path": ["Changes"], "commit_groups": [["08458bcae", "bdae2c20e", "ea834d747"]], "identity_text": "Avoid race condition while dropping obsolete replication slots (Xuneng Zhou) An incorrect unlock and log message could occur if another session immediately re-used the dropped slot's shared-memory entry.", "commit_aliases": ["08458bcae", "bdae2c20e", "ea834d747"], "source_commits": ["08458bcae"], "source_entry_id": "18.6/changes/095", "db_id": "3dd18331742596637d053910b38a1f16", "patch_ids": ["c73474c335bb9d2b86b6bc7565e6f72b"], "statement_hash": "14c10b585f72cec70dc64da094d3d2d2e80cef7b71ab92442a40f2f70c386a62", "relations": [{"rule": 2, "type": "equivalent", "target": "2724a08367b4dc82b3441236c9f9b14b", "evidence": {"same_day": true, "patch_ids": ["c73474c335bb9d2b86b6bc7565e6f72b"], "statement_hash": "14c10b585f72cec70dc64da094d3d2d2e80cef7b71ab92442a40f2f70c386a62"}}]}}, {"id": "18.6-63934e389520e7b8", "source_entry_id": "18.6/changes/096", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Avoid race condition while dropping ephemeral replication slots", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-1bc3f286c6ac2176", "source_entry_id": "17.11/changes/079", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Avoid race condition while dropping ephemeral replication slots"}], "entry": {"id": "18.6-63934e389520e7b8", "cves": [], "html": "Avoid race condition while dropping ephemeral replication slots (Zhijie Hou) §
\nThe slot-releasing code performed some additional updates to the replication slot's shared-memory entry after releasing the slot. This is unsafe since another session could immediately re-use the dropped slot's shared-memory entry. Skip those updates in the case of an ephemeral slot.
", "text": "Avoid race condition while dropping ephemeral replication slots (Zhijie Hou) § The slot-releasing code performed some additional updates to the replication slot's shared-memory entry after releasing the slot. This is unsafe since another session could immediately re-use the dropped slot's shared-memory entry. Skip those updates in the case of an ephemeral slot.", "title": "Avoid race condition while dropping ephemeral replication slots", "commits": ["f833c9207"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "27fbb2571967acc614030a8a722348f6483bb4a253dea242ebe2db84806d008d", "section_path": ["Changes"], "commit_groups": [["080d61f07", "51e79222c", "968c50845", "a4eb59d40", "f2081a780", "f833c9207"]], "identity_text": "Avoid race condition while dropping ephemeral replication slots (Zhijie Hou) The slot-releasing code performed some additional updates to the replication slot's shared-memory entry after releasing the slot. This is unsafe since another session could immediately re-use the dropped slot's shared-memory entry. Skip those updates in the case of an ephemeral slot.", "commit_aliases": ["080d61f07", "51e79222c", "968c50845", "a4eb59d40", "f2081a780", "f833c9207"], "source_commits": ["f833c9207"], "source_entry_id": "18.6/changes/096", "db_id": "e7a4717de56195de8e84ae36133e6f25", "patch_ids": ["a917b168697862cb05827b9e9d804879"], "statement_hash": "87055d6044521ae3f6b6a74d5c840e75e79be3ee687ddbb92cb366dcb1601282", "relations": [{"rule": 2, "type": "equivalent", "target": "56d06487f4f5f34eaa3c2bcb9a9adcec", "evidence": {"same_day": true, "patch_ids": ["a917b168697862cb05827b9e9d804879"], "statement_hash": "87055d6044521ae3f6b6a74d5c840e75e79be3ee687ddbb92cb366dcb1601282"}}, {"rule": 2, "type": "equivalent", "target": "68414efdd4fd28ffb448691fcc350390", "evidence": {"same_day": true, "patch_ids": ["a917b168697862cb05827b9e9d804879"], "statement_hash": "87055d6044521ae3f6b6a74d5c840e75e79be3ee687ddbb92cb366dcb1601282"}}, {"rule": 2, "type": "equivalent", "target": "acb52269a9ab57fd523cb58a71e121ec", "evidence": {"same_day": true, "patch_ids": ["a917b168697862cb05827b9e9d804879"], "statement_hash": "87055d6044521ae3f6b6a74d5c840e75e79be3ee687ddbb92cb366dcb1601282"}}, {"rule": 2, "type": "equivalent", "target": "f11ac7346f20210841ca22799f957bad", "evidence": {"same_day": true, "patch_ids": ["a917b168697862cb05827b9e9d804879"], "statement_hash": "87055d6044521ae3f6b6a74d5c840e75e79be3ee687ddbb92cb366dcb1601282"}}]}}, {"id": "18.6-caa7677e59388ffc", "source_entry_id": "18.6/changes/097", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix stale progress reports during logical replication table synchronization", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-502303232ec37c57", "source_entry_id": "17.11/changes/080", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix stale progress reports during logical replication table synchronization"}], "entry": {"id": "18.6-caa7677e59388ffc", "cves": [], "html": "Fix stale progress reports during logical replication table synchronization (Shinya Kato) §
\nPreviously, the pg_stat_progress_copy view in the subscriber would continue to show the initial COPY operation as active even after the data copy had finished. The stale entry remained visible until synchronization caught up with the publisher.
Clear base backup progress on backup failure (Chao Li) § §
\nPreviously the pg_stat_progress_basebackup view would continue to show a stale progress entry after a failure, until the replication client disconnected. pg_basebackup normally disconnects immediately, but other clients might not.
Fix possible PANIC due to concurrent drop of pgstats entries when track_functions is enabled (Sami Imseih, Michael Paquier) § § §
Clean up broken local pgstats entry after failing to obtain space for the corresponding shared hashtable entry (Niall Newman) §
\nFailure to do this led to a null-pointer dereference the next time the local entry was used.
", "text": "Clean up broken local pgstats entry after failing to obtain space for the corresponding shared hashtable entry (Niall Newman) § Failure to do this led to a null-pointer dereference the next time the local entry was used.", "title": "Clean up broken local pgstats entry after failing to obtain space for the corresponding shared hashtable entry", "commits": ["2fd8d45ec"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "ae21d24d93211a6397408fa1c2d59a596a32104ae42e7db4a2a7436bcdd24769", "section_path": ["Changes"], "commit_groups": [["10e20e59e", "2fd8d45ec", "4069df21b", "636bcd6a5", "89fc6a7c1", "fc9283b21"]], "identity_text": "Clean up broken local pgstats entry after failing to obtain space for the corresponding shared hashtable entry (Niall Newman) Failure to do this led to a null-pointer dereference the next time the local entry was used.", "commit_aliases": ["10e20e59e", "2fd8d45ec", "4069df21b", "636bcd6a5", "89fc6a7c1", "fc9283b21"], "source_commits": ["2fd8d45ec"], "source_entry_id": "18.6/changes/100", "db_id": "69bb916ea3e2500fcf1ca6568c60960f", "patch_ids": ["073249ed6bcae15bb6d4063aa8558bab"], "statement_hash": "c60eb3598315d881be3eccb1a6430b61a597e0457159bd9304d33bd0c753b70e", "relations": [{"rule": 2, "type": "equivalent", "target": "1afc7388a3b74ce2c49cb081c26f6f41", "evidence": {"same_day": true, "patch_ids": ["073249ed6bcae15bb6d4063aa8558bab"], "statement_hash": "c60eb3598315d881be3eccb1a6430b61a597e0457159bd9304d33bd0c753b70e"}}, {"rule": 2, "type": "equivalent", "target": "65cb52740b6d4b79d67968be77af89f3", "evidence": {"same_day": true, "patch_ids": ["073249ed6bcae15bb6d4063aa8558bab"], "statement_hash": "c60eb3598315d881be3eccb1a6430b61a597e0457159bd9304d33bd0c753b70e"}}, {"rule": 2, "type": "equivalent", "target": "b6f5540e817eacbe3e2ce2803c428998", "evidence": {"same_day": true, "patch_ids": ["073249ed6bcae15bb6d4063aa8558bab"], "statement_hash": "c60eb3598315d881be3eccb1a6430b61a597e0457159bd9304d33bd0c753b70e"}}]}}, {"id": "18.6-2efca855d8fe72b9", "source_entry_id": "18.6/changes/102", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "In PL/Perl, avoid NULL pointer dereference crash when working with an invalid PostgreSQL::InServer::ARRAY object", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-df7c413d42462d43", "source_entry_id": "17.11/changes/084", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "In PL/Perl, avoid NULL pointer dereference crash when working with an invalid PostgreSQL::InServer::ARRAY object"}], "entry": {"id": "18.6-2efca855d8fe72b9", "cves": [], "html": "In PL/Perl, avoid NULL pointer dereference crash when working with an invalid PostgreSQL::InServer::ARRAY object (Xing Guo) §
In PL/Python, properly check for errors when working with sequence and mapping objects (Richard Guo) §
\nPreviously, a broken object or an unhandled exception could result in a NULL pointer dereference crash.
", "text": "In PL/Python, properly check for errors when working with sequence and mapping objects (Richard Guo) § Previously, a broken object or an unhandled exception could result in a NULL pointer dereference crash.", "title": "In PL/Python, properly check for errors when working with sequence and mapping objects", "commits": ["53482fcb9"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "c779f97703863e26c6b6c406b53da7e717ecf8ef2e2938a212dac1d15ff7c366", "section_path": ["Changes"], "commit_groups": [["0b7719f74", "12bff46ff", "3dc59c173", "53482fcb9", "8612f0b7c", "e92f23bde"], ["309dc4526"]], "identity_text": "In PL/Python, properly check for errors when working with sequence and mapping objects (Richard Guo) Previously, a broken object or an unhandled exception could result in a NULL pointer dereference crash.", "commit_aliases": ["0b7719f74", "12bff46ff", "309dc4526", "3dc59c173", "53482fcb9", "8612f0b7c", "e92f23bde"], "source_commits": ["309dc4526", "53482fcb9"], "source_entry_id": "18.6/changes/103", "db_id": "c6334af88dcf8bb00a0c24becb0804c2", "patch_ids": ["82aeda458da615307371e8d49ed0abdd", "a96949fcfb8c6bac8cc1705ad8aa548e"], "statement_hash": "33d469b3040d6c202f91bb0448f11a09e5ddae64c76bb00e48ee5634543c64ee", "relations": [{"rule": 2, "type": "equivalent", "target": "1bcdb1bad2833f07d4dbdd7f3fd25692", "evidence": {"same_day": true, "patch_ids": ["82aeda458da615307371e8d49ed0abdd", "a96949fcfb8c6bac8cc1705ad8aa548e"], "statement_hash": "33d469b3040d6c202f91bb0448f11a09e5ddae64c76bb00e48ee5634543c64ee"}}, {"rule": 2, "type": "equivalent", "target": "5ee9ccfc012c4ede5db692562772a752", "evidence": {"same_day": true, "patch_ids": ["82aeda458da615307371e8d49ed0abdd", "a96949fcfb8c6bac8cc1705ad8aa548e"], "statement_hash": "33d469b3040d6c202f91bb0448f11a09e5ddae64c76bb00e48ee5634543c64ee"}}, {"rule": 2, "type": "equivalent", "target": "7c536b903c2b846285e39de4051f4dda", "evidence": {"same_day": true, "patch_ids": ["82aeda458da615307371e8d49ed0abdd", "a96949fcfb8c6bac8cc1705ad8aa548e"], "statement_hash": "33d469b3040d6c202f91bb0448f11a09e5ddae64c76bb00e48ee5634543c64ee"}}, {"rule": 2, "type": "equivalent", "target": "c7d8f5074aecff2a6209080fb7907c5d", "evidence": {"same_day": true, "patch_ids": ["82aeda458da615307371e8d49ed0abdd", "a96949fcfb8c6bac8cc1705ad8aa548e"], "statement_hash": "33d469b3040d6c202f91bb0448f11a09e5ddae64c76bb00e48ee5634543c64ee"}}]}}, {"id": "18.6-99e20888b0a13dd7", "source_entry_id": "18.6/changes/104", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "In libpq, always drain all pending bytes from the SSL or GSS decryption buffer during pqReadData()", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-ece298bedf647a6a", "source_entry_id": "17.11/changes/086", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "In libpq, always drain all pending bytes from the SSL or GSS decryption buffer during pqReadData()"}], "entry": {"id": "18.6-99e20888b0a13dd7", "cves": [], "html": "In libpq, always drain all pending bytes from the SSL or GSS decryption buffer during pqReadData() (Jacob Champion) § § § §
This avoids edge cases where libpq or its calling application waits for more data to arrive on the socket, but actually all the data has already arrived.
", "text": "In libpq, always drain all pending bytes from the SSL or GSS decryption buffer during pqReadData() (Jacob Champion) § § § § This avoids edge cases where libpq or its calling application waits for more data to arrive on the socket, but actually all the data has already arrived.", "title": "In libpq, always drain all pending bytes from the SSL or GSS decryption buffer during pqReadData()", "commits": ["2167302b7", "27761c015", "87c3a79ea", "bb0a54518"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "ae71f0d838a63f4577ab24237e763fb0ed2276579a52d8ba784b464f53b9dce1", "section_path": ["Changes"], "commit_groups": [["05908afcd", "177a2a2e3", "343594a26", "477bc27a5", "7f8745543", "bb0a54518", "d3888c90a"], ["0958c3ea4", "21a6c69ea", "27761c015", "536512f34", "6243ea6c3", "d293f0345", "f5f569713"], ["17accbe0f", "56988064b", "5ba13f8c0", "7532f2117", "87c3a79ea", "bab0a2db7", "d9eb70c9c"], ["1b018b5d1", "2167302b7", "4ecba7fa3", "c162810a5", "d3f329656", "eeb2940ae", "ffd080d94"]], "identity_text": "In libpq, always drain all pending bytes from the SSL or GSS decryption buffer during pqReadData() (Jacob Champion) This avoids edge cases where libpq or its calling application waits for more data to arrive on the socket, but actually all the data has already arrived.", "commit_aliases": ["05908afcd", "0958c3ea4", "177a2a2e3", "17accbe0f", "1b018b5d1", "2167302b7", "21a6c69ea", "27761c015", "343594a26", "477bc27a5", "4ecba7fa3", "536512f34", "56988064b", "5ba13f8c0", "6243ea6c3", "7532f2117", "7f8745543", "87c3a79ea", "bab0a2db7", "bb0a54518", "c162810a5", "d293f0345", "d3888c90a", "d3f329656", "d9eb70c9c", "eeb2940ae", "f5f569713", "ffd080d94"], "source_commits": ["2167302b7", "27761c015", "87c3a79ea", "bb0a54518"], "source_entry_id": "18.6/changes/104", "db_id": "9168ca39fb7c001030f5bfbd2405a57c", "patch_ids": ["0b824057774a76b143d700730eb3e762", "cc43f5c943c90e1a9e72f73b95bcd867", "dd46de527b9a0334591039f236b5d00d", "fdc82cd35935c0be303512dba39e65fe"], "statement_hash": "8034e64e929755fda7f40131432f08c549be661e2525d6f7be6b5192313374be", "relations": [{"rule": 2, "type": "equivalent", "target": "06f569df58220f97a2f065dcabd4567f", "evidence": {"same_day": true, "patch_ids": ["0b824057774a76b143d700730eb3e762", "cc43f5c943c90e1a9e72f73b95bcd867", "dd46de527b9a0334591039f236b5d00d", "fdc82cd35935c0be303512dba39e65fe"], "statement_hash": "8034e64e929755fda7f40131432f08c549be661e2525d6f7be6b5192313374be"}}, {"rule": 2, "type": "equivalent", "target": "964e3e4ad6311992f04c2399fc930719", "evidence": {"same_day": true, "patch_ids": ["0b824057774a76b143d700730eb3e762", "cc43f5c943c90e1a9e72f73b95bcd867", "dd46de527b9a0334591039f236b5d00d", "fdc82cd35935c0be303512dba39e65fe"], "statement_hash": "8034e64e929755fda7f40131432f08c549be661e2525d6f7be6b5192313374be"}}, {"rule": 2, "type": "equivalent", "target": "c77eeb650517090fade53e3cf3d24d00", "evidence": {"same_day": true, "patch_ids": ["0b824057774a76b143d700730eb3e762", "cc43f5c943c90e1a9e72f73b95bcd867", "dd46de527b9a0334591039f236b5d00d", "fdc82cd35935c0be303512dba39e65fe"], "statement_hash": "8034e64e929755fda7f40131432f08c549be661e2525d6f7be6b5192313374be"}}, {"rule": 2, "type": "equivalent", "target": "f60154c0b7e3d0ae2ae39034edcdc2c1", "evidence": {"same_day": true, "patch_ids": ["0b824057774a76b143d700730eb3e762", "cc43f5c943c90e1a9e72f73b95bcd867", "dd46de527b9a0334591039f236b5d00d", "fdc82cd35935c0be303512dba39e65fe"], "statement_hash": "8034e64e929755fda7f40131432f08c549be661e2525d6f7be6b5192313374be"}}]}}, {"id": "18.6-524638e22a952ee0", "source_entry_id": "18.6/changes/107", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Allow libpq to accept ParameterDescription messages exceeding 30000 bytes", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-a3c4e49ff3e57eff", "source_entry_id": "17.11/changes/087", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Allow libpq to accept ParameterDescription messages exceeding 30000 bytes"}], "entry": {"id": "18.6-524638e22a952ee0", "cves": [], "html": "Allow libpq to accept ParameterDescription messages exceeding 30000 bytes (Ning Sun) §
\nPreviously, this message type was not among those that libpq's validity heuristics believed could be long. The limit resulted in failure for prepared queries having more than 7498 parameters, which is unlikely but supported.
", "text": "Allow libpq to accept ParameterDescription messages exceeding 30000 bytes (Ning Sun) § Previously, this message type was not among those that libpq's validity heuristics believed could be long. The limit resulted in failure for prepared queries having more than 7498 parameters, which is unlikely but supported.", "title": "Allow libpq to accept ParameterDescription messages exceeding 30000 bytes", "commits": ["b1ab4bc52"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "9743df9bec312c0248fa3bbdd40827d03f169c1af78432f1e9df9d53f0a077ae", "section_path": ["Changes"], "commit_groups": [["0f63b74a4", "1b79c8d1a", "8d516d2b9", "b1ab4bc52", "e0511883c", "e4183c667"]], "identity_text": "Allow libpq to accept ParameterDescription messages exceeding 30000 bytes (Ning Sun) Previously, this message type was not among those that libpq's validity heuristics believed could be long. The limit resulted in failure for prepared queries having more than 7498 parameters, which is unlikely but supported.", "commit_aliases": ["0f63b74a4", "1b79c8d1a", "8d516d2b9", "b1ab4bc52", "e0511883c", "e4183c667"], "source_commits": ["b1ab4bc52"], "source_entry_id": "18.6/changes/107", "db_id": "c1e7d9148740f6776370a4a75311e436", "patch_ids": ["b6b26c4c8b27c2138732ea0f070c591b"], "statement_hash": "2bf8dba03893ccac611f0c0a15dfeaa8cb7ed7f18e2fbb58d26e630ffd77a548", "relations": [{"rule": 2, "type": "equivalent", "target": "5ebbe0622604b80c5219c1c82f7d9aca", "evidence": {"same_day": true, "patch_ids": ["b6b26c4c8b27c2138732ea0f070c591b"], "statement_hash": "2bf8dba03893ccac611f0c0a15dfeaa8cb7ed7f18e2fbb58d26e630ffd77a548"}}, {"rule": 2, "type": "equivalent", "target": "7b36888afdccf5778f4b3d9b3f4d4b19", "evidence": {"same_day": true, "patch_ids": ["b6b26c4c8b27c2138732ea0f070c591b"], "statement_hash": "2bf8dba03893ccac611f0c0a15dfeaa8cb7ed7f18e2fbb58d26e630ffd77a548"}}, {"rule": 2, "type": "equivalent", "target": "96f87cdaa195bfc8af2e374fe5cd785d", "evidence": {"same_day": true, "patch_ids": ["b6b26c4c8b27c2138732ea0f070c591b"], "statement_hash": "2bf8dba03893ccac611f0c0a15dfeaa8cb7ed7f18e2fbb58d26e630ffd77a548"}}, {"rule": 2, "type": "equivalent", "target": "97c44cf1d7b9b31d86691416921a75e4", "evidence": {"same_day": true, "patch_ids": ["b6b26c4c8b27c2138732ea0f070c591b"], "statement_hash": "2bf8dba03893ccac611f0c0a15dfeaa8cb7ed7f18e2fbb58d26e630ffd77a548"}}]}}, {"id": "18.6-f7ec4316771ce1eb", "source_entry_id": "18.6/changes/109", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Reject multiple descriptor header items in ecpg's GET/SET DESCRIPTOR statements", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-4edba097ad3499b7", "source_entry_id": "17.11/changes/088", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Reject multiple descriptor header items in ecpg's GET/SET DESCRIPTOR statements"}], "entry": {"id": "18.6-f7ec4316771ce1eb", "cves": [], "html": "Reject multiple descriptor header items in ecpg's GET/SET DESCRIPTOR statements (Masashi Kamura) §
Previously the grammar allowed this syntax, but broken C code was generated. Adjust the grammar and the documentation to allow only one header item.
", "text": "Reject multiple descriptor header items in ecpg's GET/SET DESCRIPTOR statements (Masashi Kamura) § Previously the grammar allowed this syntax, but broken C code was generated. Adjust the grammar and the documentation to allow only one header item.", "title": "Reject multiple descriptor header items in ecpg's GET/SET DESCRIPTOR statements", "commits": ["081434b0f"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "8fd091c57d1ece6fac2c371b58e204e819ec5818de477c5e0736e1b023f750f2", "section_path": ["Changes"], "commit_groups": [["081434b0f", "4484165b0", "4d4b73cfd", "9e8fd9f7a", "bfeddcf09", "fe8c0a762"]], "identity_text": "Reject multiple descriptor header items in ecpg's GET/SET DESCRIPTOR statements (Masashi Kamura) Previously the grammar allowed this syntax, but broken C code was generated. Adjust the grammar and the documentation to allow only one header item.", "commit_aliases": ["081434b0f", "4484165b0", "4d4b73cfd", "9e8fd9f7a", "bfeddcf09", "fe8c0a762"], "source_commits": ["081434b0f"], "source_entry_id": "18.6/changes/109", "db_id": "aa20c63216e98c98f035fa86491b5b30", "patch_ids": ["4f4dddcf40354c994e2b6668a43af20d"], "statement_hash": "e3bda298ded00b77261ba1c76b32c15895630f65da4a428ed88a0e425a4414cb", "relations": [{"rule": 2, "type": "equivalent", "target": "2d1814d3627bd7de23f302bac9690b77", "evidence": {"same_day": true, "patch_ids": ["4f4dddcf40354c994e2b6668a43af20d"], "statement_hash": "e3bda298ded00b77261ba1c76b32c15895630f65da4a428ed88a0e425a4414cb"}}, {"rule": 2, "type": "equivalent", "target": "d5ef1996d66a6c71b921d8881446c413", "evidence": {"same_day": true, "patch_ids": ["4f4dddcf40354c994e2b6668a43af20d"], "statement_hash": "e3bda298ded00b77261ba1c76b32c15895630f65da4a428ed88a0e425a4414cb"}}, {"rule": 2, "type": "equivalent", "target": "e7657a963bd66274d46d2b5a9e11a18a", "evidence": {"same_day": true, "patch_ids": ["4f4dddcf40354c994e2b6668a43af20d"], "statement_hash": "e3bda298ded00b77261ba1c76b32c15895630f65da4a428ed88a0e425a4414cb"}}, {"rule": 2, "type": "equivalent", "target": "f619d880f7a5f55846623a2af12abad1", "evidence": {"same_day": true, "patch_ids": ["4f4dddcf40354c994e2b6668a43af20d"], "statement_hash": "e3bda298ded00b77261ba1c76b32c15895630f65da4a428ed88a0e425a4414cb"}}]}}, {"id": "18.6-e95d42c0b0a749e2", "source_entry_id": "18.6/changes/111", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Make line widths match in psql's expanded aligned output format", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-410e9178511c3bd6", "source_entry_id": "17.11/changes/089", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Make line widths match in psql's expanded aligned output format"}], "entry": {"id": "18.6-e95d42c0b0a749e2", "cves": [], "html": "Make line widths match in psql's expanded aligned output format (Pavel Stehule) §
\nWhen the table's data rows are narrower than the record header lines, widen the data rows to match the headers, avoiding unsightly output.
", "text": "Make line widths match in psql's expanded aligned output format (Pavel Stehule) § When the table's data rows are narrower than the record header lines, widen the data rows to match the headers, avoiding unsightly output.", "title": "Make line widths match in psql's expanded aligned output format", "commits": ["07a6c262b"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "2d580be2068a246a98a192e4b40e46fe642aeb2c0d2fea17a0d81119c971db75", "section_path": ["Changes"], "commit_groups": [["022ba5c61", "07a6c262b", "1edbe6695", "3d0d6741d", "a4ca91ea1", "efd885d05"]], "identity_text": "Make line widths match in psql's expanded aligned output format (Pavel Stehule) When the table's data rows are narrower than the record header lines, widen the data rows to match the headers, avoiding unsightly output.", "commit_aliases": ["022ba5c61", "07a6c262b", "1edbe6695", "3d0d6741d", "a4ca91ea1", "efd885d05"], "source_commits": ["07a6c262b"], "source_entry_id": "18.6/changes/111", "db_id": "8c98433b203fc9f697cb6dfef2f22a70", "patch_ids": ["e1ed38dd6fb22dc6b3c388c344a54963"], "statement_hash": "bfb36185dbcab5e46aea9291f19969eb343ad3998992659ae2d4c88cea80e5d6", "relations": [{"rule": 2, "type": "equivalent", "target": "58d0bf8b8ffb214d0f6ab86e01e2ee4d", "evidence": {"same_day": true, "patch_ids": ["e1ed38dd6fb22dc6b3c388c344a54963"], "statement_hash": "bfb36185dbcab5e46aea9291f19969eb343ad3998992659ae2d4c88cea80e5d6"}}, {"rule": 2, "type": "equivalent", "target": "6a176afe78ae457a5f2e20281e68c1c8", "evidence": {"same_day": true, "patch_ids": ["e1ed38dd6fb22dc6b3c388c344a54963"], "statement_hash": "bfb36185dbcab5e46aea9291f19969eb343ad3998992659ae2d4c88cea80e5d6"}}, {"rule": 2, "type": "equivalent", "target": "6d353eb0c8713cda0665ed6128c86dc7", "evidence": {"same_day": true, "patch_ids": ["e1ed38dd6fb22dc6b3c388c344a54963"], "statement_hash": "bfb36185dbcab5e46aea9291f19969eb343ad3998992659ae2d4c88cea80e5d6"}}, {"rule": 2, "type": "equivalent", "target": "73be9a684058fbdc9b8dd586127fd52a", "evidence": {"same_day": true, "patch_ids": ["e1ed38dd6fb22dc6b3c388c344a54963"], "statement_hash": "bfb36185dbcab5e46aea9291f19969eb343ad3998992659ae2d4c88cea80e5d6"}}]}}, {"id": "18.6-f01251105c93da4a", "source_entry_id": "18.6/changes/113", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix psql's privilege check for showing database size in \\l+", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-3336152e1ee6addb", "source_entry_id": "17.11/changes/090", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix psql's privilege check for showing database size in \\l+"}], "entry": {"id": "18.6-f01251105c93da4a", "cves": [], "html": "Fix psql's privilege check for showing database size in \\l+ (Christoph Berg) §
The underlying server function permits users who have pg_read_all_stats privileges to see the sizes of all databases, even if they lack CONNECT privilege. But psql was unaware of that provision and would not call the function unless the user has CONNECT privilege.
Fix psql's tab completion for \\df to consider procedures too (Erik Wienhold) §
Fix thread-safety bug in pgbench (Fujii Masao) §
\nWhen pgbench runs with multiple threads and the --verbose-errors option, different threads could attempt to use the same buffer to construct error messages, leading to corrupted log output.
In pg_combinebackup, prevent infinite loop if the source file is shorter than expected (Peter Eisentraut) §
", "text": "In pg_combinebackup, prevent infinite loop if the source file is shorter than expected (Peter Eisentraut) §", "title": "In pg_combinebackup, prevent infinite loop if the source file is shorter than expected", "commits": ["d36b72894"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "e32f0075646e4a9ef32c93d9a5abb89c84e7398c492390d99d563ba6792484be", "section_path": ["Changes"], "commit_groups": [["090ce6934", "994f770a0", "d36b72894"]], "identity_text": "In pg_combinebackup, prevent infinite loop if the source file is shorter than expected (Peter Eisentraut)", "commit_aliases": ["090ce6934", "994f770a0", "d36b72894"], "source_commits": ["d36b72894"], "source_entry_id": "18.6/changes/116", "db_id": "c27420aa9b3b249ab663f9b3b7619204", "patch_ids": ["0ba00e2ae3a5e83df9d4302186a61a05"], "statement_hash": "761861ecd47105adace712b27a89e3d3f71b32c7571c4e3a163697a77fad30a7", "relations": [{"rule": 2, "type": "equivalent", "target": "0de6b21246ca038db28e1d7e7a8c33a5", "evidence": {"same_day": true, "patch_ids": ["0ba00e2ae3a5e83df9d4302186a61a05"], "statement_hash": "761861ecd47105adace712b27a89e3d3f71b32c7571c4e3a163697a77fad30a7"}}]}}, {"id": "18.6-280913453570aa34", "source_entry_id": "18.6/changes/117", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix cleanup of publisher-side objects after errors in pg_createsubscriber", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-48e3e90ffcc9370a", "source_entry_id": "17.11/changes/094", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix cleanup of publisher-side objects after errors in pg_createsubscriber"}], "entry": {"id": "18.6-280913453570aa34", "cves": [], "html": "Fix cleanup of publisher-side objects after errors in pg_createsubscriber (Nisha Moond) §
\nWhen pg_createsubscriber fails after creating logical replication objects, it should remove the publication and replication slot that it created on the publisher. Some error cases failed to do so.
", "text": "Fix cleanup of publisher-side objects after errors in pg_createsubscriber (Nisha Moond) § When pg_createsubscriber fails after creating logical replication objects, it should remove the publication and replication slot that it created on the publisher. Some error cases failed to do so.", "title": "Fix cleanup of publisher-side objects after errors in pg_createsubscriber", "commits": ["196b4b5ae"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "57682237b6273967edf6e0db2bced108af4544c26854c821f2753f04470bee76", "section_path": ["Changes"], "commit_groups": [["12d000488", "196b4b5ae", "c03784a21"]], "identity_text": "Fix cleanup of publisher-side objects after errors in pg_createsubscriber (Nisha Moond) When pg_createsubscriber fails after creating logical replication objects, it should remove the publication and replication slot that it created on the publisher. Some error cases failed to do so.", "commit_aliases": ["12d000488", "196b4b5ae", "c03784a21"], "source_commits": ["196b4b5ae"], "source_entry_id": "18.6/changes/117", "db_id": "b3b32d95005620db1dde6737c217ff79", "patch_ids": ["294a0298249f9d0b66c918ec534fd2fa"], "statement_hash": "0b52e9786bbf3135e7724a4cd772716beafec6c0f4a214b285af87f0fd2ba380", "relations": [{"rule": 2, "type": "equivalent", "target": "a5c36038d3fc8268a2ecbdc5f6d205fc", "evidence": {"same_day": true, "patch_ids": ["294a0298249f9d0b66c918ec534fd2fa"], "statement_hash": "0b52e9786bbf3135e7724a4cd772716beafec6c0f4a214b285af87f0fd2ba380"}}]}}, {"id": "18.6-ccc1d394ba38511a", "source_entry_id": "18.6/changes/118", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Use the source cluster's group-read file permissions for pg_recvlogical output files", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-7a66a4f0ad5abf3d", "source_entry_id": "17.11/changes/095", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Use the source cluster's group-read file permissions for pg_recvlogical output files"}], "entry": {"id": "18.6-ccc1d394ba38511a", "cves": [], "html": "Use the source cluster's group-read file permissions for pg_recvlogical output files (Fujii Masao) §
\npg_recvlogical was documented to behave this way, but it never actually enabled group-read.
", "text": "Use the source cluster's group-read file permissions for pg_recvlogical output files (Fujii Masao) § pg_recvlogical was documented to behave this way, but it never actually enabled group-read.", "title": "Use the source cluster's group-read file permissions for pg_recvlogical output files", "commits": ["89b4b3ae3"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "c7707d5c1907b9f8589f22c46145c7e026130a40f4b4d3662c264143afee593b", "section_path": ["Changes"], "commit_groups": [["263d1e6df", "5552a15a3", "89b4b3ae3", "9590dcfca", "ba9833a75", "ddd12d1a5"]], "identity_text": "Use the source cluster's group-read file permissions for pg_recvlogical output files (Fujii Masao) pg_recvlogical was documented to behave this way, but it never actually enabled group-read.", "commit_aliases": ["263d1e6df", "5552a15a3", "89b4b3ae3", "9590dcfca", "ba9833a75", "ddd12d1a5"], "source_commits": ["89b4b3ae3"], "source_entry_id": "18.6/changes/118", "db_id": "739e2a6e3be37fb134a81099033e7b88", "patch_ids": ["afbffd5094352bc11bf18ec699c42866"], "statement_hash": "76c08921b60501e09bdf60cd197949c5372599c542dc2702bad076644bfb808e", "relations": [{"rule": 2, "type": "equivalent", "target": "46627f579bf31b5d6613ea2ead9a438c", "evidence": {"same_day": true, "patch_ids": ["afbffd5094352bc11bf18ec699c42866"], "statement_hash": "76c08921b60501e09bdf60cd197949c5372599c542dc2702bad076644bfb808e"}}, {"rule": 2, "type": "equivalent", "target": "5e9c0809074f8046eb23cf8c625f723d", "evidence": {"same_day": true, "patch_ids": ["afbffd5094352bc11bf18ec699c42866"], "statement_hash": "76c08921b60501e09bdf60cd197949c5372599c542dc2702bad076644bfb808e"}}, {"rule": 2, "type": "equivalent", "target": "7c4fc2d9507cff650a6e11a00319e316", "evidence": {"same_day": true, "patch_ids": ["afbffd5094352bc11bf18ec699c42866"], "statement_hash": "76c08921b60501e09bdf60cd197949c5372599c542dc2702bad076644bfb808e"}}, {"rule": 2, "type": "equivalent", "target": "f4924985d224acc909a53983f158ebbe", "evidence": {"same_day": true, "patch_ids": ["afbffd5094352bc11bf18ec699c42866"], "statement_hash": "76c08921b60501e09bdf60cd197949c5372599c542dc2702bad076644bfb808e"}}]}}, {"id": "18.6-83d0b073d364f75c", "source_entry_id": "18.6/changes/123", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "In contrib/amcheck, handle short-header varlena datums correctly", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-43173bad4eaa1b27", "source_entry_id": "17.11/changes/096", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "In contrib/amcheck, handle short-header varlena datums correctly"}], "entry": {"id": "18.6-83d0b073d364f75c", "cves": [], "html": "In contrib/amcheck, handle short-header varlena datums correctly (Andrey Borodin) §
This error could result in doing excess work while verifying a btree index, but seems not to have had any worse consequences.
", "text": "In contrib/amcheck, handle short-header varlena datums correctly (Andrey Borodin) § This error could result in doing excess work while verifying a btree index, but seems not to have had any worse consequences.", "title": "In contrib/amcheck, handle short-header varlena datums correctly", "commits": ["897e79486"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "152b36f3a586a937cd005dd3f18e0bbbd573f79cc40dff4a2e1213c59f38f760", "section_path": ["Changes"], "commit_groups": [["4284476c0", "897e79486", "8abb8a155", "af09b18cb", "c89a1ca01", "da1eff08a"]], "identity_text": "In contrib/amcheck, handle short-header varlena datums correctly (Andrey Borodin) This error could result in doing excess work while verifying a btree index, but seems not to have had any worse consequences.", "commit_aliases": ["4284476c0", "897e79486", "8abb8a155", "af09b18cb", "c89a1ca01", "da1eff08a"], "source_commits": ["897e79486"], "source_entry_id": "18.6/changes/123", "db_id": "2d507c3ecfdc88b0a54eabbb1a06a7e0", "patch_ids": ["d7fc6f8977003129b1104cd80d7d07dc"], "statement_hash": "e472f473c1b1497e339e1735040e13130df76e2534eb81a81dc2b51327126c5d", "relations": [{"rule": 2, "type": "equivalent", "target": "3b8c851869278523310ddb5e0cf66c28", "evidence": {"same_day": true, "patch_ids": ["d7fc6f8977003129b1104cd80d7d07dc"], "statement_hash": "e472f473c1b1497e339e1735040e13130df76e2534eb81a81dc2b51327126c5d"}}, {"rule": 2, "type": "equivalent", "target": "45cd63fac27296a03920e2ac709b0ed6", "evidence": {"same_day": true, "patch_ids": ["d7fc6f8977003129b1104cd80d7d07dc"], "statement_hash": "e472f473c1b1497e339e1735040e13130df76e2534eb81a81dc2b51327126c5d"}}, {"rule": 2, "type": "equivalent", "target": "cdde56de8d6ffe6162fb47b834f39528", "evidence": {"same_day": true, "patch_ids": ["d7fc6f8977003129b1104cd80d7d07dc"], "statement_hash": "e472f473c1b1497e339e1735040e13130df76e2534eb81a81dc2b51327126c5d"}}, {"rule": 2, "type": "equivalent", "target": "e3d3da7d18247e58916c107812921cf0", "evidence": {"same_day": true, "patch_ids": ["d7fc6f8977003129b1104cd80d7d07dc"], "statement_hash": "e472f473c1b1497e339e1735040e13130df76e2534eb81a81dc2b51327126c5d"}}]}}, {"id": "18.6-f1427fb43b6c1e77", "source_entry_id": "18.6/changes/124", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "In contrib/btree_gist, fix NaN handling in the float4 and float8 opclasses", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-62f2c81188559a68", "source_entry_id": "17.11/changes/097", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "In contrib/btree_gist, fix NaN handling in the float4 and float8 opclasses"}], "entry": {"id": "18.6-f1427fb43b6c1e77", "cves": [], "html": "In contrib/btree_gist, fix NaN handling in the float4 and float8 opclasses (Bill Kim, Tom Lane) §
Comparisons, as well as the GiST penalty and distance functions, did not account for NaN and would give the wrong answer when handed one. It is recommended to reindex btree_gist indexes on float columns after installing this update, if there is any possibility that there are NaN entries in those columns.
In contrib/btree_gist, fix searches using a not-equal operator (Ayush Tiwari) §
For variable-length data types, the code for scanning non-leaf index pages applied the wrong comparison function, leading to wrong results and potentially crashes.
", "text": "In contrib/btree_gist, fix searches using a not-equal operator (Ayush Tiwari) § For variable-length data types, the code for scanning non-leaf index pages applied the wrong comparison function, leading to wrong results and potentially crashes.", "title": "In contrib/btree_gist, fix searches using a not-equal operator", "commits": ["12c519207"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "f473dbeeef45f9192ac0fd0459f12bff57152d3ed6af68df7b93c96933c434cd", "section_path": ["Changes"], "commit_groups": [["0663382c9", "12c519207", "286f9a3ce", "86992769e", "8f2a1b3d3", "eef644e57", "fc6649abe"]], "identity_text": "In contrib/btree_gist, fix searches using a not-equal operator (Ayush Tiwari) For variable-length data types, the code for scanning non-leaf index pages applied the wrong comparison function, leading to wrong results and potentially crashes.", "commit_aliases": ["0663382c9", "12c519207", "286f9a3ce", "86992769e", "8f2a1b3d3", "eef644e57", "fc6649abe"], "source_commits": ["12c519207"], "source_entry_id": "18.6/changes/126", "db_id": "6a17d9b57b1644e479653b086d9a3d5b", "patch_ids": ["515eccc8717dfd3bf829ad309ee292d4"], "statement_hash": "2be1ae243cd8ebc1e8e722c0adfd189a77f8b7ec2ce84c5f76afc7ac0990135a", "relations": [{"rule": 2, "type": "equivalent", "target": "635407feb25f134fd4b583a750d226fd", "evidence": {"same_day": true, "patch_ids": ["515eccc8717dfd3bf829ad309ee292d4"], "statement_hash": "2be1ae243cd8ebc1e8e722c0adfd189a77f8b7ec2ce84c5f76afc7ac0990135a"}}, {"rule": 2, "type": "equivalent", "target": "72b13e01606442471a1d73d64267d5db", "evidence": {"same_day": true, "patch_ids": ["515eccc8717dfd3bf829ad309ee292d4"], "statement_hash": "2be1ae243cd8ebc1e8e722c0adfd189a77f8b7ec2ce84c5f76afc7ac0990135a"}}, {"rule": 2, "type": "equivalent", "target": "b8f3ffff9bd8249a29d2857d5a2613d1", "evidence": {"same_day": true, "patch_ids": ["515eccc8717dfd3bf829ad309ee292d4"], "statement_hash": "2be1ae243cd8ebc1e8e722c0adfd189a77f8b7ec2ce84c5f76afc7ac0990135a"}}, {"rule": 2, "type": "equivalent", "target": "c540681583edc5cf717591e5bf65da83", "evidence": {"same_day": true, "patch_ids": ["515eccc8717dfd3bf829ad309ee292d4"], "statement_hash": "2be1ae243cd8ebc1e8e722c0adfd189a77f8b7ec2ce84c5f76afc7ac0990135a"}}]}}, {"id": "18.6-3bbe012702953660", "source_entry_id": "18.6/changes/129", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix unguarded recursion and loops in contrib/hstore_plperl, contrib/jsonb_plperl, and contrib/jsonb_plpython", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-f475bfd70799c254", "source_entry_id": "17.11/changes/099", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix unguarded recursion and loops in contrib/hstore_plperl, contrib/jsonb_plperl, and contrib/jsonb_plpython"}], "entry": {"id": "18.6-3bbe012702953660", "cves": [], "html": "Fix unguarded recursion and loops in contrib/hstore_plperl, contrib/jsonb_plperl, and contrib/jsonb_plpython (Aleksander Alekseev) § §
Prevent stack overflow when dealing with deeply nested jsonb values, and allow interruption of the infinite loop caused when attempting to dereference circular chains of Perl object references.
Fix missed release of statistics catcache entry in contrib/intarray (Man Zeng) §
This oversight led to warnings like “resource was not closed: cache pg_statistic”.
", "text": "Fix missed release of statistics catcache entry in contrib/intarray (Man Zeng) § This oversight led to warnings like “resource was not closed: cache pg_statistic”.", "title": "Fix missed release of statistics catcache entry in contrib/intarray", "commits": ["e7544c518"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "68153d5159c3c6ada0f6a07d899814308d69aa1ba7d4318b10ec41562e2e416c", "section_path": ["Changes"], "commit_groups": [["273be484a", "524cc0f63", "702a6d5f6", "94b57ab54", "a96b051a9", "e7544c518"]], "identity_text": "Fix missed release of statistics catcache entry in contrib/intarray (Man Zeng) This oversight led to warnings like resource was not closed: cache pg_statistic.", "commit_aliases": ["273be484a", "524cc0f63", "702a6d5f6", "94b57ab54", "a96b051a9", "e7544c518"], "source_commits": ["e7544c518"], "source_entry_id": "18.6/changes/130", "db_id": "531f88cd6dd693227e011632166ae87b", "patch_ids": ["ed91737595bc2b3f155e28dcd1a2eea2"], "statement_hash": "f94e4dacb87f6c952276d56347322f0e3b34e2c00c7f4e555ef6c2806632dec3", "relations": [{"rule": 2, "type": "equivalent", "target": "29b63a7300df9efc4d5ac1e96dc34cb7", "evidence": {"same_day": true, "patch_ids": ["ed91737595bc2b3f155e28dcd1a2eea2"], "statement_hash": "f94e4dacb87f6c952276d56347322f0e3b34e2c00c7f4e555ef6c2806632dec3"}}, {"rule": 2, "type": "equivalent", "target": "2c29490e6377bc8f4bb49b5d5ca76323", "evidence": {"same_day": true, "patch_ids": ["ed91737595bc2b3f155e28dcd1a2eea2"], "statement_hash": "f94e4dacb87f6c952276d56347322f0e3b34e2c00c7f4e555ef6c2806632dec3"}}, {"rule": 2, "type": "equivalent", "target": "441b437853466f13724bc66579a3d9c5", "evidence": {"same_day": true, "patch_ids": ["ed91737595bc2b3f155e28dcd1a2eea2"], "statement_hash": "f94e4dacb87f6c952276d56347322f0e3b34e2c00c7f4e555ef6c2806632dec3"}}, {"rule": 2, "type": "equivalent", "target": "a4dfb26ea114f9668f1e953f8895f530", "evidence": {"same_day": true, "patch_ids": ["ed91737595bc2b3f155e28dcd1a2eea2"], "statement_hash": "f94e4dacb87f6c952276d56347322f0e3b34e2c00c7f4e555ef6c2806632dec3"}}]}}, {"id": "18.6-b2444fb7d252ecb2", "source_entry_id": "18.6/changes/131", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "In contrib/ltree, fix integer overflow in comparisons", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-390646d2843a7323", "source_entry_id": "17.11/changes/101", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "In contrib/ltree, fix integer overflow in comparisons"}], "entry": {"id": "18.6-b2444fb7d252ecb2", "cves": [], "html": "In contrib/ltree, fix integer overflow in comparisons (Ayush Tiwari) §
ltree values containing more than about 14,653 labels resulted in wrong comparison answers due to overflow. If a btree index contains such values, it is probably corrupt and should be reindexed after installing this update.
In contrib/pgcrypto, avoid double-free crash after encountering an error while using an OSSLCipher object (Yuelin Wang) §
Fix array overrun in contrib/pg_surgery's heap_force_kill and heap_force_freeze functions (Michael Paquier) §
Attempting to change a TID whose offset number equals MaxHeapTuplesPerPage wrote one byte past the end of the allocated array, potentially crashing the server.
", "text": "Fix array overrun in contrib/pg_surgery's heap_force_kill and heap_force_freeze functions (Michael Paquier) § Attempting to change a TID whose offset number equals MaxHeapTuplesPerPage wrote one byte past the end of the allocated array, potentially crashing the server.", "title": "Fix array overrun in contrib/pg_surgery's heap_force_kill and heap_force_freeze functions", "commits": ["2b09f8a91"], "section": "Changes", "category": "bugfix", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "0d8617c88bd69699f61f86b4d43593b97925e36eb860f4273481eca4654d97d7", "section_path": ["Changes"], "commit_groups": [["0bcf19c9e", "193a4ded9", "1eda3eb07", "2b09f8a91", "51f63ba2b", "daf8bc7d4"]], "identity_text": "Fix array overrun in contrib/pg_surgery's heap_force_kill and heap_force_freeze functions (Michael Paquier) Attempting to change a TID whose offset number equals MaxHeapTuplesPerPage wrote one byte past the end of the allocated array, potentially crashing the server.", "commit_aliases": ["0bcf19c9e", "193a4ded9", "1eda3eb07", "2b09f8a91", "51f63ba2b", "daf8bc7d4"], "source_commits": ["2b09f8a91"], "source_entry_id": "18.6/changes/134", "db_id": "34c6abdf99153564a44d057cfe4b6dac", "patch_ids": ["eb798217c4bf865d1840668bc6612f6d"], "statement_hash": "0c283cf21db62b067b9adc880d22c26404e9404758237c1adc833a4aa35981ae", "relations": [{"rule": 2, "type": "equivalent", "target": "68b2c21176cad03670e2c5de5fd39431", "evidence": {"same_day": true, "patch_ids": ["eb798217c4bf865d1840668bc6612f6d"], "statement_hash": "0c283cf21db62b067b9adc880d22c26404e9404758237c1adc833a4aa35981ae"}}, {"rule": 2, "type": "equivalent", "target": "bfda1df269b11b96600aa8d604c7a26a", "evidence": {"same_day": true, "patch_ids": ["eb798217c4bf865d1840668bc6612f6d"], "statement_hash": "0c283cf21db62b067b9adc880d22c26404e9404758237c1adc833a4aa35981ae"}}, {"rule": 2, "type": "equivalent", "target": "dd33ec95e198e9db76b741cb251151f9", "evidence": {"same_day": true, "patch_ids": ["eb798217c4bf865d1840668bc6612f6d"], "statement_hash": "0c283cf21db62b067b9adc880d22c26404e9404758237c1adc833a4aa35981ae"}}, {"rule": 2, "type": "equivalent", "target": "f14b53949f2fa5150ed94f6fdbc3af9e", "evidence": {"same_day": true, "patch_ids": ["eb798217c4bf865d1840668bc6612f6d"], "statement_hash": "0c283cf21db62b067b9adc880d22c26404e9404758237c1adc833a4aa35981ae"}}]}}, {"id": "18.6-e307258545af5090", "source_entry_id": "18.6/changes/135", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "In contrib/pg_surgery, avoid infinite loop with TID arrays having more than 64K elements", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-79d5c27db04cf496", "source_entry_id": "17.11/changes/104", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "In contrib/pg_surgery, avoid infinite loop with TID arrays having more than 64K elements"}], "entry": {"id": "18.6-e307258545af5090", "cves": [], "html": "In contrib/pg_surgery, avoid infinite loop with TID arrays having more than 64K elements (Andrey Rachitskiy) §
Avoid NULL-pointer dereference in contrib/refint's check_foreign_key() (Ayush Tiwari) §
In the on-update-cascade case, a null value of a referenced column led to a crash. This is an oversight in the fix for CVE-2026-6637, but the code that was there before that wasn't really right either.
", "text": "Avoid NULL-pointer dereference in contrib/refint's check_foreign_key() (Ayush Tiwari) § In the on-update-cascade case, a null value of a referenced column led to a crash. This is an oversight in the fix for CVE-2026-6637, but the code that was there before that wasn't really right either.", "title": "Avoid NULL-pointer dereference in contrib/refint's check_foreign_key()", "commits": ["ed0c4d5af"], "section": "Changes", "category": "security", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "1057a22e1c5d835fbe3ab3dedae9abbb24679f457e5b5af6ae2f572a15177513", "section_path": ["Changes"], "commit_groups": [["1de0a711d", "611756948", "6b4de201e", "77b2d18e9", "eb93f10e2", "ed0c4d5af"]], "identity_text": "Avoid NULL-pointer dereference in contrib/refint's check_foreign_key() (Ayush Tiwari) In the on-update-cascade case, a null value of a referenced column led to a crash. This is an oversight in the fix for CVE-2026-6637, but the code that was there before that wasn't really right either.", "commit_aliases": ["1de0a711d", "611756948", "6b4de201e", "77b2d18e9", "eb93f10e2", "ed0c4d5af"], "source_commits": ["ed0c4d5af"], "source_entry_id": "18.6/changes/136", "db_id": "1404c503877f8a1f5c524fd84656cf87", "patch_ids": ["47510ee01f1ec9c76e280af528461da2"], "statement_hash": "95ffa03f4949f1fbe65efb454898eb0f8b9358951a8110fcc4b0547102b37374", "relations": [{"rule": 2, "type": "equivalent", "target": "220e195253d94eac399969a628bda519", "evidence": {"same_day": true, "patch_ids": ["47510ee01f1ec9c76e280af528461da2"], "statement_hash": "95ffa03f4949f1fbe65efb454898eb0f8b9358951a8110fcc4b0547102b37374"}}, {"rule": 2, "type": "equivalent", "target": "4a53f44037d5d1ea5b714eb8d91567ee", "evidence": {"same_day": true, "patch_ids": ["47510ee01f1ec9c76e280af528461da2"], "statement_hash": "95ffa03f4949f1fbe65efb454898eb0f8b9358951a8110fcc4b0547102b37374"}}, {"rule": 2, "type": "equivalent", "target": "98b367e0c42416fd78e2312f81ec66e2", "evidence": {"same_day": true, "patch_ids": ["47510ee01f1ec9c76e280af528461da2"], "statement_hash": "95ffa03f4949f1fbe65efb454898eb0f8b9358951a8110fcc4b0547102b37374"}}, {"rule": 2, "type": "equivalent", "target": "a4fcc13dcc4b7cf6a5470b40915f7de5", "evidence": {"same_day": true, "patch_ids": ["47510ee01f1ec9c76e280af528461da2"], "statement_hash": "95ffa03f4949f1fbe65efb454898eb0f8b9358951a8110fcc4b0547102b37374"}}]}}, {"id": "18.6-387ff665922d6204", "source_entry_id": "18.6/changes/137", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Fix contrib/seg to print segments with ~ certainty indicators correctly", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-f8ebcb7cb6568363", "source_entry_id": "17.11/changes/106", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Fix contrib/seg to print segments with ~ certainty indicators correctly"}], "entry": {"id": "18.6-387ff665922d6204", "cves": [], "html": "Fix contrib/seg to print segments with ~ certainty indicators correctly (Ewan Young) §
Due to a typo, seg_out() did not print a ~ certainty indicator attached to a segment's upper boundary. Worse, if the lower boundary had ~ while the upper boundary had no indicator, the upper boundary was not printed at all, incorrectly converting the value into an open interval.
Fix crash with namespace nodes in contrib/xml2's xpath_nodeset() function (Andrey Chernyy, Michael Paquier) §
Support building PostgreSQL with OpenSSL 4 (Daniel Gustafsson) §
", "text": "Support building PostgreSQL with OpenSSL 4 (Daniel Gustafsson) §", "title": "Support building PostgreSQL with OpenSSL 4", "commits": ["27cf3b5af"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "9be69421adf563ef48c8b372b32c2e4d99c30d055115c7dd160eb2613d7ce3d6", "section_path": ["Changes"], "commit_groups": [["086652c02", "27cf3b5af", "89d243d52", "8bcabfcce", "c7f70fa1b", "fb8befa7b"]], "identity_text": "Support building PostgreSQL with OpenSSL 4 (Daniel Gustafsson)", "commit_aliases": ["086652c02", "27cf3b5af", "89d243d52", "8bcabfcce", "c7f70fa1b", "fb8befa7b"], "source_commits": ["27cf3b5af"], "source_entry_id": "18.6/changes/139", "db_id": "c3287f3d7329f9fd4fb1dead8c819569", "patch_ids": ["17c49f696c0a31900846c5a8c98eebd4"], "statement_hash": "c7b934d532c3b5d79d29d9130c3ab4f97028c3c1aa16422bb9101d84ad828729", "relations": [{"rule": 2, "type": "equivalent", "target": "10ee20e58ffd04daecf6e5f030162c87", "evidence": {"same_day": true, "patch_ids": ["17c49f696c0a31900846c5a8c98eebd4"], "statement_hash": "c7b934d532c3b5d79d29d9130c3ab4f97028c3c1aa16422bb9101d84ad828729"}}, {"rule": 2, "type": "equivalent", "target": "3814ca74f63c29149528542a43ad21c5", "evidence": {"same_day": true, "patch_ids": ["17c49f696c0a31900846c5a8c98eebd4"], "statement_hash": "c7b934d532c3b5d79d29d9130c3ab4f97028c3c1aa16422bb9101d84ad828729"}}, {"rule": 2, "type": "equivalent", "target": "5205dd7058f572a69fe179e448446706", "evidence": {"same_day": true, "patch_ids": ["17c49f696c0a31900846c5a8c98eebd4"], "statement_hash": "c7b934d532c3b5d79d29d9130c3ab4f97028c3c1aa16422bb9101d84ad828729"}}, {"rule": 2, "type": "equivalent", "target": "5a9bafbcf49a80b12f21e542e3bae026", "evidence": {"same_day": true, "patch_ids": ["17c49f696c0a31900846c5a8c98eebd4"], "statement_hash": "c7b934d532c3b5d79d29d9130c3ab4f97028c3c1aa16422bb9101d84ad828729"}}]}}, {"id": "18.6-d9abf44820fbecc5", "source_entry_id": "18.6/changes/140", "version": "18.6", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "title": "Update time zone data files to tzdata release 2026c", "reason": "already_in_source", "method": "commits", "matches": [{"id": "17.11-8abc326e9afc0d23", "source_entry_id": "17.11/changes/109", "version": "17.11", "source_url": "/docs/release/17.11/#RELEASE-17-11-CHANGES", "title": "Update time zone data files to tzdata release 2026c"}], "entry": {"id": "18.6-d9abf44820fbecc5", "cves": [], "html": "Update time zone data files to tzdata release 2026c (Tom Lane) §
\nAlberta (America/Edmonton) will be on year-round UTC-06 (effectively, permanent DST) beginning in November 2026. This release assumes that their TZ abbreviation will be CST from that time forward. That seems likely to change, but it's unclear what new abbreviation will be used.
Morocco (Africa/Casablanca) will move to permanent UTC+00, without daylight saving time transitions, on 2026-09-20.
", "text": "Update time zone data files to tzdata release 2026c (Tom Lane) § Alberta (America/Edmonton) will be on year-round UTC-06 (effectively, permanent DST) beginning in November 2026. This release assumes that their TZ abbreviation will be CST from that time forward. That seems likely to change, but it's unclear what new abbreviation will be used. Morocco (Africa/Casablanca) will move to permanent UTC+00, without daylight saving time transitions, on 2026-09-20.", "title": "Update time zone data files to tzdata release 2026c", "commits": ["5f67124fa"], "section": "Changes", "category": "improvement", "source_url": "/docs/release/18.6/#RELEASE-18-6-CHANGES", "source_hash": "b5d88332184a238e737bbc48bbbe3050925043c34b0b9fca1b100be6365fb68c", "section_path": ["Changes"], "commit_groups": [["3c16aa293", "5f67124fa", "669438aed", "6ca405938", "796c275a0", "812cc1a73", "af7be5672"]], "identity_text": "Update time zone data files to tzdata release 2026c (Tom Lane) Alberta (America/Edmonton) will be on year-round UTC-06 (effectively, permanent DST) beginning in November 2026. This release assumes that their TZ abbreviation will be CST from that time forward. That seems likely to change, but it's unclear what new abbreviation will be used. Morocco (Africa/Casablanca) will move to permanent UTC+00, without daylight saving time transitions, on 2026-09-20.", "commit_aliases": ["3c16aa293", "5f67124fa", "669438aed", "6ca405938", "796c275a0", "812cc1a73", "af7be5672"], "source_commits": ["5f67124fa"], "source_entry_id": "18.6/changes/140", "db_id": "5d6e219dd117842cc9b25b660af47952", "patch_ids": ["b4e9971495e6df3bcbb5661de594cfb5"], "statement_hash": "db30f9e9494e81ad745b38acebea395f96ce2c6e6fd0e722f568326a3b8491a7", "relations": [{"rule": 2, "type": "equivalent", "target": "163da88262eec7e167bed3e56a48dcc3", "evidence": {"same_day": true, "patch_ids": ["b4e9971495e6df3bcbb5661de594cfb5"], "statement_hash": "db30f9e9494e81ad745b38acebea395f96ce2c6e6fd0e722f568326a3b8491a7"}}, {"rule": 2, "type": "equivalent", "target": "6c00ccb389c691ec829366a2dd6d8fd7", "evidence": {"same_day": true, "patch_ids": ["b4e9971495e6df3bcbb5661de594cfb5"], "statement_hash": "db30f9e9494e81ad745b38acebea395f96ce2c6e6fd0e722f568326a3b8491a7"}}, {"rule": 2, "type": "equivalent", "target": "ae8d1b295c148a9982765709cf1583a9", "evidence": {"same_day": true, "patch_ids": ["b4e9971495e6df3bcbb5661de594cfb5"], "statement_hash": "db30f9e9494e81ad745b38acebea395f96ce2c6e6fd0e722f568326a3b8491a7"}}, {"rule": 2, "type": "equivalent", "target": "afb53916a223205ed20435542f0bacc1", "evidence": {"same_day": true, "patch_ids": ["b4e9971495e6df3bcbb5661de594cfb5"], "statement_hash": "db30f9e9494e81ad745b38acebea395f96ce2c6e6fd0e722f568326a3b8491a7"}}]}}], "history": {"source": ["9.0.0", "9.0.1", "9.0.2", "9.0.3", "9.0.4", "9.1.0", "9.1.1", "9.1.2", "9.1.3", "9.1.4", "9.1.5", "9.2.0", "9.2.1", "9.2.2", "9.2.3", "9.2.4", "9.3.0", "9.3.1", "9.3.2", "9.3.3", "9.3.4", "9.3.5", "9.4.0", "9.4.1", "9.4.2", "9.4.3", "9.4.4", "9.4.5", "9.5.0", "9.5.1", "9.5.2", "9.5.3", "9.5.4", "9.6.0", "9.6.1", "9.6.2", "9.6.3", "9.6.4", "9.6.5", "10.0", "10.1", "10.2", "10.3", "10.4", "10.5", "11.0", "11.1", "11.2", "11.3", "11.4", "11.5", "12.0", "12.1", "12.2", "12.3", "12.4", "13.0", "13.1", "13.2", "13.3", "13.4", "14.0", "14.1", "14.2", "14.3", "14.4", "14.5", "15.0", "15.1", "15.2", "15.3", "15.4", "16.0", "16.1", "16.2", "16.3", "16.4", "17.0", "17.1", "17.2", "17.3", "17.4", "17.5", "17.6", "17.7", "17.8", "17.9", "17.10", "17.11"], "target": ["9.0.0", "9.0.1", "9.0.2", "9.0.3", "9.0.4", "9.1.0", "9.1.1", "9.1.2", "9.1.3", "9.1.4", "9.1.5", "9.2.0", "9.2.1", "9.2.2", "9.2.3", "9.2.4", "9.3.0", "9.3.1", "9.3.2", "9.3.3", "9.3.4", "9.3.5", "9.4.0", "9.4.1", "9.4.2", "9.4.3", "9.4.4", "9.4.5", "9.5.0", "9.5.1", "9.5.2", "9.5.3", "9.5.4", "9.6.0", "9.6.1", "9.6.2", "9.6.3", "9.6.4", "9.6.5", "10.0", "10.1", "10.2", "10.3", "10.4", "10.5", "11.0", "11.1", "11.2", "11.3", "11.4", "11.5", "12.0", "12.1", "12.2", "12.3", "12.4", "13.0", "13.1", "13.2", "13.3", "13.4", "14.0", "14.1", "14.2", "14.3", "14.4", "14.5", "15.0", "15.1", "15.2", "15.3", "15.4", "16.0", "16.1", "16.2", "16.3", "16.4", "17.0", "17.1", "17.2", "17.3", "17.4", "17.5", "17.6", "18.0", "18.1", "18.2", "18.3", "18.4", "18.6"], "candidates": ["18.0", "18.1", "18.2", "18.3", "18.4", "18.6"]}, "release_count": 6, "warnings": [], "source_as_of": "2026-09-26", "security_as_of": "2026-09-26"}