{"already_in_source_count":264,"candidate_count":561,"cross_major":true,"cve_available":true,"cve_count":0,"cves":[],"duplicate_count":0,"excluded_count":264,"exclusions":[{"entry":{"category":"security","commit_aliases":["00eb646ea","2393d374a","5e4fcbe53","8a2530ebc","95cce5669","d20abb587","e2fb3dfa8"],"commit_groups":[["00eb646ea","2393d374a","5e4fcbe53","8a2530ebc","95cce5669","d20abb587","e2fb3dfa8"]],"commits":["00eb646ea"],"cves":["CVE-2025-12817"],"db_id":"0b1db4254a2e3444434b0ca4004ea84b","html":"\u003cp\u003eCheck for \u003ccode\u003eCREATE\u003c/code\u003e privileges on the schema in \u003ccode\u003eCREATE STATISTICS\u003c/code\u003e (Jelte Fennema-Nio) \u003ca href=\"https://postgr.es/c/00eb646ea\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis omission allowed table owners to create statistics in any schema, potentially leading to unexpected naming conflicts.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Jelte Fennema-Nio for reporting this problem. (CVE-2025-12817)\u003c/p\u003e","id":"18.1-45bd7bfaea1c1e6c","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)","part":"changes","patch_ids":["99e1ddd8be3f2e70a07b173bce56eec6"],"relations":[{"evidence":{"patch_ids":["99e1ddd8be3f2e70a07b173bce56eec6"],"same_day":true,"statement_hash":"2fdab1083a50be24b1dca00ede9ffd5906a617c6df360497714a885f6ff9f704"},"rule":2,"target":"3aabd99e8b497ed573a9c3988472f89b","type":"equivalent"},{"evidence":{"patch_ids":["99e1ddd8be3f2e70a07b173bce56eec6"],"same_day":true,"statement_hash":"2fdab1083a50be24b1dca00ede9ffd5906a617c6df360497714a885f6ff9f704"},"rule":2,"target":"5434410099d24e095f2f3662e9b084be","type":"equivalent"},{"evidence":{"patch_ids":["99e1ddd8be3f2e70a07b173bce56eec6"],"same_day":true,"statement_hash":"2fdab1083a50be24b1dca00ede9ffd5906a617c6df360497714a885f6ff9f704"},"rule":2,"target":"6167ff71ba63659939df7295a1784bd5","type":"equivalent"},{"evidence":{"patch_ids":["99e1ddd8be3f2e70a07b173bce56eec6"],"same_day":true,"statement_hash":"2fdab1083a50be24b1dca00ede9ffd5906a617c6df360497714a885f6ff9f704"},"rule":2,"target":"7a542e168dfd911c88c2817105ab4eb1","type":"equivalent"},{"evidence":{"patch_ids":["99e1ddd8be3f2e70a07b173bce56eec6"],"same_day":true,"statement_hash":"2fdab1083a50be24b1dca00ede9ffd5906a617c6df360497714a885f6ff9f704"},"rule":2,"target":"fc4febff3c2281775597453f96dfd148","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["00eb646ea"],"source_entry_id":"18.1/changes/001","source_hash":"7c9fc98fd26352f2c8df8d62ef124c4a11c97ac338af1e68ad9300d406affc69","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"2fdab1083a50be24b1dca00ede9ffd5906a617c6df360497714a885f6ff9f704","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"},"id":"18.1-45bd7bfaea1c1e6c","matches":[{"id":"17.7-36aab10e5138d3d1","source_entry_id":"17.7/changes/001","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Check for CREATE privileges on the schema in CREATE STATISTICS","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/001","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Check for CREATE privileges on the schema in CREATE STATISTICS","version":"18.1"},{"entry":{"category":"security","commit_aliases":["585fd9b3c","600086f47","7eb8fcad8","91421565f","96d2c7e96","d6f0c0d6d","f5999f018"],"commit_groups":[["585fd9b3c","600086f47","7eb8fcad8","91421565f","96d2c7e96","d6f0c0d6d","f5999f018"]],"commits":["7eb8fcad8"],"cves":["CVE-2025-12818"],"db_id":"c53264df3df1081cfca59daebb417ae4","html":"\u003cp\u003eAvoid integer overflow in allocation-size calculations within \u003cspan\u003elibpq\u003c/span\u003e (Jacob Champion) \u003ca href=\"https://postgr.es/c/7eb8fcad8\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSeveral places in \u003cspan\u003elibpq\u003c/span\u003e 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Aleksey Solovev of Positive Technologies for reporting this problem. (CVE-2025-12818)\u003c/p\u003e","id":"18.1-3a4a5ae84a44ca49","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)","part":"changes","patch_ids":["16e4d7f7cb99380bcadbeb1a4c45eac4"],"relations":[{"evidence":{"patch_ids":["16e4d7f7cb99380bcadbeb1a4c45eac4"],"same_day":true,"statement_hash":"42e2acf7dbacc3d12e55dc8cc3dc23c6a2afed82c46ae3bf37cba022acdca1bb"},"rule":2,"target":"10c3ef25a629d41429d514190a9f5584","type":"equivalent"},{"evidence":{"patch_ids":["16e4d7f7cb99380bcadbeb1a4c45eac4"],"same_day":true,"statement_hash":"42e2acf7dbacc3d12e55dc8cc3dc23c6a2afed82c46ae3bf37cba022acdca1bb"},"rule":2,"target":"1f91b721b071de697f740c95cd556a9e","type":"equivalent"},{"evidence":{"patch_ids":["16e4d7f7cb99380bcadbeb1a4c45eac4"],"same_day":true,"statement_hash":"42e2acf7dbacc3d12e55dc8cc3dc23c6a2afed82c46ae3bf37cba022acdca1bb"},"rule":2,"target":"601fa44b8aa3f725f41f2320ba9cf51b","type":"equivalent"},{"evidence":{"patch_ids":["16e4d7f7cb99380bcadbeb1a4c45eac4"],"same_day":true,"statement_hash":"42e2acf7dbacc3d12e55dc8cc3dc23c6a2afed82c46ae3bf37cba022acdca1bb"},"rule":2,"target":"9b1eafd982ad52573adf6f2d6ae70703","type":"equivalent"},{"evidence":{"patch_ids":["16e4d7f7cb99380bcadbeb1a4c45eac4"],"same_day":true,"statement_hash":"42e2acf7dbacc3d12e55dc8cc3dc23c6a2afed82c46ae3bf37cba022acdca1bb"},"rule":2,"target":"cf7417da3f5aaff52ed6398652b5cefb","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["7eb8fcad8"],"source_entry_id":"18.1/changes/002","source_hash":"b45871c637865cee86198fd246cd8aabd5edf5df7efc227adeb36544fb4819da","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"42e2acf7dbacc3d12e55dc8cc3dc23c6a2afed82c46ae3bf37cba022acdca1bb","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"},"id":"18.1-3a4a5ae84a44ca49","matches":[{"id":"17.7-a326b8fad6479f02","source_entry_id":"17.7/changes/002","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Avoid integer overflow in allocation-size calculations within libpq","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/002","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Avoid integer overflow in allocation-size calculations within libpq","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["09f86a42f","1baae827e","1e6dfdaa0","c09a06918","dc9125111","ef5e60a9d"],"commit_groups":[["09f86a42f","dc9125111","ef5e60a9d"],["1baae827e","1e6dfdaa0","c09a06918"]],"commits":["1baae827e","dc9125111"],"cves":[],"db_id":"4870df49130804d64e1e92d7f9d6f17f","html":"\u003cp\u003ePrevent \u003cspan\u003e“\u003cspan\u003eunrecognized node type\u003c/span\u003e”\u003c/span\u003e errors when a SQL/JSON function such as \u003ccode\u003eJSON_VALUE\u003c/code\u003e has a \u003ccode\u003eDEFAULT\u003c/code\u003e clause containing a \u003ccode\u003eCOLLATE\u003c/code\u003e expression (Jian He) \u003ca href=\"https://postgr.es/c/dc9125111\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/1baae827e\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-b921a1ea6f2b8ead","identity_text":"Prevent unrecognized node type errors when a SQL/JSON function such as JSON_VALUE has a DEFAULT clause containing a COLLATE expression (Jian He)","part":"changes","patch_ids":["9aacced6a6f638f7d31013e87be76fac","b716f15276c076fd364e99593404fc28"],"relations":[{"evidence":{"patch_ids":["9aacced6a6f638f7d31013e87be76fac","b716f15276c076fd364e99593404fc28"],"same_day":true,"statement_hash":"3181f0e422077fb0af80285571b22222a84421d45cb3710f3ce56bbe5fc3852c"},"rule":2,"target":"3387a44cfd06079d33247002758176c2","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["1baae827e","dc9125111"],"source_entry_id":"18.1/changes/003","source_hash":"b8839fac421b0ed413869d4e000cad7d9a3ccfe9b3c3a11d9fafca5e41e7e8f0","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"3181f0e422077fb0af80285571b22222a84421d45cb3710f3ce56bbe5fc3852c","text":"Prevent “unrecognized node type” errors when a SQL/JSON function such as JSON_VALUE has a DEFAULT clause containing a COLLATE expression (Jian He) § §","title":"Prevent “unrecognized node type” errors when a SQL/JSON function such as JSON_VALUE has a DEFAULT clause containing a COLLATE expression"},"id":"18.1-b921a1ea6f2b8ead","matches":[{"id":"17.7-7345a25f928001c5","source_entry_id":"17.7/changes/003","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","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/003","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","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["314004021","61de81a49","843e50208","ae15cebc2","af302ff6b","c160fd469","ca0c93908"],"commit_groups":[["314004021","61de81a49","843e50208","ae15cebc2","af302ff6b","c160fd469","ca0c93908"]],"commits":["61de81a49"],"cves":[],"db_id":"1a0e9b151c18103e9e44e0d5b065435e","html":"\u003cp\u003eRemove faulty assertion in btree index cleanup (Peter Geoghegan) \u003ca href=\"https://postgr.es/c/61de81a49\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-b879ef73b7e33cee","identity_text":"Remove faulty assertion in btree index cleanup (Peter Geoghegan)","part":"changes","patch_ids":["37c608f60096a634457e03ef403861d6"],"relations":[{"evidence":{"patch_ids":["37c608f60096a634457e03ef403861d6"],"same_day":true,"statement_hash":"10a7d45ffeb0f11200d10e8732198f5dd91b4ea27bc91850c29a64cd2e8239a1"},"rule":2,"target":"0a57a548c4b77cd7d910727d3c65b3a6","type":"equivalent"},{"evidence":{"patch_ids":["37c608f60096a634457e03ef403861d6"],"same_day":true,"statement_hash":"10a7d45ffeb0f11200d10e8732198f5dd91b4ea27bc91850c29a64cd2e8239a1"},"rule":2,"target":"3933929e20ae66e9831bcbabb992d203","type":"equivalent"},{"evidence":{"patch_ids":["37c608f60096a634457e03ef403861d6"],"same_day":true,"statement_hash":"10a7d45ffeb0f11200d10e8732198f5dd91b4ea27bc91850c29a64cd2e8239a1"},"rule":2,"target":"444038cce9bb99031a082f8098e1be72","type":"equivalent"},{"evidence":{"patch_ids":["37c608f60096a634457e03ef403861d6"],"same_day":true,"statement_hash":"10a7d45ffeb0f11200d10e8732198f5dd91b4ea27bc91850c29a64cd2e8239a1"},"rule":2,"target":"488141078c6f2db091ee11544337a811","type":"equivalent"},{"evidence":{"patch_ids":["37c608f60096a634457e03ef403861d6"],"same_day":true,"statement_hash":"10a7d45ffeb0f11200d10e8732198f5dd91b4ea27bc91850c29a64cd2e8239a1"},"rule":2,"target":"9e457bb041db2cbeaeaf7995dafca323","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["61de81a49"],"source_entry_id":"18.1/changes/008","source_hash":"59bedcdf0405a0fdb81cbd2d57d7e60036379d06f239428467ffd59ad5ee4756","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"10a7d45ffeb0f11200d10e8732198f5dd91b4ea27bc91850c29a64cd2e8239a1","text":"Remove faulty assertion in btree index cleanup (Peter Geoghegan) §","title":"Remove faulty assertion in btree index cleanup"},"id":"18.1-b879ef73b7e33cee","matches":[{"id":"17.7-0a5a861bce4d8e04","source_entry_id":"17.7/changes/009","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Remove faulty assertion in btree index cleanup","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/008","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Remove faulty assertion in btree index cleanup","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["0a3d27bfe","20442cf50","23ddadf68","3b5007347","3c7b47974","419ffde23","65b0d1f74","6ef33c805","8733f0b54","a95e3d84c","bcfbd3f74","ef81697fe","f0ad41716","f4b68b033"],"commit_groups":[["0a3d27bfe","20442cf50","3b5007347","65b0d1f74","8733f0b54","bcfbd3f74","ef81697fe"],["23ddadf68","3c7b47974","419ffde23","6ef33c805","a95e3d84c","f0ad41716","f4b68b033"]],"commits":["419ffde23","8733f0b54"],"cves":[],"db_id":"5e3ad415c950ddc874e527c528e4312f","html":"\u003cp\u003eEnsure that BRIN autosummarization provides a snapshot for index expressions that need one (Álvaro Herrera) \u003ca href=\"https://postgr.es/c/419ffde23\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/8733f0b54\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, autosummarization would fail for such indexes, and then leave placeholder index tuples behind, causing the index to bloat over time.\u003c/p\u003e","id":"18.1-a00fe3bcec296ab2","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.","part":"changes","patch_ids":["31ad60583179a46f035e6ca49acb5df0","3fdff7630c20c4073bba1b6676191274"],"relations":[{"evidence":{"patch_ids":["31ad60583179a46f035e6ca49acb5df0","3fdff7630c20c4073bba1b6676191274"],"same_day":true,"statement_hash":"62e341cf9b11ac9a64fec02e85a546e8c1574a3998b12b548653d69ab6270585"},"rule":2,"target":"0cb94d7b769fa6011ab24dd8d4a5182f","type":"equivalent"},{"evidence":{"patch_ids":["31ad60583179a46f035e6ca49acb5df0","3fdff7630c20c4073bba1b6676191274"],"same_day":true,"statement_hash":"62e341cf9b11ac9a64fec02e85a546e8c1574a3998b12b548653d69ab6270585"},"rule":2,"target":"0dd09cb0d2d5f7d388110d5f734dee23","type":"equivalent"},{"evidence":{"patch_ids":["31ad60583179a46f035e6ca49acb5df0","3fdff7630c20c4073bba1b6676191274"],"same_day":true,"statement_hash":"62e341cf9b11ac9a64fec02e85a546e8c1574a3998b12b548653d69ab6270585"},"rule":2,"target":"3e8741d3d489044f4c55886a02fd1ca6","type":"equivalent"},{"evidence":{"patch_ids":["31ad60583179a46f035e6ca49acb5df0","3fdff7630c20c4073bba1b6676191274"],"same_day":true,"statement_hash":"62e341cf9b11ac9a64fec02e85a546e8c1574a3998b12b548653d69ab6270585"},"rule":2,"target":"721aeb1deeff7de3e90db706f730ab11","type":"equivalent"},{"evidence":{"patch_ids":["31ad60583179a46f035e6ca49acb5df0","3fdff7630c20c4073bba1b6676191274"],"same_day":true,"statement_hash":"62e341cf9b11ac9a64fec02e85a546e8c1574a3998b12b548653d69ab6270585"},"rule":2,"target":"7f0361a52a096ffc5b14904781aeb0bc","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["419ffde23","8733f0b54"],"source_entry_id":"18.1/changes/010","source_hash":"72084de464215059c3d1b5ad06a481c8d136be1b10eac24c155283ac177e3095","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"62e341cf9b11ac9a64fec02e85a546e8c1574a3998b12b548653d69ab6270585","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"},"id":"18.1-a00fe3bcec296ab2","matches":[{"id":"17.7-a8f10736234e0b39","source_entry_id":"17.7/changes/012","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Ensure that BRIN autosummarization provides a snapshot for index expressions that need one","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/010","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Ensure that BRIN autosummarization provides a snapshot for index expressions that need one","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["715983a81","810aaf7f2","9fd29d7ff","c28f8ca29","c4f5a59ab","eea24eb0a","ef915bf93"],"commit_groups":[["715983a81","810aaf7f2","9fd29d7ff","c28f8ca29","c4f5a59ab","eea24eb0a","ef915bf93"]],"commits":["715983a81"],"cves":[],"db_id":"393a9b7eb2a54302a3bd8b2790808ca8","html":"\u003cp\u003eFix integer-overflow hazard in BRIN index scans when the table contains close to 2\u003csup\u003e32\u003c/sup\u003e pages (Sunil S) \u003ca href=\"https://postgr.es/c/715983a81\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis oversight could result in an infinite loop or scanning of unneeded table pages.\u003c/p\u003e","id":"18.1-4d75a8abffa08925","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.","part":"changes","patch_ids":["e15f4df722672d015993ea819e9c3351"],"relations":[{"evidence":{"patch_ids":["e15f4df722672d015993ea819e9c3351"],"same_day":true,"statement_hash":"45088b42382a6f8a5eb8dc651e95a4c956a04e585cd53f0e8247416c8d6fce3f"},"rule":2,"target":"3eee9fbd93044d08fe7b761285b4eef0","type":"equivalent"},{"evidence":{"patch_ids":["e15f4df722672d015993ea819e9c3351"],"same_day":true,"statement_hash":"45088b42382a6f8a5eb8dc651e95a4c956a04e585cd53f0e8247416c8d6fce3f"},"rule":2,"target":"41c5c1173ef259c7bb96b3467e9de919","type":"equivalent"},{"evidence":{"patch_ids":["e15f4df722672d015993ea819e9c3351"],"same_day":true,"statement_hash":"45088b42382a6f8a5eb8dc651e95a4c956a04e585cd53f0e8247416c8d6fce3f"},"rule":2,"target":"c0b6100e40d8b770ece9bacc3084ea91","type":"equivalent"},{"evidence":{"patch_ids":["e15f4df722672d015993ea819e9c3351"],"same_day":true,"statement_hash":"45088b42382a6f8a5eb8dc651e95a4c956a04e585cd53f0e8247416c8d6fce3f"},"rule":2,"target":"ca0d04f29eca7d84d81b300dc4107221","type":"equivalent"},{"evidence":{"patch_ids":["e15f4df722672d015993ea819e9c3351"],"same_day":true,"statement_hash":"45088b42382a6f8a5eb8dc651e95a4c956a04e585cd53f0e8247416c8d6fce3f"},"rule":2,"target":"cbb0ef9e07e346b9959c4a482b828973","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["715983a81"],"source_entry_id":"18.1/changes/011","source_hash":"a227f200daffb8d9736fdb106e7db525288805f9d039e2aed7b51c500b5e9285","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"45088b42382a6f8a5eb8dc651e95a4c956a04e585cd53f0e8247416c8d6fce3f","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"},"id":"18.1-4d75a8abffa08925","matches":[{"id":"17.7-22b81d2b7991be50","source_entry_id":"17.7/changes/013","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","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/011","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","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["10945148e","3398b0d02","4afab175b","6911f8037","b8ecfbe5a","ceb51d09b","e4316ec4d"],"commit_groups":[["10945148e","3398b0d02","4afab175b","6911f8037","b8ecfbe5a","ceb51d09b","e4316ec4d"]],"commits":["ceb51d09b"],"cves":[],"db_id":"de262079624c4f7225fefc1938b4d6c4","html":"\u003cp\u003eFix incorrect zero-extension of stored values in JIT-generated tuple deforming code (David Rowley) \u003ca href=\"https://postgr.es/c/ceb51d09b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWhen 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 \u003cspan\u003e“\u003cspan\u003ecould not find memoization table entry\u003c/span\u003e”\u003c/span\u003e errors when using Memoize plan nodes, and there might be other symptoms.\u003c/p\u003e","id":"18.1-d78511e9b384a86b","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.","part":"changes","patch_ids":["55424639c609ad9b211ffd5ac10cc20b"],"relations":[{"evidence":{"patch_ids":["55424639c609ad9b211ffd5ac10cc20b"],"same_day":true,"statement_hash":"d62bd3e9007f7f090eba935ee43673f57b512e6913d636b18186f3f90712f8fb"},"rule":2,"target":"7c81d67412977edb96996856917b1f9a","type":"equivalent"},{"evidence":{"patch_ids":["55424639c609ad9b211ffd5ac10cc20b"],"same_day":true,"statement_hash":"d62bd3e9007f7f090eba935ee43673f57b512e6913d636b18186f3f90712f8fb"},"rule":2,"target":"8411046717133be1fc919e915895664b","type":"equivalent"},{"evidence":{"patch_ids":["55424639c609ad9b211ffd5ac10cc20b"],"same_day":true,"statement_hash":"d62bd3e9007f7f090eba935ee43673f57b512e6913d636b18186f3f90712f8fb"},"rule":2,"target":"9b610d9fca503412ae7e72eddc6e5502","type":"equivalent"},{"evidence":{"patch_ids":["55424639c609ad9b211ffd5ac10cc20b"],"same_day":true,"statement_hash":"d62bd3e9007f7f090eba935ee43673f57b512e6913d636b18186f3f90712f8fb"},"rule":2,"target":"c520d8534b29d6a33acf98a0e9c4f0ef","type":"equivalent"},{"evidence":{"patch_ids":["55424639c609ad9b211ffd5ac10cc20b"],"same_day":true,"statement_hash":"d62bd3e9007f7f090eba935ee43673f57b512e6913d636b18186f3f90712f8fb"},"rule":2,"target":"e11c7ac708a333ed4eb5a375fef717d8","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["ceb51d09b"],"source_entry_id":"18.1/changes/012","source_hash":"e82cf8c36ee531c20dbe457691d6d17ef5a6a4de2b92f57fdcfdb5db66d65a3d","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"d62bd3e9007f7f090eba935ee43673f57b512e6913d636b18186f3f90712f8fb","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"},"id":"18.1-d78511e9b384a86b","matches":[{"id":"17.7-aa1a9b53c515db45","source_entry_id":"17.7/changes/014","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix incorrect zero-extension of stored values in JIT-generated tuple deforming code","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/012","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix incorrect zero-extension of stored values in JIT-generated tuple deforming code","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["0d3074615","2992b9a07","39dcfda2d","a2387c32f","a546964db"],"commit_groups":[["0d3074615","2992b9a07","39dcfda2d","a2387c32f","a546964db"]],"commits":["a2387c32f"],"cves":[],"db_id":"13af7f30c1a66144a7c4729335ad6c55","html":"\u003cp\u003eFix incorrect logic for caching result-relation information for triggers (David Rowley, Amit Langote) \u003ca href=\"https://postgr.es/c/a2387c32f\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIn cases where partitions' column sets aren't physically identical to their parent partitioned tables' column sets, this oversight could lead to crashes.\u003c/p\u003e","id":"18.1-fa17262588de7970","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.","part":"changes","patch_ids":["aceec90d9a86d1b6d642dda660eebd6f"],"relations":[{"evidence":{"patch_ids":["aceec90d9a86d1b6d642dda660eebd6f"],"same_day":true,"statement_hash":"026782085dea5b1090d57d834e0d4c7d0bc778a784349b74f9ef89ce84fcfaef"},"rule":2,"target":"7ba23c07eaeb399e352fe32a704464e6","type":"equivalent"},{"evidence":{"patch_ids":["aceec90d9a86d1b6d642dda660eebd6f"],"same_day":true,"statement_hash":"026782085dea5b1090d57d834e0d4c7d0bc778a784349b74f9ef89ce84fcfaef"},"rule":2,"target":"ba3b5897c3d85845178cb5eee8dfba01","type":"equivalent"},{"evidence":{"patch_ids":["aceec90d9a86d1b6d642dda660eebd6f"],"same_day":true,"statement_hash":"026782085dea5b1090d57d834e0d4c7d0bc778a784349b74f9ef89ce84fcfaef"},"rule":2,"target":"bb7f7a3657690f7a6c75d641dcc65860","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["a2387c32f"],"source_entry_id":"18.1/changes/016","source_hash":"7e6a20eac8e6a679bac5be291d65d4bde10ba300dbe130df9e3bc131f6fe1ef8","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"026782085dea5b1090d57d834e0d4c7d0bc778a784349b74f9ef89ce84fcfaef","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"},"id":"18.1-fa17262588de7970","matches":[{"id":"17.7-6305949a00dd4b54","source_entry_id":"17.7/changes/015","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix incorrect logic for caching result-relation information for triggers","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/016","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix incorrect logic for caching result-relation information for triggers","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["12609fbac","12b0c0e51","24e74b962","2bb84ea7e","4a08603a2","5a9af4868","b14144325"],"commit_groups":[["12609fbac","12b0c0e51","24e74b962","2bb84ea7e","4a08603a2","5a9af4868","b14144325"]],"commits":["b14144325"],"cves":[],"db_id":"3a7c71a715168a6fe003c04ad6530b01","html":"\u003cp\u003eFix EvalPlanQual handling of foreign or custom joins that do not have an alternative local-join plan prepared for EPQ (Masahiko Sawada, Etsuro Fujita) \u003ca href=\"https://postgr.es/c/b14144325\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIn such cases the foreign or custom access method should be invoked normally, but that did not happen, typically leading to a crash.\u003c/p\u003e","id":"18.1-1ad36d259b8c4e29","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.","part":"changes","patch_ids":["4bc4b3eb3e3195a1d0e412e0c9371242"],"relations":[{"evidence":{"patch_ids":["4bc4b3eb3e3195a1d0e412e0c9371242"],"same_day":true,"statement_hash":"7701ad14c992b95ece421f86b54788df6de9143a62d4e7ff9ea0b08caf2163f5"},"rule":2,"target":"152497e1f56957947f79200f3011a52e","type":"equivalent"},{"evidence":{"patch_ids":["4bc4b3eb3e3195a1d0e412e0c9371242"],"same_day":true,"statement_hash":"7701ad14c992b95ece421f86b54788df6de9143a62d4e7ff9ea0b08caf2163f5"},"rule":2,"target":"a830cee6374ea38a3cf10eb53388b93d","type":"equivalent"},{"evidence":{"patch_ids":["4bc4b3eb3e3195a1d0e412e0c9371242"],"same_day":true,"statement_hash":"7701ad14c992b95ece421f86b54788df6de9143a62d4e7ff9ea0b08caf2163f5"},"rule":2,"target":"b4c88efd3c63eeaee70001c500504502","type":"equivalent"},{"evidence":{"patch_ids":["4bc4b3eb3e3195a1d0e412e0c9371242"],"same_day":true,"statement_hash":"7701ad14c992b95ece421f86b54788df6de9143a62d4e7ff9ea0b08caf2163f5"},"rule":2,"target":"d5c74a3284403534934e2ff5e453332e","type":"equivalent"},{"evidence":{"patch_ids":["4bc4b3eb3e3195a1d0e412e0c9371242"],"same_day":true,"statement_hash":"7701ad14c992b95ece421f86b54788df6de9143a62d4e7ff9ea0b08caf2163f5"},"rule":2,"target":"f8e7d0fe512da9f5e4221f5173c42a62","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b14144325"],"source_entry_id":"18.1/changes/018","source_hash":"68bd82f61fd04a0e7bc6338db072a1418250c1160d5cc3607107def8305a4549","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"7701ad14c992b95ece421f86b54788df6de9143a62d4e7ff9ea0b08caf2163f5","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"},"id":"18.1-1ad36d259b8c4e29","matches":[{"id":"17.7-7d939e96432565c4","source_entry_id":"17.7/changes/017","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","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/018","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","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["08c037dff","3231fd045","b753be38a","b835759ec","bdae98495","ea06f97ee"],"commit_groups":[["08c037dff","3231fd045","b753be38a","b835759ec","bdae98495","ea06f97ee"]],"commits":["08c037dff"],"cves":[],"db_id":"565728557128822df30c43191a2dbfad","html":"\u003cp\u003eAvoid duplicating hash partition constraints during \u003ccode\u003eDETACH CONCURRENTLY\u003c/code\u003e (Haiyang Li) \u003ca href=\"https://postgr.es/c/08c037dff\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eALTER TABLE DETACH PARTITION CONCURRENTLY\u003c/code\u003e was written to add a copy of the partitioning constraint to the now-detached partition. This was misguided, partially because non-concurrent \u003ccode\u003eDETACH\u003c/code\u003e 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 \u003ccode\u003eDETACH\u003c/code\u003e. 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.\u003c/p\u003e","id":"18.1-570dc654ef6dd9a2","identity_text":"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.","part":"changes","patch_ids":["c7b7e5ea3577b3d900e06cd112a51878"],"relations":[{"evidence":{"patch_ids":["c7b7e5ea3577b3d900e06cd112a51878"],"same_day":true,"statement_hash":"d5965bdd5734479eaa6212fe4307924b5fa45a4534d11494cdf8e41c2b84b97f"},"rule":2,"target":"417982fb5fc35be16b96cd9dffae86f4","type":"equivalent"},{"evidence":{"patch_ids":["c7b7e5ea3577b3d900e06cd112a51878"],"same_day":true,"statement_hash":"d5965bdd5734479eaa6212fe4307924b5fa45a4534d11494cdf8e41c2b84b97f"},"rule":2,"target":"71fe017c4d7b33e60357f0d6d3c24f44","type":"equivalent"},{"evidence":{"patch_ids":["c7b7e5ea3577b3d900e06cd112a51878"],"same_day":true,"statement_hash":"d5965bdd5734479eaa6212fe4307924b5fa45a4534d11494cdf8e41c2b84b97f"},"rule":2,"target":"cf6c332f29166e2669260e45b57ff0d2","type":"equivalent"},{"evidence":{"patch_ids":["c7b7e5ea3577b3d900e06cd112a51878"],"same_day":true,"statement_hash":"d5965bdd5734479eaa6212fe4307924b5fa45a4534d11494cdf8e41c2b84b97f"},"rule":2,"target":"d8002886e5e02df8376c5986e54462f2","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["08c037dff"],"source_entry_id":"18.1/changes/019","source_hash":"7e59da2bb8190713c1b6aaecda2d276233b7a05b5210c8dcd12d3e20b33779f5","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"d5965bdd5734479eaa6212fe4307924b5fa45a4534d11494cdf8e41c2b84b97f","text":"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.","title":"Avoid duplicating hash partition constraints during DETACH CONCURRENTLY"},"id":"18.1-570dc654ef6dd9a2","matches":[{"id":"17.7-7064942458440619","source_entry_id":"17.7/changes/018","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Avoid duplicating hash partition constraints during DETACH CONCURRENTLY","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/019","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Avoid duplicating hash partition constraints during DETACH CONCURRENTLY","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["040cc5f3c","04345d7a4","0b44f2443","643a5e96c","7180d56c5","7f239c72a","ba99c9491"],"commit_groups":[["040cc5f3c","04345d7a4","0b44f2443","643a5e96c","7180d56c5","7f239c72a","ba99c9491"]],"commits":["ba99c9491"],"cves":[],"db_id":"a8595e24703e1deff3ce7b6fe56d02db","html":"\u003cp\u003eDisallow generated columns in partition keys (Jian He, Ashutosh Bapat) \u003ca href=\"https://postgr.es/c/ba99c9491\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis was already not allowed, but the check missed some cases, such as where the column reference is implicit in a whole-row reference.\u003c/p\u003e","id":"18.1-6edf5c69ea4392a4","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.","part":"changes","patch_ids":["26b7dee3d5b5a82dd804a2b2e1ecd780"],"relations":[{"evidence":{"patch_ids":["26b7dee3d5b5a82dd804a2b2e1ecd780"],"same_day":true,"statement_hash":"5dded4849247ab37d7f44a8fd133cdab652ee07cbfab3751bd8d4ffcbdd7e99f"},"rule":2,"target":"300cd459ecbe8f82fbe0665d8d6b47c5","type":"equivalent"},{"evidence":{"patch_ids":["26b7dee3d5b5a82dd804a2b2e1ecd780"],"same_day":true,"statement_hash":"5dded4849247ab37d7f44a8fd133cdab652ee07cbfab3751bd8d4ffcbdd7e99f"},"rule":2,"target":"525dd26c2bb1d8a0169ce29cab95adac","type":"equivalent"},{"evidence":{"patch_ids":["26b7dee3d5b5a82dd804a2b2e1ecd780"],"same_day":true,"statement_hash":"5dded4849247ab37d7f44a8fd133cdab652ee07cbfab3751bd8d4ffcbdd7e99f"},"rule":2,"target":"605ca6399f9aae142eb2f308e3d598fd","type":"equivalent"},{"evidence":{"patch_ids":["26b7dee3d5b5a82dd804a2b2e1ecd780"],"same_day":true,"statement_hash":"5dded4849247ab37d7f44a8fd133cdab652ee07cbfab3751bd8d4ffcbdd7e99f"},"rule":2,"target":"8894dad53381cd45feb93c24e4fb14ba","type":"equivalent"},{"evidence":{"patch_ids":["26b7dee3d5b5a82dd804a2b2e1ecd780"],"same_day":true,"statement_hash":"5dded4849247ab37d7f44a8fd133cdab652ee07cbfab3751bd8d4ffcbdd7e99f"},"rule":2,"target":"adb9f0cae7cdccc24195248ff3704b74","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["ba99c9491"],"source_entry_id":"18.1/changes/020","source_hash":"c34ef2c7cbe47429ce0a76c1aa2caa7f267cdc4c1707565553f5dc4cd8576ddd","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"5dded4849247ab37d7f44a8fd133cdab652ee07cbfab3751bd8d4ffcbdd7e99f","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"},"id":"18.1-6edf5c69ea4392a4","matches":[{"id":"17.7-6b87f410ccf7eeba","source_entry_id":"17.7/changes/019","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Disallow generated columns in partition keys","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/020","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Disallow generated columns in partition keys","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["07f787e57","0f9e0068b","26958f4d9","3717849e6","8278737bf","aa606b931","ccfe28eb4"],"commit_groups":[["07f787e57","0f9e0068b","26958f4d9","3717849e6","8278737bf","aa606b931","ccfe28eb4"]],"commits":["0f9e0068b"],"cves":[],"db_id":"476c1d31c3b2a4f231e061a533173538","html":"\u003cp\u003eDisallow generated columns in \u003ccode\u003eCOPY ... FROM ... WHERE\u003c/code\u003e clauses (Peter Eisentraut, Jian He) \u003ca href=\"https://postgr.es/c/0f9e0068b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, 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 \u003ccode\u003eWHERE\u003c/code\u003e filtering is done.\u003c/p\u003e","id":"18.1-f93c705391287b77","identity_text":"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.","part":"changes","patch_ids":["288ff18af81cea964c777c267d44976b"],"relations":[{"evidence":{"patch_ids":["288ff18af81cea964c777c267d44976b"],"same_day":true,"statement_hash":"3e3e53285ed4984ded0685482e76482c19c858ab07dd559f8421550b25cb5dc6"},"rule":2,"target":"688b8d0a8d86ff5dfc64586a1e76d364","type":"equivalent"},{"evidence":{"patch_ids":["288ff18af81cea964c777c267d44976b"],"same_day":true,"statement_hash":"3e3e53285ed4984ded0685482e76482c19c858ab07dd559f8421550b25cb5dc6"},"rule":2,"target":"7910dd8ca51fdddfcd65a301d722ec44","type":"equivalent"},{"evidence":{"patch_ids":["288ff18af81cea964c777c267d44976b"],"same_day":true,"statement_hash":"3e3e53285ed4984ded0685482e76482c19c858ab07dd559f8421550b25cb5dc6"},"rule":2,"target":"7b8f833f1bd965ce518eb2d3e003a1dc","type":"equivalent"},{"evidence":{"patch_ids":["288ff18af81cea964c777c267d44976b"],"same_day":true,"statement_hash":"3e3e53285ed4984ded0685482e76482c19c858ab07dd559f8421550b25cb5dc6"},"rule":2,"target":"9cbb9b53b5d6bb4acf6cc0063d8379f2","type":"equivalent"},{"evidence":{"patch_ids":["288ff18af81cea964c777c267d44976b"],"same_day":true,"statement_hash":"3e3e53285ed4984ded0685482e76482c19c858ab07dd559f8421550b25cb5dc6"},"rule":2,"target":"d7b4a6585334f8e8aa07a327994e2043","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["0f9e0068b"],"source_entry_id":"18.1/changes/021","source_hash":"96a32620f5a6b43836e51a7fab983dad5c9aa7e9311a79e3a3119442e89844ac","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"3e3e53285ed4984ded0685482e76482c19c858ab07dd559f8421550b25cb5dc6","text":"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.","title":"Disallow generated columns in COPY ... FROM ... WHERE clauses"},"id":"18.1-f93c705391287b77","matches":[{"id":"17.7-0707cf226664ba13","source_entry_id":"17.7/changes/020","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Disallow generated columns in COPY ... FROM ... WHERE clauses","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/021","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Disallow generated columns in COPY ... FROM ... WHERE clauses","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["3549ffb6a","54ab74865","76613b539"],"commit_groups":[["3549ffb6a","54ab74865","76613b539"]],"commits":["76613b539"],"cves":[],"db_id":"65b586522e7240dd1f867d7850ea61db","html":"\u003cp\u003eAvoid potential use-after-free in parallel vacuum (Kevin Oommen Anish) \u003ca href=\"https://postgr.es/c/76613b539\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis bug seems to have no consequences in standard builds, but it's theoretically a hazard.\u003c/p\u003e","id":"18.1-546fe16e34bc5978","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.","part":"changes","patch_ids":["d0dc5f67240a1a53daeb03d7af4ee34b"],"relations":[{"evidence":{"patch_ids":["d0dc5f67240a1a53daeb03d7af4ee34b"],"same_day":true,"statement_hash":"e224742c5033ba7b9e4b42ddebc1f168038cd08a476019b13fb8d75e3b5bc706"},"rule":2,"target":"f0dbb32056abe3b3dfdd78472b7f273b","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["76613b539"],"source_entry_id":"18.1/changes/023","source_hash":"794966efecdda80a55b270d172d2da28726e6f70a5a5522d7467b5a2506ac2d1","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"e224742c5033ba7b9e4b42ddebc1f168038cd08a476019b13fb8d75e3b5bc706","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"},"id":"18.1-546fe16e34bc5978","matches":[{"id":"17.7-8f2649a92990dc78","source_entry_id":"17.7/changes/021","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Avoid potential use-after-free in parallel vacuum","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/023","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Avoid potential use-after-free in parallel vacuum","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["5816baa9b","6778fbca6","a95393ecd","ab16418ee","afb2cce74","d024160ff","d202ec1fb"],"commit_groups":[["5816baa9b","6778fbca6","a95393ecd","ab16418ee","afb2cce74","d024160ff","d202ec1fb"]],"commits":["d024160ff"],"cves":[],"db_id":"20af10bca614d2e3d01c9b7d89ca87a3","html":"\u003cp\u003eFix visibility checking for statistics objects in \u003ccode\u003epg_temp\u003c/code\u003e (Noah Misch) \u003ca href=\"https://postgr.es/c/d024160ff\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA statistics object located in a temporary schema cannot be named without schema qualification, but \u003ccode\u003epg_statistics_obj_is_visible()\u003c/code\u003e missed that memo and could return \u003cspan\u003e“\u003cspan\u003etrue\u003c/span\u003e”\u003c/span\u003e regardless. In turn, functions such as \u003ccode\u003epg_describe_object()\u003c/code\u003e could fail to schema-qualify the object's name as expected.\u003c/p\u003e","id":"18.1-4356f370a232f620","identity_text":"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.","part":"changes","patch_ids":["92d91f4ff61990d871fd5034eef653d7"],"relations":[{"evidence":{"patch_ids":["92d91f4ff61990d871fd5034eef653d7"],"same_day":true,"statement_hash":"6ab2a16a11fdf9756b132b2aa3b08c0bc2821a0def25ca6fd133def84e610d24"},"rule":2,"target":"12fee3df0b5233b7e8135e949ea2f87f","type":"equivalent"},{"evidence":{"patch_ids":["92d91f4ff61990d871fd5034eef653d7"],"same_day":true,"statement_hash":"6ab2a16a11fdf9756b132b2aa3b08c0bc2821a0def25ca6fd133def84e610d24"},"rule":2,"target":"7e832b26c5667abdcb7da1479c2627cc","type":"equivalent"},{"evidence":{"patch_ids":["92d91f4ff61990d871fd5034eef653d7"],"same_day":true,"statement_hash":"6ab2a16a11fdf9756b132b2aa3b08c0bc2821a0def25ca6fd133def84e610d24"},"rule":2,"target":"8294c317781f8f709b7133dfce95b792","type":"equivalent"},{"evidence":{"patch_ids":["92d91f4ff61990d871fd5034eef653d7"],"same_day":true,"statement_hash":"6ab2a16a11fdf9756b132b2aa3b08c0bc2821a0def25ca6fd133def84e610d24"},"rule":2,"target":"875f65c32c6f6827a1f949b0b14ab7c2","type":"equivalent"},{"evidence":{"patch_ids":["92d91f4ff61990d871fd5034eef653d7"],"same_day":true,"statement_hash":"6ab2a16a11fdf9756b132b2aa3b08c0bc2821a0def25ca6fd133def84e610d24"},"rule":2,"target":"9ba9c2385da1c0904fac8dc3ed1373f9","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["d024160ff"],"source_entry_id":"18.1/changes/024","source_hash":"af2707e6586fbda4dcfaf8a61041a506fb3f6863d0bde7c5e7db840d18aa8d33","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"6ab2a16a11fdf9756b132b2aa3b08c0bc2821a0def25ca6fd133def84e610d24","text":"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.","title":"Fix visibility checking for statistics objects in pg_temp"},"id":"18.1-4356f370a232f620","matches":[{"id":"17.7-542a921308709f1a","source_entry_id":"17.7/changes/022","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix visibility checking for statistics objects in pg_temp","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/024","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix visibility checking for statistics objects in pg_temp","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["23b316c36","33e7b4a7c","c72b5c536","f9993ac64","ff47f9c16"],"commit_groups":[["23b316c36","33e7b4a7c","c72b5c536","f9993ac64","ff47f9c16"]],"commits":["33e7b4a7c"],"cves":[],"db_id":"0e7b5976bd913c25991a5ff549ac5f81","html":"\u003cp\u003eFix minor memory leak during WAL replay of database creation (Nathan Bossart) \u003ca href=\"https://postgr.es/c/33e7b4a7c\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-c10f4000798b8d9f","identity_text":"Fix minor memory leak during WAL replay of database creation (Nathan Bossart)","part":"changes","patch_ids":["7b3c9562820ec298d794a69d51573920"],"relations":[{"evidence":{"patch_ids":["7b3c9562820ec298d794a69d51573920"],"same_day":true,"statement_hash":"aaf589db3ca0547c1138682c80ba4c30d7666e77fdcd70b3a9824de7014ad03c"},"rule":2,"target":"07b0f2ed9748f2ad84f75138a8f693ab","type":"equivalent"},{"evidence":{"patch_ids":["7b3c9562820ec298d794a69d51573920"],"same_day":true,"statement_hash":"aaf589db3ca0547c1138682c80ba4c30d7666e77fdcd70b3a9824de7014ad03c"},"rule":2,"target":"4be639cfbce3dac014c7f3139f4beaa7","type":"equivalent"},{"evidence":{"patch_ids":["7b3c9562820ec298d794a69d51573920"],"same_day":true,"statement_hash":"aaf589db3ca0547c1138682c80ba4c30d7666e77fdcd70b3a9824de7014ad03c"},"rule":2,"target":"52d97c7cf8fbcce26fef4b0c910e4bf6","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["33e7b4a7c"],"source_entry_id":"18.1/changes/025","source_hash":"a381a6bd43d267b9f76ad047254634c9c95e037e775f93f4d28201deb4381cb1","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"aaf589db3ca0547c1138682c80ba4c30d7666e77fdcd70b3a9824de7014ad03c","text":"Fix minor memory leak during WAL replay of database creation (Nathan Bossart) §","title":"Fix minor memory leak during WAL replay of database creation"},"id":"18.1-c10f4000798b8d9f","matches":[{"id":"17.7-200457c819df1105","source_entry_id":"17.7/changes/026","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix minor memory leak during WAL replay of database creation","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/025","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix minor memory leak during WAL replay of database creation","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["2e55cf4ef","59b215f72","62d5ee75b","7d7ebdb80","883a95646","9670032cc","a7ab6ce6a"],"commit_groups":[["2e55cf4ef","59b215f72","62d5ee75b","7d7ebdb80","883a95646","9670032cc","a7ab6ce6a"]],"commits":["9670032cc"],"cves":[],"db_id":"a8414849a53aabf5dc53c77b1324c0d5","html":"\u003cp\u003eFix incorrect reporting of replication lag in \u003ccode\u003epg_stat_replication\u003c/code\u003e view (Fujii Masao) \u003ca href=\"https://postgr.es/c/9670032cc\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf any standby server's replay LSN stopped advancing, the \u003ccode\u003ewrite_lag\u003c/code\u003e and \u003ccode\u003eflush_lag\u003c/code\u003e columns would eventually stop updating.\u003c/p\u003e","id":"18.1-b311e5c7746f8633","identity_text":"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.","part":"changes","patch_ids":["8db46f90292912189aba63435360de0e"],"relations":[{"evidence":{"patch_ids":["8db46f90292912189aba63435360de0e"],"same_day":true,"statement_hash":"64f01eee07baa6edbcfc9de58c6f4a1ee0e57ae42455a11de26eb55f15310c9b"},"rule":2,"target":"73705651f9a3f30d44ed83016f7ac1b4","type":"equivalent"},{"evidence":{"patch_ids":["8db46f90292912189aba63435360de0e"],"same_day":true,"statement_hash":"64f01eee07baa6edbcfc9de58c6f4a1ee0e57ae42455a11de26eb55f15310c9b"},"rule":2,"target":"791fcff31a58ed212a423b5a722b6f4f","type":"equivalent"},{"evidence":{"patch_ids":["8db46f90292912189aba63435360de0e"],"same_day":true,"statement_hash":"64f01eee07baa6edbcfc9de58c6f4a1ee0e57ae42455a11de26eb55f15310c9b"},"rule":2,"target":"7ca4b40fd7ad687ba5827a90faa10c14","type":"equivalent"},{"evidence":{"patch_ids":["8db46f90292912189aba63435360de0e"],"same_day":true,"statement_hash":"64f01eee07baa6edbcfc9de58c6f4a1ee0e57ae42455a11de26eb55f15310c9b"},"rule":2,"target":"81b53885fae1691a0cea71be2e9b050a","type":"equivalent"},{"evidence":{"patch_ids":["8db46f90292912189aba63435360de0e"],"same_day":true,"statement_hash":"64f01eee07baa6edbcfc9de58c6f4a1ee0e57ae42455a11de26eb55f15310c9b"},"rule":2,"target":"905cf5ba46c020ac69b28eb9f2785b5c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["9670032cc"],"source_entry_id":"18.1/changes/026","source_hash":"4072bb158c7920b7b4bb50d95772901eb7bd28f35a45d14007539c13c9364213","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"64f01eee07baa6edbcfc9de58c6f4a1ee0e57ae42455a11de26eb55f15310c9b","text":"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.","title":"Fix incorrect reporting of replication lag in pg_stat_replication view"},"id":"18.1-b311e5c7746f8633","matches":[{"id":"17.7-fbae455a9f86efab","source_entry_id":"17.7/changes/031","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix incorrect reporting of replication lag in pg_stat_replication view","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/026","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix incorrect reporting of replication lag in pg_stat_replication view","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["1db2870bb","4fd916eab","6ff7ba9fe","b00a16bae","caf529aba","f106f53df","f33e60a53"],"commit_groups":[["1db2870bb","4fd916eab","6ff7ba9fe","b00a16bae","caf529aba","f106f53df","f33e60a53"]],"commits":["6ff7ba9fe"],"cves":[],"db_id":"d99230cf9e376e84d70ff48c950dfbd4","html":"\u003cp\u003eAvoid duplicative log messages about invalid \u003ccode\u003eprimary_slot_name\u003c/code\u003e settings (Fujii Masao) \u003ca href=\"https://postgr.es/c/6ff7ba9fe\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-f9c71c1aa9e41b8f","identity_text":"Avoid duplicative log messages about invalid primary_slot_name settings (Fujii Masao)","part":"changes","patch_ids":["9c341da983ece804e7edd31cc99a78ce"],"relations":[{"evidence":{"patch_ids":["9c341da983ece804e7edd31cc99a78ce"],"same_day":true,"statement_hash":"0ffd9e32fd1eef45d9928e6dee3e2be177442a1dda1f90e9f7218a34bb08d146"},"rule":2,"target":"5c7937a41540430a37c6313f454afd47","type":"equivalent"},{"evidence":{"patch_ids":["9c341da983ece804e7edd31cc99a78ce"],"same_day":true,"statement_hash":"0ffd9e32fd1eef45d9928e6dee3e2be177442a1dda1f90e9f7218a34bb08d146"},"rule":2,"target":"5d244383e118ee187bdf1d544ea5c57a","type":"equivalent"},{"evidence":{"patch_ids":["9c341da983ece804e7edd31cc99a78ce"],"same_day":true,"statement_hash":"0ffd9e32fd1eef45d9928e6dee3e2be177442a1dda1f90e9f7218a34bb08d146"},"rule":2,"target":"9c77ea90dcad71a57f74e096fec194cc","type":"equivalent"},{"evidence":{"patch_ids":["9c341da983ece804e7edd31cc99a78ce"],"same_day":true,"statement_hash":"0ffd9e32fd1eef45d9928e6dee3e2be177442a1dda1f90e9f7218a34bb08d146"},"rule":2,"target":"cf1cf0980c4a8fd8a92c2de26d804a18","type":"equivalent"},{"evidence":{"patch_ids":["9c341da983ece804e7edd31cc99a78ce"],"same_day":true,"statement_hash":"0ffd9e32fd1eef45d9928e6dee3e2be177442a1dda1f90e9f7218a34bb08d146"},"rule":2,"target":"d5025bddb4b7e773a31ef5a7852fa818","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["6ff7ba9fe"],"source_entry_id":"18.1/changes/027","source_hash":"9a05fa4790b674064b1a98525583db56a4e66371c149f67d363856aaf68a29d3","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"0ffd9e32fd1eef45d9928e6dee3e2be177442a1dda1f90e9f7218a34bb08d146","text":"Avoid duplicative log messages about invalid primary_slot_name settings (Fujii Masao) §","title":"Avoid duplicative log messages about invalid primary_slot_name settings"},"id":"18.1-f9c71c1aa9e41b8f","matches":[{"id":"17.7-a02e0c2e2b41cb37","source_entry_id":"17.7/changes/032","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Avoid duplicative log messages about invalid primary_slot_name settings","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/027","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Avoid duplicative log messages about invalid primary_slot_name settings","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["0024f5a10","b45a8d7d8","e0dc4bbfb"],"commit_groups":[["0024f5a10","b45a8d7d8","e0dc4bbfb"]],"commits":["b45a8d7d8"],"cves":[],"db_id":"b7ea92ca342575d1da32619d7a74920a","html":"\u003cp\u003eAvoid failures when \u003ccode\u003esynchronized_standby_slots\u003c/code\u003e references nonexistent replication slots (Shlok Kyal) \u003ca href=\"https://postgr.es/c/b45a8d7d8\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-54c0160872575046","identity_text":"Avoid failures when synchronized_standby_slots references nonexistent replication slots (Shlok Kyal)","part":"changes","patch_ids":["d1630eb2f319a290f48352db21038c81"],"relations":[{"evidence":{"patch_ids":["d1630eb2f319a290f48352db21038c81"],"same_day":true,"statement_hash":"1adb1692f54e8f619f583ed21023cf15f3e54cd145c1a48e863700b08b0c1d4a"},"rule":2,"target":"e94415bf2bf6f74daabb0dd238831f93","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b45a8d7d8"],"source_entry_id":"18.1/changes/028","source_hash":"0f406430afac78443128876f868a55c777f0402b61818a0d607be1c70acbd2e0","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"1adb1692f54e8f619f583ed21023cf15f3e54cd145c1a48e863700b08b0c1d4a","text":"Avoid failures when synchronized_standby_slots references nonexistent replication slots (Shlok Kyal) §","title":"Avoid failures when synchronized_standby_slots references nonexistent replication slots"},"id":"18.1-54c0160872575046","matches":[{"id":"17.7-256c71c4a8bc7974","source_entry_id":"17.7/changes/033","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Avoid failures when synchronized_standby_slots references nonexistent replication slots","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/028","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Avoid failures when synchronized_standby_slots references nonexistent replication slots","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["0adf424b4","42348839d","912af1c7e","9a6ea00ac","bfdd1a12d","c878d9808","f57f2760e"],"commit_groups":[["0adf424b4","42348839d","912af1c7e","9a6ea00ac","bfdd1a12d","c878d9808","f57f2760e"]],"commits":["9a6ea00ac"],"cves":[],"db_id":"88acef5002288cf26f90d74ea72f7dd0","html":"\u003cp\u003eRemove the unfinished slot state file after failing to write a replication slot's state to disk (Michael Paquier) \u003ca href=\"https://postgr.es/c/9a6ea00ac\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, a failure such as out-of-disk-space resulted in leaving a temporary \u003ccode\u003estate.tmp\u003c/code\u003e file behind. That's problematic because it would block all subsequent attempts to write the state, requiring manual intervention to clean up.\u003c/p\u003e","id":"18.1-a601bee3c15f74a5","identity_text":"Remove the unfinished slot state file after failing to write a replication slot's state to disk (Michael Paquier) Previously, 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.","part":"changes","patch_ids":["6f111c88b72506ba3e2d5c84c1b1cfcf"],"relations":[{"evidence":{"patch_ids":["6f111c88b72506ba3e2d5c84c1b1cfcf"],"same_day":true,"statement_hash":"c72e99f08db7312d40c0813e006b0820aa3bd77bf507b6561ee3def67607fe72"},"rule":2,"target":"0620bfd126e45a7fb30310413dd82566","type":"equivalent"},{"evidence":{"patch_ids":["6f111c88b72506ba3e2d5c84c1b1cfcf"],"same_day":true,"statement_hash":"c72e99f08db7312d40c0813e006b0820aa3bd77bf507b6561ee3def67607fe72"},"rule":2,"target":"4f476f781039e87ea8de4907a56dfba2","type":"equivalent"},{"evidence":{"patch_ids":["6f111c88b72506ba3e2d5c84c1b1cfcf"],"same_day":true,"statement_hash":"c72e99f08db7312d40c0813e006b0820aa3bd77bf507b6561ee3def67607fe72"},"rule":2,"target":"5f4978515e70467b8cd476a8782b3741","type":"equivalent"},{"evidence":{"patch_ids":["6f111c88b72506ba3e2d5c84c1b1cfcf"],"same_day":true,"statement_hash":"c72e99f08db7312d40c0813e006b0820aa3bd77bf507b6561ee3def67607fe72"},"rule":2,"target":"8f6b3684b0c7ebef23c4baebfd451ab8","type":"equivalent"},{"evidence":{"patch_ids":["6f111c88b72506ba3e2d5c84c1b1cfcf"],"same_day":true,"statement_hash":"c72e99f08db7312d40c0813e006b0820aa3bd77bf507b6561ee3def67607fe72"},"rule":2,"target":"d3ba6564e6c91003b631012ed6405fc2","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["9a6ea00ac"],"source_entry_id":"18.1/changes/029","source_hash":"9a2261e57d450c78d7ff2e36d822d6f24474a1f6410381427fd18ddb7cc75686","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"c72e99f08db7312d40c0813e006b0820aa3bd77bf507b6561ee3def67607fe72","text":"Remove the unfinished slot state file after failing to write a replication slot's state to disk (Michael Paquier) § Previously, 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.","title":"Remove the unfinished slot state file after failing to write a replication slot's state to disk"},"id":"18.1-a601bee3c15f74a5","matches":[{"id":"17.7-fa4d518d83f33a49","source_entry_id":"17.7/changes/034","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Remove the unfinished slot state file after failing to write a replication slot's state to disk","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/029","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Remove the unfinished slot state file after failing to write a replication slot's state to disk","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["2f6e1a490","37fc5de43","a54c7a113","e41d954da"],"commit_groups":[["2f6e1a490","37fc5de43","a54c7a113","e41d954da"]],"commits":["37fc5de43"],"cves":[],"db_id":"943decff2b98c926290fdf650e4a0edc","html":"\u003cp\u003eFix mishandling of lock timeout signals in parallel apply workers for logical replication (Hayato Kuroda) \u003ca href=\"https://postgr.es/c/37fc5de43\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe same signal number was being used for both worker shutdown and lock timeout, leading to confusion.\u003c/p\u003e","id":"18.1-b4b351d19dc05865","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.","part":"changes","patch_ids":["b3db903786744763190489d6bf47d765"],"relations":[{"evidence":{"patch_ids":["b3db903786744763190489d6bf47d765"],"same_day":true,"statement_hash":"eeca05449e3cc33c400da91c2fe568d3d74ef1488cd64e05a219a1d4578a1575"},"rule":2,"target":"50ee30b81e767311733d723cd36948c0","type":"equivalent"},{"evidence":{"patch_ids":["b3db903786744763190489d6bf47d765"],"same_day":true,"statement_hash":"eeca05449e3cc33c400da91c2fe568d3d74ef1488cd64e05a219a1d4578a1575"},"rule":2,"target":"b1d5f444628e0aea3eb678b0a2d29dfa","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["37fc5de43"],"source_entry_id":"18.1/changes/030","source_hash":"714e58270e4ca5f91f9e2d91bc61604ea15cf638406700f413135f063d7942c8","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"eeca05449e3cc33c400da91c2fe568d3d74ef1488cd64e05a219a1d4578a1575","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"},"id":"18.1-b4b351d19dc05865","matches":[{"id":"17.7-2f08c0b5ad93baa5","source_entry_id":"17.7/changes/035","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix mishandling of lock timeout signals in parallel apply workers for logical replication","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/030","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix mishandling of lock timeout signals in parallel apply workers for logical replication","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["17b2d5ec7","25b484080","9b6109607","a14201073","a1b8b3b2e","da5ea6c70","e7340b484"],"commit_groups":[["17b2d5ec7","25b484080","9b6109607","a14201073","a1b8b3b2e","da5ea6c70","e7340b484"]],"commits":["a14201073"],"cves":[],"db_id":"5e6622b056fdeebae1797bcd6bab73d8","html":"\u003cp\u003eAvoid unwanted WAL receiver shutdown when switching from streaming to archive WAL source (Xuneng Zhou) \u003ca href=\"https://postgr.es/c/a14201073\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eDuring 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.\u003c/p\u003e","id":"18.1-a20d69b97abaf6de","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.","part":"changes","patch_ids":["c329a1ce9ca7c1f3b46341c92f972ea9"],"relations":[{"evidence":{"patch_ids":["c329a1ce9ca7c1f3b46341c92f972ea9"],"same_day":true,"statement_hash":"94e86829e542dbec362b5314cb0d0420170b66f94aea79d642bd1905c93f5d74"},"rule":2,"target":"186f1aca8e166170a7cedbb47670ed32","type":"equivalent"},{"evidence":{"patch_ids":["c329a1ce9ca7c1f3b46341c92f972ea9"],"same_day":true,"statement_hash":"94e86829e542dbec362b5314cb0d0420170b66f94aea79d642bd1905c93f5d74"},"rule":2,"target":"74dc0b8668a34ee86a69e81b07977ac3","type":"equivalent"},{"evidence":{"patch_ids":["c329a1ce9ca7c1f3b46341c92f972ea9"],"same_day":true,"statement_hash":"94e86829e542dbec362b5314cb0d0420170b66f94aea79d642bd1905c93f5d74"},"rule":2,"target":"7e82176acdf9327aca4da62b00d1400a","type":"equivalent"},{"evidence":{"patch_ids":["c329a1ce9ca7c1f3b46341c92f972ea9"],"same_day":true,"statement_hash":"94e86829e542dbec362b5314cb0d0420170b66f94aea79d642bd1905c93f5d74"},"rule":2,"target":"b76ca1acc7d0e06651b84c05d5298bb5","type":"equivalent"},{"evidence":{"patch_ids":["c329a1ce9ca7c1f3b46341c92f972ea9"],"same_day":true,"statement_hash":"94e86829e542dbec362b5314cb0d0420170b66f94aea79d642bd1905c93f5d74"},"rule":2,"target":"c392b0b8a9a1720a5f28a1d62993d15b","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["a14201073"],"source_entry_id":"18.1/changes/031","source_hash":"1e48a276127802a798f2d83743e6434e202fd58ee0a2faa8438270cc38bed7ca","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"94e86829e542dbec362b5314cb0d0420170b66f94aea79d642bd1905c93f5d74","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"},"id":"18.1-a20d69b97abaf6de","matches":[{"id":"17.7-0a048ec34f6d4d74","source_entry_id":"17.7/changes/036","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Avoid unwanted WAL receiver shutdown when switching from streaming to archive WAL source","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/031","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Avoid unwanted WAL receiver shutdown when switching from streaming to archive WAL source","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["32b95fc71","a61592253","b07682bce","b46efe904","c40761759"],"commit_groups":[["32b95fc71","a61592253","b07682bce","b46efe904","c40761759"]],"commits":["32b95fc71"],"cves":[],"db_id":"01678f172fb01945bdf37dee98659abb","html":"\u003cp\u003eFix use-after-free issue in the relation synchronization cache maintained by the \u003cspan\u003epgoutput\u003c/span\u003e logical decoding plugin (Vignesh C, Masahiko Sawada) \u003ca href=\"https://postgr.es/c/32b95fc71\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAn error during logical decoding could result in crashes in subsequent logical decoding attempts in the same session. The case is only reachable when \u003cspan\u003epgoutput\u003c/span\u003e is invoked via SQL functions.\u003c/p\u003e","id":"18.1-5ac1192568f3b470","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.","part":"changes","patch_ids":["f0d90b350350451bd966913a51e4879b"],"relations":[{"evidence":{"patch_ids":["f0d90b350350451bd966913a51e4879b"],"same_day":true,"statement_hash":"a5100d60852834442dddf7c470eb3398c76e0d2de98829a3277bf107f97642fc"},"rule":2,"target":"88eeed6b80c39786442df0b17dadee4a","type":"equivalent"},{"evidence":{"patch_ids":["f0d90b350350451bd966913a51e4879b"],"same_day":true,"statement_hash":"a5100d60852834442dddf7c470eb3398c76e0d2de98829a3277bf107f97642fc"},"rule":2,"target":"b5c5a46598eb51eef76d3c62dc981396","type":"equivalent"},{"evidence":{"patch_ids":["f0d90b350350451bd966913a51e4879b"],"same_day":true,"statement_hash":"a5100d60852834442dddf7c470eb3398c76e0d2de98829a3277bf107f97642fc"},"rule":2,"target":"bd8536eb35145d43f731406b08299135","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["32b95fc71"],"source_entry_id":"18.1/changes/032","source_hash":"5e0d3bf538ab0c71063d21857506abb59dbd382251a7f9371a0e85c8a0ca57f3","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"a5100d60852834442dddf7c470eb3398c76e0d2de98829a3277bf107f97642fc","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"},"id":"18.1-5ac1192568f3b470","matches":[{"id":"17.7-db1ad25a90aef00e","source_entry_id":"17.7/changes/038","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","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/032","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","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["bf3dba508","d43209468","e3714dc05","f3fb6bc9f"],"commit_groups":[["bf3dba508","d43209468","e3714dc05","f3fb6bc9f"]],"commits":["bf3dba508"],"cves":[],"db_id":"dbc091f15023788511302d163d035b51","html":"\u003cp\u003eAvoid unnecessary invalidation of logical replication slots (Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/bf3dba508\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-11b960ad24efa0be","identity_text":"Avoid unnecessary invalidation of logical replication slots (Bertrand Drouvot)","part":"changes","patch_ids":["6ea9f1034627e064a66a9993eefe3326"],"relations":[{"evidence":{"patch_ids":["6ea9f1034627e064a66a9993eefe3326"],"same_day":true,"statement_hash":"2258d0e5693992de151b50019fd28e9463cd70463c082a7437cf067dd3c0016c"},"rule":2,"target":"cb9ea43000f5f0564c0ad169585ea59f","type":"equivalent"},{"evidence":{"patch_ids":["6ea9f1034627e064a66a9993eefe3326"],"same_day":true,"statement_hash":"2258d0e5693992de151b50019fd28e9463cd70463c082a7437cf067dd3c0016c"},"rule":2,"target":"d82a9dd65733472f8ceb24aa092ce2c1","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["bf3dba508"],"source_entry_id":"18.1/changes/033","source_hash":"8314a67474fb2faf2aa29f6d4a6461256fd1f4b2de6a62e94ae410489e1838d1","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"2258d0e5693992de151b50019fd28e9463cd70463c082a7437cf067dd3c0016c","text":"Avoid unnecessary invalidation of logical replication slots (Bertrand Drouvot) §","title":"Avoid unnecessary invalidation of logical replication slots"},"id":"18.1-11b960ad24efa0be","matches":[{"id":"17.7-7503f801e6751f4a","source_entry_id":"17.7/changes/039","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Avoid unnecessary invalidation of logical replication slots","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/033","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Avoid unnecessary invalidation of logical replication slots","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["03bf7a12c","4c53519e1","75a555d61","9883e3cd1","b48ae226e","e91eb4ad6","f91666c83"],"commit_groups":[["03bf7a12c","4c53519e1","75a555d61","9883e3cd1","b48ae226e","e91eb4ad6","f91666c83"]],"commits":["b48ae226e"],"cves":[],"db_id":"54e06bd3860e1bbda5ac887cf9128e18","html":"\u003cp\u003eFix incorrect printing of messages about failures in checking whether the user has Windows administrator privilege (Bryan Green) \u003ca href=\"https://postgr.es/c/b48ae226e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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.\u003c/p\u003e","id":"18.1-0bab432ae295bddb","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.","part":"changes","patch_ids":["d55ac972fc177556ea4a0e974c012182"],"relations":[{"evidence":{"patch_ids":["d55ac972fc177556ea4a0e974c012182"],"same_day":true,"statement_hash":"eaba82bd3ddf1952b1b8d1f5d8eb79c610f601c3b23948c4873ea0e85ca0e1ef"},"rule":2,"target":"1bce0a6531645bd3f70523a4fd591cf3","type":"equivalent"},{"evidence":{"patch_ids":["d55ac972fc177556ea4a0e974c012182"],"same_day":true,"statement_hash":"eaba82bd3ddf1952b1b8d1f5d8eb79c610f601c3b23948c4873ea0e85ca0e1ef"},"rule":2,"target":"27ca4eb718e79592fec76dc7fda731c1","type":"equivalent"},{"evidence":{"patch_ids":["d55ac972fc177556ea4a0e974c012182"],"same_day":true,"statement_hash":"eaba82bd3ddf1952b1b8d1f5d8eb79c610f601c3b23948c4873ea0e85ca0e1ef"},"rule":2,"target":"92380498a4385f5ba77ddf5e840497f2","type":"equivalent"},{"evidence":{"patch_ids":["d55ac972fc177556ea4a0e974c012182"],"same_day":true,"statement_hash":"eaba82bd3ddf1952b1b8d1f5d8eb79c610f601c3b23948c4873ea0e85ca0e1ef"},"rule":2,"target":"bf9e24f2b769f783785421c6c4666a0a","type":"equivalent"},{"evidence":{"patch_ids":["d55ac972fc177556ea4a0e974c012182"],"same_day":true,"statement_hash":"eaba82bd3ddf1952b1b8d1f5d8eb79c610f601c3b23948c4873ea0e85ca0e1ef"},"rule":2,"target":"fc910ae34d590e376c66274cf6b8087f","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b48ae226e"],"source_entry_id":"18.1/changes/035","source_hash":"5b3d2f02beb4e4207ef2adb44b13c503bb6ce3715b669e0353ee71a40523866b","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"eaba82bd3ddf1952b1b8d1f5d8eb79c610f601c3b23948c4873ea0e85ca0e1ef","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"},"id":"18.1-0bab432ae295bddb","matches":[{"id":"17.7-6554bc7b77289e22","source_entry_id":"17.7/changes/041","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","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/035","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","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["6d8acb777","a9515f294","c775bf048","d4baa327a"],"commit_groups":[["6d8acb777","a9515f294","c775bf048","d4baa327a"]],"commits":["6d8acb777"],"cves":[],"db_id":"78099173e39c6c3e78fe3e6dbd3ae346","html":"\u003cp\u003eAvoid crash when attempting to test \u003cspan\u003ePostgreSQL\u003c/span\u003e with certain libsanitizer options (Emmanuel Sibi, Jacob Champion) \u003ca href=\"https://postgr.es/c/6d8acb777\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-c00c424726e8c2ba","identity_text":"Avoid crash when attempting to test PostgreSQL with certain libsanitizer options (Emmanuel Sibi, Jacob Champion)","part":"changes","patch_ids":["0aa2e1766b342d485aa4d51817595af8"],"relations":[{"evidence":{"patch_ids":["0aa2e1766b342d485aa4d51817595af8"],"same_day":true,"statement_hash":"8083d2803e957ae96e87e94e8d681a4e2bbd775e61d5de91ea925956e3a45ce9"},"rule":2,"target":"1a27f92e7f186016d17a28e80fd6ba2a","type":"equivalent"},{"evidence":{"patch_ids":["0aa2e1766b342d485aa4d51817595af8"],"same_day":true,"statement_hash":"8083d2803e957ae96e87e94e8d681a4e2bbd775e61d5de91ea925956e3a45ce9"},"rule":2,"target":"3fe9f73cb5b5abb15f5187f203890f07","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["6d8acb777"],"source_entry_id":"18.1/changes/036","source_hash":"02b71b367fa5b096a4d78c9500bb07dc328a3f881cd84ef6bb00ab944d1b7821","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"8083d2803e957ae96e87e94e8d681a4e2bbd775e61d5de91ea925956e3a45ce9","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"},"id":"18.1-c00c424726e8c2ba","matches":[{"id":"17.7-9ade7eda82977791","source_entry_id":"17.7/changes/043","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Avoid crash when attempting to test PostgreSQL with certain libsanitizer options","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/036","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Avoid crash when attempting to test PostgreSQL with certain libsanitizer options","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["50eb4e118","7b955c227","86bd9497f","af3a79e08","bd6f986c9","cdc04a6c3","f3420e006"],"commit_groups":[["50eb4e118","7b955c227","86bd9497f","af3a79e08","bd6f986c9","cdc04a6c3","f3420e006"]],"commits":["af3a79e08"],"cves":[],"db_id":"8df4cb56b5956e0bcfd2f6b1733b74cc","html":"\u003cp\u003eFix false memory-context-checking warnings in debug builds on 64-bit Windows (David Rowley) \u003ca href=\"https://postgr.es/c/af3a79e08\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-6ea24c894273b60d","identity_text":"Fix false memory-context-checking warnings in debug builds on 64-bit Windows (David Rowley)","part":"changes","patch_ids":["61b56c5fae6f5e9db534484ddd08ba36"],"relations":[{"evidence":{"patch_ids":["61b56c5fae6f5e9db534484ddd08ba36"],"same_day":true,"statement_hash":"318257c40de6d58edd2102cd728c1f712d4472c110c6470d0b05fd6cea50be8a"},"rule":2,"target":"01aaa14579e082646793b4e27afbf21b","type":"equivalent"},{"evidence":{"patch_ids":["61b56c5fae6f5e9db534484ddd08ba36"],"same_day":true,"statement_hash":"318257c40de6d58edd2102cd728c1f712d4472c110c6470d0b05fd6cea50be8a"},"rule":2,"target":"0acaf19cbd02c251f9c72a3566ceafd2","type":"equivalent"},{"evidence":{"patch_ids":["61b56c5fae6f5e9db534484ddd08ba36"],"same_day":true,"statement_hash":"318257c40de6d58edd2102cd728c1f712d4472c110c6470d0b05fd6cea50be8a"},"rule":2,"target":"801cc326322f22aa573edf2c98d1162f","type":"equivalent"},{"evidence":{"patch_ids":["61b56c5fae6f5e9db534484ddd08ba36"],"same_day":true,"statement_hash":"318257c40de6d58edd2102cd728c1f712d4472c110c6470d0b05fd6cea50be8a"},"rule":2,"target":"84067ed8a3ba1028de01b8a46f2000b9","type":"equivalent"},{"evidence":{"patch_ids":["61b56c5fae6f5e9db534484ddd08ba36"],"same_day":true,"statement_hash":"318257c40de6d58edd2102cd728c1f712d4472c110c6470d0b05fd6cea50be8a"},"rule":2,"target":"fc378456b09d8aee7ced8ece43c87341","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["af3a79e08"],"source_entry_id":"18.1/changes/037","source_hash":"331b95d0ec60c21a82adc672dd67221a36a5f899be5338cdfc4a478771cdb3d1","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"318257c40de6d58edd2102cd728c1f712d4472c110c6470d0b05fd6cea50be8a","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"},"id":"18.1-6ea24c894273b60d","matches":[{"id":"17.7-a455f9dd0199fe9d","source_entry_id":"17.7/changes/044","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix false memory-context-checking warnings in debug builds on 64-bit Windows","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/037","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix false memory-context-checking warnings in debug builds on 64-bit Windows","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["0be39b4b1","3fc9aa5b0","7504d2be9","78a284b0b","9ca79896a","b7f6798c0"],"commit_groups":[["0be39b4b1","3fc9aa5b0","7504d2be9","78a284b0b","9ca79896a","b7f6798c0"]],"commits":["78a284b0b"],"cves":[],"db_id":"f25c1bf3d1b0bc45940ba06662dd7fac","html":"\u003cp\u003eCorrectly handle \u003ccode\u003eGROUP BY DISTINCT\u003c/code\u003e in PL/pgSQL assignment statements (Tom Lane) \u003ca href=\"https://postgr.es/c/78a284b0b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe parser failed to record the \u003ccode\u003eDISTINCT\u003c/code\u003e option in this context, so that the command would act as if it were plain \u003ccode\u003eGROUP BY\u003c/code\u003e.\u003c/p\u003e","id":"18.1-ea24cf69287cae1d","identity_text":"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.","part":"changes","patch_ids":["a73af4d4bc9077b2b6083baf3ae9afa7"],"relations":[{"evidence":{"patch_ids":["a73af4d4bc9077b2b6083baf3ae9afa7"],"same_day":true,"statement_hash":"4b45bae1f781f46524306017d2565200da9a292424814416e43bb0c51c2b250a"},"rule":2,"target":"5d72fc4fde390c5d9153f30aa3ce32f6","type":"equivalent"},{"evidence":{"patch_ids":["a73af4d4bc9077b2b6083baf3ae9afa7"],"same_day":true,"statement_hash":"4b45bae1f781f46524306017d2565200da9a292424814416e43bb0c51c2b250a"},"rule":2,"target":"bed9ac21d6b5104de301b89d80efe413","type":"equivalent"},{"evidence":{"patch_ids":["a73af4d4bc9077b2b6083baf3ae9afa7"],"same_day":true,"statement_hash":"4b45bae1f781f46524306017d2565200da9a292424814416e43bb0c51c2b250a"},"rule":2,"target":"c4e592f337961adba07d32ea163af2ef","type":"equivalent"},{"evidence":{"patch_ids":["a73af4d4bc9077b2b6083baf3ae9afa7"],"same_day":true,"statement_hash":"4b45bae1f781f46524306017d2565200da9a292424814416e43bb0c51c2b250a"},"rule":2,"target":"f4fe056566c9e56e900ccb3ae467d6d1","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["78a284b0b"],"source_entry_id":"18.1/changes/038","source_hash":"ccb6d64adcdbf2c6e068be824161cde849fbbbabffc0fb6b594d3ca7fa507330","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"4b45bae1f781f46524306017d2565200da9a292424814416e43bb0c51c2b250a","text":"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.","title":"Correctly handle GROUP BY DISTINCT in PL/pgSQL assignment statements"},"id":"18.1-ea24cf69287cae1d","matches":[{"id":"17.7-da35b615699d0e38","source_entry_id":"17.7/changes/045","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Correctly handle GROUP BY DISTINCT in PL/pgSQL assignment statements","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/038","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Correctly handle GROUP BY DISTINCT in PL/pgSQL assignment statements","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["447a794f6","4cde73259","798b19d27","7fb8c9240","cbfd4d0f8","d90c92d1c","fbc41a145"],"commit_groups":[["447a794f6","4cde73259","798b19d27","7fb8c9240","cbfd4d0f8","d90c92d1c","fbc41a145"]],"commits":["447a794f6"],"cves":[],"db_id":"8ed8073833432a5a8b59221fab2bfd05","html":"\u003cp\u003eAvoid leaking memory when handling a SQL error within PL/Python (Tom Lane) \u003ca href=\"https://postgr.es/c/447a794f6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis fixes a session-lifespan memory leak introduced in our previous minor releases.\u003c/p\u003e","id":"18.1-da9fd9dc692db55b","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.","part":"changes","patch_ids":["304183406b9fbfa71ce70fb98dd02b07"],"relations":[{"evidence":{"patch_ids":["304183406b9fbfa71ce70fb98dd02b07"],"same_day":true,"statement_hash":"9ed1c89d3ad5eea0e6de5ada0081665e4f99165f891937f5603d7020851959b0"},"rule":2,"target":"1cc5187c2c4ae41cf3accaadaacb20c6","type":"equivalent"},{"evidence":{"patch_ids":["304183406b9fbfa71ce70fb98dd02b07"],"same_day":true,"statement_hash":"9ed1c89d3ad5eea0e6de5ada0081665e4f99165f891937f5603d7020851959b0"},"rule":2,"target":"21e26aeb99c1f4efef5ee4d427588817","type":"equivalent"},{"evidence":{"patch_ids":["304183406b9fbfa71ce70fb98dd02b07"],"same_day":true,"statement_hash":"9ed1c89d3ad5eea0e6de5ada0081665e4f99165f891937f5603d7020851959b0"},"rule":2,"target":"4567a5ad601fcfb6e367a0d5788654f3","type":"equivalent"},{"evidence":{"patch_ids":["304183406b9fbfa71ce70fb98dd02b07"],"same_day":true,"statement_hash":"9ed1c89d3ad5eea0e6de5ada0081665e4f99165f891937f5603d7020851959b0"},"rule":2,"target":"6e6104594627174dfaa8204ac54cf50d","type":"equivalent"},{"evidence":{"patch_ids":["304183406b9fbfa71ce70fb98dd02b07"],"same_day":true,"statement_hash":"9ed1c89d3ad5eea0e6de5ada0081665e4f99165f891937f5603d7020851959b0"},"rule":2,"target":"f72d5243e6c8215039615db964cfa0bc","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["447a794f6"],"source_entry_id":"18.1/changes/039","source_hash":"25faaa57d44fc2401c1508fc419ebddb55e64b28ada29d9926422d8ebd635ad6","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"9ed1c89d3ad5eea0e6de5ada0081665e4f99165f891937f5603d7020851959b0","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"},"id":"18.1-da9fd9dc692db55b","matches":[{"id":"17.7-518a9f7a9e8762ea","source_entry_id":"17.7/changes/046","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Avoid leaking memory when handling a SQL error within PL/Python","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/039","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Avoid leaking memory when handling a SQL error within PL/Python","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["1c4671f7b","46c4478db","771b106d1","d83879a32","ea78bd6d5","f46d77377","fc287cf3c"],"commit_groups":[["1c4671f7b","46c4478db","771b106d1","d83879a32","ea78bd6d5","f46d77377","fc287cf3c"]],"commits":["d83879a32"],"cves":[],"db_id":"3832ee9d1af37cef22d9ed22d51db616","html":"\u003cp\u003eFix \u003cspan\u003elibpq\u003c/span\u003e's handling of socket-related errors on Windows within its GSSAPI logic (Ning Wu, Tom Lane) \u003ca href=\"https://postgr.es/c/d83879a32\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e","id":"18.1-476a2e50c1064c29","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.","part":"changes","patch_ids":["f0205fc96ae7aa099587d15ffc5b8b43"],"relations":[{"evidence":{"patch_ids":["f0205fc96ae7aa099587d15ffc5b8b43"],"same_day":true,"statement_hash":"a697933e21baa20247c447c1011997c652387adcb7183a91d2cc940f1de7888e"},"rule":2,"target":"8a5e4771e1d3efc837da936303fe3e69","type":"equivalent"},{"evidence":{"patch_ids":["f0205fc96ae7aa099587d15ffc5b8b43"],"same_day":true,"statement_hash":"a697933e21baa20247c447c1011997c652387adcb7183a91d2cc940f1de7888e"},"rule":2,"target":"8c6a6507bd4112a04aa052cc681036ab","type":"equivalent"},{"evidence":{"patch_ids":["f0205fc96ae7aa099587d15ffc5b8b43"],"same_day":true,"statement_hash":"a697933e21baa20247c447c1011997c652387adcb7183a91d2cc940f1de7888e"},"rule":2,"target":"9d30ea675f07706c069fc213482c9a49","type":"equivalent"},{"evidence":{"patch_ids":["f0205fc96ae7aa099587d15ffc5b8b43"],"same_day":true,"statement_hash":"a697933e21baa20247c447c1011997c652387adcb7183a91d2cc940f1de7888e"},"rule":2,"target":"a676ca60cf7c395fb8962ab60a474d3e","type":"equivalent"},{"evidence":{"patch_ids":["f0205fc96ae7aa099587d15ffc5b8b43"],"same_day":true,"statement_hash":"a697933e21baa20247c447c1011997c652387adcb7183a91d2cc940f1de7888e"},"rule":2,"target":"f5be3f6b8947f88fed54b1476ce5d760","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["d83879a32"],"source_entry_id":"18.1/changes/040","source_hash":"4e01a398b7a3630fc13c41e6ed53709ed17ec704a2fa09b13e0ea903399baa0b","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"a697933e21baa20247c447c1011997c652387adcb7183a91d2cc940f1de7888e","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"},"id":"18.1-476a2e50c1064c29","matches":[{"id":"17.7-b2fb5b95a8bca3b8","source_entry_id":"17.7/changes/048","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","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/040","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","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["0fe07fa11","615ff828e","c945b06d5"],"commit_groups":[["0fe07fa11","615ff828e","c945b06d5"]],"commits":["0fe07fa11"],"cves":[],"db_id":"85612db122ce32a9a8151af8dbfda6f6","html":"\u003cp\u003eFix dumping of non-inherited not-null constraints on inherited table columns (Dilip Kumar) \u003ca href=\"https://postgr.es/c/0fe07fa11\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003epg_dump\u003c/span\u003e failed to preserve such constraints when dumping from a pre-v18 server.\u003c/p\u003e","id":"18.1-3a4e23af29635f95","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.","part":"changes","patch_ids":["db74f7b93632cf3feac193a4a7cb92b1"],"relations":[{"evidence":{"patch_ids":["db74f7b93632cf3feac193a4a7cb92b1"],"same_day":true,"statement_hash":"d1c264837bf2a17f1e917f30c81224f49f46e1a8e41803a62145abbe33b00e90"},"rule":2,"target":"093d5c7edafa8bd73b4b72cdfe2bb656","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["0fe07fa11"],"source_entry_id":"18.1/changes/041","source_hash":"04f06ec63a25c2d1bf641d23a4aebcbc0991f4c4683b5a54880fd018960bbe46","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"d1c264837bf2a17f1e917f30c81224f49f46e1a8e41803a62145abbe33b00e90","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"},"id":"18.1-3a4e23af29635f95","matches":[{"id":"17.7-ea1ba6103ffdb14f","source_entry_id":"17.7/changes/049","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix dumping of non-inherited not-null constraints on inherited table columns","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/041","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix dumping of non-inherited not-null constraints on inherited table columns","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["06c1ee6b7","162e70ea0","4921a5972","4cc3b4445","6062c3db3","7419c99a2","d20df9590"],"commit_groups":[["06c1ee6b7","162e70ea0","4921a5972","4cc3b4445","6062c3db3","7419c99a2","d20df9590"]],"commits":["162e70ea0"],"cves":[],"db_id":"0e30416d744287728e67dfa91ecd903e","html":"\u003cp\u003eFix \u003cspan\u003epg_dump\u003c/span\u003e's sorting of foreign key constraints (Álvaro Herrera) \u003ca href=\"https://postgr.es/c/162e70ea0\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eEnsure consistent ordering of these database objects, as was already done for other object types.\u003c/p\u003e","id":"18.1-596e4425a92cbba4","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.","part":"changes","patch_ids":["754d79e483197bda5a8bed16ebe180ac"],"relations":[{"evidence":{"patch_ids":["754d79e483197bda5a8bed16ebe180ac"],"same_day":true},"rule":2,"target":"5d051ea674aeb3f3b326a89ded32901f","type":"related"},{"evidence":{"patch_ids":["754d79e483197bda5a8bed16ebe180ac"],"same_day":true},"rule":2,"target":"5d200915f65582fc2484f8ef24cc008e","type":"related"},{"evidence":{"patch_ids":["754d79e483197bda5a8bed16ebe180ac"],"same_day":true},"rule":2,"target":"9bedf67fa0860d232401ec8b1b5b9bf5","type":"related"},{"evidence":{"patch_ids":["754d79e483197bda5a8bed16ebe180ac"],"same_day":true},"rule":2,"target":"9fe254aca98ebddd5297b74ffc1dfbb8","type":"related"},{"evidence":{"patch_ids":["754d79e483197bda5a8bed16ebe180ac"],"same_day":true},"rule":2,"target":"c1d4d17be6dfafe4eaeda5f8c6d009ad","type":"related"}],"section":"Changes","section_path":["Changes"],"source_commits":["162e70ea0"],"source_entry_id":"18.1/changes/042","source_hash":"00384e1f4ea3ef405d77d3d12ab30dfec35e04c99d3980730024aa6c0aeda8f8","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"cdf4d041c1de8192b2513985b95aa43b724c20b0cabb65a8b86c1a98ee9fa82c","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"},"id":"18.1-596e4425a92cbba4","matches":[{"id":"17.7-6339fccd8bd64678","source_entry_id":"17.7/changes/051","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix pg_dump's sorting of default ACLs and foreign key constraints","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/042","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix pg_dump's sorting of foreign key constraints","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["1518b7d76","277dec651","2efca1633","33276cd02","40dc710a6","6a4009747","8980c724b","8b9924bce","92268b35d","a239c4a0c","aa1fcd087","bf18e9bd7","c865f5b9f","e686010c5","ec017a305"],"commit_groups":[["1518b7d76","6a4009747","a239c4a0c","bf18e9bd7"],["277dec651","2efca1633","33276cd02","40dc710a6","8b9924bce","aa1fcd087","c865f5b9f"],["8980c724b","92268b35d","e686010c5","ec017a305"]],"commits":["6a4009747","8980c724b","aa1fcd087"],"cves":[],"db_id":"db9de757f72a73bd069a8b786f5b8120","html":"\u003cp\u003eFix assorted errors in the data compression logic in \u003cspan\u003epg_dump\u003c/span\u003e and \u003cspan\u003epg_restore\u003c/span\u003e (Daniel Gustafsson, Tom Lane) \u003ca href=\"https://postgr.es/c/8980c724b\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/6a4009747\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/aa1fcd087\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eError 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. \u003cspan\u003epg_dump\u003c/span\u003e 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.\u003c/p\u003e","id":"18.1-939176032400286d","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.","part":"changes","patch_ids":["34d09b07f99c29b50cf53cc13100ea10","4eef07986dd4d4d15a60a29e5a15998d","c6e514b9bc3c0e05d2b6d2fc63af7a54"],"relations":[{"evidence":{"patch_ids":["34d09b07f99c29b50cf53cc13100ea10","4eef07986dd4d4d15a60a29e5a15998d","c6e514b9bc3c0e05d2b6d2fc63af7a54"],"same_day":true,"statement_hash":"e1d5e819c74cee28f2154059267d12fd8e6cfc4c9d5affbaf9861a9f4788798c"},"rule":2,"target":"12b4dd9512e147889a0b739f2bbf5ade","type":"equivalent"},{"evidence":{"patch_ids":["34d09b07f99c29b50cf53cc13100ea10","4eef07986dd4d4d15a60a29e5a15998d","c6e514b9bc3c0e05d2b6d2fc63af7a54"],"same_day":true,"statement_hash":"e1d5e819c74cee28f2154059267d12fd8e6cfc4c9d5affbaf9861a9f4788798c"},"rule":2,"target":"2cc366c16ddf487970d4c1a069ddef4d","type":"equivalent"},{"evidence":{"patch_ids":["34d09b07f99c29b50cf53cc13100ea10","4eef07986dd4d4d15a60a29e5a15998d","c6e514b9bc3c0e05d2b6d2fc63af7a54"],"same_day":true,"statement_hash":"e1d5e819c74cee28f2154059267d12fd8e6cfc4c9d5affbaf9861a9f4788798c"},"rule":2,"target":"94448a696df6dbc1fc249f870067647a","type":"equivalent"},{"evidence":{"patch_ids":["34d09b07f99c29b50cf53cc13100ea10","4eef07986dd4d4d15a60a29e5a15998d","c6e514b9bc3c0e05d2b6d2fc63af7a54"],"same_day":true,"statement_hash":"e1d5e819c74cee28f2154059267d12fd8e6cfc4c9d5affbaf9861a9f4788798c"},"rule":2,"target":"d6f9f1f62ddef6d134088a2d74e99a56","type":"equivalent"},{"evidence":{"patch_ids":["34d09b07f99c29b50cf53cc13100ea10","4eef07986dd4d4d15a60a29e5a15998d","c6e514b9bc3c0e05d2b6d2fc63af7a54"],"same_day":true,"statement_hash":"e1d5e819c74cee28f2154059267d12fd8e6cfc4c9d5affbaf9861a9f4788798c"},"rule":2,"target":"f2020f100f9176ff2a2e8a154fa90714","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["6a4009747","8980c724b","aa1fcd087"],"source_entry_id":"18.1/changes/043","source_hash":"00493561410c0849a110c594a3ee4af2d87a29dcfdfa2c25d12df8526aad92c2","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"e1d5e819c74cee28f2154059267d12fd8e6cfc4c9d5affbaf9861a9f4788798c","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"},"id":"18.1-939176032400286d","matches":[{"id":"17.7-2c512121eb50a880","source_entry_id":"17.7/changes/054","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","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/043","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","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["640590bb4","902c08887","9b3beb7c6","b5cefc197","c00637b5f","de6de069d","f1a2f3a0c"],"commit_groups":[["640590bb4","902c08887","9b3beb7c6","b5cefc197","c00637b5f","de6de069d","f1a2f3a0c"]],"commits":["c00637b5f"],"cves":[],"db_id":"9a22121acd6baa6a9fb3c0a600e6f745","html":"\u003cp\u003eFix \u003cspan\u003epgbench\u003c/span\u003e to error out cleanly if a \u003ccode\u003eCOPY\u003c/code\u003e operation is started (Anthonin Bonnefoy) \u003ca href=\"https://postgr.es/c/c00637b5f\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003epgbench\u003c/span\u003e doesn't intend to support this case, but previously it went into an infinite loop.\u003c/p\u003e","id":"18.1-cccbae91c7612842","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.","part":"changes","patch_ids":["1d095caebd3e91308930c0f046a8615d"],"relations":[{"evidence":{"patch_ids":["1d095caebd3e91308930c0f046a8615d"],"same_day":true,"statement_hash":"b9c6e08e4a0d18e06d97c410e1ac9358f7012ae1718e6db0cee8ee8626b7d2eb"},"rule":2,"target":"0ab8c685f0a9c83205700ee9f16ec69d","type":"equivalent"},{"evidence":{"patch_ids":["1d095caebd3e91308930c0f046a8615d"],"same_day":true,"statement_hash":"b9c6e08e4a0d18e06d97c410e1ac9358f7012ae1718e6db0cee8ee8626b7d2eb"},"rule":2,"target":"37f3a4ecb0a18fd8795547a2f62aa746","type":"equivalent"},{"evidence":{"patch_ids":["1d095caebd3e91308930c0f046a8615d"],"same_day":true,"statement_hash":"b9c6e08e4a0d18e06d97c410e1ac9358f7012ae1718e6db0cee8ee8626b7d2eb"},"rule":2,"target":"4fdb075299b2c8dbb29b9dd63ffefa18","type":"equivalent"},{"evidence":{"patch_ids":["1d095caebd3e91308930c0f046a8615d"],"same_day":true,"statement_hash":"b9c6e08e4a0d18e06d97c410e1ac9358f7012ae1718e6db0cee8ee8626b7d2eb"},"rule":2,"target":"5e3a31a811c1f52525f624d8ce076894","type":"equivalent"},{"evidence":{"patch_ids":["1d095caebd3e91308930c0f046a8615d"],"same_day":true,"statement_hash":"b9c6e08e4a0d18e06d97c410e1ac9358f7012ae1718e6db0cee8ee8626b7d2eb"},"rule":2,"target":"69889021274de78f6f31d01dd2b4ab62","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c00637b5f"],"source_entry_id":"18.1/changes/044","source_hash":"aaf3614d26baed6713030ff063ec3b445c7c4ca96d13485a346fe73062aa4547","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"b9c6e08e4a0d18e06d97c410e1ac9358f7012ae1718e6db0cee8ee8626b7d2eb","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"},"id":"18.1-cccbae91c7612842","matches":[{"id":"17.7-be37552c2ac3a78e","source_entry_id":"17.7/changes/055","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix pgbench to error out cleanly if a COPY operation is started","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/044","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix pgbench to error out cleanly if a COPY operation is started","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["19d4f9ffc","29aabbc43","36c4d30c8","7d7e81d1e","a912118c6","bdccb6302","cb21e1f92"],"commit_groups":[["19d4f9ffc","29aabbc43","36c4d30c8","7d7e81d1e","a912118c6","bdccb6302","cb21e1f92"]],"commits":["29aabbc43"],"cves":[],"db_id":"1d96ae50e45c2122b3c99a80eb6187c3","html":"\u003cp\u003eFix \u003cspan\u003epgbench\u003c/span\u003e's reporting of multiple errors (Yugo Nagata) \u003ca href=\"https://postgr.es/c/29aabbc43\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIn cases where two successive \u003ccode\u003ePQgetResult\u003c/code\u003e calls both fail, \u003cspan\u003epgbench\u003c/span\u003e might report the wrong error message.\u003c/p\u003e","id":"18.1-1b36133d506932f3","identity_text":"Fix pgbench's reporting of multiple errors (Yugo Nagata) In cases where two successive PQgetResult calls both fail, pgbench might report the wrong error message.","part":"changes","patch_ids":["a5b36b8efb6e0c7a3849524c97a420e5"],"relations":[{"evidence":{"patch_ids":["a5b36b8efb6e0c7a3849524c97a420e5"],"same_day":true,"statement_hash":"5a1e945c185bdfb836e9ed6ea3c7c6dcdc70d0b00e3add742a673cd7968eb604"},"rule":2,"target":"66d73925f2523f78c99a3eab09ad1adf","type":"equivalent"},{"evidence":{"patch_ids":["a5b36b8efb6e0c7a3849524c97a420e5"],"same_day":true,"statement_hash":"5a1e945c185bdfb836e9ed6ea3c7c6dcdc70d0b00e3add742a673cd7968eb604"},"rule":2,"target":"89b980f6be2175b2b8c7c6d55f591881","type":"equivalent"},{"evidence":{"patch_ids":["a5b36b8efb6e0c7a3849524c97a420e5"],"same_day":true,"statement_hash":"5a1e945c185bdfb836e9ed6ea3c7c6dcdc70d0b00e3add742a673cd7968eb604"},"rule":2,"target":"a2a875aae536c9dfb223ec32572d4b63","type":"equivalent"},{"evidence":{"patch_ids":["a5b36b8efb6e0c7a3849524c97a420e5"],"same_day":true,"statement_hash":"5a1e945c185bdfb836e9ed6ea3c7c6dcdc70d0b00e3add742a673cd7968eb604"},"rule":2,"target":"ac7703f3c51d491b3572192678a5d998","type":"equivalent"},{"evidence":{"patch_ids":["a5b36b8efb6e0c7a3849524c97a420e5"],"same_day":true,"statement_hash":"5a1e945c185bdfb836e9ed6ea3c7c6dcdc70d0b00e3add742a673cd7968eb604"},"rule":2,"target":"e0ccdf500bb8f7ee5932c7d3db2e536e","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["29aabbc43"],"source_entry_id":"18.1/changes/045","source_hash":"0a9a79db7f564ffb66c19c925af523af67d17b9ae6e9af66f58e3de70a75edce","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"5a1e945c185bdfb836e9ed6ea3c7c6dcdc70d0b00e3add742a673cd7968eb604","text":"Fix pgbench's reporting of multiple errors (Yugo Nagata) § In cases where two successive PQgetResult calls both fail, pgbench might report the wrong error message.","title":"Fix pgbench's reporting of multiple errors"},"id":"18.1-1b36133d506932f3","matches":[{"id":"17.7-180d8349ffb479b3","source_entry_id":"17.7/changes/056","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix pgbench's reporting of multiple errors","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/045","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix pgbench's reporting of multiple errors","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["704f51771","8b2e290bd","8bb174295","c736808e0","f39d9164b"],"commit_groups":[["704f51771","8b2e290bd","8bb174295","c736808e0","f39d9164b"]],"commits":["c736808e0"],"cves":[],"db_id":"43ed98fa322ca8711e3dbbd5e9dc0db8","html":"\u003cp\u003eIn \u003cspan\u003epgbench\u003c/span\u003e, fix faulty assertion about errors in pipeline mode (Yugo Nagata) \u003ca href=\"https://postgr.es/c/c736808e0\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-b61a0464e2059730","identity_text":"In pgbench, fix faulty assertion about errors in pipeline mode (Yugo Nagata)","part":"changes","patch_ids":["f0e6502c068cd0b05ad542efb11a232c"],"relations":[{"evidence":{"patch_ids":["f0e6502c068cd0b05ad542efb11a232c"],"same_day":true,"statement_hash":"c50d603a6fb129cae06cebd4c235fac3d99cea47d3329930dbc75796a0ec35f9"},"rule":2,"target":"8c4b9756ea8e54675c2636e769219add","type":"equivalent"},{"evidence":{"patch_ids":["f0e6502c068cd0b05ad542efb11a232c"],"same_day":true,"statement_hash":"c50d603a6fb129cae06cebd4c235fac3d99cea47d3329930dbc75796a0ec35f9"},"rule":2,"target":"c29def4a30c507bcae5d3354625ab08e","type":"equivalent"},{"evidence":{"patch_ids":["f0e6502c068cd0b05ad542efb11a232c"],"same_day":true,"statement_hash":"c50d603a6fb129cae06cebd4c235fac3d99cea47d3329930dbc75796a0ec35f9"},"rule":2,"target":"fd360afbc940d89de171ce1ab0838f25","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c736808e0"],"source_entry_id":"18.1/changes/046","source_hash":"77b36d627e09dac6cd7488622db7fe44901325044109792211e10a5388426f46","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"c50d603a6fb129cae06cebd4c235fac3d99cea47d3329930dbc75796a0ec35f9","text":"In pgbench, fix faulty assertion about errors in pipeline mode (Yugo Nagata) §","title":"In pgbench, fix faulty assertion about errors in pipeline mode"},"id":"18.1-b61a0464e2059730","matches":[{"id":"17.7-f15c7a567546a9d4","source_entry_id":"17.7/changes/057","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"In pgbench, fix faulty assertion about errors in pipeline mode","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/046","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"In pgbench, fix faulty assertion about errors in pipeline mode","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["4eb6992af","9224c3025","e2072b47b"],"commit_groups":[["4eb6992af","9224c3025","e2072b47b"]],"commits":["e2072b47b"],"cves":[],"db_id":"7e8fa99b0b4955f6b3cb8bd43181225f","html":"\u003cp\u003eFix per-file memory leakage in \u003cspan\u003epg_combinebackup\u003c/span\u003e (Tom Lane) \u003ca href=\"https://postgr.es/c/e2072b47b\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-e9df74682a19abe9","identity_text":"Fix per-file memory leakage in pg_combinebackup (Tom Lane)","part":"changes","patch_ids":["4adc1ba9937db7990ee1e4b0eed20095"],"relations":[{"evidence":{"patch_ids":["4adc1ba9937db7990ee1e4b0eed20095"],"same_day":true,"statement_hash":"cfb0b2884d442379e85fa76d1328a0c95c85939f1727ad5b8efc4d89d3dd1b86"},"rule":2,"target":"027928a265dc472699b9bfa81f7bcb4c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["e2072b47b"],"source_entry_id":"18.1/changes/047","source_hash":"4beb5cc1ed2c64b638cb70a8db3931edfbd458d919a6d4634c21202e7b74ec70","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"cfb0b2884d442379e85fa76d1328a0c95c85939f1727ad5b8efc4d89d3dd1b86","text":"Fix per-file memory leakage in pg_combinebackup (Tom Lane) §","title":"Fix per-file memory leakage in pg_combinebackup"},"id":"18.1-e9df74682a19abe9","matches":[{"id":"17.7-b1cf6e244790fd85","source_entry_id":"17.7/changes/058","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix per-file memory leakage in pg_combinebackup","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/047","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix per-file memory leakage in pg_combinebackup","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["0beb7e933","71aa2e114","79643105a","7d8d36289","815fcfb20","8ae0f6a0c","b6090ed96","eab9e4e27","eb9ee4d18"],"commit_groups":[["0beb7e933","79643105a","7d8d36289","815fcfb20","b6090ed96","eab9e4e27","eb9ee4d18"],["71aa2e114","8ae0f6a0c"]],"commits":["0beb7e933","71aa2e114"],"cves":[],"db_id":"23b0ca06794cbfef601b73e5a2401894","html":"\u003cp\u003eEnsure that \u003ccode\u003econtrib/pg_buffercache\u003c/code\u003e functions can be canceled (Satyanarayana Narlapuram, Yuhang Qiu) \u003ca href=\"https://postgr.es/c/71aa2e114\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/0beb7e933\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSome code paths were capable of running for a long time without checking for interrupts.\u003c/p\u003e","id":"18.1-1f106ef831d50ecf","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.","part":"changes","patch_ids":["d2b70a45c15a7f7e00e59b3284c07ad6","f86d6a1c7709338528c20336c0252405"],"relations":[{"evidence":{"patch_ids":["d2b70a45c15a7f7e00e59b3284c07ad6","f86d6a1c7709338528c20336c0252405"],"same_day":true,"statement_hash":"344e018da37d95afbc286749fed1e20d7328753b9e73f81484fee0e1e4996dc5"},"rule":2,"target":"3caee2c365e58c61931cc0a6fb332c39","type":"equivalent"},{"evidence":{"patch_ids":["d2b70a45c15a7f7e00e59b3284c07ad6","f86d6a1c7709338528c20336c0252405"],"same_day":true,"statement_hash":"344e018da37d95afbc286749fed1e20d7328753b9e73f81484fee0e1e4996dc5"},"rule":2,"target":"7400b4918533b966fb90032b2caf5c76","type":"equivalent"},{"evidence":{"patch_ids":["d2b70a45c15a7f7e00e59b3284c07ad6","f86d6a1c7709338528c20336c0252405"],"same_day":true,"statement_hash":"344e018da37d95afbc286749fed1e20d7328753b9e73f81484fee0e1e4996dc5"},"rule":2,"target":"79d155685a49b3acf32f431174e9c679","type":"equivalent"},{"evidence":{"patch_ids":["d2b70a45c15a7f7e00e59b3284c07ad6","f86d6a1c7709338528c20336c0252405"],"same_day":true,"statement_hash":"344e018da37d95afbc286749fed1e20d7328753b9e73f81484fee0e1e4996dc5"},"rule":2,"target":"b091d219fb5bea6297016707e7154f0e","type":"equivalent"},{"evidence":{"patch_ids":["d2b70a45c15a7f7e00e59b3284c07ad6","f86d6a1c7709338528c20336c0252405"],"same_day":true,"statement_hash":"344e018da37d95afbc286749fed1e20d7328753b9e73f81484fee0e1e4996dc5"},"rule":2,"target":"ee81b22deb19121826702e15ee5489ea","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["0beb7e933","71aa2e114"],"source_entry_id":"18.1/changes/048","source_hash":"c599c52708a4edefe8f956e7bf25970113653d3e96118a198d838931b6795ad9","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"344e018da37d95afbc286749fed1e20d7328753b9e73f81484fee0e1e4996dc5","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"},"id":"18.1-1f106ef831d50ecf","matches":[{"id":"17.7-f96cf4298c654962","source_entry_id":"17.7/changes/059","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Ensure that contrib/pg_buffercache functions can be canceled","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/048","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Ensure that contrib/pg_buffercache functions can be canceled","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["19a64f567","208927e65","3ccf8e9ac","6c03ae8d6","a0551bc57","c26a8eaf6","c29d32d27","d4e8c37cc","da44d71e7","f146eb45c","fae0ce5e3"],"commit_groups":[["19a64f567","208927e65","3ccf8e9ac","6c03ae8d6","a0551bc57","f146eb45c","fae0ce5e3"],["c26a8eaf6","c29d32d27","d4e8c37cc","da44d71e7"]],"commits":["3ccf8e9ac","c29d32d27"],"cves":[],"db_id":"7129d623484df099235339952f193f4c","html":"\u003cp\u003eFix \u003ccode\u003econtrib/pg_prewarm\u003c/code\u003e's privilege checks for indexes (Ayush Vatsa, Nathan Bossart) \u003ca href=\"https://postgr.es/c/3ccf8e9ac\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/c29d32d27\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003epg_prewarm()\u003c/code\u003e requires \u003ccode\u003eSELECT\u003c/code\u003e 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 \u003ccode\u003eSELECT\u003c/code\u003e privilege on the index's table.\u003c/p\u003e","id":"18.1-f8e1ff87a5a4083e","identity_text":"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.","part":"changes","patch_ids":["593f9867c4bc16279f7375b5d5b7bfbf","8c7292bf48a3ed03b018b065e91c99c2"],"relations":[{"evidence":{"patch_ids":["593f9867c4bc16279f7375b5d5b7bfbf","8c7292bf48a3ed03b018b065e91c99c2"],"same_day":true,"statement_hash":"63d7be72922345e05e8da847c09e4ceabcc0c7cc62752dd3d2faf59e861df9ef"},"rule":2,"target":"1d5915ef7928256380a928b89822c11e","type":"equivalent"},{"evidence":{"patch_ids":["593f9867c4bc16279f7375b5d5b7bfbf","8c7292bf48a3ed03b018b065e91c99c2"],"same_day":true,"statement_hash":"63d7be72922345e05e8da847c09e4ceabcc0c7cc62752dd3d2faf59e861df9ef"},"rule":2,"target":"2c079e365c3426a6ab1ebdaac4390c79","type":"equivalent"},{"evidence":{"patch_ids":["593f9867c4bc16279f7375b5d5b7bfbf","8c7292bf48a3ed03b018b065e91c99c2"],"same_day":true,"statement_hash":"63d7be72922345e05e8da847c09e4ceabcc0c7cc62752dd3d2faf59e861df9ef"},"rule":2,"target":"31eace56fdb35b76792ceb947abcef9f","type":"equivalent"},{"evidence":{"patch_ids":["593f9867c4bc16279f7375b5d5b7bfbf","8c7292bf48a3ed03b018b065e91c99c2"],"same_day":true,"statement_hash":"63d7be72922345e05e8da847c09e4ceabcc0c7cc62752dd3d2faf59e861df9ef"},"rule":2,"target":"3560cbeb90a220549c8020a4c4e51a43","type":"equivalent"},{"evidence":{"patch_ids":["593f9867c4bc16279f7375b5d5b7bfbf","8c7292bf48a3ed03b018b065e91c99c2"],"same_day":true,"statement_hash":"63d7be72922345e05e8da847c09e4ceabcc0c7cc62752dd3d2faf59e861df9ef"},"rule":2,"target":"a09e1c9f229a62cef60e445720a79b1c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["3ccf8e9ac","c29d32d27"],"source_entry_id":"18.1/changes/049","source_hash":"186023c491be0cd6fbbca12661f6e4129cfda922dee5307de13c526e36051b90","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"63d7be72922345e05e8da847c09e4ceabcc0c7cc62752dd3d2faf59e861df9ef","text":"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.","title":"Fix contrib/pg_prewarm's privilege checks for indexes"},"id":"18.1-f8e1ff87a5a4083e","matches":[{"id":"17.7-56eb4d27523e9522","source_entry_id":"17.7/changes/060","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix contrib/pg_prewarm's privilege checks for indexes","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/049","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix contrib/pg_prewarm's privilege checks for indexes","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["036decbba","49b5f0b53","684a745f5","c0f9fe877","c207bf473","ee2dbcad0","fc295beb7"],"commit_groups":[["036decbba","49b5f0b53","684a745f5","c0f9fe877","c207bf473","ee2dbcad0","fc295beb7"]],"commits":["fc295beb7"],"cves":[],"db_id":"7cf5a3928b0125574395c382ed52c5b1","html":"\u003cp\u003eMake \u003ccode\u003econtrib/pgstattuple\u003c/code\u003e more robust about empty or invalid index pages (Nitin Motiani) \u003ca href=\"https://postgr.es/c/fc295beb7\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eCount 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.\u003c/p\u003e","id":"18.1-e14a404bd57c041c","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.","part":"changes","patch_ids":["1ec2ccb4b684e5f57590aab9c7c2a444"],"relations":[{"evidence":{"patch_ids":["1ec2ccb4b684e5f57590aab9c7c2a444"],"same_day":true,"statement_hash":"c02e1d95147e0120948e2eb5839f7964fb935bba934375858d2457ca4e09c98d"},"rule":2,"target":"3be631a7028f49faa7a328c190d249c2","type":"equivalent"},{"evidence":{"patch_ids":["1ec2ccb4b684e5f57590aab9c7c2a444"],"same_day":true,"statement_hash":"c02e1d95147e0120948e2eb5839f7964fb935bba934375858d2457ca4e09c98d"},"rule":2,"target":"a6ec20ccdb529fbc57070c204bf73a7c","type":"equivalent"},{"evidence":{"patch_ids":["1ec2ccb4b684e5f57590aab9c7c2a444"],"same_day":true,"statement_hash":"c02e1d95147e0120948e2eb5839f7964fb935bba934375858d2457ca4e09c98d"},"rule":2,"target":"bd4e2931635023fef1578e6a6ef3185b","type":"equivalent"},{"evidence":{"patch_ids":["1ec2ccb4b684e5f57590aab9c7c2a444"],"same_day":true,"statement_hash":"c02e1d95147e0120948e2eb5839f7964fb935bba934375858d2457ca4e09c98d"},"rule":2,"target":"dbdca19037730dda97abc3c0ca87e248","type":"equivalent"},{"evidence":{"patch_ids":["1ec2ccb4b684e5f57590aab9c7c2a444"],"same_day":true,"statement_hash":"c02e1d95147e0120948e2eb5839f7964fb935bba934375858d2457ca4e09c98d"},"rule":2,"target":"e2d3ae73f7d42937b9fa7746740e86a5","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["fc295beb7"],"source_entry_id":"18.1/changes/051","source_hash":"4a9c9202864842215eaa32a776e7fc7fc5d43dfb49b5a9dedc863dc9a43b240b","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"c02e1d95147e0120948e2eb5839f7964fb935bba934375858d2457ca4e09c98d","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"},"id":"18.1-e14a404bd57c041c","matches":[{"id":"17.7-a0ddb7978278cea0","source_entry_id":"17.7/changes/061","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Make contrib/pgstattuple more robust about empty or invalid index pages","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/051","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Make contrib/pgstattuple more robust about empty or invalid index pages","version":"18.1"},{"entry":{"category":"improvement","commit_aliases":["03d9140cb","1c7cba4c5","2f76ffe5e","77b5b2c6f","c5d34f4a5","d8ba910b0","f8ccab0e9"],"commit_groups":[["03d9140cb","1c7cba4c5","2f76ffe5e","77b5b2c6f","c5d34f4a5","d8ba910b0","f8ccab0e9"]],"commits":["f8ccab0e9"],"cves":[],"db_id":"9973d17e573aa27107b7da92a46de435","html":"\u003cp\u003eHarden our read and write barrier macros to satisfy Clang (Thomas Munro) \u003ca href=\"https://postgr.es/c/f8ccab0e9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWe supposed that \u003ccode\u003e__atomic_thread_fence()\u003c/code\u003e 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.\u003c/p\u003e","id":"18.1-01cf9fc9542209e8","identity_text":"Harden our read and write barrier macros to satisfy Clang (Thomas Munro) We 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.","part":"changes","patch_ids":["b4a97942a0ea85e91703f83ee712a3fd"],"relations":[{"evidence":{"patch_ids":["b4a97942a0ea85e91703f83ee712a3fd"],"same_day":true,"statement_hash":"c12ad45ebeb9c503935945a282e17d8d51255745e7eb3b429b9a388f273c231f"},"rule":2,"target":"0f40c60d2dbfd4f861d301a4bd773172","type":"equivalent"},{"evidence":{"patch_ids":["b4a97942a0ea85e91703f83ee712a3fd"],"same_day":true,"statement_hash":"c12ad45ebeb9c503935945a282e17d8d51255745e7eb3b429b9a388f273c231f"},"rule":2,"target":"1fe492cfff8c21a99fc7f4ba788cd84a","type":"equivalent"},{"evidence":{"patch_ids":["b4a97942a0ea85e91703f83ee712a3fd"],"same_day":true,"statement_hash":"c12ad45ebeb9c503935945a282e17d8d51255745e7eb3b429b9a388f273c231f"},"rule":2,"target":"b638f0acce8b684dfe425af564feddc5","type":"equivalent"},{"evidence":{"patch_ids":["b4a97942a0ea85e91703f83ee712a3fd"],"same_day":true,"statement_hash":"c12ad45ebeb9c503935945a282e17d8d51255745e7eb3b429b9a388f273c231f"},"rule":2,"target":"c4e42b13aa01ac375f66b2a5c94f5042","type":"equivalent"},{"evidence":{"patch_ids":["b4a97942a0ea85e91703f83ee712a3fd"],"same_day":true,"statement_hash":"c12ad45ebeb9c503935945a282e17d8d51255745e7eb3b429b9a388f273c231f"},"rule":2,"target":"e3b76d3ec7d1f519b67e8ae7478d0aaf","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["f8ccab0e9"],"source_entry_id":"18.1/changes/052","source_hash":"4858e02470ee3ab0e8252521f5fdbd4155778d06053de4dea4a59a9b54e4feee","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"c12ad45ebeb9c503935945a282e17d8d51255745e7eb3b429b9a388f273c231f","text":"Harden our read and write barrier macros to satisfy Clang (Thomas Munro) § We 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.","title":"Harden our read and write barrier macros to satisfy Clang"},"id":"18.1-01cf9fc9542209e8","matches":[{"id":"17.7-a358469faddcaf65","source_entry_id":"17.7/changes/062","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Harden our read and write barrier macros to satisfy Clang","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/052","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Harden our read and write barrier macros to satisfy Clang","version":"18.1"},{"entry":{"category":"bugfix","commit_aliases":["33202cba8","56cd332f8","6aa04a60c","6ad9378c9","a506b0c0a","a8933194e","f768f5a7d"],"commit_groups":[["33202cba8","56cd332f8","6aa04a60c","6ad9378c9","a506b0c0a","a8933194e","f768f5a7d"]],"commits":["6aa04a60c"],"cves":[],"db_id":"d67ac864844bc85b56699c92c83fc1da","html":"\u003cp\u003eFix PGXS build infrastructure to support building NLS \u003ccode\u003epo\u003c/code\u003e files for extensions (Ryo Matsumura) \u003ca href=\"https://postgr.es/c/6aa04a60c\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-dd957d885d3cf6e3","identity_text":"Fix PGXS build infrastructure to support building NLS po files for extensions (Ryo Matsumura)","part":"changes","patch_ids":["7ddf0a3958f313c5fa75ca694052c55e"],"relations":[{"evidence":{"patch_ids":["7ddf0a3958f313c5fa75ca694052c55e"],"same_day":true,"statement_hash":"2ca0251a2ba28046a94807acfb884e8c62e152a0aff4d67baabf8f4a86329212"},"rule":2,"target":"21f7ae374d258cb2db45f49e1739fb36","type":"equivalent"},{"evidence":{"patch_ids":["7ddf0a3958f313c5fa75ca694052c55e"],"same_day":true,"statement_hash":"2ca0251a2ba28046a94807acfb884e8c62e152a0aff4d67baabf8f4a86329212"},"rule":2,"target":"48d2bb2f625a9045a6c2a66786680255","type":"equivalent"},{"evidence":{"patch_ids":["7ddf0a3958f313c5fa75ca694052c55e"],"same_day":true,"statement_hash":"2ca0251a2ba28046a94807acfb884e8c62e152a0aff4d67baabf8f4a86329212"},"rule":2,"target":"711c7248f36605616eeeb824bcc65676","type":"equivalent"},{"evidence":{"patch_ids":["7ddf0a3958f313c5fa75ca694052c55e"],"same_day":true,"statement_hash":"2ca0251a2ba28046a94807acfb884e8c62e152a0aff4d67baabf8f4a86329212"},"rule":2,"target":"7316bd641f6446319509fd69461d044f","type":"equivalent"},{"evidence":{"patch_ids":["7ddf0a3958f313c5fa75ca694052c55e"],"same_day":true,"statement_hash":"2ca0251a2ba28046a94807acfb884e8c62e152a0aff4d67baabf8f4a86329212"},"rule":2,"target":"af5e130f17b3c07e10f7f34dc42b2531","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["6aa04a60c"],"source_entry_id":"18.1/changes/053","source_hash":"788d09ad30c1fc302c5b1c881bcefc6dce6b9624c52973e7f3b26f0de16d8600","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"2ca0251a2ba28046a94807acfb884e8c62e152a0aff4d67baabf8f4a86329212","text":"Fix PGXS build infrastructure to support building NLS po files for extensions (Ryo Matsumura) §","title":"Fix PGXS build infrastructure to support building NLS po files for extensions"},"id":"18.1-dd957d885d3cf6e3","matches":[{"id":"17.7-5aeee6b10815f848","source_entry_id":"17.7/changes/065","source_url":"/docs/release/17.7/#RELEASE-17-7-CHANGES","title":"Fix PGXS build infrastructure to support building NLS po files for extensions","version":"17.7"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.1/changes/053","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","title":"Fix PGXS build infrastructure to support building NLS po files for extensions","version":"18.1"},{"entry":{"category":"security","commit_aliases":["3b6588cd9","3d160401b","429aeaebd","595956fc7","60e7ae41a","b39d38139"],"commit_groups":[["3b6588cd9","3d160401b","429aeaebd","595956fc7","60e7ae41a","b39d38139"]],"commits":["3b6588cd9"],"cves":["CVE-2026-2003"],"db_id":"020aec6d98ff35dcd4eca87ecb7d21fd","html":"\u003cp\u003eGuard against unexpected dimensions of \u003ccode\u003eoidvector\u003c/code\u003e/\u003ccode\u003eint2vector\u003c/code\u003e (Tom Lane) \u003ca href=\"https://postgr.es/c/3b6588cd9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Altan Birler for reporting this problem. (CVE-2026-2003)\u003c/p\u003e","id":"18.2-5c52afa7301594c6","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)","part":"changes","patch_ids":["e625ea93052fd4dfb5ad354c3e4c3569"],"relations":[{"evidence":{"patch_ids":["e625ea93052fd4dfb5ad354c3e4c3569"],"same_day":true,"statement_hash":"ce3b678bc249d2400e6f33b017d19a152d1f885b7690423e0e17ba0530a55787"},"rule":2,"target":"8db55cd2cacfbefb7d8380baee0440a5","type":"equivalent"},{"evidence":{"patch_ids":["e625ea93052fd4dfb5ad354c3e4c3569"],"same_day":true,"statement_hash":"ce3b678bc249d2400e6f33b017d19a152d1f885b7690423e0e17ba0530a55787"},"rule":2,"target":"93680dc2fc005fc9bc0a92b7d80ee23b","type":"equivalent"},{"evidence":{"patch_ids":["e625ea93052fd4dfb5ad354c3e4c3569"],"same_day":true,"statement_hash":"ce3b678bc249d2400e6f33b017d19a152d1f885b7690423e0e17ba0530a55787"},"rule":2,"target":"d474cd2cf9a4505bba396d502fe366fe","type":"equivalent"},{"evidence":{"patch_ids":["e625ea93052fd4dfb5ad354c3e4c3569"],"same_day":true,"statement_hash":"ce3b678bc249d2400e6f33b017d19a152d1f885b7690423e0e17ba0530a55787"},"rule":2,"target":"dadfe1bd35a127e4b2350a876ce5f39d","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["3b6588cd9"],"source_entry_id":"18.2/changes/001","source_hash":"fe994475fb9f99a34b9728f5a5e7ac9315c8f8a27bd6204ddfa72d82ab2f7d91","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"ce3b678bc249d2400e6f33b017d19a152d1f885b7690423e0e17ba0530a55787","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"},"id":"18.2-5c52afa7301594c6","matches":[{"id":"17.8-a1109c4f32ae03d0","source_entry_id":"17.8/changes/001","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Guard against unexpected dimensions of oidvector/int2vector","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/001","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Guard against unexpected dimensions of oidvector/int2vector","version":"18.2"},{"entry":{"category":"security","commit_aliases":["3ecc84cce","66ddac698","7e82d9a04","841d42cc4","8ebdf41c2","91d7c0bfd","9fa38c572","b69af3dda","b764b26f2","bbf5bcf58","c0887b39d","d484bc260","dbb09fd8e","dd3ad2a4d","deb464a40","ea3bf3498"],"commit_groups":[["3ecc84cce","9fa38c572","d484bc260","dbb09fd8e"],["66ddac698","841d42cc4","91d7c0bfd","b764b26f2","bbf5bcf58","ea3bf3498"],["7e82d9a04","8ebdf41c2","b69af3dda","c0887b39d","dd3ad2a4d","deb464a40"]],"commits":["66ddac698","b69af3dda"],"cves":["CVE-2026-2004"],"db_id":"853a0accddf2290afda1b4c5d74207ed","html":"\u003cp\u003eHarden selectivity estimators against being attached to operators that accept unexpected data types (Tom Lane) \u003ca href=\"https://postgr.es/c/66ddac698\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/b69af3dda\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003econtrib/intarray\u003c/code\u003e 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Daniel Firer, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2004)\u003c/p\u003e","id":"18.2-0a3add9d9f709ebd","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)","part":"changes","patch_ids":["2f2e483656bae2dbe55158c3365123bd","356a9ce59861f3c9318ff0c7fe53f540","4bc40137a21f6b104cb7a2aaf123c445"],"relations":[{"evidence":{"patch_ids":["2f2e483656bae2dbe55158c3365123bd","356a9ce59861f3c9318ff0c7fe53f540","4bc40137a21f6b104cb7a2aaf123c445"],"same_day":true,"statement_hash":"bf854d211c57f15bce3aa7bbb099f8690284afbf8188626b5fdf9bd083214cc4"},"rule":2,"target":"184452363a4be8fbad69f06eb60df539","type":"equivalent"},{"evidence":{"patch_ids":["2f2e483656bae2dbe55158c3365123bd","356a9ce59861f3c9318ff0c7fe53f540","4bc40137a21f6b104cb7a2aaf123c445"],"same_day":true,"statement_hash":"bf854d211c57f15bce3aa7bbb099f8690284afbf8188626b5fdf9bd083214cc4"},"rule":2,"target":"3cfe051a6ace1086d9ff67af367a40f4","type":"equivalent"},{"evidence":{"patch_ids":["2f2e483656bae2dbe55158c3365123bd","356a9ce59861f3c9318ff0c7fe53f540","4bc40137a21f6b104cb7a2aaf123c445"],"same_day":true,"statement_hash":"bf854d211c57f15bce3aa7bbb099f8690284afbf8188626b5fdf9bd083214cc4"},"rule":2,"target":"b368f952921e7f029d36869bd2860743","type":"equivalent"},{"evidence":{"patch_ids":["2f2e483656bae2dbe55158c3365123bd","356a9ce59861f3c9318ff0c7fe53f540","4bc40137a21f6b104cb7a2aaf123c445"],"same_day":true,"statement_hash":"bf854d211c57f15bce3aa7bbb099f8690284afbf8188626b5fdf9bd083214cc4"},"rule":2,"target":"eb75ba70d74784578edba6ea18a6aaf9","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["66ddac698","b69af3dda","dbb09fd8e"],"source_entry_id":"18.2/changes/002","source_hash":"5f2877c96b4d6a2170fba3c7e8bcac2815e78cd423e2e9f62e69ec8dee5ebdaa","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"bf854d211c57f15bce3aa7bbb099f8690284afbf8188626b5fdf9bd083214cc4","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"},"id":"18.2-0a3add9d9f709ebd","matches":[{"id":"17.8-66e960e22441cfaa","source_entry_id":"17.8/changes/002","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Harden selectivity estimators against being attached to operators that accept unexpected data types","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/002","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Harden selectivity estimators against being attached to operators that accept unexpected data types","version":"18.2"},{"entry":{"category":"security","commit_aliases":["01de2e32d","209f387b8","379695d3c","527b730f4","7a7d9693c","9a9982ec6"],"commit_groups":[["01de2e32d","209f387b8","379695d3c","527b730f4","7a7d9693c","9a9982ec6"]],"commits":["209f387b8"],"cves":["CVE-2026-2005"],"db_id":"ef4c4d388861428d41d8694448d1ec90","html":"\u003cp\u003eFix buffer overrun in \u003ccode\u003econtrib/pgcrypto\u003c/code\u003e's PGP decryption functions (Michael Paquier) \u003ca href=\"https://postgr.es/c/209f387b8\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eDecrypting a crafted message with an overlength session key caused a buffer overrun, with consequences as bad as arbitrary code execution.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Team Xint Code, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2005)\u003c/p\u003e","id":"18.2-c6669984145bd55c","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)","part":"changes","patch_ids":["8812c5ce4844c4609945e75b3dad003d"],"relations":[{"evidence":{"patch_ids":["8812c5ce4844c4609945e75b3dad003d"],"same_day":true,"statement_hash":"643330e49824e6c84ee06b67cc1febd73b94c839951a2861efc8c384a23e8307"},"rule":2,"target":"bdd4104dfc3659a38e0f0389ee19b847","type":"equivalent"},{"evidence":{"patch_ids":["8812c5ce4844c4609945e75b3dad003d"],"same_day":true,"statement_hash":"643330e49824e6c84ee06b67cc1febd73b94c839951a2861efc8c384a23e8307"},"rule":2,"target":"d0b0ce25a07e9ad598056180477520b6","type":"equivalent"},{"evidence":{"patch_ids":["8812c5ce4844c4609945e75b3dad003d"],"same_day":true,"statement_hash":"643330e49824e6c84ee06b67cc1febd73b94c839951a2861efc8c384a23e8307"},"rule":2,"target":"e4dd47f240a98be34ae099044d8a2b56","type":"equivalent"},{"evidence":{"patch_ids":["8812c5ce4844c4609945e75b3dad003d"],"same_day":true,"statement_hash":"643330e49824e6c84ee06b67cc1febd73b94c839951a2861efc8c384a23e8307"},"rule":2,"target":"e7bf20473d33d5835462a40fa9fd5552","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["209f387b8"],"source_entry_id":"18.2/changes/003","source_hash":"791a96f3e49adc249c0a775ab7d8472cdeebaadf676276ed6cf8345c0921e5fc","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"643330e49824e6c84ee06b67cc1febd73b94c839951a2861efc8c384a23e8307","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"},"id":"18.2-c6669984145bd55c","matches":[{"id":"17.8-ad02898fb1831e36","source_entry_id":"17.8/changes/003","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix buffer overrun in contrib/pgcrypto's PGP decryption functions","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/003","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix buffer overrun in contrib/pgcrypto's PGP decryption functions","version":"18.2"},{"entry":{"category":"security","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"],"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"]],"commits":["4543b02af","7b5fc85be","b0f5d25bc","b42709194","df0852fe0","efef05ba9"],"cves":["CVE-2026-2006"],"db_id":"66ef8e4bb930ff6d7fb76f1509e60bdb","html":"\u003cp\u003eFix inadequate validation of multibyte character lengths (Thomas Munro, Noah Misch) \u003ca href=\"https://postgr.es/c/df0852fe0\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/efef05ba9\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/7b5fc85be\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/b0f5d25bc\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/b42709194\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/4543b02af\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAssorted 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 \u003cspan\u003e“\u003cspan\u003einvalid byte sequence for encoding\u003c/span\u003e”\u003c/span\u003e errors when string functions process invalid text that has been stored in the database.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Paul Gerste and Moritz Sanft, as part of zeroday.cloud, for reporting this problem. (CVE-2026-2006)\u003c/p\u003e","id":"18.2-b28dc0bb7dc6b053","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)","part":"changes","patch_ids":["495ed616c5c9d01200b34ff986191d76","8b94976f553df832eb256817e06f6e8e","a8ccf4d965aea8d430069f2b4025b384","b98e99e748716baf094e4d11553e19ae","e1e546efb1e21ef2c167c052b7fc2c27","ef48875931b707685e95ea56147ddbe5"],"relations":[{"evidence":{"patch_ids":["495ed616c5c9d01200b34ff986191d76","8b94976f553df832eb256817e06f6e8e","a8ccf4d965aea8d430069f2b4025b384","b98e99e748716baf094e4d11553e19ae","e1e546efb1e21ef2c167c052b7fc2c27","ef48875931b707685e95ea56147ddbe5"],"same_day":true,"statement_hash":"6c6e0d081c08625c5f6ce833f7e79f2bb277ec939453acd9d359f724272d34eb"},"rule":2,"target":"25b98554e64d0842a180907318bd502a","type":"equivalent"},{"evidence":{"patch_ids":["495ed616c5c9d01200b34ff986191d76","8b94976f553df832eb256817e06f6e8e","a8ccf4d965aea8d430069f2b4025b384","b98e99e748716baf094e4d11553e19ae","e1e546efb1e21ef2c167c052b7fc2c27","ef48875931b707685e95ea56147ddbe5"],"same_day":true,"statement_hash":"6c6e0d081c08625c5f6ce833f7e79f2bb277ec939453acd9d359f724272d34eb"},"rule":2,"target":"2fee65050d60d6944038f5de1fd6e77f","type":"equivalent"},{"evidence":{"patch_ids":["495ed616c5c9d01200b34ff986191d76","8b94976f553df832eb256817e06f6e8e","a8ccf4d965aea8d430069f2b4025b384","b98e99e748716baf094e4d11553e19ae","e1e546efb1e21ef2c167c052b7fc2c27","ef48875931b707685e95ea56147ddbe5"],"same_day":true,"statement_hash":"6c6e0d081c08625c5f6ce833f7e79f2bb277ec939453acd9d359f724272d34eb"},"rule":2,"target":"c7f1c767af36d148849ecf12abc7b39c","type":"equivalent"},{"evidence":{"patch_ids":["495ed616c5c9d01200b34ff986191d76","8b94976f553df832eb256817e06f6e8e","a8ccf4d965aea8d430069f2b4025b384","b98e99e748716baf094e4d11553e19ae","e1e546efb1e21ef2c167c052b7fc2c27","ef48875931b707685e95ea56147ddbe5"],"same_day":true,"statement_hash":"6c6e0d081c08625c5f6ce833f7e79f2bb277ec939453acd9d359f724272d34eb"},"rule":2,"target":"e5c2b929807dffd0fc80d18ac5ef27da","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["4543b02af","7b5fc85be","b0f5d25bc","b42709194","df0852fe0","efef05ba9"],"source_entry_id":"18.2/changes/004","source_hash":"d557f73b34b4644693c2136f42999479e3bf11299615ca496ccfc56912747e88","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"6c6e0d081c08625c5f6ce833f7e79f2bb277ec939453acd9d359f724272d34eb","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"},"id":"18.2-b28dc0bb7dc6b053","matches":[{"id":"17.8-0378679c62701a5e","source_entry_id":"17.8/changes/004","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix inadequate validation of multibyte character lengths","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/004","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix inadequate validation of multibyte character lengths","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["075a763e2","12bc32917","1c8c3206f","35b5c62c3","9f5a58aac","b85397481"],"commit_groups":[["075a763e2","12bc32917","1c8c3206f","35b5c62c3","9f5a58aac","b85397481"]],"commits":["12bc32917"],"cves":[],"db_id":"968c190ce539c030cfe3824a0cddc761","html":"\u003cp\u003eDon't allow CTE references in sub-selects to determine semantic levels of aggregate functions (Tom Lane) \u003ca href=\"https://postgr.es/c/12bc32917\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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.\u003c/p\u003e","id":"18.2-d6f0ddb2f2597bb2","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.","part":"changes","patch_ids":["b900772ffaf16070ad5c6f3ee9476799"],"relations":[{"evidence":{"patch_ids":["b900772ffaf16070ad5c6f3ee9476799"],"same_day":true,"statement_hash":"aca5184caeda78eb5d5b9152a6295b4c451d3d7324fcbaae36c120961950e059"},"rule":2,"target":"128a16829eb01aeea2a683fa84040725","type":"equivalent"},{"evidence":{"patch_ids":["b900772ffaf16070ad5c6f3ee9476799"],"same_day":true,"statement_hash":"aca5184caeda78eb5d5b9152a6295b4c451d3d7324fcbaae36c120961950e059"},"rule":2,"target":"4864352d8953061a7f3e2f942fd405e2","type":"equivalent"},{"evidence":{"patch_ids":["b900772ffaf16070ad5c6f3ee9476799"],"same_day":true,"statement_hash":"aca5184caeda78eb5d5b9152a6295b4c451d3d7324fcbaae36c120961950e059"},"rule":2,"target":"cc9e6465c86b962c0dda27e8afcac193","type":"equivalent"},{"evidence":{"patch_ids":["b900772ffaf16070ad5c6f3ee9476799"],"same_day":true,"statement_hash":"aca5184caeda78eb5d5b9152a6295b4c451d3d7324fcbaae36c120961950e059"},"rule":2,"target":"dcc6e6d85b35d0422b8e17422a731c4a","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["12bc32917"],"source_entry_id":"18.2/changes/008","source_hash":"7441d1eca0c2bfb6db24f0e89519196554b2eb9ff55fca9d77f788145bc59a02","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"aca5184caeda78eb5d5b9152a6295b4c451d3d7324fcbaae36c120961950e059","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"},"id":"18.2-d6f0ddb2f2597bb2","matches":[{"id":"17.8-69605b7e08548aa0","source_entry_id":"17.8/changes/005","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","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/008","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","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["b4307ae2e","c5824536e","c5fc17dda","c6ce4dcf9","e7391bbf1"],"commit_groups":[["b4307ae2e","c5824536e","c5fc17dda","c6ce4dcf9","e7391bbf1"]],"commits":["c6ce4dcf9"],"cves":[],"db_id":"e753c6457f34a85baec08d989ba33d82","html":"\u003cp\u003eFix trigger transition table capture for \u003ccode\u003eMERGE\u003c/code\u003e in CTE queries (Dean Rasheed) \u003ca href=\"https://postgr.es/c/c6ce4dcf9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWhen executing a data-modifying CTE query containing both a \u003ccode\u003eMERGE\u003c/code\u003e and another DML operation on a table with statement-level \u003ccode\u003eAFTER\u003c/code\u003e triggers, the transition tables passed to the triggers would not include the rows affected by the \u003ccode\u003eMERGE\u003c/code\u003e, only those affected by the other operation(s).\u003c/p\u003e","id":"18.2-449ed1ba9b72a08e","identity_text":"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).","part":"changes","patch_ids":["9cb7a95ca83cc42e1b56a8fbc492d52e"],"relations":[{"evidence":{"patch_ids":["9cb7a95ca83cc42e1b56a8fbc492d52e"],"same_day":true,"statement_hash":"66d5665f7806451842ea09bab53ec96bcabb424e0cd66ec57fdd516b027ac4f9"},"rule":2,"target":"67486d10436f31c845689f24645f975f","type":"equivalent"},{"evidence":{"patch_ids":["9cb7a95ca83cc42e1b56a8fbc492d52e"],"same_day":true,"statement_hash":"66d5665f7806451842ea09bab53ec96bcabb424e0cd66ec57fdd516b027ac4f9"},"rule":2,"target":"d454fc992715ec69f11869ffab65efab","type":"equivalent"},{"evidence":{"patch_ids":["9cb7a95ca83cc42e1b56a8fbc492d52e"],"same_day":true,"statement_hash":"66d5665f7806451842ea09bab53ec96bcabb424e0cd66ec57fdd516b027ac4f9"},"rule":2,"target":"d4a6c61bfb31b9d9da04d2ea0c6cf39b","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c6ce4dcf9"],"source_entry_id":"18.2/changes/009","source_hash":"f0f05b23484c67560aedd4d68f8ad30f449b5ab9539724f34f75fc1723abd0a3","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"66d5665f7806451842ea09bab53ec96bcabb424e0cd66ec57fdd516b027ac4f9","text":"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).","title":"Fix trigger transition table capture for MERGE in CTE queries"},"id":"18.2-449ed1ba9b72a08e","matches":[{"id":"17.8-a05a36b6df4c6b60","source_entry_id":"17.8/changes/006","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix trigger transition table capture for MERGE in CTE queries","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/009","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix trigger transition table capture for MERGE in CTE queries","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["687533b39","6d2fa44d2","933f67fb6","9f4b7bfc5","f9a468c66","fab386f74"],"commit_groups":[["687533b39","6d2fa44d2","933f67fb6","9f4b7bfc5","f9a468c66","fab386f74"]],"commits":["9f4b7bfc5"],"cves":[],"db_id":"f4b5a0c770a80f36d1c78eef1f635128","html":"\u003cp\u003eFix failure when all children of a partitioned target table of an update or delete have been pruned (Amit Langote) \u003ca href=\"https://postgr.es/c/9f4b7bfc5\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIn such cases, the executor could report \u003cspan\u003e“\u003cspan\u003ecould not find junk ctid column\u003c/span\u003e”\u003c/span\u003e errors, even though nothing needs to be done.\u003c/p\u003e","id":"18.2-6f5d6058ff3801ed","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.","part":"changes","patch_ids":["9a0dd248bccac339f799f84ddd7d8025"],"relations":[{"evidence":{"patch_ids":["9a0dd248bccac339f799f84ddd7d8025"],"same_day":true,"statement_hash":"2d865ce2ec1c605811a5336cc6b79b917602006b9d88ed02a66f1499e94eb2b3"},"rule":2,"target":"179b2113d34cec63f6ed7d3339773014","type":"equivalent"},{"evidence":{"patch_ids":["9a0dd248bccac339f799f84ddd7d8025"],"same_day":true,"statement_hash":"2d865ce2ec1c605811a5336cc6b79b917602006b9d88ed02a66f1499e94eb2b3"},"rule":2,"target":"4ced629daa2801c0202dec91097dd571","type":"equivalent"},{"evidence":{"patch_ids":["9a0dd248bccac339f799f84ddd7d8025"],"same_day":true,"statement_hash":"2d865ce2ec1c605811a5336cc6b79b917602006b9d88ed02a66f1499e94eb2b3"},"rule":2,"target":"63da9c3d80fbdcaacf4a6c8e130df7a3","type":"equivalent"},{"evidence":{"patch_ids":["9a0dd248bccac339f799f84ddd7d8025"],"same_day":true,"statement_hash":"2d865ce2ec1c605811a5336cc6b79b917602006b9d88ed02a66f1499e94eb2b3"},"rule":2,"target":"7a4315af35989c84209f54d435f1bc39","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["9f4b7bfc5"],"source_entry_id":"18.2/changes/011","source_hash":"ae613928441a2248bf5dcb5b91ec42acf14302127242c9163500608ef0f6674e","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"2d865ce2ec1c605811a5336cc6b79b917602006b9d88ed02a66f1499e94eb2b3","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"},"id":"18.2-6f5d6058ff3801ed","matches":[{"id":"17.8-47d93f8afe450b73","source_entry_id":"17.8/changes/007","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix failure when all children of a partitioned target table of an update or delete have been pruned","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/011","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix failure when all children of a partitioned target table of an update or delete have been pruned","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["4297a3519","7027dd499","cae812741","ccde5be68"],"commit_groups":[["4297a3519","7027dd499","cae812741","ccde5be68"]],"commits":["ccde5be68"],"cves":[],"db_id":"4b3957065e21f608944a30199fa8b0a3","html":"\u003cp\u003eAvoid possible planner failure when a query contains duplicate window function calls (Meng Zhang, David Rowley) \u003ca href=\"https://postgr.es/c/ccde5be68\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eConfusion over de-duplication of such calls could result in errors like \u003cspan\u003e“\u003cspan\u003eWindowFunc with winref 2 assigned to WindowAgg with winref 1\u003c/span\u003e”\u003c/span\u003e.\u003c/p\u003e","id":"18.2-339f2dc7a8d3edca","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.","part":"changes","patch_ids":["fa4bfd3b1304bc4a95cf26b478914aab"],"relations":[{"evidence":{"patch_ids":["fa4bfd3b1304bc4a95cf26b478914aab"],"same_day":true,"statement_hash":"392afbf3348f0707bd8555b9a123869d33484aee1e6cef1a77967d81fcb6e73e"},"rule":2,"target":"74b77b8e6ab0ea1bc12ae9243c478255","type":"equivalent"},{"evidence":{"patch_ids":["fa4bfd3b1304bc4a95cf26b478914aab"],"same_day":true,"statement_hash":"392afbf3348f0707bd8555b9a123869d33484aee1e6cef1a77967d81fcb6e73e"},"rule":2,"target":"7ac52809fbfe8babeb50e09de2f149dc","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["ccde5be68"],"source_entry_id":"18.2/changes/014","source_hash":"fc0dae4adf33bc18af8510a13791cb63b3243cb74e0fb7ec0534f349211c5782","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"392afbf3348f0707bd8555b9a123869d33484aee1e6cef1a77967d81fcb6e73e","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"},"id":"18.2-339f2dc7a8d3edca","matches":[{"id":"17.8-a2c5213ddb6acb5c","source_entry_id":"17.8/changes/008","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Avoid possible planner failure when a query contains duplicate window function calls","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/014","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Avoid possible planner failure when a query contains duplicate window function calls","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["5528e8d10","9e77323fc","a212877dc","b497766a8","e79b27662","f19502f04"],"commit_groups":[["5528e8d10","9e77323fc","a212877dc","b497766a8","e79b27662","f19502f04"]],"commits":["a212877dc"],"cves":[],"db_id":"ed2a57d1a47eb0ac687c6d995081429b","html":"\u003cp\u003eAllow indexscans on partial hash indexes even when the index's predicate implies the truth of the WHERE clause (Tom Lane) \u003ca href=\"https://postgr.es/c/a212877dc\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eNormally 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.\u003c/p\u003e","id":"18.2-61e225cdb2ce1f36","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.","part":"changes","patch_ids":["371e0fb22b0b4c3ce7000e6e8780d0ab"],"relations":[{"evidence":{"patch_ids":["371e0fb22b0b4c3ce7000e6e8780d0ab"],"same_day":true,"statement_hash":"978f69342e3def3b8ca6380a3dacf1634fda30feb1db7c0f20d33cad5e6b4dac"},"rule":2,"target":"46491fe43c6b06ae0b36463bb9ec508d","type":"equivalent"},{"evidence":{"patch_ids":["371e0fb22b0b4c3ce7000e6e8780d0ab"],"same_day":true,"statement_hash":"978f69342e3def3b8ca6380a3dacf1634fda30feb1db7c0f20d33cad5e6b4dac"},"rule":2,"target":"b1cd37aac266a35b85d498fbf852a341","type":"equivalent"},{"evidence":{"patch_ids":["371e0fb22b0b4c3ce7000e6e8780d0ab"],"same_day":true,"statement_hash":"978f69342e3def3b8ca6380a3dacf1634fda30feb1db7c0f20d33cad5e6b4dac"},"rule":2,"target":"be90b044d06ac445fb5ba563113882da","type":"equivalent"},{"evidence":{"patch_ids":["371e0fb22b0b4c3ce7000e6e8780d0ab"],"same_day":true,"statement_hash":"978f69342e3def3b8ca6380a3dacf1634fda30feb1db7c0f20d33cad5e6b4dac"},"rule":2,"target":"f2b4b6b2c2b28f97888464f6ce6ad3fa","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["a212877dc"],"source_entry_id":"18.2/changes/020","source_hash":"940c123fdafbfd46e4011394da6445710439a88097114f626d24be102a557cfb","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"978f69342e3def3b8ca6380a3dacf1634fda30feb1db7c0f20d33cad5e6b4dac","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"},"id":"18.2-61e225cdb2ce1f36","matches":[{"id":"17.8-845083cdcffc5df5","source_entry_id":"17.8/changes/009","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","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/020","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","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["460d97020","4b6d096a0","951b60f7a","a5277700e","ab4256869","d77a5f981"],"commit_groups":[["460d97020","4b6d096a0","951b60f7a","a5277700e","ab4256869","d77a5f981"]],"commits":["d77a5f981"],"cves":[],"db_id":"0937f4c4aaa8ff37a519ed8e315b4268","html":"\u003cp\u003eDo not emit WAL for unlogged BRIN indexes (Kirill Reshke) \u003ca href=\"https://postgr.es/c/d77a5f981\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eOne 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.\u003c/p\u003e","id":"18.2-569b26ba06e60ceb","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.","part":"changes","patch_ids":["548b71793684eb7a3b4dc68f7e774931"],"relations":[{"evidence":{"patch_ids":["548b71793684eb7a3b4dc68f7e774931"],"same_day":true,"statement_hash":"14bc5b9ab44a24425a2aaf5ae8e65539cd475fa7e779fdd338932c2bec859e4f"},"rule":2,"target":"293acf13040f24b30864b10bd699a3a0","type":"equivalent"},{"evidence":{"patch_ids":["548b71793684eb7a3b4dc68f7e774931"],"same_day":true,"statement_hash":"14bc5b9ab44a24425a2aaf5ae8e65539cd475fa7e779fdd338932c2bec859e4f"},"rule":2,"target":"5e595f6d6c44016c34bfdd305d261a1f","type":"equivalent"},{"evidence":{"patch_ids":["548b71793684eb7a3b4dc68f7e774931"],"same_day":true,"statement_hash":"14bc5b9ab44a24425a2aaf5ae8e65539cd475fa7e779fdd338932c2bec859e4f"},"rule":2,"target":"a7d18f384393c9a111537f87704719de","type":"equivalent"},{"evidence":{"patch_ids":["548b71793684eb7a3b4dc68f7e774931"],"same_day":true,"statement_hash":"14bc5b9ab44a24425a2aaf5ae8e65539cd475fa7e779fdd338932c2bec859e4f"},"rule":2,"target":"e2905bab9de145b119d05715dee49169","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["d77a5f981"],"source_entry_id":"18.2/changes/021","source_hash":"4916ac87639a386a3af9712d074cb0e4c0ef07680859c6be41649e5274b34329","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"14bc5b9ab44a24425a2aaf5ae8e65539cd475fa7e779fdd338932c2bec859e4f","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"},"id":"18.2-569b26ba06e60ceb","matches":[{"id":"17.8-91a20d38e502ab15","source_entry_id":"17.8/changes/010","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Do not emit WAL for unlogged BRIN indexes","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/021","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Do not emit WAL for unlogged BRIN indexes","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["053e1868b","0bdc777e8","0c862646c","0e8eaa218","1a469d7b5","21a9014cf","321ec5462","44e8c60be","797e9ea6e","7b069a187","82fa6b78d","84f1bf4af","8eeb4a0f7","c2682810a","c2e58c071","d02c03ddc","d80d5f099","eba917d36"],"commit_groups":[["053e1868b","1a469d7b5","321ec5462","8eeb4a0f7","d02c03ddc","eba917d36"],["0bdc777e8","0e8eaa218","21a9014cf","82fa6b78d","84f1bf4af","d80d5f099"],["0c862646c","44e8c60be","797e9ea6e","7b069a187","c2682810a","c2e58c071"]],"commits":["321ec5462","7b069a187","82fa6b78d"],"cves":[],"db_id":"9ff198dcfbb11c56f5a356cc045a2e21","html":"\u003cp\u003ePrevent truncation of CLOG that is still needed by unread \u003ccode\u003eNOTIFY\u003c/code\u003e messages (Joel Jacobson, Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/321ec5462\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/7b069a187\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/82fa6b78d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis fix prevents \u003cspan\u003e“\u003cspan\u003ecould not access status of transaction\u003c/span\u003e”\u003c/span\u003e errors when a backend is slow to absorb \u003ccode\u003eNOTIFY\u003c/code\u003e messages.\u003c/p\u003e","id":"18.2-0a2a82e68a475c0b","identity_text":"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.","part":"changes","patch_ids":["049c4c1146a404bda2c88a886f6a54f5","2e0dbedb2008ef722d72cb29c205b12b","f451d1b52bfa95906c50f2afbd378177"],"relations":[{"evidence":{"patch_ids":["049c4c1146a404bda2c88a886f6a54f5","2e0dbedb2008ef722d72cb29c205b12b","f451d1b52bfa95906c50f2afbd378177"],"same_day":true,"statement_hash":"5649a8930d269e6b71be2eb73aebd23736ffad2e22f4acbfe83ddfebe1ce9f36"},"rule":2,"target":"51e86dfcb154e6afc9dffcc36abdfb81","type":"equivalent"},{"evidence":{"patch_ids":["049c4c1146a404bda2c88a886f6a54f5","2e0dbedb2008ef722d72cb29c205b12b","f451d1b52bfa95906c50f2afbd378177"],"same_day":true,"statement_hash":"5649a8930d269e6b71be2eb73aebd23736ffad2e22f4acbfe83ddfebe1ce9f36"},"rule":2,"target":"b59bb775aaba7282f555785a3372d9b7","type":"equivalent"},{"evidence":{"patch_ids":["049c4c1146a404bda2c88a886f6a54f5","2e0dbedb2008ef722d72cb29c205b12b","f451d1b52bfa95906c50f2afbd378177"],"same_day":true,"statement_hash":"5649a8930d269e6b71be2eb73aebd23736ffad2e22f4acbfe83ddfebe1ce9f36"},"rule":2,"target":"b91addf2aa923755ae6d33001e1ecedf","type":"equivalent"},{"evidence":{"patch_ids":["049c4c1146a404bda2c88a886f6a54f5","2e0dbedb2008ef722d72cb29c205b12b","f451d1b52bfa95906c50f2afbd378177"],"same_day":true,"statement_hash":"5649a8930d269e6b71be2eb73aebd23736ffad2e22f4acbfe83ddfebe1ce9f36"},"rule":2,"target":"fc6cc5e241bcf4f346b4c240b4ebb59c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["321ec5462","7b069a187","82fa6b78d"],"source_entry_id":"18.2/changes/023","source_hash":"80036028fc43f6a1424113e48c2042ee0819051992e415beff5ba6bdaa114795","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"5649a8930d269e6b71be2eb73aebd23736ffad2e22f4acbfe83ddfebe1ce9f36","text":"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.","title":"Prevent truncation of CLOG that is still needed by unread NOTIFY messages"},"id":"18.2-0a2a82e68a475c0b","matches":[{"id":"17.8-4391ac8372980d16","source_entry_id":"17.8/changes/011","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Prevent truncation of CLOG that is still needed by unread NOTIFY messages","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/023","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Prevent truncation of CLOG that is still needed by unread NOTIFY messages","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["1b4699090","7cb05dd2d","aab4a84bb","b1da37de2","b821c9292","c1a5bde00"],"commit_groups":[["1b4699090","7cb05dd2d","aab4a84bb","b1da37de2","b821c9292","c1a5bde00"]],"commits":["aab4a84bb"],"cves":[],"db_id":"2578b5de351f2e0a0f1cb1385293acf1","html":"\u003cp\u003eEscalate errors occurring during \u003ccode\u003eNOTIFY\u003c/code\u003e message processing to FATAL, i.e. close the connection (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/aab4a84bb\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFormerly, if a backend got an error while absorbing a \u003ccode\u003eNOTIFY\u003c/code\u003e 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 \u003ccode\u003eNOTIFY\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eAlso, if the connection is idle at the time of receiving a \u003ccode\u003eNOTIFY\u003c/code\u003e 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.\u003c/p\u003e","id":"18.2-073ea8d2455d251d","identity_text":"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.","part":"changes","patch_ids":["4e4c8262cf4b59a9a0c02b859c31ba93"],"relations":[{"evidence":{"patch_ids":["4e4c8262cf4b59a9a0c02b859c31ba93"],"same_day":true,"statement_hash":"205197bc16f626c3fb09afea881f30f8da7d367c145557afffb3084d4cb8e343"},"rule":2,"target":"2b671b11e767f32199661c5675739435","type":"equivalent"},{"evidence":{"patch_ids":["4e4c8262cf4b59a9a0c02b859c31ba93"],"same_day":true,"statement_hash":"205197bc16f626c3fb09afea881f30f8da7d367c145557afffb3084d4cb8e343"},"rule":2,"target":"340f3cdce36c643b1f14a964c498f497","type":"equivalent"},{"evidence":{"patch_ids":["4e4c8262cf4b59a9a0c02b859c31ba93"],"same_day":true,"statement_hash":"205197bc16f626c3fb09afea881f30f8da7d367c145557afffb3084d4cb8e343"},"rule":2,"target":"a44a10f8650876c478bd97a4096ffb22","type":"equivalent"},{"evidence":{"patch_ids":["4e4c8262cf4b59a9a0c02b859c31ba93"],"same_day":true,"statement_hash":"205197bc16f626c3fb09afea881f30f8da7d367c145557afffb3084d4cb8e343"},"rule":2,"target":"d4ce5365c9cfca02e6db88e5179af61a","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["aab4a84bb"],"source_entry_id":"18.2/changes/024","source_hash":"09846176004935d266902d069bce32a6d91b5b71097d0060ae2c4b814edbd8c0","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"205197bc16f626c3fb09afea881f30f8da7d367c145557afffb3084d4cb8e343","text":"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.","title":"Escalate errors occurring during NOTIFY message processing to FATAL, i.e. close the connection"},"id":"18.2-073ea8d2455d251d","matches":[{"id":"17.8-9232f0a43f14d80d","source_entry_id":"17.8/changes/012","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Escalate errors occurring during NOTIFY message processing to FATAL, i.e. close the connection","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/024","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Escalate errors occurring during NOTIFY message processing to FATAL, i.e. close the connection","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["1b92fe7bb","5749d95d4","d6c415c4b"],"commit_groups":[["1b92fe7bb","5749d95d4","d6c415c4b"]],"commits":["5749d95d4"],"cves":[],"db_id":"25fcb7323829da37f0ce18de95018eec","html":"\u003cp\u003eFix erroneous counting of updates in \u003ccode\u003eEXPLAIN ANALYZE MERGE\u003c/code\u003e with a concurrent update (Dean Rasheed) \u003ca href=\"https://postgr.es/c/5749d95d4\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis situation led to an incorrect count of \u003cspan\u003e“\u003cspan\u003eskipped\u003c/span\u003e”\u003c/span\u003e tuples in \u003ccode\u003eEXPLAIN\u003c/code\u003e's output, or to an assertion failure in an assert-enabled build.\u003c/p\u003e","id":"18.2-6bf24a3ded894f6c","identity_text":"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.","part":"changes","patch_ids":["2609b24658a7707034f782947e9967cc"],"relations":[{"evidence":{"patch_ids":["2609b24658a7707034f782947e9967cc"],"same_day":true,"statement_hash":"d84813ce8e9759afdcfc9b4a4e63c281f7b3b02a756d0a01e9e44928e95b9078"},"rule":2,"target":"0cbfe95ba5642b68cc4518c9e5648046","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["5749d95d4"],"source_entry_id":"18.2/changes/026","source_hash":"869b53748e1daa06b1079f29d8747208ce8a19c53697acc70e68d26522124547","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"d84813ce8e9759afdcfc9b4a4e63c281f7b3b02a756d0a01e9e44928e95b9078","text":"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.","title":"Fix erroneous counting of updates in EXPLAIN ANALYZE MERGE with a concurrent update"},"id":"18.2-6bf24a3ded894f6c","matches":[{"id":"17.8-ebe5acebca0a9592","source_entry_id":"17.8/changes/013","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix erroneous counting of updates in EXPLAIN ANALYZE MERGE with a concurrent update","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/026","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix erroneous counting of updates in EXPLAIN ANALYZE MERGE with a concurrent update","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["3e3a80f62","5d5487cd2","7efef18ff","955f55068","b6201c76e","bb87d7fef"],"commit_groups":[["3e3a80f62","5d5487cd2","7efef18ff","955f55068","b6201c76e","bb87d7fef"]],"commits":["3e3a80f62"],"cves":[],"db_id":"d4cc08cb8b81ba921b2e9bc0318b23a2","html":"\u003cp\u003eFix bug in following update chain when locking a tuple (Jasper Smit) \u003ca href=\"https://postgr.es/c/3e3a80f62\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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 \u003ccode\u003eVACUUM\u003c/code\u003e and then re-used. That could cause unexpected transaction delays or deadlocks. Errors associated with having identified the wrong tuple have also been observed.\u003c/p\u003e","id":"18.2-96ad5c05e88ce8b6","identity_text":"Fix bug in following update chain when locking a tuple (Jasper Smit) This 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.","part":"changes","patch_ids":["e3dafdb5e648603a0ea08c3d21ee84d7"],"relations":[{"evidence":{"patch_ids":["e3dafdb5e648603a0ea08c3d21ee84d7"],"same_day":true,"statement_hash":"ae47dc62dd8aef911c4966b610546ed3a91d32ad6ba6e73105bd7411263a30d1"},"rule":2,"target":"4f4cdca5150cc29cfd55ff6bd60fa8f1","type":"equivalent"},{"evidence":{"patch_ids":["e3dafdb5e648603a0ea08c3d21ee84d7"],"same_day":true,"statement_hash":"ae47dc62dd8aef911c4966b610546ed3a91d32ad6ba6e73105bd7411263a30d1"},"rule":2,"target":"5ccdb2c39df1f114f475423eacc2efdd","type":"equivalent"},{"evidence":{"patch_ids":["e3dafdb5e648603a0ea08c3d21ee84d7"],"same_day":true,"statement_hash":"ae47dc62dd8aef911c4966b610546ed3a91d32ad6ba6e73105bd7411263a30d1"},"rule":2,"target":"814dec09a6214d7245a3c0e86beb4e1d","type":"equivalent"},{"evidence":{"patch_ids":["e3dafdb5e648603a0ea08c3d21ee84d7"],"same_day":true,"statement_hash":"ae47dc62dd8aef911c4966b610546ed3a91d32ad6ba6e73105bd7411263a30d1"},"rule":2,"target":"8954f19da0659a10c8106e76f12e9ccc","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["3e3a80f62"],"source_entry_id":"18.2/changes/027","source_hash":"aaabd7b3b88beca355be28b2c64c1bfdcec6f70d7d2f448af2ed53f3240ede76","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"ae47dc62dd8aef911c4966b610546ed3a91d32ad6ba6e73105bd7411263a30d1","text":"Fix bug in following update chain when locking a tuple (Jasper Smit) § This 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.","title":"Fix bug in following update chain when locking a tuple"},"id":"18.2-96ad5c05e88ce8b6","matches":[{"id":"17.8-50532778c9796546","source_entry_id":"17.8/changes/014","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix bug in following update chain when locking a tuple","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/027","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix bug in following update chain when locking a tuple","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["ad569b54a","c80b0c9d6","ecd275718"],"commit_groups":[["ad569b54a","c80b0c9d6","ecd275718"]],"commits":["c80b0c9d6"],"cves":[],"db_id":"5de4dbe75c947fa408b59b064069c0f4","html":"\u003cp\u003eFix incorrect handling of incremental backups of large tables (Robert Haas, Oleg Tkachenko) \u003ca href=\"https://postgr.es/c/c80b0c9d6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf a table exceeding 1GB (or in general, the installation's segment size) is truncated by \u003ccode\u003eVACUUM\u003c/code\u003e between the base backup and the incremental backup, \u003cspan\u003epg_combinebackup\u003c/span\u003e could fail with an error about \u003cspan\u003e“\u003cspan\u003etruncation block length in excess of segment size\u003c/span\u003e”\u003c/span\u003e. This prevented restoring the incremental backup.\u003c/p\u003e","id":"18.2-ac8dbfd270ee5d7f","identity_text":"Fix incorrect handling of incremental backups of large tables (Robert Haas, Oleg Tkachenko) If 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.","part":"changes","patch_ids":["be976872554bd99653b2dd720a84a67c"],"relations":[{"evidence":{"patch_ids":["be976872554bd99653b2dd720a84a67c"],"same_day":true,"statement_hash":"417141a765e5e572f0440e8e2d390439f63b06fcb081832123c771ab5f3c3769"},"rule":2,"target":"396235bc9daa1f15f99178df7bd67a76","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c80b0c9d6"],"source_entry_id":"18.2/changes/028","source_hash":"6529e03f77a10cddc3b78636e480b45fd15e00747523e407587c5dec4351a08b","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"417141a765e5e572f0440e8e2d390439f63b06fcb081832123c771ab5f3c3769","text":"Fix incorrect handling of incremental backups of large tables (Robert Haas, Oleg Tkachenko) § If 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.","title":"Fix incorrect handling of incremental backups of large tables"},"id":"18.2-ac8dbfd270ee5d7f","matches":[{"id":"17.8-9171e2849738082f","source_entry_id":"17.8/changes/016","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix incorrect handling of incremental backups of large tables","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/028","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix incorrect handling of incremental backups of large tables","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["1943ceb38","4071fe900","980b7c736","9cbb1d21d","b926ff137","f6df78173"],"commit_groups":[["1943ceb38","4071fe900","980b7c736","9cbb1d21d","b926ff137","f6df78173"]],"commits":["1943ceb38"],"cves":[],"db_id":"5ad3db5c0edaa4934f3f9d9b4709c52d","html":"\u003cp\u003eFix potential backend process crash at process exit due to trying to release a lock in an already-unmapped shared memory segment (Rahila Syed) \u003ca href=\"https://postgr.es/c/1943ceb38\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-c5a2be58244ca433","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)","part":"changes","patch_ids":["126653f8f3297278586a3928c56e06f3"],"relations":[{"evidence":{"patch_ids":["126653f8f3297278586a3928c56e06f3"],"same_day":true,"statement_hash":"92dcd4d1c3bd738dad9644948eb1cd6efd94bdefcd3219e424732f890c0bceb3"},"rule":2,"target":"125f7282ee77b2dbf96db553539c22c4","type":"equivalent"},{"evidence":{"patch_ids":["126653f8f3297278586a3928c56e06f3"],"same_day":true,"statement_hash":"92dcd4d1c3bd738dad9644948eb1cd6efd94bdefcd3219e424732f890c0bceb3"},"rule":2,"target":"45af7190ae2808ef37392b8f701626cf","type":"equivalent"},{"evidence":{"patch_ids":["126653f8f3297278586a3928c56e06f3"],"same_day":true,"statement_hash":"92dcd4d1c3bd738dad9644948eb1cd6efd94bdefcd3219e424732f890c0bceb3"},"rule":2,"target":"7be6eebc70de0b6a710a45541a4092f0","type":"equivalent"},{"evidence":{"patch_ids":["126653f8f3297278586a3928c56e06f3"],"same_day":true,"statement_hash":"92dcd4d1c3bd738dad9644948eb1cd6efd94bdefcd3219e424732f890c0bceb3"},"rule":2,"target":"d2811b8c558ee3336f69ce2dee648262","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["1943ceb38"],"source_entry_id":"18.2/changes/029","source_hash":"180197e1a61f1d8e7a43fa25597e6fab706a833f5b2345e7c840fbb264d9daf7","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"92dcd4d1c3bd738dad9644948eb1cd6efd94bdefcd3219e424732f890c0bceb3","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"},"id":"18.2-c5a2be58244ca433","matches":[{"id":"17.8-ff65f3935e08be00","source_entry_id":"17.8/changes/017","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix potential backend process crash at process exit due to trying to release a lock in an already-unmapped shared memory segment","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/029","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix potential backend process crash at process exit due to trying to release a lock in an already-unmapped shared memory segment","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["09532a78b","102bdaa9b","46be454ca","a563ac619","c7946e6f3","d3ad4cef6"],"commit_groups":[["09532a78b","102bdaa9b","46be454ca","a563ac619","c7946e6f3","d3ad4cef6"]],"commits":["09532a78b"],"cves":[],"db_id":"3a7694cde691f1c0a64647d256362d79","html":"\u003cp\u003eGuard against incorrect truncation of the multixact log after a crash (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/09532a78b\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-8b23c352cad22240","identity_text":"Guard against incorrect truncation of the multixact log after a crash (Heikki Linnakangas)","part":"changes","patch_ids":["67a73a4872f6b3f005ad7fe4e9077027"],"relations":[{"evidence":{"patch_ids":["67a73a4872f6b3f005ad7fe4e9077027"],"same_day":true,"statement_hash":"dfecdaac190eb4e172c44ceae68abad6d5cc283f60c6a947351bcef843a944ad"},"rule":2,"target":"06c8d0231b48925fde45dbbe5447711a","type":"equivalent"},{"evidence":{"patch_ids":["67a73a4872f6b3f005ad7fe4e9077027"],"same_day":true,"statement_hash":"dfecdaac190eb4e172c44ceae68abad6d5cc283f60c6a947351bcef843a944ad"},"rule":2,"target":"423a226c0afa155ba2f8b3bf4d809b9b","type":"equivalent"},{"evidence":{"patch_ids":["67a73a4872f6b3f005ad7fe4e9077027"],"same_day":true,"statement_hash":"dfecdaac190eb4e172c44ceae68abad6d5cc283f60c6a947351bcef843a944ad"},"rule":2,"target":"543d98a0d64e54acd061d5327cda0d92","type":"equivalent"},{"evidence":{"patch_ids":["67a73a4872f6b3f005ad7fe4e9077027"],"same_day":true,"statement_hash":"dfecdaac190eb4e172c44ceae68abad6d5cc283f60c6a947351bcef843a944ad"},"rule":2,"target":"98b43daf45e235647020ad11a022bebb","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["09532a78b"],"source_entry_id":"18.2/changes/031","source_hash":"b4d9d073ee0c207fd4db7a4b87e25dfeb96b650630b7eb32cdefaef578df0398","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"dfecdaac190eb4e172c44ceae68abad6d5cc283f60c6a947351bcef843a944ad","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"},"id":"18.2-8b23c352cad22240","matches":[{"id":"17.8-9e854c237f5aabf9","source_entry_id":"17.8/changes/018","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Guard against incorrect truncation of the multixact log after a crash","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/031","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Guard against incorrect truncation of the multixact log after a crash","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["06907e864","300575fe2","36b8f4974","52b27f585","c48829ed8","ea3524cff"],"commit_groups":[["06907e864","300575fe2","36b8f4974","52b27f585","c48829ed8","ea3524cff"]],"commits":["06907e864"],"cves":[],"db_id":"2011af15ea6d97b67e6182e61860c8c7","html":"\u003cp\u003eFix possibly mis-encoded result of \u003ccode\u003epg_stat_get_backend_activity()\u003c/code\u003e (Chao Li) \u003ca href=\"https://postgr.es/c/06907e864\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e","id":"18.2-08c685de487e23d3","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.","part":"changes","patch_ids":["b809be4e7827182df22fb9f71f25cf1d"],"relations":[{"evidence":{"patch_ids":["b809be4e7827182df22fb9f71f25cf1d"],"same_day":true,"statement_hash":"18f9c2bfb3fe8f5033800a59729a09db060ed74ea247b46aee7ee09268737178"},"rule":2,"target":"1d61f99b846c4ede8289346c443c6eab","type":"equivalent"},{"evidence":{"patch_ids":["b809be4e7827182df22fb9f71f25cf1d"],"same_day":true,"statement_hash":"18f9c2bfb3fe8f5033800a59729a09db060ed74ea247b46aee7ee09268737178"},"rule":2,"target":"3fc6fbb291fd58ddb3732e1040a55913","type":"equivalent"},{"evidence":{"patch_ids":["b809be4e7827182df22fb9f71f25cf1d"],"same_day":true,"statement_hash":"18f9c2bfb3fe8f5033800a59729a09db060ed74ea247b46aee7ee09268737178"},"rule":2,"target":"962171149258cdfb98c25d6f7cda03e4","type":"equivalent"},{"evidence":{"patch_ids":["b809be4e7827182df22fb9f71f25cf1d"],"same_day":true,"statement_hash":"18f9c2bfb3fe8f5033800a59729a09db060ed74ea247b46aee7ee09268737178"},"rule":2,"target":"c6e97abc5a7f6b7dd2f4f8bbf960d054","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["06907e864"],"source_entry_id":"18.2/changes/032","source_hash":"29530afde8264c142f5ab853dcdea08e713d94dabb80e54bdacfb0c892aafb74","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"18f9c2bfb3fe8f5033800a59729a09db060ed74ea247b46aee7ee09268737178","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()"},"id":"18.2-08c685de487e23d3","matches":[{"id":"17.8-5b4587fee1692efc","source_entry_id":"17.8/changes/019","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix possibly mis-encoded result of pg_stat_get_backend_activity()","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/032","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix possibly mis-encoded result of pg_stat_get_backend_activity()","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["0fc2f533a","1a9a49699","3853f6168","699293d27","b3ccb0a2c","b863d8d87"],"commit_groups":[["0fc2f533a","1a9a49699","3853f6168","699293d27","b3ccb0a2c","b863d8d87"]],"commits":["b863d8d87"],"cves":[],"db_id":"e532d3e562a8bcd039083d7610c4fe02","html":"\u003cp\u003eGuard against recursive memory context logging (Fujii Masao) \u003ca href=\"https://postgr.es/c/b863d8d87\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA constant flow of signals requesting memory context logging could cause recursive execution of the logging code, which in theory could lead to stack overflow.\u003c/p\u003e","id":"18.2-92cabc87c606add7","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.","part":"changes","patch_ids":["5f2e29ee0f0a335aba7ffbb8c5262c9e"],"relations":[{"evidence":{"patch_ids":["5f2e29ee0f0a335aba7ffbb8c5262c9e"],"same_day":true,"statement_hash":"b5c2d3f4f692a615b47c23616523ca27bef0dcd03455868cfc0d756ea0575dd4"},"rule":2,"target":"6911fcfb9b3a10c2cb527c328b7e80dd","type":"equivalent"},{"evidence":{"patch_ids":["5f2e29ee0f0a335aba7ffbb8c5262c9e"],"same_day":true,"statement_hash":"b5c2d3f4f692a615b47c23616523ca27bef0dcd03455868cfc0d756ea0575dd4"},"rule":2,"target":"69b5630e62f581864e385c3537959829","type":"equivalent"},{"evidence":{"patch_ids":["5f2e29ee0f0a335aba7ffbb8c5262c9e"],"same_day":true,"statement_hash":"b5c2d3f4f692a615b47c23616523ca27bef0dcd03455868cfc0d756ea0575dd4"},"rule":2,"target":"76d6a4cdde5956fd5fdf83af6a0f6953","type":"equivalent"},{"evidence":{"patch_ids":["5f2e29ee0f0a335aba7ffbb8c5262c9e"],"same_day":true,"statement_hash":"b5c2d3f4f692a615b47c23616523ca27bef0dcd03455868cfc0d756ea0575dd4"},"rule":2,"target":"cdc054743d9f7923ca54a8a0dd5eba4d","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b863d8d87"],"source_entry_id":"18.2/changes/033","source_hash":"61d8b79df234e3b08f9a7ceddb5eb530fc8c77363e6950b382ec3018c466cec6","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"b5c2d3f4f692a615b47c23616523ca27bef0dcd03455868cfc0d756ea0575dd4","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"},"id":"18.2-92cabc87c606add7","matches":[{"id":"17.8-a1b611399d727246","source_entry_id":"17.8/changes/020","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Guard against recursive memory context logging","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/033","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Guard against recursive memory context logging","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["12c2f843c","1d0fc2499","1d9f7fbba","57df5ab80","bd2726d3e","f1a6e622b"],"commit_groups":[["12c2f843c","1d0fc2499","1d9f7fbba","57df5ab80","bd2726d3e","f1a6e622b"]],"commits":["57df5ab80"],"cves":[],"db_id":"a0538505db5e86d813d403a8571068b8","html":"\u003cp\u003eFix memory context usage when reinitializing a parallel execution context (Jakub Wartak, Jeevan Chalke) \u003ca href=\"https://postgr.es/c/57df5ab80\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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 \u003cspan\u003ePostgreSQL\u003c/span\u003e, but we have reports of trouble in extensions.\u003c/p\u003e","id":"18.2-f56daebc6196999a","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.","part":"changes","patch_ids":["4c076010d0ab56e908326be07c1b73c6"],"relations":[{"evidence":{"patch_ids":["4c076010d0ab56e908326be07c1b73c6"],"same_day":true,"statement_hash":"b3c3fe87f6d12f96eb766c99214c419b7d35f4a67646f0e2ac1a8abac3576cb0"},"rule":2,"target":"0e538a4d4cac5aac8cab0d86cc46e6d8","type":"equivalent"},{"evidence":{"patch_ids":["4c076010d0ab56e908326be07c1b73c6"],"same_day":true,"statement_hash":"b3c3fe87f6d12f96eb766c99214c419b7d35f4a67646f0e2ac1a8abac3576cb0"},"rule":2,"target":"770932eb6650d49472c43e2db5c83969","type":"equivalent"},{"evidence":{"patch_ids":["4c076010d0ab56e908326be07c1b73c6"],"same_day":true,"statement_hash":"b3c3fe87f6d12f96eb766c99214c419b7d35f4a67646f0e2ac1a8abac3576cb0"},"rule":2,"target":"82f0fec30baf25cedac6f47fedd86a1a","type":"equivalent"},{"evidence":{"patch_ids":["4c076010d0ab56e908326be07c1b73c6"],"same_day":true,"statement_hash":"b3c3fe87f6d12f96eb766c99214c419b7d35f4a67646f0e2ac1a8abac3576cb0"},"rule":2,"target":"c0e0fccdb1ff80df5a7c450903b3c742","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["57df5ab80"],"source_entry_id":"18.2/changes/034","source_hash":"8b856562e302886b3980dd226fc10bab94afbb0d74beb879683b401621aa77ee","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"b3c3fe87f6d12f96eb766c99214c419b7d35f4a67646f0e2ac1a8abac3576cb0","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"},"id":"18.2-f56daebc6196999a","matches":[{"id":"17.8-cdcf22c5f5200747","source_entry_id":"17.8/changes/021","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix memory context usage when reinitializing a parallel execution context","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/034","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix memory context usage when reinitializing a parallel execution context","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["02ba5e3be","489695554","4d689a176","4d936c3ff","635166913","789d65364","81416e101","8ba61bc06","8cfb174a6","b9a02b978","cad40cec2","e46041fd9"],"commit_groups":[["02ba5e3be","489695554","4d689a176","4d936c3ff","b9a02b978","cad40cec2"],["635166913","789d65364","81416e101","8ba61bc06","8cfb174a6","e46041fd9"]],"commits":["02ba5e3be","e46041fd9"],"cves":[],"db_id":"9d39be361a73eeb011b1508852d458c4","html":"\u003cp\u003eSet next multixid's offset when creating a new multixid, to remove the wait loop that was needed in corner cases (Andrey Borodin) \u003ca href=\"https://postgr.es/c/e46041fd9\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/02ba5e3be\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe previous logic could get stuck waiting for an update that would never occur.\u003c/p\u003e","id":"18.2-0eb611cc5bc18380","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.","part":"changes","patch_ids":["7a935cadcf10c6b2317e3231e31323b6","ee608729a6ebedc95a84b653d7e6f795"],"relations":[{"evidence":{"patch_ids":["7a935cadcf10c6b2317e3231e31323b6","ee608729a6ebedc95a84b653d7e6f795"],"same_day":true,"statement_hash":"3820414d3ddce5f6a358db922abd2d2d57a70d8990ca5c41a3b91f78a7e3261d"},"rule":2,"target":"1d8beb2475d7ec3ee5619d442f62f4e4","type":"equivalent"},{"evidence":{"patch_ids":["7a935cadcf10c6b2317e3231e31323b6","ee608729a6ebedc95a84b653d7e6f795"],"same_day":true,"statement_hash":"3820414d3ddce5f6a358db922abd2d2d57a70d8990ca5c41a3b91f78a7e3261d"},"rule":2,"target":"2b4c07606e0901ac70bb0fbb4680ebbe","type":"equivalent"},{"evidence":{"patch_ids":["7a935cadcf10c6b2317e3231e31323b6","ee608729a6ebedc95a84b653d7e6f795"],"same_day":true,"statement_hash":"3820414d3ddce5f6a358db922abd2d2d57a70d8990ca5c41a3b91f78a7e3261d"},"rule":2,"target":"df073012abdc28126571ebecafb9c308","type":"equivalent"},{"evidence":{"patch_ids":["7a935cadcf10c6b2317e3231e31323b6","ee608729a6ebedc95a84b653d7e6f795"],"same_day":true,"statement_hash":"3820414d3ddce5f6a358db922abd2d2d57a70d8990ca5c41a3b91f78a7e3261d"},"rule":2,"target":"fff819d80d05a70e4ebf82ab7f9c951a","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["02ba5e3be","e46041fd9"],"source_entry_id":"18.2/changes/035","source_hash":"14e17e5ba91c9882b49a56627e0b767d34ca9a5f5d8ada7687bd25381c2eb477","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"3820414d3ddce5f6a358db922abd2d2d57a70d8990ca5c41a3b91f78a7e3261d","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"},"id":"18.2-0eb611cc5bc18380","matches":[{"id":"17.8-351e263e26b0031c","source_entry_id":"17.8/changes/022","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","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/035","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","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["134a8ee22","2d5b97b8c","3881561d7","4d288e33b","b880d9a02","c09096503"],"commit_groups":[["134a8ee22","2d5b97b8c","3881561d7","4d288e33b","b880d9a02","c09096503"]],"commits":["b880d9a02"],"cves":[],"db_id":"b1252119d1b5ac0ac5230ba9b7fb844b","html":"\u003cp\u003eAvoid rewriting data-modifying CTEs more than once (Bernice Southey, Dean Rasheed) \u003ca href=\"https://postgr.es/c/b880d9a02\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFormerly, 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.\u003c/p\u003e","id":"18.2-598e6b46a303e445","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.","part":"changes","patch_ids":["e0f79f9c321f69bef485ae997c61c414"],"relations":[{"evidence":{"patch_ids":["e0f79f9c321f69bef485ae997c61c414"],"same_day":true,"statement_hash":"45d7e282599aa005c97ba4f77c0f61900b8c96a1633aa3b113857a26515155bb"},"rule":2,"target":"6e6c8a0f6889fba17b9d4ea6308a8d7a","type":"equivalent"},{"evidence":{"patch_ids":["e0f79f9c321f69bef485ae997c61c414"],"same_day":true,"statement_hash":"45d7e282599aa005c97ba4f77c0f61900b8c96a1633aa3b113857a26515155bb"},"rule":2,"target":"c9710e1b97bbf384a5536e25246c2c1e","type":"equivalent"},{"evidence":{"patch_ids":["e0f79f9c321f69bef485ae997c61c414"],"same_day":true,"statement_hash":"45d7e282599aa005c97ba4f77c0f61900b8c96a1633aa3b113857a26515155bb"},"rule":2,"target":"f467408bfd650872bf1654f4ee4ec70d","type":"equivalent"},{"evidence":{"patch_ids":["e0f79f9c321f69bef485ae997c61c414"],"same_day":true,"statement_hash":"45d7e282599aa005c97ba4f77c0f61900b8c96a1633aa3b113857a26515155bb"},"rule":2,"target":"fa9d76713707441eef7a725233377166","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b880d9a02"],"source_entry_id":"18.2/changes/036","source_hash":"44ccaf69d17829570c1688499434a08725e7185f58e5fd6536d6717c13cb3725","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"45d7e282599aa005c97ba4f77c0f61900b8c96a1633aa3b113857a26515155bb","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"},"id":"18.2-598e6b46a303e445","matches":[{"id":"17.8-fed0bc33b201283d","source_entry_id":"17.8/changes/023","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Avoid rewriting data-modifying CTEs more than once","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/036","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Avoid rewriting data-modifying CTEs more than once","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["2fc5c5062","b83bcc0df","dbdc717ac"],"commit_groups":[["2fc5c5062","b83bcc0df","dbdc717ac"]],"commits":["b83bcc0df"],"cves":[],"db_id":"35cb139db6fcca1cb726591686762d5e","html":"\u003cp\u003eAllow retrying initialization of a DSM registry entry (Nathan Bossart) \u003ca href=\"https://postgr.es/c/b83bcc0df\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf 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.\u003c/p\u003e","id":"18.2-44b11be419e13584","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.","part":"changes","patch_ids":["e358cc1d91845e3da8aaed14c787dcd0"],"relations":[{"evidence":{"patch_ids":["e358cc1d91845e3da8aaed14c787dcd0"],"same_day":true,"statement_hash":"6f8c9dfe61ba11aac117897b8a16e2c125090ad069d80ce5e2ebe812b2891a73"},"rule":2,"target":"5039c49f944e0ea8e42e7eb5859d47f5","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b83bcc0df"],"source_entry_id":"18.2/changes/037","source_hash":"1d9998e86e6642435db7d6ef25747b4e039b914ac3ac16e0428251aa6d99ebbb","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"6f8c9dfe61ba11aac117897b8a16e2c125090ad069d80ce5e2ebe812b2891a73","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"},"id":"18.2-44b11be419e13584","matches":[{"id":"17.8-be3128d810d25a5b","source_entry_id":"17.8/changes/024","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Allow retrying initialization of a DSM registry entry","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/037","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Allow retrying initialization of a DSM registry entry","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["14161bca4","1aa57e9ed","68ebdf2b0","95ef6f490","dc7c77f82","f5927da4f"],"commit_groups":[["14161bca4","1aa57e9ed","68ebdf2b0","95ef6f490","dc7c77f82","f5927da4f"]],"commits":["68ebdf2b0"],"cves":[],"db_id":"afebd143b96e516829ea82f80f213765","html":"\u003cp\u003eFail recovery if WAL does not exist back to the redo point indicated by the checkpoint record (Nitin Jadhav) \u003ca href=\"https://postgr.es/c/68ebdf2b0\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAdd 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.\u003c/p\u003e","id":"18.2-48e29718af30085d","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.","part":"changes","patch_ids":["4b87107464945d5170bed63f81ff3790"],"relations":[{"evidence":{"patch_ids":["4b87107464945d5170bed63f81ff3790"],"same_day":true,"statement_hash":"3acaee6f8628ca0f43630afaa8799cc5ced91cfb215bf493f91ad515f4af1034"},"rule":2,"target":"011195db7fe270680db938124518987b","type":"equivalent"},{"evidence":{"patch_ids":["4b87107464945d5170bed63f81ff3790"],"same_day":true,"statement_hash":"3acaee6f8628ca0f43630afaa8799cc5ced91cfb215bf493f91ad515f4af1034"},"rule":2,"target":"3f4035b04c1c0e9ba08acef72e76fc91","type":"equivalent"},{"evidence":{"patch_ids":["4b87107464945d5170bed63f81ff3790"],"same_day":true,"statement_hash":"3acaee6f8628ca0f43630afaa8799cc5ced91cfb215bf493f91ad515f4af1034"},"rule":2,"target":"7e009c5e3ee2635f5a3f2d6750f1a823","type":"equivalent"},{"evidence":{"patch_ids":["4b87107464945d5170bed63f81ff3790"],"same_day":true,"statement_hash":"3acaee6f8628ca0f43630afaa8799cc5ced91cfb215bf493f91ad515f4af1034"},"rule":2,"target":"ea5f140766dc7aa68dd175c861036247","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["68ebdf2b0"],"source_entry_id":"18.2/changes/040","source_hash":"a97d834694985c925575808f5404b4fed36f485d77bdb9ddc03de6d8e2eda696","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"3acaee6f8628ca0f43630afaa8799cc5ced91cfb215bf493f91ad515f4af1034","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"},"id":"18.2-48e29718af30085d","matches":[{"id":"17.8-3d4d2474ea729f43","source_entry_id":"17.8/changes/025","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","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/040","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","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["0687a6eb0","6ca8506ea","ae45c7296","bb08ac7ac","bea57a6b4","f20b79059"],"commit_groups":[["0687a6eb0","6ca8506ea","ae45c7296","bb08ac7ac","bea57a6b4","f20b79059"]],"commits":["bea57a6b4"],"cves":[],"db_id":"7e3fc1d0791de552b876cdb2454f31d0","html":"\u003cp\u003eAvoid scribbling on the source query tree during \u003ccode\u003eALTER PUBLICATION\u003c/code\u003e (Sunil S) \u003ca href=\"https://postgr.es/c/bea57a6b4\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis error had the visible effect that an event trigger fired for the query would see only the first \u003ccode\u003epublish\u003c/code\u003e option, even if several had been specified. If such a query were set up as a prepared statement, re-executions would misbehave too.\u003c/p\u003e","id":"18.2-4ab1376a3267c027","identity_text":"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.","part":"changes","patch_ids":["27aaed0fd0399be3426c4d05cf88f583"],"relations":[{"evidence":{"patch_ids":["27aaed0fd0399be3426c4d05cf88f583"],"same_day":true,"statement_hash":"097d4d62aa891693f59702842928f93c4d533cb5aa5f4af54c5237246f6933dd"},"rule":2,"target":"382e740a0f9f434506934984bfab5d72","type":"equivalent"},{"evidence":{"patch_ids":["27aaed0fd0399be3426c4d05cf88f583"],"same_day":true,"statement_hash":"097d4d62aa891693f59702842928f93c4d533cb5aa5f4af54c5237246f6933dd"},"rule":2,"target":"609a67b3d1e8a8770d3091b2429519a7","type":"equivalent"},{"evidence":{"patch_ids":["27aaed0fd0399be3426c4d05cf88f583"],"same_day":true,"statement_hash":"097d4d62aa891693f59702842928f93c4d533cb5aa5f4af54c5237246f6933dd"},"rule":2,"target":"bb090370862ac9b9ba54fb93b71c4869","type":"equivalent"},{"evidence":{"patch_ids":["27aaed0fd0399be3426c4d05cf88f583"],"same_day":true,"statement_hash":"097d4d62aa891693f59702842928f93c4d533cb5aa5f4af54c5237246f6933dd"},"rule":2,"target":"ef85167b2646b7c7d896a19a6abb3509","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["bea57a6b4"],"source_entry_id":"18.2/changes/041","source_hash":"ec943f003283b9e8429e711f9384fae3ee7c8daa5bf31daa2e374009331fae12","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"097d4d62aa891693f59702842928f93c4d533cb5aa5f4af54c5237246f6933dd","text":"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.","title":"Avoid scribbling on the source query tree during ALTER PUBLICATION"},"id":"18.2-4ab1376a3267c027","matches":[{"id":"17.8-51768104ffbbb8b1","source_entry_id":"17.8/changes/026","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Avoid scribbling on the source query tree during ALTER PUBLICATION","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/041","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Avoid scribbling on the source query tree during ALTER PUBLICATION","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["75f3428f2","797fc5d1b","7a990e801","d926462d8","f7eb44e0f"],"commit_groups":[["75f3428f2","797fc5d1b","7a990e801","d926462d8","f7eb44e0f"]],"commits":["797fc5d1b"],"cves":[],"db_id":"88f8d8a25ce40f7bce801ec6d1ceb806","html":"\u003cp\u003ePass connection options specified in \u003ccode\u003eCREATE SUBSCRIPTION ... CONNECTION\u003c/code\u003e to the publisher's walsender (Fujii Masao) \u003ca href=\"https://postgr.es/c/797fc5d1b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eBefore this fix, the \u003ccode\u003eoptions\u003c/code\u003e 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 \u003cspan\u003ePostgreSQL\u003c/span\u003e version 15 broke it, so restore the previous behavior.\u003c/p\u003e","id":"18.2-a7e8eb1d775d340e","identity_text":"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.","part":"changes","patch_ids":["568bc4b03123c66fa5044fb184e67302"],"relations":[{"evidence":{"patch_ids":["568bc4b03123c66fa5044fb184e67302"],"same_day":true,"statement_hash":"943489b5b1d830bbee00976c647cb6322ea03fa5558af6ad16b83a9deefb106c"},"rule":2,"target":"14350aa55158b13629c79743cee560e0","type":"equivalent"},{"evidence":{"patch_ids":["568bc4b03123c66fa5044fb184e67302"],"same_day":true,"statement_hash":"943489b5b1d830bbee00976c647cb6322ea03fa5558af6ad16b83a9deefb106c"},"rule":2,"target":"2854750f46ab8bd38a28c1cfd5ae77c9","type":"equivalent"},{"evidence":{"patch_ids":["568bc4b03123c66fa5044fb184e67302"],"same_day":true,"statement_hash":"943489b5b1d830bbee00976c647cb6322ea03fa5558af6ad16b83a9deefb106c"},"rule":2,"target":"e6adf36f29967b514be061f08ac43c83","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["797fc5d1b"],"source_entry_id":"18.2/changes/042","source_hash":"7f7628e43957aa95b0cf8dee9f0d665bb345bfc2cf17334fe95ddeadb2e19f3a","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"943489b5b1d830bbee00976c647cb6322ea03fa5558af6ad16b83a9deefb106c","text":"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.","title":"Pass connection options specified in CREATE SUBSCRIPTION ... CONNECTION to the publisher's walsender"},"id":"18.2-a7e8eb1d775d340e","matches":[{"id":"17.8-8dc05bb27f841a6c","source_entry_id":"17.8/changes/027","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Pass connection options specified in CREATE SUBSCRIPTION ... CONNECTION to the publisher's walsender","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/042","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Pass connection options specified in CREATE SUBSCRIPTION ... CONNECTION to the publisher's walsender","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["006dd4b2e","1c60f7236","24cce33c3","3243c0177","3510ebeb0","3a98f989e","7406df605","851f6649c","919c9fa13","9649f1adf","aae05622a","d3ceb2084"],"commit_groups":[["006dd4b2e","24cce33c3","3510ebeb0","7406df605","aae05622a","d3ceb2084"],["1c60f7236","3a98f989e","9649f1adf"],["3243c0177","851f6649c","919c9fa13"]],"commits":["1c60f7236","919c9fa13","d3ceb2084"],"cves":[],"db_id":"cb75695174eb56fb419b9a98e09580cc","html":"\u003cp\u003ePrevent invalidation of newly created or newly synced replication slots (Zhijie Hou) \u003ca href=\"https://postgr.es/c/919c9fa13\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/1c60f7236\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/d3ceb2084\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA 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.\u003c/p\u003e","id":"18.2-882569f761ef0610","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.","part":"changes","patch_ids":["52eeca007f2cc833bd086bea5398b6dd","e27e8fc7ff675146f1b638a98637021e","fd534fc2f99acb10d2ff04bf0f822f81"],"relations":[{"evidence":{"patch_ids":["52eeca007f2cc833bd086bea5398b6dd","e27e8fc7ff675146f1b638a98637021e","fd534fc2f99acb10d2ff04bf0f822f81"],"same_day":true,"statement_hash":"a7634872b97f0a43a006c3dc4f9851bc65d8af6cd588b4009553b843b6ae22d9"},"rule":2,"target":"2e44c2dcd00ca731067ba5c1a7a9a31c","type":"equivalent"},{"evidence":{"patch_ids":["52eeca007f2cc833bd086bea5398b6dd","e27e8fc7ff675146f1b638a98637021e","fd534fc2f99acb10d2ff04bf0f822f81"],"same_day":true,"statement_hash":"a7634872b97f0a43a006c3dc4f9851bc65d8af6cd588b4009553b843b6ae22d9"},"rule":2,"target":"54b2a393bc7cb86ab19eb7c660bb2004","type":"equivalent"},{"evidence":{"patch_ids":["52eeca007f2cc833bd086bea5398b6dd","e27e8fc7ff675146f1b638a98637021e","fd534fc2f99acb10d2ff04bf0f822f81"],"same_day":true,"statement_hash":"a7634872b97f0a43a006c3dc4f9851bc65d8af6cd588b4009553b843b6ae22d9"},"rule":2,"target":"7045b64c3c70e172ffa2ef8c1ae90896","type":"equivalent"},{"evidence":{"patch_ids":["52eeca007f2cc833bd086bea5398b6dd","e27e8fc7ff675146f1b638a98637021e","fd534fc2f99acb10d2ff04bf0f822f81"],"same_day":true,"statement_hash":"a7634872b97f0a43a006c3dc4f9851bc65d8af6cd588b4009553b843b6ae22d9"},"rule":2,"target":"d1a860dc00a9dc81973d46ece96b0748","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["1c60f7236","919c9fa13","d3ceb2084"],"source_entry_id":"18.2/changes/043","source_hash":"88ca5df37ed03978aa067a4d4c868b6246df884c64949b108a4266a212778954","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"a7634872b97f0a43a006c3dc4f9851bc65d8af6cd588b4009553b843b6ae22d9","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"},"id":"18.2-882569f761ef0610","matches":[{"id":"17.8-2ab0d69c3c8683d7","source_entry_id":"17.8/changes/028","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Prevent invalidation of newly created or newly synced replication slots","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/043","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Prevent invalidation of newly created or newly synced replication slots","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["123b851ab","2a5225b99","57048d6e1","821466722","fa557d300","fd7c86cfa"],"commit_groups":[["123b851ab","2a5225b99","57048d6e1","821466722","fa557d300","fd7c86cfa"]],"commits":["fd7c86cfa"],"cves":[],"db_id":"669fa902ee7eb1553fc960938aa0101f","html":"\u003cp\u003eFix race condition in computing a replication slot's required xmin (Zhijie Hou) \u003ca href=\"https://postgr.es/c/fd7c86cfa\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis could lead to the error \u003cspan\u003e“\u003cspan\u003ecannot build an initial slot snapshot as oldest safe xid follows snapshot's xmin\u003c/span\u003e”\u003c/span\u003e.\u003c/p\u003e","id":"18.2-7907d70dfbb36d36","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.","part":"changes","patch_ids":["c967ad30d8508306bc9949d6c7504333"],"relations":[{"evidence":{"patch_ids":["c967ad30d8508306bc9949d6c7504333"],"same_day":true,"statement_hash":"8dd9f0879870a4299a9d543db5674a7348ed2b9228376a7028ea153ac3afb369"},"rule":2,"target":"5b75bdc74484bae30e1e7fdc965c9335","type":"equivalent"},{"evidence":{"patch_ids":["c967ad30d8508306bc9949d6c7504333"],"same_day":true,"statement_hash":"8dd9f0879870a4299a9d543db5674a7348ed2b9228376a7028ea153ac3afb369"},"rule":2,"target":"8dfd1735c21afd64306b7ba15b0a34a0","type":"equivalent"},{"evidence":{"patch_ids":["c967ad30d8508306bc9949d6c7504333"],"same_day":true,"statement_hash":"8dd9f0879870a4299a9d543db5674a7348ed2b9228376a7028ea153ac3afb369"},"rule":2,"target":"97d0bb3c79bb34e32cf7ac9c088a6cc5","type":"equivalent"},{"evidence":{"patch_ids":["c967ad30d8508306bc9949d6c7504333"],"same_day":true,"statement_hash":"8dd9f0879870a4299a9d543db5674a7348ed2b9228376a7028ea153ac3afb369"},"rule":2,"target":"ed4968909e48309a69552757b02c2ad7","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["fd7c86cfa"],"source_entry_id":"18.2/changes/044","source_hash":"5b4375f3820b11314c74407155165bb30cc4d0b1dcf897beef596b8f61a11e84","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"8dd9f0879870a4299a9d543db5674a7348ed2b9228376a7028ea153ac3afb369","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"},"id":"18.2-7907d70dfbb36d36","matches":[{"id":"17.8-73bf563728deef29","source_entry_id":"17.8/changes/029","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix race condition in computing a replication slot's required xmin","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/044","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix race condition in computing a replication slot's required xmin","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["25a04aa52","8e0d32a4a","90d1beef6","b07c32619","e063ccc72","e22e9ab0c"],"commit_groups":[["25a04aa52","8e0d32a4a","90d1beef6","b07c32619","e063ccc72","e22e9ab0c"]],"commits":["b07c32619"],"cves":[],"db_id":"0641edcbe436f507275b2cfe99e6bfe1","html":"\u003cp\u003eDuring initial synchronization of a logical replication subscription, commit the addition of a \u003ccode\u003epg_replication_origin\u003c/code\u003e entry before starting to copy data (Zhijie Hou) \u003ca href=\"https://postgr.es/c/b07c32619\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, if the copy step failed, the new \u003ccode\u003epg_replication_origin\u003c/code\u003e entry would be lost due to transaction rollback. This led to inconsistent state in shared memory.\u003c/p\u003e","id":"18.2-2de557ccdda45f50","identity_text":"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.","part":"changes","patch_ids":["8e425bf3652841f2fadba06865081f6e"],"relations":[{"evidence":{"patch_ids":["8e425bf3652841f2fadba06865081f6e"],"same_day":true,"statement_hash":"7d150c67ee78399daa2e94cde2a4147e691fc12beccfdee6012621884edbcb26"},"rule":2,"target":"5bdf0ada14933155ce231f2e53c4a971","type":"equivalent"},{"evidence":{"patch_ids":["8e425bf3652841f2fadba06865081f6e"],"same_day":true,"statement_hash":"7d150c67ee78399daa2e94cde2a4147e691fc12beccfdee6012621884edbcb26"},"rule":2,"target":"6868525096474e94a6c61c14b66bef91","type":"equivalent"},{"evidence":{"patch_ids":["8e425bf3652841f2fadba06865081f6e"],"same_day":true,"statement_hash":"7d150c67ee78399daa2e94cde2a4147e691fc12beccfdee6012621884edbcb26"},"rule":2,"target":"ca66bcb2ba08cd3e614c66d8cd512695","type":"equivalent"},{"evidence":{"patch_ids":["8e425bf3652841f2fadba06865081f6e"],"same_day":true,"statement_hash":"7d150c67ee78399daa2e94cde2a4147e691fc12beccfdee6012621884edbcb26"},"rule":2,"target":"eb4ae0a26d975941de9f63f06cf9d77f","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b07c32619"],"source_entry_id":"18.2/changes/045","source_hash":"1ce542a92ac46eb50f4fd3e150ef6882855df63afe3683aa9bb289269947a7f1","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"7d150c67ee78399daa2e94cde2a4147e691fc12beccfdee6012621884edbcb26","text":"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.","title":"During initial synchronization of a logical replication subscription, commit the addition of a pg_replication_origin entry before starting to copy data"},"id":"18.2-2de557ccdda45f50","matches":[{"id":"17.8-e95d66b2b17f79c5","source_entry_id":"17.8/changes/030","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","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/045","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","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["0ed8f1afb","1528b0d89","2f7ffe124","63a65adf4"],"commit_groups":[["0ed8f1afb","1528b0d89","2f7ffe124","63a65adf4"]],"commits":["2f7ffe124"],"cves":[],"db_id":"3e82f89211515507e8f8677f313d3799","html":"\u003cp\u003eDon't advance logical replication progress after a parallel worker apply failure (Zhijie Hou) \u003ca href=\"https://postgr.es/c/2f7ffe124\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe previous behavior allowed transactions to be lost by a subscriber.\u003c/p\u003e","id":"18.2-434a2b6b0d42abc4","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.","part":"changes","patch_ids":["9d8b1309e987cb63c5164f0ac19628f4"],"relations":[{"evidence":{"patch_ids":["9d8b1309e987cb63c5164f0ac19628f4"],"same_day":true,"statement_hash":"843a95a8685d2abb66e22dcecb3ca218c807c27fb6410d57c5646106423458aa"},"rule":2,"target":"0f5fb8d4e546a502c86c3683cd965e48","type":"equivalent"},{"evidence":{"patch_ids":["9d8b1309e987cb63c5164f0ac19628f4"],"same_day":true,"statement_hash":"843a95a8685d2abb66e22dcecb3ca218c807c27fb6410d57c5646106423458aa"},"rule":2,"target":"d3f0ce1d0627ffd85c57f5963d822b33","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["2f7ffe124"],"source_entry_id":"18.2/changes/046","source_hash":"c17ef3ba75ba5fa5aac564f44981db3ee27f8743c1b4e5bfc13e722e0597619e","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"843a95a8685d2abb66e22dcecb3ca218c807c27fb6410d57c5646106423458aa","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"},"id":"18.2-434a2b6b0d42abc4","matches":[{"id":"17.8-e6867fece2c6f2d4","source_entry_id":"17.8/changes/031","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Don't advance logical replication progress after a parallel worker apply failure","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/046","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Don't advance logical replication progress after a parallel worker apply failure","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["04396eacd","6c61c69d5","f2818868a"],"commit_groups":[["04396eacd","6c61c69d5","f2818868a"]],"commits":["6c61c69d5"],"cves":[],"db_id":"b79cdfd53c29fdec5dd1d0dff7f08fee","html":"\u003cp\u003eFix logical replication slotsync worker processes to handle LOCK_TIMEOUT signals correctly (Zhijie Hou) \u003ca href=\"https://postgr.es/c/6c61c69d5\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, timeout signals were effectively ignored.\u003c/p\u003e","id":"18.2-2a6c1c4c27f67acd","identity_text":"Fix logical replication slotsync worker processes to handle LOCK_TIMEOUT signals correctly (Zhijie Hou) Previously, timeout signals were effectively ignored.","part":"changes","patch_ids":["bdd6c0273fd3cdf835c31867877f6167"],"relations":[{"evidence":{"patch_ids":["bdd6c0273fd3cdf835c31867877f6167"],"same_day":true,"statement_hash":"f0b98267cefa8d08da7ffcca6c441a22dd2c4323a5763263e96b18dd48ae7fc5"},"rule":2,"target":"516169d81baba61d618e37237bc53276","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["6c61c69d5"],"source_entry_id":"18.2/changes/047","source_hash":"017587a58ab5429b97a836037d4a2dcc806817c09eeeafb775bf2d12edd94f1f","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"f0b98267cefa8d08da7ffcca6c441a22dd2c4323a5763263e96b18dd48ae7fc5","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"},"id":"18.2-2a6c1c4c27f67acd","matches":[{"id":"17.8-f2b54a080f4d7fca","source_entry_id":"17.8/changes/032","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix logical replication slotsync worker processes to handle LOCK_TIMEOUT signals correctly","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/047","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix logical replication slotsync worker processes to handle LOCK_TIMEOUT signals correctly","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["23b25586d","2514f1c77","9ed411e08","a2eeb04f3","c3770181c","ef8465588"],"commit_groups":[["23b25586d","2514f1c77","9ed411e08","a2eeb04f3","c3770181c","ef8465588"]],"commits":["9ed411e08"],"cves":[],"db_id":"06594efa4344da118700b1c48988f5e4","html":"\u003cp\u003eFix possible failure with \u003cspan\u003e“\u003cspan\u003eunexpected data beyond EOF\u003c/span\u003e”\u003c/span\u003e during restart of a streaming replica server (Anthonin Bonnefoy) \u003ca href=\"https://postgr.es/c/9ed411e08\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-c52d288613257e1b","identity_text":"Fix possible failure with unexpected data beyond EOF during restart of a streaming replica server (Anthonin Bonnefoy)","part":"changes","patch_ids":["5162c78b0f9af44ee53c5daf07030ba8"],"relations":[{"evidence":{"patch_ids":["5162c78b0f9af44ee53c5daf07030ba8"],"same_day":true,"statement_hash":"6b8e19ac39d2a905a6b06a59a41de464bc6a62cc815b31c6e858ae96438db9ab"},"rule":2,"target":"668c3f03c522a5db8d076f179e064027","type":"equivalent"},{"evidence":{"patch_ids":["5162c78b0f9af44ee53c5daf07030ba8"],"same_day":true,"statement_hash":"6b8e19ac39d2a905a6b06a59a41de464bc6a62cc815b31c6e858ae96438db9ab"},"rule":2,"target":"8d924571fb5bee478b47c49ff89fa7f5","type":"equivalent"},{"evidence":{"patch_ids":["5162c78b0f9af44ee53c5daf07030ba8"],"same_day":true,"statement_hash":"6b8e19ac39d2a905a6b06a59a41de464bc6a62cc815b31c6e858ae96438db9ab"},"rule":2,"target":"a321a63cf72d9e7f3afd2ff1e5a2c814","type":"equivalent"},{"evidence":{"patch_ids":["5162c78b0f9af44ee53c5daf07030ba8"],"same_day":true,"statement_hash":"6b8e19ac39d2a905a6b06a59a41de464bc6a62cc815b31c6e858ae96438db9ab"},"rule":2,"target":"a79b7d220801497e224783e6369f7957","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["9ed411e08"],"source_entry_id":"18.2/changes/048","source_hash":"0ac3e36bd9eb803636d4bc335fbd3e6c1cd2c90d25709b74f7c9a37a8a9bdc37","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"6b8e19ac39d2a905a6b06a59a41de464bc6a62cc815b31c6e858ae96438db9ab","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"},"id":"18.2-c52d288613257e1b","matches":[{"id":"17.8-ca1e290b0cb2dd09","source_entry_id":"17.8/changes/033","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","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/048","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","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["15ba0702c","519fa0433","b5511fed5"],"commit_groups":[["15ba0702c","519fa0433","b5511fed5"]],"commits":["15ba0702c"],"cves":[],"db_id":"54166f9d89f4ebad4b6522ec9d70d5f6","html":"\u003cp\u003eFix error reporting for SQL/JSON path type mismatches (Jian He) \u003ca href=\"https://postgr.es/c/15ba0702c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe code could produce a \u003cspan\u003e“\u003cspan\u003ecache lookup failed for type 0\u003c/span\u003e”\u003c/span\u003e error instead of the intended complaint about the path expression not being of the right type.\u003c/p\u003e","id":"18.2-a3a0f5425174a83a","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.","part":"changes","patch_ids":["280990af5b3469c06fb7ff61c204b4ef"],"relations":[{"evidence":{"patch_ids":["280990af5b3469c06fb7ff61c204b4ef"],"same_day":true,"statement_hash":"125204f7b1e9d0130c0fb80a18be78fa7ce15ceea1fb46138ad538ba516556af"},"rule":2,"target":"8483ae615f87a4c8e095a563aecd48c8","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["15ba0702c"],"source_entry_id":"18.2/changes/049","source_hash":"2e243fce6b9135a007fbafb79736adc7b43b27bd3e12b89d1e6be0a5b8436842","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"125204f7b1e9d0130c0fb80a18be78fa7ce15ceea1fb46138ad538ba516556af","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"},"id":"18.2-a3a0f5425174a83a","matches":[{"id":"17.8-2a0ef06d727eafaf","source_entry_id":"17.8/changes/034","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix error reporting for SQL/JSON path type mismatches","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/049","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix error reporting for SQL/JSON path type mismatches","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["349107537","3ad05640b","821c4d27b","84b787ae6","a65995947","c35e5dd9a"],"commit_groups":[["349107537","3ad05640b","821c4d27b","84b787ae6","a65995947","c35e5dd9a"]],"commits":["c35e5dd9a"],"cves":[],"db_id":"bcd807761d1a951aa85d661bf8df019c","html":"\u003cp\u003eFix erroneous tracking of column position when parsing partition range bounds (myzhen) \u003ca href=\"https://postgr.es/c/c35e5dd9a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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.\u003c/p\u003e","id":"18.2-3915ae13b44752be","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.","part":"changes","patch_ids":["6f0c6912e975c2e11453b9af7373ff2b"],"relations":[{"evidence":{"patch_ids":["6f0c6912e975c2e11453b9af7373ff2b"],"same_day":true,"statement_hash":"99c55def0f9f50d97f55530e56d1c92347af0e9dedfe788a482bbfd2a5b86232"},"rule":2,"target":"3d999c9c39b345cf00d6c149f77369bc","type":"equivalent"},{"evidence":{"patch_ids":["6f0c6912e975c2e11453b9af7373ff2b"],"same_day":true,"statement_hash":"99c55def0f9f50d97f55530e56d1c92347af0e9dedfe788a482bbfd2a5b86232"},"rule":2,"target":"775ee6e8b3e233efe9c85fc527d0a5d4","type":"equivalent"},{"evidence":{"patch_ids":["6f0c6912e975c2e11453b9af7373ff2b"],"same_day":true,"statement_hash":"99c55def0f9f50d97f55530e56d1c92347af0e9dedfe788a482bbfd2a5b86232"},"rule":2,"target":"8da33c76c87cf129799d93a7efd47d96","type":"equivalent"},{"evidence":{"patch_ids":["6f0c6912e975c2e11453b9af7373ff2b"],"same_day":true,"statement_hash":"99c55def0f9f50d97f55530e56d1c92347af0e9dedfe788a482bbfd2a5b86232"},"rule":2,"target":"bb4e430870bc5f4909df899b3e4e6a47","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c35e5dd9a"],"source_entry_id":"18.2/changes/050","source_hash":"fa85d72517344f820a9769f83967f877f4194c8f595ca694fae0c2e502a1d930","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"99c55def0f9f50d97f55530e56d1c92347af0e9dedfe788a482bbfd2a5b86232","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"},"id":"18.2-3915ae13b44752be","matches":[{"id":"17.8-1ae71997df1c5c19","source_entry_id":"17.8/changes/035","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix erroneous tracking of column position when parsing partition range bounds","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/050","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix erroneous tracking of column position when parsing partition range bounds","version":"18.2"},{"entry":{"category":"bugfix","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"],"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"]],"commits":["2ca4464b6","69ee81932","ab61f0087","acfa422c3","cff2ef984"],"cves":[],"db_id":"c28d793705797c568ae351065c8bf92d","html":"\u003cp\u003eFix assorted minor errors in error messages (Man Zeng, Tianchen Zhang) \u003ca href=\"https://postgr.es/c/acfa422c3\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/2ca4464b6\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/ab61f0087\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/69ee81932\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/cff2ef984\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFor 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.\u003c/p\u003e","id":"18.2-2eb9c2c4100a1830","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.","part":"changes","patch_ids":["1b2d3003a616272db51c764aca05446f","9747f7cd321d1b9a8c5ab680817d174b","d322434f9f1579628716983e1ddfa411","dafc2603cafe575939465f2fd551a6ac","e9fdf560cb4a79421801e80c5b2933b7"],"relations":[{"evidence":{"patch_ids":["1b2d3003a616272db51c764aca05446f","9747f7cd321d1b9a8c5ab680817d174b","d322434f9f1579628716983e1ddfa411","dafc2603cafe575939465f2fd551a6ac","e9fdf560cb4a79421801e80c5b2933b7"],"same_day":true,"statement_hash":"1c12bc1b49de92034a5abdd2caee35fcf65ab113a875838de01715e754830737"},"rule":2,"target":"03e8508ea8a410388767d947c24e8eb3","type":"equivalent"},{"evidence":{"patch_ids":["1b2d3003a616272db51c764aca05446f","9747f7cd321d1b9a8c5ab680817d174b","d322434f9f1579628716983e1ddfa411","dafc2603cafe575939465f2fd551a6ac","e9fdf560cb4a79421801e80c5b2933b7"],"same_day":true,"statement_hash":"1c12bc1b49de92034a5abdd2caee35fcf65ab113a875838de01715e754830737"},"rule":2,"target":"040254b8395148f9ed2820a7a9e7de75","type":"equivalent"},{"evidence":{"patch_ids":["1b2d3003a616272db51c764aca05446f","9747f7cd321d1b9a8c5ab680817d174b","d322434f9f1579628716983e1ddfa411","dafc2603cafe575939465f2fd551a6ac","e9fdf560cb4a79421801e80c5b2933b7"],"same_day":true,"statement_hash":"1c12bc1b49de92034a5abdd2caee35fcf65ab113a875838de01715e754830737"},"rule":2,"target":"6391fdf7551cb6b17994c91b76215a9f","type":"equivalent"},{"evidence":{"patch_ids":["1b2d3003a616272db51c764aca05446f","9747f7cd321d1b9a8c5ab680817d174b","d322434f9f1579628716983e1ddfa411","dafc2603cafe575939465f2fd551a6ac","e9fdf560cb4a79421801e80c5b2933b7"],"same_day":true,"statement_hash":"1c12bc1b49de92034a5abdd2caee35fcf65ab113a875838de01715e754830737"},"rule":2,"target":"e4eecf733b283aee3b3d1c824dbc8e27","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["2ca4464b6","69ee81932","ab61f0087","acfa422c3","cff2ef984"],"source_entry_id":"18.2/changes/051","source_hash":"3a2e503ffa840257c48e18ab773638404e85b6cf64ba6cd94646de3511c66bcf","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"1c12bc1b49de92034a5abdd2caee35fcf65ab113a875838de01715e754830737","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"},"id":"18.2-2eb9c2c4100a1830","matches":[{"id":"17.8-4eafc20a792cccfc","source_entry_id":"17.8/changes/036","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix assorted minor errors in error messages","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/051","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix assorted minor errors in error messages","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["7600dc79c","cbdd09ae1","d0bb0e5b3","de8081c30","e5d99b4d9","f1c6b153c"],"commit_groups":[["7600dc79c","cbdd09ae1","d0bb0e5b3","de8081c30","e5d99b4d9","f1c6b153c"]],"commits":["f1c6b153c"],"cves":[],"db_id":"6c8a23f42fdf36b27a5c63a60ef638ee","html":"\u003cp\u003eFix failure to perform function inlining when doing JIT compilation with LLVM version 17 or later (Anthonin Bonnefoy) \u003ca href=\"https://postgr.es/c/f1c6b153c\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-53f3b7ffe4f6fe06","identity_text":"Fix failure to perform function inlining when doing JIT compilation with LLVM version 17 or later (Anthonin Bonnefoy)","part":"changes","patch_ids":["5add9e288aea8ead5625b1ab17f4b389"],"relations":[{"evidence":{"patch_ids":["5add9e288aea8ead5625b1ab17f4b389"],"same_day":true,"statement_hash":"d9b663cb80004c186d8a4f9af93bb5b74dc9a0534dcc279ee72325534d3c24af"},"rule":2,"target":"1d826bf62f1c8707e84a00b08bca6cc2","type":"equivalent"},{"evidence":{"patch_ids":["5add9e288aea8ead5625b1ab17f4b389"],"same_day":true,"statement_hash":"d9b663cb80004c186d8a4f9af93bb5b74dc9a0534dcc279ee72325534d3c24af"},"rule":2,"target":"23db3b0771d0b80deb078c18239bf311","type":"equivalent"},{"evidence":{"patch_ids":["5add9e288aea8ead5625b1ab17f4b389"],"same_day":true,"statement_hash":"d9b663cb80004c186d8a4f9af93bb5b74dc9a0534dcc279ee72325534d3c24af"},"rule":2,"target":"41aa0fa812e386b3bf111e16e5ca824b","type":"equivalent"},{"evidence":{"patch_ids":["5add9e288aea8ead5625b1ab17f4b389"],"same_day":true,"statement_hash":"d9b663cb80004c186d8a4f9af93bb5b74dc9a0534dcc279ee72325534d3c24af"},"rule":2,"target":"da5340b311cf457b0c8052e7119f6c5c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["f1c6b153c"],"source_entry_id":"18.2/changes/052","source_hash":"9981fa0cf79c4c8beef5d9a46dae95989b255aff0b13e70cfe22036f2abce7d8","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"d9b663cb80004c186d8a4f9af93bb5b74dc9a0534dcc279ee72325534d3c24af","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"},"id":"18.2-53f3b7ffe4f6fe06","matches":[{"id":"17.8-c185802f4eacb2ea","source_entry_id":"17.8/changes/037","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","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/052","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","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["035a1f5ac","0dceba21d","55164852d","600acd34b","60215eae7","912cfa314"],"commit_groups":[["035a1f5ac","0dceba21d","55164852d","600acd34b","60215eae7","912cfa314"]],"commits":["912cfa314"],"cves":[],"db_id":"e7ed91f4e25921028767eb7d80e59575","html":"\u003cp\u003eAdjust our JIT code to work with LLVM 21 (Holger Hoffstätte) \u003ca href=\"https://postgr.es/c/912cfa314\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe previous coding failed to compile on aarch64 machines.\u003c/p\u003e","id":"18.2-bf063586f9119b1e","identity_text":"Adjust our JIT code to work with LLVM 21 (Holger Hoffstätte) The previous coding failed to compile on aarch64 machines.","part":"changes","patch_ids":["66d712c94d1e5df73fed0dd65d77b242"],"relations":[{"evidence":{"patch_ids":["66d712c94d1e5df73fed0dd65d77b242"],"same_day":true,"statement_hash":"3c6749ca7e34ce305cd7020f2256a99d6e58f6a41cedef18deedef24299c3cdc"},"rule":2,"target":"084e13baf0a1aaa1b6831e50a2e8b014","type":"equivalent"},{"evidence":{"patch_ids":["66d712c94d1e5df73fed0dd65d77b242"],"same_day":true,"statement_hash":"3c6749ca7e34ce305cd7020f2256a99d6e58f6a41cedef18deedef24299c3cdc"},"rule":2,"target":"51e665bd2f8466b41d80cf0223c7e413","type":"equivalent"},{"evidence":{"patch_ids":["66d712c94d1e5df73fed0dd65d77b242"],"same_day":true,"statement_hash":"3c6749ca7e34ce305cd7020f2256a99d6e58f6a41cedef18deedef24299c3cdc"},"rule":2,"target":"c7ea32ba825d2c7140b0017b02f1a3ec","type":"equivalent"},{"evidence":{"patch_ids":["66d712c94d1e5df73fed0dd65d77b242"],"same_day":true,"statement_hash":"3c6749ca7e34ce305cd7020f2256a99d6e58f6a41cedef18deedef24299c3cdc"},"rule":2,"target":"cff57c5be469c947c3ffe128e6ba5e35","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["912cfa314"],"source_entry_id":"18.2/changes/053","source_hash":"642123a264bfa926555231fb51c1f55785277efb74e7e05d7068980643cc565b","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"3c6749ca7e34ce305cd7020f2256a99d6e58f6a41cedef18deedef24299c3cdc","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"},"id":"18.2-bf063586f9119b1e","matches":[{"id":"17.8-64e9296142cf419d","source_entry_id":"17.8/changes/038","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Adjust our JIT code to work with LLVM 21","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/053","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Adjust our JIT code to work with LLVM 21","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["33e3de6d7","4dac22aa1","e37b59802","f94e9141a"],"commit_groups":[["33e3de6d7","4dac22aa1","e37b59802","f94e9141a"]],"commits":["33e3de6d7"],"cves":[],"db_id":"21858e94e3aeea81abfb43c5e1981b1c","html":"\u003cp\u003eAdd new server parameter \u003ca href=\"/docs/18/runtime-config-resource.html#GUC-FILE-EXTEND-METHOD\"\u003efile_extend_method\u003c/a\u003e to control use of \u003ccode\u003eposix_fallocate()\u003c/code\u003e (Thomas Munro) \u003ca href=\"https://postgr.es/c/33e3de6d7\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003ePostgreSQL\u003c/span\u003e version 16 and later will use \u003ccode\u003eposix_fallocate()\u003c/code\u003e, 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 \u003ccode\u003eposix_fallocate()\u003c/code\u003e, and XFS could produce spurious \u003ccode\u003eENOSPC\u003c/code\u003e errors in older Linux kernel versions. To provide a workaround, introduce this new server parameter. Setting \u003ccode\u003efile_extend_method\u003c/code\u003e to \u003ccode\u003ewrite_zeros\u003c/code\u003e will cause the server to return to the old method of extending files by writing blocks of zeroes.\u003c/p\u003e","id":"18.2-03a42dee6cc753ad","identity_text":"Add new server parameter guc-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.","part":"changes","patch_ids":["a7b44dde4fd829d977d49b09a9e92844"],"relations":[{"evidence":{"patch_ids":["a7b44dde4fd829d977d49b09a9e92844"],"same_day":true,"statement_hash":"5c68aeb05030a49c506a17d2a099ad9d1dea4d8b209cb3fdb53b69f77666342f"},"rule":2,"target":"1190447ef9e06df061dbd62c7fd05aa7","type":"equivalent"},{"evidence":{"patch_ids":["a7b44dde4fd829d977d49b09a9e92844"],"same_day":true,"statement_hash":"5c68aeb05030a49c506a17d2a099ad9d1dea4d8b209cb3fdb53b69f77666342f"},"rule":2,"target":"831a2a1707eb5395bf41f9e7b4720b03","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["33e3de6d7"],"source_entry_id":"18.2/changes/056","source_hash":"0763504b59f32586bd0ff315aa6677dae3416479e0120c8722fe71ac102de530","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"5c68aeb05030a49c506a17d2a099ad9d1dea4d8b209cb3fdb53b69f77666342f","text":"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.","title":"Add new server parameter file_extend_method to control use of posix_fallocate()"},"id":"18.2-03a42dee6cc753ad","matches":[{"id":"17.8-3210c07692952f51","source_entry_id":"17.8/changes/039","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Add new server parameter file_extend_method to control use of posix_fallocate()","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/056","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Add new server parameter file_extend_method to control use of posix_fallocate()","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["045185913","0666ccc16","45d92b76d","4da5c33a3","80e8ec772","a7d06e74d","b3c8119e2","bebb281b0","bec2a0aa3","c507ba55f","d62a258cd","f24af0e04"],"commit_groups":[["045185913","0666ccc16","a7d06e74d","bec2a0aa3"],["45d92b76d","4da5c33a3","80e8ec772","b3c8119e2"],["bebb281b0","c507ba55f","d62a258cd","f24af0e04"]],"commits":["4da5c33a3","a7d06e74d","bebb281b0"],"cves":[],"db_id":"fa4848909b9ff58346d80a375d2238ce","html":"\u003cp\u003eHonor \u003ccode\u003eopen()\u003c/code\u003e's \u003ccode\u003eO_CLOEXEC\u003c/code\u003e flag on Windows (Bryan Green, Thomas Munro) \u003ca href=\"https://postgr.es/c/bebb281b0\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/a7d06e74d\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/4da5c33a3\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eMake this flag work like it does on POSIX platforms, so that we don't leak file handles into child processes such as \u003ccode\u003eCOPY TO/FROM PROGRAM\u003c/code\u003e. While that leakage hasn't caused many problems, it seems undesirable.\u003c/p\u003e","id":"18.2-10e49010a4ad318c","identity_text":"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.","part":"changes","patch_ids":["095b8a9ad1149ec7e6b384f86412045c","16e4048c75704084d232d66835f3cf6e","493ffab07cbb8d27c6dbcf9cf0a4cab6"],"relations":[{"evidence":{"patch_ids":["095b8a9ad1149ec7e6b384f86412045c","16e4048c75704084d232d66835f3cf6e","493ffab07cbb8d27c6dbcf9cf0a4cab6"],"same_day":true,"statement_hash":"485d2888baf50e5c83a886ec0fc75091bea61287485912424715911ca20d90c7"},"rule":2,"target":"003ad72554700873dc6210b7a5e54e84","type":"equivalent"},{"evidence":{"patch_ids":["095b8a9ad1149ec7e6b384f86412045c","16e4048c75704084d232d66835f3cf6e","493ffab07cbb8d27c6dbcf9cf0a4cab6"],"same_day":true,"statement_hash":"485d2888baf50e5c83a886ec0fc75091bea61287485912424715911ca20d90c7"},"rule":2,"target":"6b80a0f86b8e07e750eef0cc17220a4a","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["4da5c33a3","a7d06e74d","bebb281b0"],"source_entry_id":"18.2/changes/057","source_hash":"020a5f8c42b63941e930482cc638cddc844a411b4e170096b1d3565c877d9537","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"485d2888baf50e5c83a886ec0fc75091bea61287485912424715911ca20d90c7","text":"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.","title":"Honor open()'s O_CLOEXEC flag on Windows"},"id":"18.2-10e49010a4ad318c","matches":[{"id":"17.8-8c683b207dde44d9","source_entry_id":"17.8/changes/040","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Honor open()'s O_CLOEXEC flag on Windows","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/057","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Honor open()'s O_CLOEXEC flag on Windows","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["59c2f7efa","5eac1d68f","7369656fa","c0bf15729"],"commit_groups":[["59c2f7efa","5eac1d68f","7369656fa","c0bf15729"]],"commits":["5eac1d68f"],"cves":[],"db_id":"c730bdc0e2bcae412d1b558e6989e803","html":"\u003cp\u003eFix failure to parse long options on the server command line in Solaris executables built with meson (Tom Lane) \u003ca href=\"https://postgr.es/c/5eac1d68f\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-ca3da398904bd780","identity_text":"Fix failure to parse long options on the server command line in Solaris executables built with meson (Tom Lane)","part":"changes","patch_ids":["133a9f9fce49cbd34f1b9ba0b7dee391"],"relations":[{"evidence":{"patch_ids":["133a9f9fce49cbd34f1b9ba0b7dee391"],"same_day":true,"statement_hash":"5ef581baf9ed7ef45975ff2c7d893c9da8f950d13c68cd98fea4606121f2a7ac"},"rule":2,"target":"563cd6c38790a66a34d7d2cbdab27f36","type":"equivalent"},{"evidence":{"patch_ids":["133a9f9fce49cbd34f1b9ba0b7dee391"],"same_day":true,"statement_hash":"5ef581baf9ed7ef45975ff2c7d893c9da8f950d13c68cd98fea4606121f2a7ac"},"rule":2,"target":"ae36e9e2da103cf26dac76edbf8412a6","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["5eac1d68f"],"source_entry_id":"18.2/changes/058","source_hash":"f1d750e251da7d0c5b6c6b1df9e1accdcbd5f93f3d2ebd78c2af2fe02f60fa7d","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"5ef581baf9ed7ef45975ff2c7d893c9da8f950d13c68cd98fea4606121f2a7ac","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"},"id":"18.2-ca3da398904bd780","matches":[{"id":"17.8-c28c500f08d6dda7","source_entry_id":"17.8/changes/041","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix failure to parse long options on the server command line in Solaris executables built with meson","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/058","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix failure to parse long options on the server command line in Solaris executables built with meson","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["29a3e22f3","32b236644","3995e4a9d","a1407dade","bcfca332f","d66a922f9"],"commit_groups":[["29a3e22f3","32b236644","3995e4a9d","a1407dade","bcfca332f","d66a922f9"]],"commits":["bcfca332f"],"cves":[],"db_id":"92b88e55c652dfa1fcdde3f0953f3285","html":"\u003cp\u003eSupport process title changes on GNU/Hurd (Michael Banck) \u003ca href=\"https://postgr.es/c/bcfca332f\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-e1336b6079ff8d5b","identity_text":"Support process title changes on GNU/Hurd (Michael Banck)","part":"changes","patch_ids":["f27aa5a2659577ffa2455a4c94564743"],"relations":[{"evidence":{"patch_ids":["f27aa5a2659577ffa2455a4c94564743"],"same_day":true,"statement_hash":"c996e792f260f0d512b6a6524e3b46eed7769d4f17a4584a012601680f44fc4f"},"rule":2,"target":"45f431c4bd4cad50e4053b47f371bd3f","type":"equivalent"},{"evidence":{"patch_ids":["f27aa5a2659577ffa2455a4c94564743"],"same_day":true,"statement_hash":"c996e792f260f0d512b6a6524e3b46eed7769d4f17a4584a012601680f44fc4f"},"rule":2,"target":"465d44f8b93dc009feaa8d1fac573196","type":"equivalent"},{"evidence":{"patch_ids":["f27aa5a2659577ffa2455a4c94564743"],"same_day":true,"statement_hash":"c996e792f260f0d512b6a6524e3b46eed7769d4f17a4584a012601680f44fc4f"},"rule":2,"target":"b14342e6824ed37b82078bd9a6cc21e1","type":"equivalent"},{"evidence":{"patch_ids":["f27aa5a2659577ffa2455a4c94564743"],"same_day":true,"statement_hash":"c996e792f260f0d512b6a6524e3b46eed7769d4f17a4584a012601680f44fc4f"},"rule":2,"target":"d2f91f9760f28a721378c4e8d76ef619","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["bcfca332f"],"source_entry_id":"18.2/changes/059","source_hash":"3651cd00413e52bb3457a26d79d84c86f9729cad9edaec4ba29371fdb93f26e0","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"c996e792f260f0d512b6a6524e3b46eed7769d4f17a4584a012601680f44fc4f","text":"Support process title changes on GNU/Hurd (Michael Banck) §","title":"Support process title changes on GNU/Hurd"},"id":"18.2-e1336b6079ff8d5b","matches":[{"id":"17.8-3cbfa3eb5e11672e","source_entry_id":"17.8/changes/042","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Support process title changes on GNU/Hurd","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/059","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Support process title changes on GNU/Hurd","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["1cdc07ad5","573e679a2","d49936f30"],"commit_groups":[["1cdc07ad5","573e679a2","d49936f30"]],"commits":["573e679a2"],"cves":[],"db_id":"df5cb5704fef8f74897251fa0c3be081","html":"\u003cp\u003eAvoid \u003cspan\u003epg_dump\u003c/span\u003e assertion failure in binary-upgrade mode (Vignesh C) \u003ca href=\"https://postgr.es/c/573e679a2\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFailure to handle subscription-relation objects in the object sorting code triggered an assertion, though there were no serious ill effects in production builds.\u003c/p\u003e","id":"18.2-ee37d4b2b910a503","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.","part":"changes","patch_ids":["ed0dc1c369ce52f90f050a02c31cfe22"],"relations":[{"evidence":{"patch_ids":["ed0dc1c369ce52f90f050a02c31cfe22"],"same_day":true,"statement_hash":"305d4ecb2b90454723cac5826da3903c1efb32bfae398fdc085bfa0cabab291a"},"rule":2,"target":"4494339208c66bea624ef04f8e7162d7","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["573e679a2"],"source_entry_id":"18.2/changes/064","source_hash":"30e87eaba4d7329f1777ef3c10be9b4eeeb69ede053339decb40edbf95012f34","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"305d4ecb2b90454723cac5826da3903c1efb32bfae398fdc085bfa0cabab291a","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"},"id":"18.2-ee37d4b2b910a503","matches":[{"id":"17.8-fb87d1ddb8333f9e","source_entry_id":"17.8/changes/043","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Avoid pg_dump assertion failure in binary-upgrade mode","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/064","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Avoid pg_dump assertion failure in binary-upgrade mode","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["00e64e35c","4aa0ac057","5bc251b28"],"commit_groups":[["00e64e35c","4aa0ac057","5bc251b28"]],"commits":["00e64e35c"],"cves":[],"db_id":"110c54d4f77bbbf3b3cb5646c3d03270","html":"\u003cp\u003eFix incorrect error handling in \u003cspan\u003epgbench\u003c/span\u003e with multiple \u003ccode\u003e\\syncpipeline\u003c/code\u003e commands in pipeline mode (Yugo Nagata) \u003ca href=\"https://postgr.es/c/00e64e35c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf multiple \u003ccode\u003e\\syncpipeline\u003c/code\u003e commands are encountered after a query error, \u003cspan\u003epgbench\u003c/span\u003e would report \u003cspan\u003e“\u003cspan\u003efailed to exit pipeline mode\u003c/span\u003e”\u003c/span\u003e, or get an assertion failure in an assert-enabled build.\u003c/p\u003e","id":"18.2-e7bddef1f2dbe17d","identity_text":"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.","part":"changes","patch_ids":["abe851e3d64606b4d1f39d5998d6d005"],"relations":[{"evidence":{"patch_ids":["abe851e3d64606b4d1f39d5998d6d005"],"same_day":true,"statement_hash":"1cdefe00c629d46dbeafbb68e1efcdba4901e90682edb67326771603d66f0385"},"rule":2,"target":"e6397b23168007fedda0f3f80287907f","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["00e64e35c"],"source_entry_id":"18.2/changes/065","source_hash":"faa30a575df1ae78579de5ecbb4f392a5468803fa8d63169d08e576c223c33b3","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"1cdefe00c629d46dbeafbb68e1efcdba4901e90682edb67326771603d66f0385","text":"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.","title":"Fix incorrect error handling in pgbench with multiple \\syncpipeline commands in pipeline mode"},"id":"18.2-e7bddef1f2dbe17d","matches":[{"id":"17.8-db3cf1766c83bbad","source_entry_id":"17.8/changes/044","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix incorrect error handling in pgbench with multiple \\syncpipeline commands in pipeline mode","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/065","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix incorrect error handling in pgbench with multiple \\syncpipeline commands in pipeline mode","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["11cc0f452","19594271c","7c494072b","890cc81b6","d5b4f3a6d","f2e0ca0af"],"commit_groups":[["11cc0f452","19594271c","7c494072b","890cc81b6","d5b4f3a6d","f2e0ca0af"]],"commits":["19594271c"],"cves":[],"db_id":"5f928cd7f1a940e12cd51a8ce19d06f6","html":"\u003cp\u003eMake \u003cspan\u003epg_resetwal\u003c/span\u003e print the updated value when changing OldestXID (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/19594271c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIt already did that for every other variable it can change.\u003c/p\u003e","id":"18.2-12ea46c5ca32b0f2","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.","part":"changes","patch_ids":["f29e862445ceccbb303aaae2f778a19b"],"relations":[{"evidence":{"patch_ids":["f29e862445ceccbb303aaae2f778a19b"],"same_day":true,"statement_hash":"7e00b6482e7aa0b9a1cb427214f076ddb806bf1fa199c1cf0ab023c54c2dd96a"},"rule":2,"target":"22be50f61755ecf5187af28b01545b41","type":"equivalent"},{"evidence":{"patch_ids":["f29e862445ceccbb303aaae2f778a19b"],"same_day":true,"statement_hash":"7e00b6482e7aa0b9a1cb427214f076ddb806bf1fa199c1cf0ab023c54c2dd96a"},"rule":2,"target":"47e617ce37a58405cf4c7f033f26b641","type":"equivalent"},{"evidence":{"patch_ids":["f29e862445ceccbb303aaae2f778a19b"],"same_day":true,"statement_hash":"7e00b6482e7aa0b9a1cb427214f076ddb806bf1fa199c1cf0ab023c54c2dd96a"},"rule":2,"target":"500d9d80888f7caeb4b4801bee95301d","type":"equivalent"},{"evidence":{"patch_ids":["f29e862445ceccbb303aaae2f778a19b"],"same_day":true,"statement_hash":"7e00b6482e7aa0b9a1cb427214f076ddb806bf1fa199c1cf0ab023c54c2dd96a"},"rule":2,"target":"94c5ea9aed8ffadf4043f33f201ed4e5","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["19594271c"],"source_entry_id":"18.2/changes/066","source_hash":"7d0671d0086f58d8e012489b82175ffdaeea54f9aec8617fd497a06c1f4dc1b7","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"7e00b6482e7aa0b9a1cb427214f076ddb806bf1fa199c1cf0ab023c54c2dd96a","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"},"id":"18.2-12ea46c5ca32b0f2","matches":[{"id":"17.8-0aca6daf3559b899","source_entry_id":"17.8/changes/045","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Make pg_resetwal print the updated value when changing OldestXID","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/066","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Make pg_resetwal print the updated value when changing OldestXID","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["8747b969f","94939c5f3","97cd4b65a","cb2ef0e92","e039b09f8"],"commit_groups":[["8747b969f","94939c5f3","97cd4b65a","cb2ef0e92","e039b09f8"]],"commits":["8747b969f"],"cves":[],"db_id":"a4ce7629005a43b316bb9b4fbdb478ad","html":"\u003cp\u003eMake \u003cspan\u003epg_resetwal\u003c/span\u003e allow setting next multixact xid to 0 or next multixact offset to UINT32_MAX (Maxim Orlov) \u003ca href=\"https://postgr.es/c/8747b969f\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese 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.\u003c/p\u003e","id":"18.2-b3adbf7cc127bf87","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.","part":"changes","patch_ids":["0f6a9848b48d4b26e3e4691043d1c86b"],"relations":[{"evidence":{"patch_ids":["0f6a9848b48d4b26e3e4691043d1c86b"],"same_day":true,"statement_hash":"55f06afcc35f279a01bd7723ea6dc23f0393b803bcd2fbe9ea5c0600d99ed0ea"},"rule":2,"target":"4da7f3aac2517d05e54bea6d3c1ab25e","type":"equivalent"},{"evidence":{"patch_ids":["0f6a9848b48d4b26e3e4691043d1c86b"],"same_day":true,"statement_hash":"55f06afcc35f279a01bd7723ea6dc23f0393b803bcd2fbe9ea5c0600d99ed0ea"},"rule":2,"target":"89127b250f2abea1a64f754f71c48c77","type":"equivalent"},{"evidence":{"patch_ids":["0f6a9848b48d4b26e3e4691043d1c86b"],"same_day":true,"statement_hash":"55f06afcc35f279a01bd7723ea6dc23f0393b803bcd2fbe9ea5c0600d99ed0ea"},"rule":2,"target":"ba56a98c48c3c98e929510554c2c7d1f","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["8747b969f"],"source_entry_id":"18.2/changes/067","source_hash":"19aa11ac03ecd9743883b5b3b7d28a4034c78e536b691f1127ad247cf62f9794","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"55f06afcc35f279a01bd7723ea6dc23f0393b803bcd2fbe9ea5c0600d99ed0ea","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"},"id":"18.2-b3adbf7cc127bf87","matches":[{"id":"17.8-6a1deb077e1799c1","source_entry_id":"17.8/changes/046","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","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/067","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","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["098a1fab8","1f28982e4","3c83a2a0a","607a67c5e","6bd469d26","ce2f575b7","dcddd6987","df93f94dd","e1a327dc4"],"commit_groups":[["098a1fab8","1f28982e4","3c83a2a0a","607a67c5e","dcddd6987","e1a327dc4"],["6bd469d26","ce2f575b7","df93f94dd"]],"commits":["3c83a2a0a","df93f94dd"],"cves":[],"db_id":"955a03e6ef46153a22d64b4e82c47168","html":"\u003cp\u003eIn \u003ccode\u003econtrib/amcheck\u003c/code\u003e, use the correct snapshot for btree index parent checks (Mihail Nikalayeu) \u003ca href=\"https://postgr.es/c/df93f94dd\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/3c83a2a0a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe previous coding caused spurious errors when examining indexes created with \u003ccode\u003eCREATE INDEX CONCURRENTLY\u003c/code\u003e.\u003c/p\u003e","id":"18.2-bbfcc39776d1a2a4","identity_text":"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.","part":"changes","patch_ids":["1e97ec2b7912c8b7c0ec7e7abd017428","a29fe4baf41fba16dd4afb02acc16023"],"relations":[{"evidence":{"patch_ids":["1e97ec2b7912c8b7c0ec7e7abd017428","a29fe4baf41fba16dd4afb02acc16023"],"same_day":true,"statement_hash":"087497339e462790a79c92291f5c2d4d3a17e08435df6c64e32dc876bc1de14d"},"rule":2,"target":"493a72cf1959504f8641847b78bd08a1","type":"equivalent"},{"evidence":{"patch_ids":["1e97ec2b7912c8b7c0ec7e7abd017428","a29fe4baf41fba16dd4afb02acc16023"],"same_day":true,"statement_hash":"087497339e462790a79c92291f5c2d4d3a17e08435df6c64e32dc876bc1de14d"},"rule":2,"target":"8bafe8c0e161e1a9a94a09493833d987","type":"equivalent"},{"evidence":{"patch_ids":["1e97ec2b7912c8b7c0ec7e7abd017428","a29fe4baf41fba16dd4afb02acc16023"],"same_day":true,"statement_hash":"087497339e462790a79c92291f5c2d4d3a17e08435df6c64e32dc876bc1de14d"},"rule":2,"target":"8c9e41f976444baa74aa90d4929a9857","type":"equivalent"},{"evidence":{"patch_ids":["1e97ec2b7912c8b7c0ec7e7abd017428","a29fe4baf41fba16dd4afb02acc16023"],"same_day":true,"statement_hash":"087497339e462790a79c92291f5c2d4d3a17e08435df6c64e32dc876bc1de14d"},"rule":2,"target":"d68c80f0e4be35945733a8602d932285","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["3c83a2a0a","df93f94dd"],"source_entry_id":"18.2/changes/068","source_hash":"9326fd49078399bcb649954f0bd02440c060b83b9344d667e3d08342bb8c7469","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"087497339e462790a79c92291f5c2d4d3a17e08435df6c64e32dc876bc1de14d","text":"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.","title":"In contrib/amcheck, use the correct snapshot for btree index parent checks"},"id":"18.2-bbfcc39776d1a2a4","matches":[{"id":"17.8-ab740b8bd4036a5f","source_entry_id":"17.8/changes/047","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"In contrib/amcheck, use the correct snapshot for btree index parent checks","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/068","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"In contrib/amcheck, use the correct snapshot for btree index parent checks","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["182901626","19e786727","7792bdc45","cbe04e5d7","e8ae59445","fbb4b6078"],"commit_groups":[["182901626","19e786727","7792bdc45","cbe04e5d7","e8ae59445","fbb4b6078"]],"commits":["19e786727"],"cves":[],"db_id":"cd3fba00555984ba827b4d51519989d9","html":"\u003cp\u003eFix \u003ccode\u003econtrib/amcheck\u003c/code\u003e to handle \u003cspan\u003e“\u003cspan\u003ehalf-dead\u003c/span\u003e”\u003c/span\u003e btree index pages correctly (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/19e786727\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eamcheck\u003c/code\u003e expected such a page to have a parent downlink, but it does not, leading to a false error report about \u003cspan\u003e“\u003cspan\u003emismatch between parent key and child high key\u003c/span\u003e”\u003c/span\u003e.\u003c/p\u003e","id":"18.2-cb9b48895e2b846c","identity_text":"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.","part":"changes","patch_ids":["f7e8ed321d6ed6ededda523198e8e879"],"relations":[{"evidence":{"patch_ids":["f7e8ed321d6ed6ededda523198e8e879"],"same_day":true,"statement_hash":"235569affe45bc821b8a939af4bf327951ad127f8ac6150fb4810ff7876efdc5"},"rule":2,"target":"7d94ee89b853fd7d6f3bb697328e1fed","type":"equivalent"},{"evidence":{"patch_ids":["f7e8ed321d6ed6ededda523198e8e879"],"same_day":true,"statement_hash":"235569affe45bc821b8a939af4bf327951ad127f8ac6150fb4810ff7876efdc5"},"rule":2,"target":"b0c422d1b24cdfdcd3828e41eecc8d38","type":"equivalent"},{"evidence":{"patch_ids":["f7e8ed321d6ed6ededda523198e8e879"],"same_day":true,"statement_hash":"235569affe45bc821b8a939af4bf327951ad127f8ac6150fb4810ff7876efdc5"},"rule":2,"target":"bb53eff1677e4a2b4b54e1dcbe8a077d","type":"equivalent"},{"evidence":{"patch_ids":["f7e8ed321d6ed6ededda523198e8e879"],"same_day":true,"statement_hash":"235569affe45bc821b8a939af4bf327951ad127f8ac6150fb4810ff7876efdc5"},"rule":2,"target":"c7f51c102edaf4e048fd2d187271f417","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["19e786727"],"source_entry_id":"18.2/changes/069","source_hash":"8fa96693fff98265a0eba650e2e0dafe814e655826a1332ee1b546918eac0d02","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"235569affe45bc821b8a939af4bf327951ad127f8ac6150fb4810ff7876efdc5","text":"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”.","title":"Fix contrib/amcheck to handle “half-dead” btree index pages correctly"},"id":"18.2-cb9b48895e2b846c","matches":[{"id":"17.8-9f60cb27b127637e","source_entry_id":"17.8/changes/048","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix contrib/amcheck to handle “half-dead” btree index pages correctly","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/069","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix contrib/amcheck to handle “half-dead” btree index pages correctly","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["50c63ebb0","5a2d1df00","6c05ef572","721b58fbe","a4cb21ea9","f2a6df9fd"],"commit_groups":[["50c63ebb0","5a2d1df00","6c05ef572","721b58fbe","a4cb21ea9","f2a6df9fd"]],"commits":["50c63ebb0"],"cves":[],"db_id":"8501633eefd4ba0be52ed6a8edf74102","html":"\u003cp\u003eFix \u003ccode\u003econtrib/amcheck\u003c/code\u003e to handle incomplete btree root page splits correctly (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/50c63ebb0\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eamcheck\u003c/code\u003e could report a false error about \u003cspan\u003e“\u003cspan\u003eblock is not true root\u003c/span\u003e”\u003c/span\u003e.\u003c/p\u003e","id":"18.2-9de86ea05d414299","identity_text":"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.","part":"changes","patch_ids":["bc0672786aac6981e442848cef632af7"],"relations":[{"evidence":{"patch_ids":["bc0672786aac6981e442848cef632af7"],"same_day":true,"statement_hash":"a09b91d29cb6145c6b4b8a47f79add91a36b52c7cd5b33ff456ebcbee2d174eb"},"rule":2,"target":"0961927e1e1f17e976e1fe45d36dd9ce","type":"equivalent"},{"evidence":{"patch_ids":["bc0672786aac6981e442848cef632af7"],"same_day":true,"statement_hash":"a09b91d29cb6145c6b4b8a47f79add91a36b52c7cd5b33ff456ebcbee2d174eb"},"rule":2,"target":"36d6b9b121e09182786381bf1019a5a6","type":"equivalent"},{"evidence":{"patch_ids":["bc0672786aac6981e442848cef632af7"],"same_day":true,"statement_hash":"a09b91d29cb6145c6b4b8a47f79add91a36b52c7cd5b33ff456ebcbee2d174eb"},"rule":2,"target":"67e3b43981f7755a637c3f6f8538cf81","type":"equivalent"},{"evidence":{"patch_ids":["bc0672786aac6981e442848cef632af7"],"same_day":true,"statement_hash":"a09b91d29cb6145c6b4b8a47f79add91a36b52c7cd5b33ff456ebcbee2d174eb"},"rule":2,"target":"c098597887b2f2c2a2d33ae0dfbe3669","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["50c63ebb0"],"source_entry_id":"18.2/changes/070","source_hash":"8b82126eb1d80a76e95cd0e4eb336c2056c96da83f69395171038e994fb18a1a","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"a09b91d29cb6145c6b4b8a47f79add91a36b52c7cd5b33ff456ebcbee2d174eb","text":"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”.","title":"Fix contrib/amcheck to handle incomplete btree root page splits correctly"},"id":"18.2-9de86ea05d414299","matches":[{"id":"17.8-5b1a363a1650f076","source_entry_id":"17.8/changes/049","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix contrib/amcheck to handle incomplete btree root page splits correctly","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/070","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix contrib/amcheck to handle incomplete btree root page splits correctly","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["07c1c6ec5","4f49e4b55","54f82c4aa","67a6fd507","a5f2dc421","c89510431"],"commit_groups":[["07c1c6ec5","4f49e4b55","54f82c4aa","67a6fd507","a5f2dc421","c89510431"]],"commits":["07c1c6ec5"],"cves":[],"db_id":"e129aabe6a0e432884befb054f303449","html":"\u003cp\u003eFix edge-case integer overflow in \u003ccode\u003econtrib/intarray\u003c/code\u003e's selectivity estimator for \u003ccode\u003e@@\u003c/code\u003e (Chao Li) \u003ca href=\"https://postgr.es/c/07c1c6ec5\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis could cause poor selectivity estimates to be produced for cases involving the maximum integer value.\u003c/p\u003e","id":"18.2-a45188e655691d38","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.","part":"changes","patch_ids":["6827108dafb7fb952c98263cf81bfb12"],"relations":[{"evidence":{"patch_ids":["6827108dafb7fb952c98263cf81bfb12"],"same_day":true,"statement_hash":"15b336d5589f6d629fe8bb0549cd193d78524753cdd06cfede921f7dce003daf"},"rule":2,"target":"1285579c66ecba8872eb8b17f3bc4e1b","type":"equivalent"},{"evidence":{"patch_ids":["6827108dafb7fb952c98263cf81bfb12"],"same_day":true,"statement_hash":"15b336d5589f6d629fe8bb0549cd193d78524753cdd06cfede921f7dce003daf"},"rule":2,"target":"59e2d3bf9637de09505f940988dcd182","type":"equivalent"},{"evidence":{"patch_ids":["6827108dafb7fb952c98263cf81bfb12"],"same_day":true,"statement_hash":"15b336d5589f6d629fe8bb0549cd193d78524753cdd06cfede921f7dce003daf"},"rule":2,"target":"81dbabd3964ac7d16575fec8b0e775d4","type":"equivalent"},{"evidence":{"patch_ids":["6827108dafb7fb952c98263cf81bfb12"],"same_day":true,"statement_hash":"15b336d5589f6d629fe8bb0549cd193d78524753cdd06cfede921f7dce003daf"},"rule":2,"target":"8280d414e29b698e7a7b5bdab7d65a67","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["07c1c6ec5"],"source_entry_id":"18.2/changes/072","source_hash":"0406ef3ec261ae8dfc6ed54bf7e8d656476a289a09885f44526d65c22f1e2707","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"15b336d5589f6d629fe8bb0549cd193d78524753cdd06cfede921f7dce003daf","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 @@"},"id":"18.2-a45188e655691d38","matches":[{"id":"17.8-ab6fdf5f76b2dd4a","source_entry_id":"17.8/changes/050","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix edge-case integer overflow in contrib/intarray's selectivity estimator for @@","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/072","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix edge-case integer overflow in contrib/intarray's selectivity estimator for @@","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["335b2f30b","84d5efa7e","898991966","b80227c0a","b8cfe9dc2","f79e239e0"],"commit_groups":[["335b2f30b","84d5efa7e","898991966","b80227c0a","b8cfe9dc2","f79e239e0"]],"commits":["f79e239e0"],"cves":[],"db_id":"a7c924b73b0998bc9111869833cc9355","html":"\u003cp\u003eFix multibyte-encoding issue in \u003ccode\u003econtrib/ltree\u003c/code\u003e (Jeff Davis) \u003ca href=\"https://postgr.es/c/f79e239e0\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe previous coding could pass an incomplete multibyte character to \u003ccode\u003elower()\u003c/code\u003e, probably resulting in incorrect behavior.\u003c/p\u003e","id":"18.2-4b1b9fbd0223faf3","identity_text":"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.","part":"changes","patch_ids":["ce03709afde90a593822361bba7a645d"],"relations":[{"evidence":{"patch_ids":["ce03709afde90a593822361bba7a645d"],"same_day":true,"statement_hash":"df18b7dd23fc4a736b53dee8298de471bf4398537e381437dba5d40d41b4e8c8"},"rule":2,"target":"68d5a5585afcd2453c96b9409ff4eb3e","type":"equivalent"},{"evidence":{"patch_ids":["ce03709afde90a593822361bba7a645d"],"same_day":true,"statement_hash":"df18b7dd23fc4a736b53dee8298de471bf4398537e381437dba5d40d41b4e8c8"},"rule":2,"target":"81f250eccec05588f1ee61ab46a58eef","type":"equivalent"},{"evidence":{"patch_ids":["ce03709afde90a593822361bba7a645d"],"same_day":true,"statement_hash":"df18b7dd23fc4a736b53dee8298de471bf4398537e381437dba5d40d41b4e8c8"},"rule":2,"target":"d009a076d5863b0968962c0a478ad63c","type":"equivalent"},{"evidence":{"patch_ids":["ce03709afde90a593822361bba7a645d"],"same_day":true,"statement_hash":"df18b7dd23fc4a736b53dee8298de471bf4398537e381437dba5d40d41b4e8c8"},"rule":2,"target":"d10631fe1ac5049f82fdf79ee53d5075","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["f79e239e0"],"source_entry_id":"18.2/changes/073","source_hash":"1b3ea9b9fd7b0b74a653230b73b439d93c2fb66c05c85a60e3b6e6a64caa34f2","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"df18b7dd23fc4a736b53dee8298de471bf4398537e381437dba5d40d41b4e8c8","text":"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.","title":"Fix multibyte-encoding issue in contrib/ltree"},"id":"18.2-4b1b9fbd0223faf3","matches":[{"id":"17.8-cb9f9359b4259ec9","source_entry_id":"17.8/changes/051","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Fix multibyte-encoding issue in contrib/ltree","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/073","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Fix multibyte-encoding issue in contrib/ltree","version":"18.2"},{"entry":{"category":"improvement","commit_aliases":["00410b76d","228fe0c3e","6574bee64","8bbf28191","d852d105e","f87c0b84e"],"commit_groups":[["00410b76d","228fe0c3e","6574bee64","8bbf28191","d852d105e","f87c0b84e"]],"commits":["6574bee64"],"cves":[],"db_id":"1e212940a15748de8b9d8f9f8a00221c","html":"\u003cp\u003eUpdate time zone data files to \u003cspan\u003etzdata\u003c/span\u003e release 2025c (Tom Lane) \u003ca href=\"https://postgr.es/c/6574bee64\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe only change is in historical data for pre-1976 timestamps in Baja California.\u003c/p\u003e","id":"18.2-4cbf16ee6dc57970","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.","part":"changes","patch_ids":["248cd6c3eee33cd4c82f09ee1d6af621"],"relations":[{"evidence":{"patch_ids":["248cd6c3eee33cd4c82f09ee1d6af621"],"same_day":true,"statement_hash":"da0a28a77bd7a205873150e5d6559af4853f986168d43f9537c2dbe1b0158a5b"},"rule":2,"target":"6a2a6f129d457a35195c94f742bac1c7","type":"equivalent"},{"evidence":{"patch_ids":["248cd6c3eee33cd4c82f09ee1d6af621"],"same_day":true,"statement_hash":"da0a28a77bd7a205873150e5d6559af4853f986168d43f9537c2dbe1b0158a5b"},"rule":2,"target":"8fe4829a60aad3b491b6cf8cc56b6b67","type":"equivalent"},{"evidence":{"patch_ids":["248cd6c3eee33cd4c82f09ee1d6af621"],"same_day":true,"statement_hash":"da0a28a77bd7a205873150e5d6559af4853f986168d43f9537c2dbe1b0158a5b"},"rule":2,"target":"af6fece6fb7485ca9609d00ddf419b69","type":"equivalent"},{"evidence":{"patch_ids":["248cd6c3eee33cd4c82f09ee1d6af621"],"same_day":true,"statement_hash":"da0a28a77bd7a205873150e5d6559af4853f986168d43f9537c2dbe1b0158a5b"},"rule":2,"target":"e11e7a4857357ba2a4255391b7eb4033","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["6574bee64"],"source_entry_id":"18.2/changes/075","source_hash":"bb2f3728e4b9f6f7fccf237ab4892ab16d5f39075e844a735198a307cb87d00a","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"da0a28a77bd7a205873150e5d6559af4853f986168d43f9537c2dbe1b0158a5b","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"},"id":"18.2-4cbf16ee6dc57970","matches":[{"id":"17.8-6f023224ced53b65","source_entry_id":"17.8/changes/052","source_url":"/docs/release/17.8/#RELEASE-17-8-CHANGES","title":"Update time zone data files to tzdata release 2025c","version":"17.8"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.2/changes/075","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","title":"Update time zone data files to tzdata release 2025c","version":"18.2"},{"entry":{"category":"bugfix","commit_aliases":["23064542f","4a36c89f1","547a8aaa7","817f74600","899de38d8"],"commit_groups":[["23064542f","4a36c89f1","547a8aaa7","817f74600","899de38d8"]],"commits":["817f74600"],"cves":[],"db_id":"6d7df9238b789e2555fe1290d455a61a","html":"\u003cp\u003eFix failure after replaying a multixid truncation record from WAL that was generated by an older minor version (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/817f74600\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eErroneous logic for coping with the way that previous versions handled multixid wraparound led to replay failure, with messages like \u003cspan\u003e“\u003cspan\u003ecould not access status of transaction\u003c/span\u003e”\u003c/span\u003e. 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.\u003c/p\u003e","id":"18.3-ad611cd1e209983f","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.","part":"changes","patch_ids":["e8c592597fe0c522a838714ea94d192e"],"relations":[{"evidence":{"patch_ids":["e8c592597fe0c522a838714ea94d192e"],"same_day":true,"statement_hash":"cf611d327c6efbb05b8c3c3eec25baadc4b81f3015eda12031c5dfd70647d75d"},"rule":2,"target":"269e20cac41b248d80f469e35fb3be04","type":"equivalent"},{"evidence":{"patch_ids":["e8c592597fe0c522a838714ea94d192e"],"same_day":true,"statement_hash":"cf611d327c6efbb05b8c3c3eec25baadc4b81f3015eda12031c5dfd70647d75d"},"rule":2,"target":"54acee06ad9ee6f00cba048e48dfdadc","type":"equivalent"},{"evidence":{"patch_ids":["e8c592597fe0c522a838714ea94d192e"],"same_day":true,"statement_hash":"cf611d327c6efbb05b8c3c3eec25baadc4b81f3015eda12031c5dfd70647d75d"},"rule":2,"target":"ac9d069b97f39c99f4c9540523c6dd01","type":"equivalent"},{"evidence":{"patch_ids":["e8c592597fe0c522a838714ea94d192e"],"same_day":true,"statement_hash":"cf611d327c6efbb05b8c3c3eec25baadc4b81f3015eda12031c5dfd70647d75d"},"rule":2,"target":"bb4c9dfad3173d99906963ab569e5990","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["817f74600"],"source_entry_id":"18.3/changes/001","source_hash":"103f7a064258041866386b1c934b5dc1e6ae4ca6f921231e67b0cb23889c5b2d","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","statement_hash":"cf611d327c6efbb05b8c3c3eec25baadc4b81f3015eda12031c5dfd70647d75d","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"},"id":"18.3-ad611cd1e209983f","matches":[{"id":"17.9-80ecbcad5117683e","source_entry_id":"17.9/changes/001","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","version":"17.9"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.3/changes/001","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","version":"18.3"},{"entry":{"category":"security","commit_aliases":["14b1fd617","2280ab354","4174e41b9","44fc85bbf","45eb47230","4644f8b23","50d361f62","5b305ebcc","5d5232bc3","6e045e1a6","8cef93d8a","8e73530f1","9f4fd119b","a0769e74d","a20eb248c","bdfb37228","d04b34d68","ec86152e0"],"commit_groups":[["14b1fd617","5d5232bc3","6e045e1a6","9f4fd119b","a20eb248c","bdfb37228"],["2280ab354","50d361f62","8cef93d8a","a0769e74d","d04b34d68","ec86152e0"],["4174e41b9","44fc85bbf","45eb47230","4644f8b23","5b305ebcc","8e73530f1"]],"commits":["4174e41b9","6e045e1a6","d04b34d68"],"cves":["CVE-2026-2006"],"db_id":"9b63cad6030353d772f1330dfd687e9f","html":"\u003cp\u003eAvoid incorrect complaint of invalid encoding when \u003ccode\u003esubstring()\u003c/code\u003e is applied to \u003cspan\u003e“\u003cspan\u003etoasted\u003c/span\u003e”\u003c/span\u003e data (Noah Misch) \u003ca href=\"https://postgr.es/c/6e045e1a6\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/d04b34d68\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/4174e41b9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe fix for CVE-2026-2006 was too aggressive and could raise an error about an incomplete character in cases that are actually valid.\u003c/p\u003e","id":"18.3-77113f5b52409590","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.","part":"changes","patch_ids":["924bc2a7b62c922890c6948fec9b1504","b621552d0483c3fe9118c60e77f297ab","fe6380c6909ab3efff6be8983b7f18a1"],"relations":[{"evidence":{"patch_ids":["924bc2a7b62c922890c6948fec9b1504","b621552d0483c3fe9118c60e77f297ab","fe6380c6909ab3efff6be8983b7f18a1"],"same_day":true,"statement_hash":"b34aae4222592f29a7ecee54df249e73bebb9346d81b2e5c859347ba8c1ea747"},"rule":2,"target":"2913b28e99dd666bc31951814a799735","type":"equivalent"},{"evidence":{"patch_ids":["924bc2a7b62c922890c6948fec9b1504","b621552d0483c3fe9118c60e77f297ab","fe6380c6909ab3efff6be8983b7f18a1"],"same_day":true,"statement_hash":"b34aae4222592f29a7ecee54df249e73bebb9346d81b2e5c859347ba8c1ea747"},"rule":2,"target":"91516991913d971894a1428891e4772e","type":"equivalent"},{"evidence":{"patch_ids":["924bc2a7b62c922890c6948fec9b1504","b621552d0483c3fe9118c60e77f297ab","fe6380c6909ab3efff6be8983b7f18a1"],"same_day":true,"statement_hash":"b34aae4222592f29a7ecee54df249e73bebb9346d81b2e5c859347ba8c1ea747"},"rule":2,"target":"da9fc04e8b825c72955bd70be9fd53ee","type":"equivalent"},{"evidence":{"patch_ids":["924bc2a7b62c922890c6948fec9b1504","b621552d0483c3fe9118c60e77f297ab","fe6380c6909ab3efff6be8983b7f18a1"],"same_day":true,"statement_hash":"b34aae4222592f29a7ecee54df249e73bebb9346d81b2e5c859347ba8c1ea747"},"rule":2,"target":"fe28a154c085da9085a635db8d9d4460","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["4174e41b9","6e045e1a6","d04b34d68"],"source_entry_id":"18.3/changes/002","source_hash":"385042f170395ab48ac62db0063a8cbfa5ec36f5acc462be6ce28d90a0d3e02c","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","statement_hash":"b34aae4222592f29a7ecee54df249e73bebb9346d81b2e5c859347ba8c1ea747","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"},"id":"18.3-77113f5b52409590","matches":[{"id":"17.9-24d7e69f6ec0ae9a","source_entry_id":"17.9/changes/002","source_url":"/docs/release/17.9/#RELEASE-17-9-CHANGES","title":"Avoid incorrect complaint of invalid encoding when substring() is applied to “toasted” data","version":"17.9"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.3/changes/002","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","title":"Avoid incorrect complaint of invalid encoding when substring() is applied to “toasted” data","version":"18.3"},{"entry":{"category":"bugfix","commit_aliases":["691977d37","bcaf1b510","ec20a4552","ed57c207c"],"commit_groups":[["691977d37","bcaf1b510","ec20a4552","ed57c207c"]],"commits":["ed57c207c"],"cves":[],"db_id":"18fdbd910c49cc504248c6225d989414","html":"\u003cp\u003eFix computation of the set of potentially-nulling outer joins for the output of a \u003ccode\u003eLATERAL UNION ALL\u003c/code\u003e subquery (Richard Guo) \u003ca href=\"https://postgr.es/c/ed57c207c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis error could lead to skipping \u003ccode\u003eNOT NULL\u003c/code\u003e tests in the mistaken belief that they were unnecessary, resulting in wrong query output.\u003c/p\u003e","id":"18.3-cd0444df0515373f","identity_text":"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.","part":"changes","patch_ids":["39b9ce1d361dcaf187c274f11f3f2877"],"relations":[{"evidence":{"patch_ids":["39b9ce1d361dcaf187c274f11f3f2877"],"same_day":true,"statement_hash":"ba69358a1b83d31e612c77f1471616df5093300bce97f33f1049bcfb8058f683"},"rule":2,"target":"b67986c165e36a1a03e1f26aa1714455","type":"equivalent"},{"evidence":{"patch_ids":["39b9ce1d361dcaf187c274f11f3f2877"],"same_day":true,"statement_hash":"ba69358a1b83d31e612c77f1471616df5093300bce97f33f1049bcfb8058f683"},"rule":2,"target":"b8d8d19411ef9eb6905835bde4b0a556","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["ed57c207c"],"source_entry_id":"18.3/changes/005","source_hash":"302cb4fe2adf6432d8f08ed99bb29e82b7882f2d697a8f894356bbe18a9632f6","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","statement_hash":"ba69358a1b83d31e612c77f1471616df5093300bce97f33f1049bcfb8058f683","text":"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.","title":"Fix computation of the set of potentially-nulling outer joins for the output of a LATERAL UNION ALL subquery"},"id":"18.3-cd0444df0515373f","matches":[{"id":"17.9-1441e21296f1914d","source_entry_id":"17.9/changes/003","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","version":"17.9"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.3/changes/005","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","version":"18.3"},{"entry":{"category":"bugfix","commit_aliases":["2332911ae","53463b4b2","78a5e3074","82b495cdd","842473337","ebc53ca7b"],"commit_groups":[["2332911ae","53463b4b2","78a5e3074","82b495cdd","842473337","ebc53ca7b"]],"commits":["53463b4b2"],"cves":[],"db_id":"51c535e1e5383ba40f60f95b951f7542","html":"\u003cp\u003eFix \u003ccode\u003epg_stat_get_backend_wait_event()\u003c/code\u003e and \u003ccode\u003epg_stat_get_backend_wait_event_type()\u003c/code\u003e to report values for auxiliary processes (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/53463b4b2\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously these functions returned NULL for auxiliary processes, but that's inconsistent with the \u003ccode\u003epg_stat_activity\u003c/code\u003e view.\u003c/p\u003e","id":"18.3-a63ceb8e607a4b1d","identity_text":"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.","part":"changes","patch_ids":["54586dcff5ba8f38c9bad3069e4ffc52"],"relations":[{"evidence":{"patch_ids":["54586dcff5ba8f38c9bad3069e4ffc52"],"same_day":true,"statement_hash":"f5b50524b8ec05ef6a3e7bcc10dc01af6ebe577734eff3be2cb39b4262840b90"},"rule":2,"target":"0fa32f0f7fbb9d8c7a7a1cfeaa993230","type":"equivalent"},{"evidence":{"patch_ids":["54586dcff5ba8f38c9bad3069e4ffc52"],"same_day":true,"statement_hash":"f5b50524b8ec05ef6a3e7bcc10dc01af6ebe577734eff3be2cb39b4262840b90"},"rule":2,"target":"b1227a7b977e0fdde28e2260fd4055ca","type":"equivalent"},{"evidence":{"patch_ids":["54586dcff5ba8f38c9bad3069e4ffc52"],"same_day":true,"statement_hash":"f5b50524b8ec05ef6a3e7bcc10dc01af6ebe577734eff3be2cb39b4262840b90"},"rule":2,"target":"ca6d569bfd12f83cd8b663f7b1b14c38","type":"equivalent"},{"evidence":{"patch_ids":["54586dcff5ba8f38c9bad3069e4ffc52"],"same_day":true,"statement_hash":"f5b50524b8ec05ef6a3e7bcc10dc01af6ebe577734eff3be2cb39b4262840b90"},"rule":2,"target":"d389f553498aab12a33e8658e42c2ebd","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["53463b4b2"],"source_entry_id":"18.3/changes/007","source_hash":"91a5c560e1bbd5f686e75fe66a5b3021d7fc701042d51efc04e223bf814b2b9a","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","statement_hash":"f5b50524b8ec05ef6a3e7bcc10dc01af6ebe577734eff3be2cb39b4262840b90","text":"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.","title":"Fix pg_stat_get_backend_wait_event() and pg_stat_get_backend_wait_event_type() to report values for auxiliary processes"},"id":"18.3-a63ceb8e607a4b1d","matches":[{"id":"17.9-49611ef76ca99838","source_entry_id":"17.9/changes/004","source_url":"/docs/release/17.9/#RELEASE-17-9-CHANGES","title":"Fix pg_stat_get_backend_wait_event() and pg_stat_get_backend_wait_event_type() to report values for auxiliary processes","version":"17.9"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.3/changes/007","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","title":"Fix pg_stat_get_backend_wait_event() and pg_stat_get_backend_wait_event_type() to report values for auxiliary processes","version":"18.3"},{"entry":{"category":"bugfix","commit_aliases":["254b15cbf","2b93d3820","9863c9075","c66f4cff1","ce4b7e3a1","dfd850980"],"commit_groups":[["254b15cbf","2b93d3820","9863c9075","c66f4cff1","ce4b7e3a1","dfd850980"]],"commits":["ce4b7e3a1"],"cves":[],"db_id":"d7289871637eb477a52d704b8b129dee","html":"\u003cp\u003eFix casting a composite-type variable to a domain type when returning its value from a PL/pgSQL function (Tom Lane) \u003ca href=\"https://postgr.es/c/ce4b7e3a1\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf the variable's value is NULL, a \u003cspan\u003e“\u003cspan\u003ecache lookup failed for type 0\u003c/span\u003e”\u003c/span\u003e error resulted.\u003c/p\u003e","id":"18.3-68534f113dfbb27d","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.","part":"changes","patch_ids":["4682bfcc99694f6b7bf7c07af3082c2e"],"relations":[{"evidence":{"patch_ids":["4682bfcc99694f6b7bf7c07af3082c2e"],"same_day":true,"statement_hash":"257a19cad310234769985e6594cf9f32698b7849a63b72427ee23e58e321e7d5"},"rule":2,"target":"08e9766e078b0f98d664963d7351568a","type":"equivalent"},{"evidence":{"patch_ids":["4682bfcc99694f6b7bf7c07af3082c2e"],"same_day":true,"statement_hash":"257a19cad310234769985e6594cf9f32698b7849a63b72427ee23e58e321e7d5"},"rule":2,"target":"1f6375c5be0406ebaeab1ddd1281f48a","type":"equivalent"},{"evidence":{"patch_ids":["4682bfcc99694f6b7bf7c07af3082c2e"],"same_day":true,"statement_hash":"257a19cad310234769985e6594cf9f32698b7849a63b72427ee23e58e321e7d5"},"rule":2,"target":"509c9d18c03750ab5a1af4533e9e3f71","type":"equivalent"},{"evidence":{"patch_ids":["4682bfcc99694f6b7bf7c07af3082c2e"],"same_day":true,"statement_hash":"257a19cad310234769985e6594cf9f32698b7849a63b72427ee23e58e321e7d5"},"rule":2,"target":"b3e55b2d8440115c6283ddb4434aed5d","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["ce4b7e3a1"],"source_entry_id":"18.3/changes/008","source_hash":"fbea03cca43c2b95870d7024da9123755c4689d0eebbc20fd8aab766b4475f49","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","statement_hash":"257a19cad310234769985e6594cf9f32698b7849a63b72427ee23e58e321e7d5","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"},"id":"18.3-68534f113dfbb27d","matches":[{"id":"17.9-00f1ed550848c3b5","source_entry_id":"17.9/changes/005","source_url":"/docs/release/17.9/#RELEASE-17-9-CHANGES","title":"Fix casting a composite-type variable to a domain type when returning its value from a PL/pgSQL function","version":"17.9"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.3/changes/008","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","title":"Fix casting a composite-type variable to a domain type when returning its value from a PL/pgSQL function","version":"18.3"},{"entry":{"category":"bugfix","commit_aliases":["0dfbe42da","31d0b917d","4a0843c53","63c05e03b","a6f823e77","f604cc695"],"commit_groups":[["0dfbe42da","31d0b917d","4a0843c53","63c05e03b","a6f823e77","f604cc695"]],"commits":["4a0843c53"],"cves":[],"db_id":"302f35b8c992f59981d9c8bbcbf80b74","html":"\u003cp\u003eFix potential null pointer dereference in \u003ccode\u003econtrib/hstore\u003c/code\u003e's binary input function (Michael Paquier) \u003ca href=\"https://postgr.es/c/4a0843c53\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003ehstore\u003c/code\u003e's receive function crashed on input containing duplicate keys. \u003ccode\u003ehstore\u003c/code\u003e 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.\u003c/p\u003e","id":"18.3-72cba4c8d34e077e","identity_text":"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.","part":"changes","patch_ids":["05e85f727ef4e88378a37028157d43b6"],"relations":[{"evidence":{"patch_ids":["05e85f727ef4e88378a37028157d43b6"],"same_day":true,"statement_hash":"d3475d54feed07f63eac9d89bc0052bdf62514368b9675dd5fa3bbf2749ab52d"},"rule":2,"target":"333c171c538037b7ded4bd4a610b1799","type":"equivalent"},{"evidence":{"patch_ids":["05e85f727ef4e88378a37028157d43b6"],"same_day":true,"statement_hash":"d3475d54feed07f63eac9d89bc0052bdf62514368b9675dd5fa3bbf2749ab52d"},"rule":2,"target":"3a65408ffac19ce6c90d333d8d5318cf","type":"equivalent"},{"evidence":{"patch_ids":["05e85f727ef4e88378a37028157d43b6"],"same_day":true,"statement_hash":"d3475d54feed07f63eac9d89bc0052bdf62514368b9675dd5fa3bbf2749ab52d"},"rule":2,"target":"6c2d1768700fe19270f371e13fa79343","type":"equivalent"},{"evidence":{"patch_ids":["05e85f727ef4e88378a37028157d43b6"],"same_day":true,"statement_hash":"d3475d54feed07f63eac9d89bc0052bdf62514368b9675dd5fa3bbf2749ab52d"},"rule":2,"target":"88acf3ddcff5993038ed18e0a7157844","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["4a0843c53"],"source_entry_id":"18.3/changes/009","source_hash":"20214df866b099d0ab12c5b30e2b32054f6cf39fae39bed47e62534149a7a8af","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","statement_hash":"d3475d54feed07f63eac9d89bc0052bdf62514368b9675dd5fa3bbf2749ab52d","text":"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.","title":"Fix potential null pointer dereference in contrib/hstore's binary input function"},"id":"18.3-72cba4c8d34e077e","matches":[{"id":"17.9-09236fba7643dbb2","source_entry_id":"17.9/changes/006","source_url":"/docs/release/17.9/#RELEASE-17-9-CHANGES","title":"Fix potential null pointer dereference in contrib/hstore's binary input function","version":"17.9"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.3/changes/009","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","title":"Fix potential null pointer dereference in contrib/hstore's binary input function","version":"18.3"},{"entry":{"category":"security","commit_aliases":["14a4a7040","16fda4df6","32a4ce55c","3b4e66739","3fb66d302","66cf26b9e","6dffaeb8e","b63f25bdd","c2e6ef863","f7a191f53"],"commit_groups":[["14a4a7040","16fda4df6","6dffaeb8e","c2e6ef863"],["32a4ce55c","3b4e66739","3fb66d302","66cf26b9e","b63f25bdd","f7a191f53"]],"commits":["f7a191f53"],"cves":["CVE-2026-6479"],"db_id":"1ca6ff4a849ed2960fad43a403e2b932","html":"\u003cp\u003ePrevent unbounded recursion while processing startup packets (Michael Paquier) \u003ca href=\"https://postgr.es/c/f7a191f53\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA malicious client could crash the connected backend by alternating rejected SSL and GSS encryption requests indefinitely.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Calif.io (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-6479)\u003c/p\u003e","id":"18.4-63ab78ae660e7424","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)","part":"changes","patch_ids":["4309351724f2df44d6eb12d700f03a90","fce882e6fdda4deccb44245cc5966b20"],"relations":[{"evidence":{"patch_ids":["4309351724f2df44d6eb12d700f03a90","fce882e6fdda4deccb44245cc5966b20"],"same_day":true,"statement_hash":"879026f1f07a4d172337b9e457cc300e4ed2d558396bcc627770e4ef108f69d4"},"rule":2,"target":"3d1e0d9f6f6214fb84bb4b9d4f9402aa","type":"equivalent"},{"evidence":{"patch_ids":["4309351724f2df44d6eb12d700f03a90","fce882e6fdda4deccb44245cc5966b20"],"same_day":true,"statement_hash":"879026f1f07a4d172337b9e457cc300e4ed2d558396bcc627770e4ef108f69d4"},"rule":2,"target":"473b135d9b59dfa88e1611d1141570ee","type":"equivalent"},{"evidence":{"patch_ids":["4309351724f2df44d6eb12d700f03a90","fce882e6fdda4deccb44245cc5966b20"],"same_day":true,"statement_hash":"879026f1f07a4d172337b9e457cc300e4ed2d558396bcc627770e4ef108f69d4"},"rule":2,"target":"91cb80c58929d3256c8543b647d98328","type":"equivalent"},{"evidence":{"patch_ids":["4309351724f2df44d6eb12d700f03a90","fce882e6fdda4deccb44245cc5966b20"],"same_day":true,"statement_hash":"879026f1f07a4d172337b9e457cc300e4ed2d558396bcc627770e4ef108f69d4"},"rule":2,"target":"e49a23129f6590195a74fcbcc51115f9","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["6dffaeb8e","f7a191f53"],"source_entry_id":"18.4/changes/001","source_hash":"8eaf08bcf7fecada977588ace5d26a12bbe548a1f16e4ee3c3ef360450230814","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"879026f1f07a4d172337b9e457cc300e4ed2d558396bcc627770e4ef108f69d4","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"},"id":"18.4-63ab78ae660e7424","matches":[{"id":"17.10-11e46f0b0085f2d6","source_entry_id":"17.10/changes/001","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Prevent unbounded recursion while processing startup packets","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/001","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Prevent unbounded recursion while processing startup packets","version":"18.4"},{"entry":{"category":"security","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"],"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"]],"commits":["01e568b8c","3fbec9e50","55328e3a9","67dd6243d","8d1489d50","c7fb9f765","dd8af778d","e1c30458a","f3cee4dc4"],"cves":["CVE-2026-6473"],"db_id":"acba67a334312f97f378ad9d28899a71","html":"\u003cp\u003eFix assorted integer overflows in memory-allocation calculations (Tom Lane, Nathan Bossart, Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/e1c30458a\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/01e568b8c\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/f3cee4dc4\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/dd8af778d\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/55328e3a9\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/67dd6243d\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/8d1489d50\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/c7fb9f765\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/3fbec9e50\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eVarious 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Xint Code, Bruce Dang, Sven Klemm, and Pavel Kohout for reporting these problems. (CVE-2026-6473)\u003c/p\u003e","id":"18.4-0ecf0348f34312bf","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)","part":"changes","patch_ids":["0ef31353c016842f07a477e36bffc11a","18b75605d90ace7a2cf8047352074614","522ba1e579ed17edbf8f9a554cef9734","5ee943f19c8b14a26d6f6e850b4c2e4a","67e33d81b6d11e90e4032802100b1f9a","722cd5796fd759e519e27c59ed0f5bc7","8b4c7be6720ec411561a3216285eb5c2","9be6f17ccc7861ac218a3159257353f5","9c6a62a34c14fe610b5925191c0d43bf","ac6798245b6fb47cbaf616c47755bec8"],"relations":[{"evidence":{"patch_ids":["0ef31353c016842f07a477e36bffc11a","18b75605d90ace7a2cf8047352074614","522ba1e579ed17edbf8f9a554cef9734","5ee943f19c8b14a26d6f6e850b4c2e4a","67e33d81b6d11e90e4032802100b1f9a","722cd5796fd759e519e27c59ed0f5bc7","8b4c7be6720ec411561a3216285eb5c2","9be6f17ccc7861ac218a3159257353f5","9c6a62a34c14fe610b5925191c0d43bf","ac6798245b6fb47cbaf616c47755bec8"],"same_day":true,"statement_hash":"e134dbaa858fe12a3a5fc6391ac874300d57d4269c0f25b416434cdc943690d8"},"rule":2,"target":"2566881ea25d8a61c2245b4b04c49f1a","type":"equivalent"},{"evidence":{"patch_ids":["0ef31353c016842f07a477e36bffc11a","18b75605d90ace7a2cf8047352074614","522ba1e579ed17edbf8f9a554cef9734","5ee943f19c8b14a26d6f6e850b4c2e4a","67e33d81b6d11e90e4032802100b1f9a","722cd5796fd759e519e27c59ed0f5bc7","8b4c7be6720ec411561a3216285eb5c2","9be6f17ccc7861ac218a3159257353f5","9c6a62a34c14fe610b5925191c0d43bf","ac6798245b6fb47cbaf616c47755bec8"],"same_day":true,"statement_hash":"e134dbaa858fe12a3a5fc6391ac874300d57d4269c0f25b416434cdc943690d8"},"rule":2,"target":"295b1d4dab2d6e770a4f53cf19a7aaa0","type":"equivalent"},{"evidence":{"patch_ids":["0ef31353c016842f07a477e36bffc11a","18b75605d90ace7a2cf8047352074614","522ba1e579ed17edbf8f9a554cef9734","5ee943f19c8b14a26d6f6e850b4c2e4a","67e33d81b6d11e90e4032802100b1f9a","722cd5796fd759e519e27c59ed0f5bc7","8b4c7be6720ec411561a3216285eb5c2","9be6f17ccc7861ac218a3159257353f5","9c6a62a34c14fe610b5925191c0d43bf","ac6798245b6fb47cbaf616c47755bec8"],"same_day":true,"statement_hash":"e134dbaa858fe12a3a5fc6391ac874300d57d4269c0f25b416434cdc943690d8"},"rule":2,"target":"8efe22f93b8d48d1a299e86b11c402e5","type":"equivalent"},{"evidence":{"patch_ids":["0ef31353c016842f07a477e36bffc11a","18b75605d90ace7a2cf8047352074614","522ba1e579ed17edbf8f9a554cef9734","5ee943f19c8b14a26d6f6e850b4c2e4a","67e33d81b6d11e90e4032802100b1f9a","722cd5796fd759e519e27c59ed0f5bc7","8b4c7be6720ec411561a3216285eb5c2","9be6f17ccc7861ac218a3159257353f5","9c6a62a34c14fe610b5925191c0d43bf","ac6798245b6fb47cbaf616c47755bec8"],"same_day":true,"statement_hash":"e134dbaa858fe12a3a5fc6391ac874300d57d4269c0f25b416434cdc943690d8"},"rule":2,"target":"f0345a5abb8aa96f05fce3fbd32e6535","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["01e568b8c","3fbec9e50","55328e3a9","67dd6243d","8d1489d50","c7fb9f765","dd8af778d","e1c30458a","e5babf754","f3cee4dc4"],"source_entry_id":"18.4/changes/002","source_hash":"d24e4f43bca1a58fcfd0d015d99c4bb296a743a14acfd85222c166d23b42b54e","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"e134dbaa858fe12a3a5fc6391ac874300d57d4269c0f25b416434cdc943690d8","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"},"id":"18.4-0ecf0348f34312bf","matches":[{"id":"17.10-a0bf50b47f7c6ba2","source_entry_id":"17.10/changes/002","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix assorted integer overflows in memory-allocation calculations","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/002","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix assorted integer overflows in memory-allocation calculations","version":"18.4"},{"entry":{"category":"security","commit_aliases":["c2e44c370","d389415ff","d7de7fa84"],"commit_groups":[["c2e44c370","d389415ff","d7de7fa84"]],"commits":["c2e44c370"],"cves":["CVE-2026-6476"],"db_id":"eda2bad4600ad30b4d662076df8c2604","html":"\u003cp\u003eProperly quote subscription names in \u003cspan\u003epg_createsubscriber\u003c/span\u003e (Nathan Bossart) \u003ca href=\"https://postgr.es/c/c2e44c370\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Yu Kunpeng for reporting this problem. (CVE-2026-6476)\u003c/p\u003e","id":"18.4-5bdcbd2e82271018","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)","part":"changes","patch_ids":["e720680b86f42b77dffa98182668476a"],"relations":[{"evidence":{"patch_ids":["e720680b86f42b77dffa98182668476a"],"same_day":true,"statement_hash":"ab8d616fe93986f065230107e451ba6882c134da9ddc1a51188a772cce10dc27"},"rule":2,"target":"c1016302d421112d19c9bbb963270941","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c2e44c370"],"source_entry_id":"18.4/changes/003","source_hash":"17f99eabd06cf32577fabbdc981f5e198df7045ca49ae684e192861912efaed4","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"ab8d616fe93986f065230107e451ba6882c134da9ddc1a51188a772cce10dc27","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"},"id":"18.4-5bdcbd2e82271018","matches":[{"id":"17.10-927543ba721f9720","source_entry_id":"17.10/changes/003","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Properly quote subscription names in pg_createsubscriber","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/003","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Properly quote subscription names in pg_createsubscriber","version":"18.4"},{"entry":{"category":"security","commit_aliases":["248a433cd","46b4f5c11","cb35d7306","f0f59b658"],"commit_groups":[["248a433cd","46b4f5c11","cb35d7306","f0f59b658"]],"commits":["cb35d7306"],"cves":["CVE-2026-6638"],"db_id":"160fa6992f90d49b5edf0769aa32c248","html":"\u003cp\u003eProperly quote object names in logical replication origin checks (Pavel Kohout) \u003ca href=\"https://postgr.es/c/cb35d7306\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eALTER SUBSCRIPTION ... REFRESH PUBLICATION\u003c/code\u003e interpolated schema and relation names into SQL commands without quoting them, allowing execution of arbitrary SQL on the publisher.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Pavel Kohout for reporting this problem. (CVE-2026-6638)\u003c/p\u003e","id":"18.4-a09de455386cd30a","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)","part":"changes","patch_ids":["a9b5d94f4021c4259f919029b9984225"],"relations":[{"evidence":{"patch_ids":["a9b5d94f4021c4259f919029b9984225"],"same_day":true,"statement_hash":"13a92db4a9747d0e4148764ace1c5b2427bc1582543dea88fe555dd3a4b24743"},"rule":2,"target":"6b9ad77c2d8c8cf7ed6c43c56746b015","type":"equivalent"},{"evidence":{"patch_ids":["a9b5d94f4021c4259f919029b9984225"],"same_day":true,"statement_hash":"13a92db4a9747d0e4148764ace1c5b2427bc1582543dea88fe555dd3a4b24743"},"rule":2,"target":"f75aecc1c0c865955094a916f7c78463","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["cb35d7306"],"source_entry_id":"18.4/changes/004","source_hash":"c82b2de372a07bda2f6f26acdea7a434159414051129759fc5db1e843d3db9d1","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"13a92db4a9747d0e4148764ace1c5b2427bc1582543dea88fe555dd3a4b24743","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"},"id":"18.4-a09de455386cd30a","matches":[{"id":"17.10-fdd0ba1867f4cdc1","source_entry_id":"17.10/changes/004","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Properly quote object names in logical replication origin checks","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/004","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Properly quote object names in logical replication origin checks","version":"18.4"},{"entry":{"category":"security","commit_aliases":["2d267ffc4","3ed3dbbf4","5919e0005","62ad26266","7fe365693","d388e1d7f"],"commit_groups":[["2d267ffc4","3ed3dbbf4","5919e0005","62ad26266","7fe365693","d388e1d7f"]],"commits":["62ad26266"],"cves":["CVE-2026-6473"],"db_id":"afe38bbdb09239daec9610fc4bf0002f","html":"\u003cp\u003eReject over-length options in \u003ccode\u003ets_headline()\u003c/code\u003e (Michael Paquier) \u003ca href=\"https://postgr.es/c/62ad26266\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003ccode\u003eStartSel\u003c/code\u003e, \u003ccode\u003eStopSel\u003c/code\u003e and \u003ccode\u003eFragmentDelimiter\u003c/code\u003e strings must not exceed 32Kb in length, but this was not checked for. An over-length value would typically crash the server.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Xint Code for reporting this problem. (CVE-2026-6473)\u003c/p\u003e","id":"18.4-2463210164fd4e42","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)","part":"changes","patch_ids":["8457c408eab825cef1442be8b008d331"],"relations":[{"evidence":{"patch_ids":["8457c408eab825cef1442be8b008d331"],"same_day":true,"statement_hash":"fa5b62f6b191298714caf3ad9670542a5ca5106f71c0bcc2d9d2de48ba2a0330"},"rule":2,"target":"0d396ecb6f57179d943c76706100debf","type":"equivalent"},{"evidence":{"patch_ids":["8457c408eab825cef1442be8b008d331"],"same_day":true,"statement_hash":"fa5b62f6b191298714caf3ad9670542a5ca5106f71c0bcc2d9d2de48ba2a0330"},"rule":2,"target":"4e96017be5ce2c6f1d23bf476a962747","type":"equivalent"},{"evidence":{"patch_ids":["8457c408eab825cef1442be8b008d331"],"same_day":true,"statement_hash":"fa5b62f6b191298714caf3ad9670542a5ca5106f71c0bcc2d9d2de48ba2a0330"},"rule":2,"target":"c2a972753505f1b0a01bf236c883ccad","type":"equivalent"},{"evidence":{"patch_ids":["8457c408eab825cef1442be8b008d331"],"same_day":true,"statement_hash":"fa5b62f6b191298714caf3ad9670542a5ca5106f71c0bcc2d9d2de48ba2a0330"},"rule":2,"target":"ca39bd1c4d36eb3d5c6808cd66068408","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["62ad26266"],"source_entry_id":"18.4/changes/005","source_hash":"b56e9415b151349836349dbc81e45dce003139337b9aa8a7181363531af7f086","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"fa5b62f6b191298714caf3ad9670542a5ca5106f71c0bcc2d9d2de48ba2a0330","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()"},"id":"18.4-2463210164fd4e42","matches":[{"id":"17.10-b66b265350df29d2","source_entry_id":"17.10/changes/005","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Reject over-length options in ts_headline()","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/005","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Reject over-length options in ts_headline()","version":"18.4"},{"entry":{"category":"security","commit_aliases":["126a236ba","24e0e3254","2c8226f52","4197c880c","76ab76f87","79b7847c7","a386d14fe","a50ae8306","ba27389c2","c3fff3950","c6e7a9ef3","ec8ded4b3"],"commit_groups":[["126a236ba","24e0e3254","4197c880c","76ab76f87","a50ae8306","ba27389c2"],["2c8226f52","79b7847c7","a386d14fe","c3fff3950","c6e7a9ef3","ec8ded4b3"]],"commits":["ba27389c2","c6e7a9ef3"],"cves":["CVE-2026-6474"],"db_id":"2a60ebdc5466fdb8ded5b7dd70ff560e","html":"\u003cp\u003eGuard against malicious time zone names in \u003ccode\u003etimeofday()\u003c/code\u003e and \u003ccode\u003epg_strftime()\u003c/code\u003e (Tom Lane) \u003ca href=\"https://postgr.es/c/ba27389c2\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/c6e7a9ef3\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA crafted time zone setting could pass \u003ccode\u003e%\u003c/code\u003e sequences to \u003ccode\u003esnprintf()\u003c/code\u003e, potentially causing crashes or disclosure of server memory. Another path to similar results was to overflow the limited-size output buffer used by \u003ccode\u003epg_strftime()\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Xint Code for reporting this problem. (CVE-2026-6474)\u003c/p\u003e","id":"18.4-3645e80ffc91fcb0","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)","part":"changes","patch_ids":["3f00e8116f67649860ad5a155650db89","b65bcdf6c5ef035597912c09e793606a"],"relations":[{"evidence":{"patch_ids":["3f00e8116f67649860ad5a155650db89","b65bcdf6c5ef035597912c09e793606a"],"same_day":true,"statement_hash":"28222af75396ae38d496fb3a6ca7635e107ba94454753d5b681b8db434552806"},"rule":2,"target":"4746c5c97c413c4b367427dcc53d74f9","type":"equivalent"},{"evidence":{"patch_ids":["3f00e8116f67649860ad5a155650db89","b65bcdf6c5ef035597912c09e793606a"],"same_day":true,"statement_hash":"28222af75396ae38d496fb3a6ca7635e107ba94454753d5b681b8db434552806"},"rule":2,"target":"943c74b8816c45111e8f6f3e4682a426","type":"equivalent"},{"evidence":{"patch_ids":["3f00e8116f67649860ad5a155650db89","b65bcdf6c5ef035597912c09e793606a"],"same_day":true,"statement_hash":"28222af75396ae38d496fb3a6ca7635e107ba94454753d5b681b8db434552806"},"rule":2,"target":"c35bb2a8a5d8d6153139912fa574f1be","type":"equivalent"},{"evidence":{"patch_ids":["3f00e8116f67649860ad5a155650db89","b65bcdf6c5ef035597912c09e793606a"],"same_day":true,"statement_hash":"28222af75396ae38d496fb3a6ca7635e107ba94454753d5b681b8db434552806"},"rule":2,"target":"f0c61a3ee0b896c91466e00b431d94ba","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["ba27389c2","c6e7a9ef3"],"source_entry_id":"18.4/changes/007","source_hash":"42e13a8c73d5ecbda4d68a436b303713cfb25440d6aff65d86f397133aaff833","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"28222af75396ae38d496fb3a6ca7635e107ba94454753d5b681b8db434552806","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()"},"id":"18.4-3645e80ffc91fcb0","matches":[{"id":"17.10-f68835d296474e15","source_entry_id":"17.10/changes/006","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Guard against malicious time zone names in timeofday() and pg_strftime()","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/007","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Guard against malicious time zone names in timeofday() and pg_strftime()","version":"18.4"},{"entry":{"category":"security","commit_aliases":["08c397b02","4793fc41f","8bca85e9f","a44780f41","c27ba08cd","d92852d62"],"commit_groups":[["08c397b02","4793fc41f","8bca85e9f","a44780f41","c27ba08cd","d92852d62"]],"commits":["a44780f41"],"cves":["CVE-2026-6472"],"db_id":"d9b882bba9a59b55e34aa99621e22473","html":"\u003cp\u003eWhen creating a multirange type, ensure the user has \u003ccode\u003eCREATE\u003c/code\u003e privilege on the schema specified for the multirange type (Jelte Fennema-Nio) \u003ca href=\"https://postgr.es/c/a44780f41\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Jelte Fennema-Nio for reporting this problem. (CVE-2026-6472)\u003c/p\u003e","id":"18.4-5cd7cd57980a1193","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)","part":"changes","patch_ids":["1c201360c1e263b311b7234d83ff89be"],"relations":[{"evidence":{"patch_ids":["1c201360c1e263b311b7234d83ff89be"],"same_day":true,"statement_hash":"d04d5cbb5906b8e6e39e901491618574dca51ad80d7a3a625a786fceaddfddfd"},"rule":2,"target":"482afe166c3411e42aa15c76ef043f3e","type":"equivalent"},{"evidence":{"patch_ids":["1c201360c1e263b311b7234d83ff89be"],"same_day":true,"statement_hash":"d04d5cbb5906b8e6e39e901491618574dca51ad80d7a3a625a786fceaddfddfd"},"rule":2,"target":"65fdc90a340d7a6f096d34d54ccaf154","type":"equivalent"},{"evidence":{"patch_ids":["1c201360c1e263b311b7234d83ff89be"],"same_day":true,"statement_hash":"d04d5cbb5906b8e6e39e901491618574dca51ad80d7a3a625a786fceaddfddfd"},"rule":2,"target":"8f0e03a85bb45cde24bbedf7f781a5d5","type":"equivalent"},{"evidence":{"patch_ids":["1c201360c1e263b311b7234d83ff89be"],"same_day":true,"statement_hash":"d04d5cbb5906b8e6e39e901491618574dca51ad80d7a3a625a786fceaddfddfd"},"rule":2,"target":"c06039568f80f491221fd94687f0285e","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["a44780f41"],"source_entry_id":"18.4/changes/008","source_hash":"d62318111e6c324435000f823b575ec7304c8e7d730a7361206b709d1236e1d4","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"d04d5cbb5906b8e6e39e901491618574dca51ad80d7a3a625a786fceaddfddfd","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"},"id":"18.4-5cd7cd57980a1193","matches":[{"id":"17.10-7b894433ca4b5fde","source_entry_id":"17.10/changes/007","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","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/008","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","version":"18.4"},{"entry":{"category":"security","commit_aliases":["00e27235e","1604939b2","4608619a1","5924e256c","8e34acfda","9dcfcb92f","b282280e9","c4e7435b3","c95275f18","d93ef4131"],"commit_groups":[["00e27235e","4608619a1","5924e256c","c4e7435b3","c95275f18","d93ef4131"],["1604939b2","8e34acfda","9dcfcb92f","b282280e9"]],"commits":["d93ef4131"],"cves":["CVE-2026-6478"],"db_id":"c468a98baa6993bf40cb569c73528c72","html":"\u003cp\u003eUse timing-safe string comparisons in authentication code (Michael Paquier) \u003ca href=\"https://postgr.es/c/d93ef4131\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eUse \u003ccode\u003etimingsafe_bcmp()\u003c/code\u003e instead of \u003ccode\u003ememcmp()\u003c/code\u003e or \u003ccode\u003estrcmp()\u003c/code\u003e 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Joe Conway for reporting this problem. (CVE-2026-6478)\u003c/p\u003e","id":"18.4-81a3fe71f66e6eb4","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)","part":"changes","patch_ids":["4f5cfd9b1166f378c5d2d04fe94dad87","7fbe706dd59ebe4eced7f18fe6cbf482"],"relations":[{"evidence":{"patch_ids":["4f5cfd9b1166f378c5d2d04fe94dad87","7fbe706dd59ebe4eced7f18fe6cbf482"],"same_day":true,"statement_hash":"7b7eca3255c6f7cb268565088cc6e073ca0b27ad15442af2772a39e51cbfd149"},"rule":2,"target":"049d75b9e50ceb48ee3ba2c6a5d0f494","type":"equivalent"},{"evidence":{"patch_ids":["4f5cfd9b1166f378c5d2d04fe94dad87","7fbe706dd59ebe4eced7f18fe6cbf482"],"same_day":true,"statement_hash":"7b7eca3255c6f7cb268565088cc6e073ca0b27ad15442af2772a39e51cbfd149"},"rule":2,"target":"0851fa23f0d4449b2336783af8c0b37f","type":"equivalent"},{"evidence":{"patch_ids":["4f5cfd9b1166f378c5d2d04fe94dad87","7fbe706dd59ebe4eced7f18fe6cbf482"],"same_day":true,"statement_hash":"7b7eca3255c6f7cb268565088cc6e073ca0b27ad15442af2772a39e51cbfd149"},"rule":2,"target":"15b60135e3ecea3f472e4441792a26d0","type":"equivalent"},{"evidence":{"patch_ids":["4f5cfd9b1166f378c5d2d04fe94dad87","7fbe706dd59ebe4eced7f18fe6cbf482"],"same_day":true,"statement_hash":"7b7eca3255c6f7cb268565088cc6e073ca0b27ad15442af2772a39e51cbfd149"},"rule":2,"target":"f4fc92fe7fa973d00f46d80cff768f2c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["8e34acfda","d93ef4131"],"source_entry_id":"18.4/changes/009","source_hash":"31ac0fd6ff577a6e44248a0cccbeba45ddd27760609e5b903596b279c704b45d","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"7b7eca3255c6f7cb268565088cc6e073ca0b27ad15442af2772a39e51cbfd149","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"},"id":"18.4-81a3fe71f66e6eb4","matches":[{"id":"17.10-61c7a5bccb286bea","source_entry_id":"17.10/changes/008","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Use timing-safe string comparisons in authentication code","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/009","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Use timing-safe string comparisons in authentication code","version":"18.4"},{"entry":{"category":"security","commit_aliases":["614474996","8ac723b2b","bd4811493","be0136440","d88c7be15","e3a1f83ea"],"commit_groups":[["614474996","8ac723b2b","bd4811493","be0136440","d88c7be15","e3a1f83ea"]],"commits":["be0136440"],"cves":["CVE-2026-6477"],"db_id":"847daceb397313a24d7c441b2b0558f1","html":"\u003cp\u003eMark \u003ccode\u003ePQfn()\u003c/code\u003e as unsafe, and avoid using it within \u003cspan\u003elibpq\u003c/span\u003e (Nathan Bossart) \u003ca href=\"https://postgr.es/c/be0136440\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFor a non-integral result type, \u003ccode\u003ePQfn()\u003c/code\u003e 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 \u003cspan\u003elibpq\u003c/span\u003e, use a variant version that can apply the missing check.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Yu Kunpeng and Martin Heistermann for reporting this problem. (CVE-2026-6477)\u003c/p\u003e","id":"18.4-d46d3c9f5a15e9ff","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)","part":"changes","patch_ids":["751c917289b90832d6991f8f4911d6cc"],"relations":[{"evidence":{"patch_ids":["751c917289b90832d6991f8f4911d6cc"],"same_day":true,"statement_hash":"1bf9b2e2db6cb6f0cc68cfddc7ca5a446d8e7408a35bce897eda2f59aec7605b"},"rule":2,"target":"4ab9970767b3ef4f9da60c3566967c2b","type":"equivalent"},{"evidence":{"patch_ids":["751c917289b90832d6991f8f4911d6cc"],"same_day":true,"statement_hash":"1bf9b2e2db6cb6f0cc68cfddc7ca5a446d8e7408a35bce897eda2f59aec7605b"},"rule":2,"target":"5659c5fab9b3c23718775a073679d763","type":"equivalent"},{"evidence":{"patch_ids":["751c917289b90832d6991f8f4911d6cc"],"same_day":true,"statement_hash":"1bf9b2e2db6cb6f0cc68cfddc7ca5a446d8e7408a35bce897eda2f59aec7605b"},"rule":2,"target":"954548c0ee471a5891175ee04e881030","type":"equivalent"},{"evidence":{"patch_ids":["751c917289b90832d6991f8f4911d6cc"],"same_day":true,"statement_hash":"1bf9b2e2db6cb6f0cc68cfddc7ca5a446d8e7408a35bce897eda2f59aec7605b"},"rule":2,"target":"fcce310e332c33500cf3c168aae9bd79","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["be0136440"],"source_entry_id":"18.4/changes/010","source_hash":"7fc11295c46055a4824819e76fe0415c3ae41f7901858f49c5c1b096f57994a9","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"1bf9b2e2db6cb6f0cc68cfddc7ca5a446d8e7408a35bce897eda2f59aec7605b","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"},"id":"18.4-d46d3c9f5a15e9ff","matches":[{"id":"17.10-a3a6ffe2e68f9c70","source_entry_id":"17.10/changes/009","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Mark PQfn() as unsafe, and avoid using it within libpq","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/010","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Mark PQfn() as unsafe, and avoid using it within libpq","version":"18.4"},{"entry":{"category":"security","commit_aliases":["0c83fe8e4","498829dca","6778af13e","6a67c540a","8f881e188","a1063eece"],"commit_groups":[["0c83fe8e4","498829dca","6778af13e","6a67c540a","8f881e188","a1063eece"]],"commits":["6a67c540a"],"cves":["CVE-2026-6475"],"db_id":"4327318e7057209dbe42b98400f9d4be","html":"\u003cp\u003ePrevent path traversal in \u003cspan\u003epg_basebackup\u003c/span\u003e and \u003cspan\u003epg_rewind\u003c/span\u003e (Michael Paquier) \u003ca href=\"https://postgr.es/c/6a67c540a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks XlabAI Team of Tencent Xuanwu Lab and Valery Gubanov for reporting this problem. (CVE-2026-6475)\u003c/p\u003e","id":"18.4-ad40fa4da3cebaa2","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)","part":"changes","patch_ids":["642e466aa03c3fea1f14f662cc164373"],"relations":[{"evidence":{"patch_ids":["642e466aa03c3fea1f14f662cc164373"],"same_day":true,"statement_hash":"f4e8ae9e638997395a0957d148112ff560c0e68ac13f1311986f81899f914d10"},"rule":2,"target":"4bae8e6eba13d8b7f663721c981765fa","type":"equivalent"},{"evidence":{"patch_ids":["642e466aa03c3fea1f14f662cc164373"],"same_day":true,"statement_hash":"f4e8ae9e638997395a0957d148112ff560c0e68ac13f1311986f81899f914d10"},"rule":2,"target":"5bc8c04625ad184faa480aea65f22c87","type":"equivalent"},{"evidence":{"patch_ids":["642e466aa03c3fea1f14f662cc164373"],"same_day":true,"statement_hash":"f4e8ae9e638997395a0957d148112ff560c0e68ac13f1311986f81899f914d10"},"rule":2,"target":"869c70a85bc692a897810d4c6c2c8001","type":"equivalent"},{"evidence":{"patch_ids":["642e466aa03c3fea1f14f662cc164373"],"same_day":true,"statement_hash":"f4e8ae9e638997395a0957d148112ff560c0e68ac13f1311986f81899f914d10"},"rule":2,"target":"a4a793034a07393a1194f5d901c7e563","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["6a67c540a"],"source_entry_id":"18.4/changes/011","source_hash":"6bc165e3208c831cfd8f34eec3a461fc0569e52e0b5e8ba62286675169fa1d64","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"f4e8ae9e638997395a0957d148112ff560c0e68ac13f1311986f81899f914d10","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"},"id":"18.4-ad40fa4da3cebaa2","matches":[{"id":"17.10-91d502adb9e9905a","source_entry_id":"17.10/changes/010","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Prevent path traversal in pg_basebackup and pg_rewind","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/011","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Prevent path traversal in pg_basebackup and pg_rewind","version":"18.4"},{"entry":{"category":"security","commit_aliases":["05e73b5c3","074702525","2b429d887","43451a7a2","479823a71","5c1069c35","6f0bff33d","84a9f2641","906ea101d","c4d04cc48","c5790ec4f","fc1fd3d97"],"commit_groups":[["05e73b5c3","2b429d887","479823a71","6f0bff33d","906ea101d","fc1fd3d97"],["074702525","43451a7a2","5c1069c35","84a9f2641","c4d04cc48","c5790ec4f"]],"commits":["05e73b5c3","c5790ec4f"],"cves":["CVE-2026-6473"],"db_id":"9a6b47b64707d2aaa7ed6ba0484070e5","html":"\u003cp\u003eGuard against field overflow within \u003ccode\u003econtrib/intarray\u003c/code\u003e's \u003ccode\u003equery_int\u003c/code\u003e type and \u003ccode\u003econtrib/ltree\u003c/code\u003e's \u003ccode\u003eltxtquery\u003c/code\u003e type (Tom Lane) \u003ca href=\"https://postgr.es/c/c5790ec4f\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/05e73b5c3\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eParsing 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Xint Code for reporting this problem. (CVE-2026-6473)\u003c/p\u003e","id":"18.4-2061b554e1b2edfa","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)","part":"changes","patch_ids":["6f7401152b77a4e4d59e752f19e8486b","b419665d09a38659e641b360731e56da"],"relations":[{"evidence":{"patch_ids":["6f7401152b77a4e4d59e752f19e8486b","b419665d09a38659e641b360731e56da"],"same_day":true,"statement_hash":"eab56845994726033024137f96b0dd1e892a863aae111c3043e8a088bf26c0d7"},"rule":2,"target":"0423b242e381085c16cb62849b04525f","type":"equivalent"},{"evidence":{"patch_ids":["6f7401152b77a4e4d59e752f19e8486b","b419665d09a38659e641b360731e56da"],"same_day":true,"statement_hash":"eab56845994726033024137f96b0dd1e892a863aae111c3043e8a088bf26c0d7"},"rule":2,"target":"2ad1fdfa4b929eb7b74591983f7fe071","type":"equivalent"},{"evidence":{"patch_ids":["6f7401152b77a4e4d59e752f19e8486b","b419665d09a38659e641b360731e56da"],"same_day":true,"statement_hash":"eab56845994726033024137f96b0dd1e892a863aae111c3043e8a088bf26c0d7"},"rule":2,"target":"9f97314dd0efbba664c1f83e75fb5fa1","type":"equivalent"},{"evidence":{"patch_ids":["6f7401152b77a4e4d59e752f19e8486b","b419665d09a38659e641b360731e56da"],"same_day":true,"statement_hash":"eab56845994726033024137f96b0dd1e892a863aae111c3043e8a088bf26c0d7"},"rule":2,"target":"d29898a37787b811ca1a66114dcaa530","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["05e73b5c3","c5790ec4f"],"source_entry_id":"18.4/changes/012","source_hash":"c072da4c6c8e8d11286a2d5d62c06b65f9880c2bd66f39eebf44dfba434afe5b","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"eab56845994726033024137f96b0dd1e892a863aae111c3043e8a088bf26c0d7","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"},"id":"18.4-2061b554e1b2edfa","matches":[{"id":"17.10-992f2d3fb9146406","source_entry_id":"17.10/changes/011","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","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/012","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","version":"18.4"},{"entry":{"category":"security","commit_aliases":["2f1b16e86","6b6b26fde","7f019f341","8c3426110","9c2fa5b6a","b545c3787"],"commit_groups":[["2f1b16e86","6b6b26fde","7f019f341","8c3426110","9c2fa5b6a","b545c3787"]],"commits":["7f019f341"],"cves":["CVE-2026-6473"],"db_id":"f1ea7b13a59ce4a556a97a665b13ddd9","html":"\u003cp\u003eGuard against overly long values of \u003ccode\u003econtrib/ltree\u003c/code\u003e's \u003ccode\u003elquery\u003c/code\u003e type (Michael Paquier) \u003ca href=\"https://postgr.es/c/7f019f341\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eValues with more than 64K items caused internal overflows, potentially resulting in stack smashes or wrong answers.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Vergissmeinnicht, A1ex, and Jihe Wang for reporting this problem. (CVE-2026-6473)\u003c/p\u003e","id":"18.4-eb36ae972f5e73e4","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)","part":"changes","patch_ids":["82d1afadeb06a657e558ea1b226d290b"],"relations":[{"evidence":{"patch_ids":["82d1afadeb06a657e558ea1b226d290b"],"same_day":true,"statement_hash":"0f082737f7f109cba8da33aebd4d21f85a8ca0c9ac333cd92d1eafa83684e6e1"},"rule":2,"target":"6aa8f69f3021e6633c690bc4d069a359","type":"equivalent"},{"evidence":{"patch_ids":["82d1afadeb06a657e558ea1b226d290b"],"same_day":true,"statement_hash":"0f082737f7f109cba8da33aebd4d21f85a8ca0c9ac333cd92d1eafa83684e6e1"},"rule":2,"target":"abd21d034ac90949aacffcced38f44c8","type":"equivalent"},{"evidence":{"patch_ids":["82d1afadeb06a657e558ea1b226d290b"],"same_day":true,"statement_hash":"0f082737f7f109cba8da33aebd4d21f85a8ca0c9ac333cd92d1eafa83684e6e1"},"rule":2,"target":"b026af4117fde9e94388242432e381e0","type":"equivalent"},{"evidence":{"patch_ids":["82d1afadeb06a657e558ea1b226d290b"],"same_day":true,"statement_hash":"0f082737f7f109cba8da33aebd4d21f85a8ca0c9ac333cd92d1eafa83684e6e1"},"rule":2,"target":"e57528b755cb641d030a2490a8ecb83e","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["7f019f341"],"source_entry_id":"18.4/changes/013","source_hash":"c636424e1165ad48a14eaeae8259fc21c63fc45076252ce264efb1a7fef87996","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"0f082737f7f109cba8da33aebd4d21f85a8ca0c9ac333cd92d1eafa83684e6e1","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"},"id":"18.4-eb36ae972f5e73e4","matches":[{"id":"17.10-ac24cc16660e8737","source_entry_id":"17.10/changes/012","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Guard against overly long values of contrib/ltree's lquery type","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/013","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Guard against overly long values of contrib/ltree's lquery type","version":"18.4"},{"entry":{"category":"security","commit_aliases":["1ebda7da9","260e97733","2b026df29","2dc64ef28","710995782","8053235ab"],"commit_groups":[["1ebda7da9","260e97733","2b026df29","2dc64ef28","710995782","8053235ab"]],"commits":["1ebda7da9"],"cves":["CVE-2026-6637"],"db_id":"7f0c9646c89bca074cd9e0bbd964087f","html":"\u003cp\u003ePrevent SQL injection and buffer overruns in \u003ccode\u003econtrib/spi\u003c/code\u003e (Nathan Bossart) \u003ca href=\"https://postgr.es/c/1ebda7da9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003echeck_foreign_key()\u003c/code\u003e 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Nikolay Samokhvalov for reporting this problem. (CVE-2026-6637)\u003c/p\u003e","id":"18.4-723bbbf2b375795c","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)","part":"changes","patch_ids":["41547e1e28b3ed62af00bb9fe154772c"],"relations":[{"evidence":{"patch_ids":["41547e1e28b3ed62af00bb9fe154772c"],"same_day":true,"statement_hash":"7b1c0422aa1716161960ade63e1f312c46555a948c91e3b00a8e5c748e70d047"},"rule":2,"target":"47e292139214a78fca35c140daf58270","type":"equivalent"},{"evidence":{"patch_ids":["41547e1e28b3ed62af00bb9fe154772c"],"same_day":true,"statement_hash":"7b1c0422aa1716161960ade63e1f312c46555a948c91e3b00a8e5c748e70d047"},"rule":2,"target":"5c27c1f393abf9296bda616730209a61","type":"equivalent"},{"evidence":{"patch_ids":["41547e1e28b3ed62af00bb9fe154772c"],"same_day":true,"statement_hash":"7b1c0422aa1716161960ade63e1f312c46555a948c91e3b00a8e5c748e70d047"},"rule":2,"target":"80646ad1b79ca8538cfec18dd2e574d7","type":"equivalent"},{"evidence":{"patch_ids":["41547e1e28b3ed62af00bb9fe154772c"],"same_day":true,"statement_hash":"7b1c0422aa1716161960ade63e1f312c46555a948c91e3b00a8e5c748e70d047"},"rule":2,"target":"b9f0b8c87f7b233c50090282e467d8ed","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["1ebda7da9"],"source_entry_id":"18.4/changes/014","source_hash":"d1e23fbdb69b2138879701aaf07def7e140aa1af21e7ee27298e304aed0ca7d2","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"7b1c0422aa1716161960ade63e1f312c46555a948c91e3b00a8e5c748e70d047","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"},"id":"18.4-723bbbf2b375795c","matches":[{"id":"17.10-24a0ab68af146f7d","source_entry_id":"17.10/changes/013","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Prevent SQL injection and buffer overruns in contrib/spi","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/014","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Prevent SQL injection and buffer overruns in contrib/spi","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["1132af22c","13226050e","172034f6e","574581b50","5a24cef08","5a55ea507","5c214b58b","748fe9e60","8395446df","872c9fae7","a1b754558","b62f514ac","ba82de48e","bab4f7fa5","bed3ffbf9","d0e73bb18","e8fd5e579","f76686ce7"],"commit_groups":[["1132af22c","ba82de48e"],["13226050e","172034f6e","574581b50","5a24cef08","bab4f7fa5","bed3ffbf9"],["5a55ea507","748fe9e60","8395446df","872c9fae7","b62f514ac","d0e73bb18"],["5c214b58b","a1b754558"],["e8fd5e579","f76686ce7"]],"commits":["1132af22c","5c214b58b","b62f514ac","bed3ffbf9","e8fd5e579"],"cves":[],"db_id":"ab7deff460d412d778fdd667ced2079e","html":"\u003cp\u003eCheck for nondeterministic collations before assuming that an equality condition on a collatable type implies uniqueness (Richard Guo) \u003ca href=\"https://postgr.es/c/e8fd5e579\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/1132af22c\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/5c214b58b\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/b62f514ac\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/bed3ffbf9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eNumerous planner optimizations assume that, for example, at most one table row can satisfy \u003ccode\u003eWHERE x = 'abc'\u003c/code\u003e if there is a unique index on \u003ccode\u003ex\u003c/code\u003e. However this conclusion is unsafe in general if the index and the \u003ccode\u003eWHERE\u003c/code\u003e 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 \u003ccode\u003eWHERE\u003c/code\u003e clause or the index has a nondeterministic collation.\u003c/p\u003e","id":"18.4-984de78400375246","identity_text":"Check for nondeterministic collations before assuming that an equality condition on a collatable type implies uniqueness (Richard Guo) Numerous 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.","part":"changes","patch_ids":["316cf0ea770f560e72ab5371605b5513","5c112866699f7434ac81094a7defff94","91c3ff9eba57946197b7ff56e14fa51c","d3eef434b7b707e4192750663780aead","fd47d8d847172b542e4dd373ddd10da1"],"relations":[{"evidence":{"patch_ids":["316cf0ea770f560e72ab5371605b5513","5c112866699f7434ac81094a7defff94","91c3ff9eba57946197b7ff56e14fa51c","d3eef434b7b707e4192750663780aead","fd47d8d847172b542e4dd373ddd10da1"],"same_day":true,"statement_hash":"6402b6aac418981ce0968875628d2940ac41a846f0268ecb70dd927a13b74c1f"},"rule":2,"target":"01495853fe95f595fce2399c30d4c266","type":"equivalent"},{"evidence":{"patch_ids":["316cf0ea770f560e72ab5371605b5513","5c112866699f7434ac81094a7defff94","91c3ff9eba57946197b7ff56e14fa51c","d3eef434b7b707e4192750663780aead","fd47d8d847172b542e4dd373ddd10da1"],"same_day":true,"statement_hash":"6402b6aac418981ce0968875628d2940ac41a846f0268ecb70dd927a13b74c1f"},"rule":2,"target":"14aca2f70b5d43150bf21abea06182b1","type":"equivalent"},{"evidence":{"patch_ids":["316cf0ea770f560e72ab5371605b5513","5c112866699f7434ac81094a7defff94","91c3ff9eba57946197b7ff56e14fa51c","d3eef434b7b707e4192750663780aead","fd47d8d847172b542e4dd373ddd10da1"],"same_day":true,"statement_hash":"6402b6aac418981ce0968875628d2940ac41a846f0268ecb70dd927a13b74c1f"},"rule":2,"target":"be78fda4d4ae3aff51c46044542ecdd6","type":"equivalent"},{"evidence":{"patch_ids":["316cf0ea770f560e72ab5371605b5513","5c112866699f7434ac81094a7defff94","91c3ff9eba57946197b7ff56e14fa51c","d3eef434b7b707e4192750663780aead","fd47d8d847172b542e4dd373ddd10da1"],"same_day":true,"statement_hash":"6402b6aac418981ce0968875628d2940ac41a846f0268ecb70dd927a13b74c1f"},"rule":2,"target":"c3e4bc289412c6b44dec384e088dc836","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["1132af22c","5c214b58b","b62f514ac","bed3ffbf9","e8fd5e579"],"source_entry_id":"18.4/changes/015","source_hash":"2ccb980c9c51c9b8a35b8bc0df111406fcf95017c9c5aa3e0cdb7f0691db78d7","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"6402b6aac418981ce0968875628d2940ac41a846f0268ecb70dd927a13b74c1f","text":"Check for nondeterministic collations before assuming that an equality condition on a collatable type implies uniqueness (Richard Guo) § § § § § Numerous 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.","title":"Check for nondeterministic collations before assuming that an equality condition on a collatable type implies uniqueness"},"id":"18.4-984de78400375246","matches":[{"id":"17.10-3d0256182db9ecf0","source_entry_id":"17.10/changes/014","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","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/015","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","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["16fb94605","53cb4ec1d","766d40286","798dabe83","cfcd57111","d509be4ac","f0ac6d494"],"commit_groups":[["16fb94605","766d40286","cfcd57111","d509be4ac"],["53cb4ec1d","798dabe83","f0ac6d494"]],"commits":["16fb94605"],"cves":[],"db_id":"cbba3da86525413deddd8a183780866b","html":"\u003cp\u003eFix incomplete removal of relation references in \u003ccode\u003eRestrictInfo\u003c/code\u003e structs during join removal (Tom Lane) \u003ca href=\"https://postgr.es/c/16fb94605\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis oversight has been shown to result in planner failures such as unexpected \u003cspan\u003e“\u003cspan\u003eFULL JOIN is only supported with merge-joinable or hash-joinable join conditions\u003c/span\u003e”\u003c/span\u003e errors. It may also have caused failure to consider valid plans in other cases.\u003c/p\u003e","id":"18.4-316d774d0290fc1b","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.","part":"changes","patch_ids":["22c06d077427cb5284041785d0e8cde1","8989faf5448f269deb8ac79dc2a63860"],"relations":[{"evidence":{"patch_ids":["22c06d077427cb5284041785d0e8cde1","8989faf5448f269deb8ac79dc2a63860"],"same_day":true,"statement_hash":"bbc0a2274d4af257fa49e43eafaf28ca0f12217996c9c00ed63e12bf89b35109"},"rule":2,"target":"0a61b6485e0144413b6e68fbe7763a8f","type":"equivalent"},{"evidence":{"patch_ids":["22c06d077427cb5284041785d0e8cde1","8989faf5448f269deb8ac79dc2a63860"],"same_day":true,"statement_hash":"bbc0a2274d4af257fa49e43eafaf28ca0f12217996c9c00ed63e12bf89b35109"},"rule":2,"target":"53d5de052cfe73ed3dbffe04ba42ff12","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["16fb94605","f0ac6d494"],"source_entry_id":"18.4/changes/016","source_hash":"7890a55f50302b7ca4e67825cbefbb79c5ca02ec380951e76604a48bda8c0624","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"bbc0a2274d4af257fa49e43eafaf28ca0f12217996c9c00ed63e12bf89b35109","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"},"id":"18.4-316d774d0290fc1b","matches":[{"id":"17.10-d93df01ed01294f0","source_entry_id":"17.10/changes/015","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix incomplete removal of relation references in RestrictInfo structs during join removal","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/016","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix incomplete removal of relation references in RestrictInfo structs during join removal","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["07b257189","7062bd577","8e39951be","9d6208939","c6a79be3f","e528bfe97"],"commit_groups":[["07b257189","7062bd577","8e39951be","9d6208939","c6a79be3f","e528bfe97"]],"commits":["e528bfe97"],"cves":[],"db_id":"090655eebbd07936e4cb9d733f25b629","html":"\u003cp\u003eFix incorrect handling of \u003ccode\u003eNEW\u003c/code\u003e generated columns in rule actions and rule qualifications (Richard Guo, Dean Rasheed) \u003ca href=\"https://postgr.es/c/e528bfe97\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, such column references would produce NULL in \u003ccode\u003eINSERT\u003c/code\u003e cases, or be equivalent to the \u003ccode\u003eOLD\u003c/code\u003e value in \u003ccode\u003eUPDATE\u003c/code\u003e cases.\u003c/p\u003e","id":"18.4-e3a990357e448509","identity_text":"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.","part":"changes","patch_ids":["9ef2d4ec0243bfe037d4994449c1e950"],"relations":[{"evidence":{"patch_ids":["9ef2d4ec0243bfe037d4994449c1e950"],"same_day":true,"statement_hash":"af928f89db398ea67c9d32398c345b90e862839c58fbce5eefd58aea84a8cc63"},"rule":2,"target":"47046c8c15b5c7b8a2538a455bf90e7f","type":"equivalent"},{"evidence":{"patch_ids":["9ef2d4ec0243bfe037d4994449c1e950"],"same_day":true,"statement_hash":"af928f89db398ea67c9d32398c345b90e862839c58fbce5eefd58aea84a8cc63"},"rule":2,"target":"8d80511e26d842f1435d2598f5f3bbaf","type":"equivalent"},{"evidence":{"patch_ids":["9ef2d4ec0243bfe037d4994449c1e950"],"same_day":true,"statement_hash":"af928f89db398ea67c9d32398c345b90e862839c58fbce5eefd58aea84a8cc63"},"rule":2,"target":"924c81d81cc88aec8a63bf143f2a1b9d","type":"equivalent"},{"evidence":{"patch_ids":["9ef2d4ec0243bfe037d4994449c1e950"],"same_day":true,"statement_hash":"af928f89db398ea67c9d32398c345b90e862839c58fbce5eefd58aea84a8cc63"},"rule":2,"target":"c8b55f6e2f83066024ceec0fb6fec616","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["e528bfe97"],"source_entry_id":"18.4/changes/021","source_hash":"304f3b7a18486857e4eac015eeb283a4f5a0a477ff7ecf49fa3bf8bd19c82f21","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"af928f89db398ea67c9d32398c345b90e862839c58fbce5eefd58aea84a8cc63","text":"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.","title":"Fix incorrect handling of NEW generated columns in rule actions and rule qualifications"},"id":"18.4-e3a990357e448509","matches":[{"id":"17.10-5a2d4121326fa353","source_entry_id":"17.10/changes/016","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix incorrect handling of NEW generated columns in rule actions and rule qualifications","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/021","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix incorrect handling of NEW generated columns in rule actions and rule qualifications","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["07e833e3c","11c2c0cc8","3c7a6bbe6","40fa04e7c","681a91d29"],"commit_groups":[["07e833e3c","11c2c0cc8","3c7a6bbe6","40fa04e7c","681a91d29"]],"commits":["11c2c0cc8"],"cves":[],"db_id":"8f94a546a98010653153df93291c1daa","html":"\u003cp\u003eFix spurious \u003cspan\u003e“\u003cspan\u003egenerated columns are not supported in COPY FROM WHERE conditions\u003c/span\u003e”\u003c/span\u003e errors (Tom Lane) \u003ca href=\"https://postgr.es/c/11c2c0cc8\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eUse of a system column in a \u003ccode\u003eCOPY FROM WHERE\u003c/code\u003e condition could sometimes incorrectly report this error.\u003c/p\u003e","id":"18.4-734d0400d44f5a3f","identity_text":"Fix spurious generated columns are not supported in COPY FROM WHERE conditions errors (Tom Lane) Use of a system column in a COPY FROM WHERE condition could sometimes incorrectly report this error.","part":"changes","patch_ids":["ffbf1ec2eaa36c2627f1603a95fc907d"],"relations":[{"evidence":{"patch_ids":["ffbf1ec2eaa36c2627f1603a95fc907d"],"same_day":true,"statement_hash":"d39bf8499a6b555306ab12d7b050ccd17449a702d3330d112766f10a63c6d66d"},"rule":2,"target":"245fb332b7d69bd5dc49fa8d57502aa2","type":"equivalent"},{"evidence":{"patch_ids":["ffbf1ec2eaa36c2627f1603a95fc907d"],"same_day":true,"statement_hash":"d39bf8499a6b555306ab12d7b050ccd17449a702d3330d112766f10a63c6d66d"},"rule":2,"target":"440131012dd49c3c07164d3cb19f4dc4","type":"equivalent"},{"evidence":{"patch_ids":["ffbf1ec2eaa36c2627f1603a95fc907d"],"same_day":true,"statement_hash":"d39bf8499a6b555306ab12d7b050ccd17449a702d3330d112766f10a63c6d66d"},"rule":2,"target":"8df2189076f2cd8cbe00157fbb1a0189","type":"equivalent"},{"evidence":{"patch_ids":["ffbf1ec2eaa36c2627f1603a95fc907d"],"same_day":true,"statement_hash":"d39bf8499a6b555306ab12d7b050ccd17449a702d3330d112766f10a63c6d66d"},"rule":2,"target":"91f89865543bf2e44365694aaed7f1c5","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["11c2c0cc8"],"source_entry_id":"18.4/changes/023","source_hash":"3ded2519af91f618651841221f070506306f043b8ac6ff8592dec5231f982e50","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"d39bf8499a6b555306ab12d7b050ccd17449a702d3330d112766f10a63c6d66d","text":"Fix spurious “generated columns are not supported in COPY FROM WHERE conditions” errors (Tom Lane) § Use of a system column in a COPY FROM WHERE condition could sometimes incorrectly report this error.","title":"Fix spurious “generated columns are not supported in COPY FROM WHERE conditions” errors"},"id":"18.4-734d0400d44f5a3f","matches":[{"id":"17.10-ff70dbd91aa208f5","source_entry_id":"17.10/changes/017","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix spurious “generated columns are not supported in COPY FROM WHERE conditions” errors","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/023","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix spurious “generated columns are not supported in COPY FROM WHERE conditions” errors","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["13fab378e","177037341","2dcac93c0","8bfaae6fb","f6e63d4b8"],"commit_groups":[["13fab378e","177037341","2dcac93c0","8bfaae6fb","f6e63d4b8"]],"commits":["13fab378e"],"cves":[],"db_id":"bfb26a4ca22c86d79dfde428bbcc3c24","html":"\u003cp\u003eCorrectly report a serialization failure when \u003ccode\u003eMERGE\u003c/code\u003e encounters a concurrently-updated tuple in repeatable-read or serializable mode (Tender Wang) \u003ca href=\"https://postgr.es/c/13fab378e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, such cases behaved the same as in lower isolation levels.\u003c/p\u003e","id":"18.4-34de9da81adc1f79","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.","part":"changes","patch_ids":["569476436f6f49fe3fc1c20af4157acf"],"relations":[{"evidence":{"patch_ids":["569476436f6f49fe3fc1c20af4157acf"],"same_day":true,"statement_hash":"298c05dfef81a90cfb05f72e7375c2ceb55354d2b8c327b08b686d82ad2857b4"},"rule":2,"target":"3f720165e3e8a599ba151cefd48b97e8","type":"equivalent"},{"evidence":{"patch_ids":["569476436f6f49fe3fc1c20af4157acf"],"same_day":true,"statement_hash":"298c05dfef81a90cfb05f72e7375c2ceb55354d2b8c327b08b686d82ad2857b4"},"rule":2,"target":"6827747aec40694708ad07aebaf4d3c0","type":"equivalent"},{"evidence":{"patch_ids":["569476436f6f49fe3fc1c20af4157acf"],"same_day":true,"statement_hash":"298c05dfef81a90cfb05f72e7375c2ceb55354d2b8c327b08b686d82ad2857b4"},"rule":2,"target":"f9969f9244f4ca14ba57359448274286","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["13fab378e"],"source_entry_id":"18.4/changes/024","source_hash":"8a02358aa03c1255369f0fa3de56d57dc1d5929292b77353d5fb36ce49a717a6","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"298c05dfef81a90cfb05f72e7375c2ceb55354d2b8c327b08b686d82ad2857b4","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"},"id":"18.4-34de9da81adc1f79","matches":[{"id":"17.10-7ae06d40b417bc3b","source_entry_id":"17.10/changes/018","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Correctly report a serialization failure when MERGE encounters a concurrently-updated tuple in repeatable-read or serializable mode","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/024","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Correctly report a serialization failure when MERGE encounters a concurrently-updated tuple in repeatable-read or serializable mode","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["149c875fc","6cf49e804","76d15a7ee","7bb519635","81b56b47c","a0104b447"],"commit_groups":[["149c875fc","6cf49e804","76d15a7ee","7bb519635","81b56b47c","a0104b447"]],"commits":["149c875fc"],"cves":[],"db_id":"4b8420c7de509df1179d8ee1c1364ee6","html":"\u003cp\u003eFix \u003ccode\u003eCREATE TABLE ... LIKE ... INCLUDING STATISTICS\u003c/code\u003e for cases where the source table has dropped column(s) (Julien Tachoires) \u003ca href=\"https://postgr.es/c/149c875fc\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIn such cases, extended statistics objects could be copied incorrectly, or the command could give an incorrect error.\u003c/p\u003e","id":"18.4-da4a103ca5dfdddc","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.","part":"changes","patch_ids":["910e6f19667b7b2c274a7cfa4cfbf09c"],"relations":[{"evidence":{"patch_ids":["910e6f19667b7b2c274a7cfa4cfbf09c"],"same_day":true,"statement_hash":"468cd074434d5b124a2f3ad7e4d4363935368333f67c114d461285e65aadff62"},"rule":2,"target":"259f6916a28a7dd3bbeb72cc130b41a9","type":"equivalent"},{"evidence":{"patch_ids":["910e6f19667b7b2c274a7cfa4cfbf09c"],"same_day":true,"statement_hash":"468cd074434d5b124a2f3ad7e4d4363935368333f67c114d461285e65aadff62"},"rule":2,"target":"2e2724c6cc505b0329f5a78d83fd96cb","type":"equivalent"},{"evidence":{"patch_ids":["910e6f19667b7b2c274a7cfa4cfbf09c"],"same_day":true,"statement_hash":"468cd074434d5b124a2f3ad7e4d4363935368333f67c114d461285e65aadff62"},"rule":2,"target":"d68baf1e5d412f66c44df3a681238123","type":"equivalent"},{"evidence":{"patch_ids":["910e6f19667b7b2c274a7cfa4cfbf09c"],"same_day":true,"statement_hash":"468cd074434d5b124a2f3ad7e4d4363935368333f67c114d461285e65aadff62"},"rule":2,"target":"e7ce3c2946bfdef059fc3d3621ffd79d","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["149c875fc"],"source_entry_id":"18.4/changes/025","source_hash":"ea4e0ec26e93b0117e68bbc15ef5d3f14ae1a23e12f8b9de9a4092a49e7865a7","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"468cd074434d5b124a2f3ad7e4d4363935368333f67c114d461285e65aadff62","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)"},"id":"18.4-da4a103ca5dfdddc","matches":[{"id":"17.10-b893eef62a42d4d7","source_entry_id":"17.10/changes/019","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)","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/025","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)","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["0859000d0","313355d68","5713ac248","9d3e094f1","becf6d269","d809b16d1"],"commit_groups":[["0859000d0","313355d68","5713ac248","9d3e094f1","becf6d269","d809b16d1"]],"commits":["5713ac248"],"cves":[],"db_id":"9efa82150808ee72d1b174825d7f47d3","html":"\u003cp\u003eAllow \u003ccode\u003eALTER INDEX ... ATTACH PARTITION\u003c/code\u003e to mark the parent index valid if appropriate (Sami Imseih) \u003ca href=\"https://postgr.es/c/5713ac248\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThere 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.\u003c/p\u003e","id":"18.4-720217f77930b818","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.","part":"changes","patch_ids":["6f61faf076a411f9a9c18c51b74befa0"],"relations":[{"evidence":{"patch_ids":["6f61faf076a411f9a9c18c51b74befa0"],"same_day":true,"statement_hash":"d56280bb59ca7a2079394584e577949d3d1706a31278203bdc18b376a97f5ff5"},"rule":2,"target":"15a0dfb907bce338c1244951e2379584","type":"equivalent"},{"evidence":{"patch_ids":["6f61faf076a411f9a9c18c51b74befa0"],"same_day":true,"statement_hash":"d56280bb59ca7a2079394584e577949d3d1706a31278203bdc18b376a97f5ff5"},"rule":2,"target":"3b47c18aac1b9d5d839c6ae4de3ae964","type":"equivalent"},{"evidence":{"patch_ids":["6f61faf076a411f9a9c18c51b74befa0"],"same_day":true,"statement_hash":"d56280bb59ca7a2079394584e577949d3d1706a31278203bdc18b376a97f5ff5"},"rule":2,"target":"73eae229fd96afa624d3ae9343724889","type":"equivalent"},{"evidence":{"patch_ids":["6f61faf076a411f9a9c18c51b74befa0"],"same_day":true,"statement_hash":"d56280bb59ca7a2079394584e577949d3d1706a31278203bdc18b376a97f5ff5"},"rule":2,"target":"ef8cca025501a2f559a921e005a2df3a","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["5713ac248"],"source_entry_id":"18.4/changes/026","source_hash":"c7fb37f05c0c507003df5df3db21d5e4b480562fdecf037cd46f08d0a5239949","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"d56280bb59ca7a2079394584e577949d3d1706a31278203bdc18b376a97f5ff5","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"},"id":"18.4-720217f77930b818","matches":[{"id":"17.10-a232240e214fd3cc","source_entry_id":"17.10/changes/020","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Allow ALTER INDEX ... ATTACH PARTITION to mark the parent index valid if appropriate","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/026","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Allow ALTER INDEX ... ATTACH PARTITION to mark the parent index valid if appropriate","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["3a35ab1d0","703fee3b2","876fa84a2","a19edb66a","c11f87b1a","c6f369e58"],"commit_groups":[["3a35ab1d0","703fee3b2","876fa84a2","a19edb66a","c11f87b1a","c6f369e58"]],"commits":["c11f87b1a"],"cves":[],"db_id":"36e2e07d71e68b4283223f19d2984e7c","html":"\u003cp\u003eFix \u003ccode\u003eALTER FOREIGN DATA WRAPPER\u003c/code\u003e to not drop the wrapper object's dependency on its handler function (Jeff Davis) \u003ca href=\"https://postgr.es/c/c11f87b1a\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.4-58699ca9b2eb6554","identity_text":"Fix ALTER FOREIGN DATA WRAPPER to not drop the wrapper object's dependency on its handler function (Jeff Davis)","part":"changes","patch_ids":["ab36c14d9b156ed146006d208e168c67"],"relations":[{"evidence":{"patch_ids":["ab36c14d9b156ed146006d208e168c67"],"same_day":true,"statement_hash":"1a75240d366859df37d3b685fc9650cc7048b3331f03f5d7f2e32b3b26bb2ef6"},"rule":2,"target":"40f08757d4fdd0da278e5767f13b1a9d","type":"equivalent"},{"evidence":{"patch_ids":["ab36c14d9b156ed146006d208e168c67"],"same_day":true,"statement_hash":"1a75240d366859df37d3b685fc9650cc7048b3331f03f5d7f2e32b3b26bb2ef6"},"rule":2,"target":"44fad7589f9dabcb24fd01bc1b9f0ef9","type":"equivalent"},{"evidence":{"patch_ids":["ab36c14d9b156ed146006d208e168c67"],"same_day":true,"statement_hash":"1a75240d366859df37d3b685fc9650cc7048b3331f03f5d7f2e32b3b26bb2ef6"},"rule":2,"target":"b31bf5bb21c7900491a09645d594ea7f","type":"equivalent"},{"evidence":{"patch_ids":["ab36c14d9b156ed146006d208e168c67"],"same_day":true,"statement_hash":"1a75240d366859df37d3b685fc9650cc7048b3331f03f5d7f2e32b3b26bb2ef6"},"rule":2,"target":"f47e2288275d1a173744e2f85b16ba59","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c11f87b1a"],"source_entry_id":"18.4/changes/028","source_hash":"eac770e06525f8446d703396de4d9a5ab15d9341327a5268ff67c532a250c968","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"1a75240d366859df37d3b685fc9650cc7048b3331f03f5d7f2e32b3b26bb2ef6","text":"Fix ALTER FOREIGN DATA WRAPPER to not drop the wrapper object's dependency on its handler function (Jeff Davis) §","title":"Fix ALTER FOREIGN DATA WRAPPER to not drop the wrapper object's dependency on its handler function"},"id":"18.4-58699ca9b2eb6554","matches":[{"id":"17.10-c4bb8ccc29a46458","source_entry_id":"17.10/changes/021","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","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/028","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","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["06e304524","34ebeb15c","54343f6f9","c7a1d5fc6","dd4069197","ff8f27d6e"],"commit_groups":[["06e304524","34ebeb15c","54343f6f9","c7a1d5fc6","dd4069197","ff8f27d6e"]],"commits":["ff8f27d6e"],"cves":[],"db_id":"e65839c47b604979321948f58b376888","html":"\u003cp\u003eDisallow making a composite type be a member of itself via a multirange (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/ff8f27d6e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWe already forbade such cases when the intermediate type is a domain, array, composite type, or range; but multiranges were overlooked.\u003c/p\u003e","id":"18.4-ccc5811ee220170a","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.","part":"changes","patch_ids":["31c00f6d7ed28a6712dcf1e113075156"],"relations":[{"evidence":{"patch_ids":["31c00f6d7ed28a6712dcf1e113075156"],"same_day":true,"statement_hash":"6b4527853dd5e8e984500173324ec598d423dfc66e71302f1bdff48a4af1e5d2"},"rule":2,"target":"aaf1253e3301e7ce01966fdecb2168ff","type":"equivalent"},{"evidence":{"patch_ids":["31c00f6d7ed28a6712dcf1e113075156"],"same_day":true,"statement_hash":"6b4527853dd5e8e984500173324ec598d423dfc66e71302f1bdff48a4af1e5d2"},"rule":2,"target":"db27ce7162c0f5f66e5e36b2b4394be0","type":"equivalent"},{"evidence":{"patch_ids":["31c00f6d7ed28a6712dcf1e113075156"],"same_day":true,"statement_hash":"6b4527853dd5e8e984500173324ec598d423dfc66e71302f1bdff48a4af1e5d2"},"rule":2,"target":"dbfa0390a811562580299aed6addef7f","type":"equivalent"},{"evidence":{"patch_ids":["31c00f6d7ed28a6712dcf1e113075156"],"same_day":true,"statement_hash":"6b4527853dd5e8e984500173324ec598d423dfc66e71302f1bdff48a4af1e5d2"},"rule":2,"target":"e0d6011d1ad1750ec99d7b452609aa5c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["ff8f27d6e"],"source_entry_id":"18.4/changes/031","source_hash":"8cc04a190a027ed7f7331686746174c2996429342f086de4aa3471e8450824e3","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"6b4527853dd5e8e984500173324ec598d423dfc66e71302f1bdff48a4af1e5d2","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"},"id":"18.4-ccc5811ee220170a","matches":[{"id":"17.10-a17faaa60c3b23db","source_entry_id":"17.10/changes/022","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Disallow making a composite type be a member of itself via a multirange","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/031","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Disallow making a composite type be a member of itself via a multirange","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["0d866282b","1bd90c887","49315de0c","6b2e091f0","6ce5c310b","d29808e35"],"commit_groups":[["0d866282b","1bd90c887","49315de0c","6b2e091f0","6ce5c310b","d29808e35"]],"commits":["49315de0c"],"cves":[],"db_id":"c5c180d0b102c66e23f3e5c67497661a","html":"\u003cp\u003eFix datum-image comparisons to be insensitive to sign-extension variations (David Rowley) \u003ca href=\"https://postgr.es/c/49315de0c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis fixes some situations that previously led to \u003cspan\u003e“\u003cspan\u003ecould not find memoization table entry\u003c/span\u003e”\u003c/span\u003e errors or wrong query results.\u003c/p\u003e","id":"18.4-4ed3df97c772ff79","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.","part":"changes","patch_ids":["8b2152dc84fbefe58a465b0d497fe197"],"relations":[{"evidence":{"patch_ids":["8b2152dc84fbefe58a465b0d497fe197"],"same_day":true,"statement_hash":"95b38df8932c40bbb6eed0884f5ec817fd4ee7218c45df42545da1f44dd8095a"},"rule":2,"target":"5cabc37ab2a14b9bb0980c3ed400e023","type":"equivalent"},{"evidence":{"patch_ids":["8b2152dc84fbefe58a465b0d497fe197"],"same_day":true,"statement_hash":"95b38df8932c40bbb6eed0884f5ec817fd4ee7218c45df42545da1f44dd8095a"},"rule":2,"target":"6de901a8850aaba4f6cb4f60757fd10b","type":"equivalent"},{"evidence":{"patch_ids":["8b2152dc84fbefe58a465b0d497fe197"],"same_day":true,"statement_hash":"95b38df8932c40bbb6eed0884f5ec817fd4ee7218c45df42545da1f44dd8095a"},"rule":2,"target":"e186e88d722a03078d4189e25842fa12","type":"equivalent"},{"evidence":{"patch_ids":["8b2152dc84fbefe58a465b0d497fe197"],"same_day":true,"statement_hash":"95b38df8932c40bbb6eed0884f5ec817fd4ee7218c45df42545da1f44dd8095a"},"rule":2,"target":"f9a962dc778922758842bad523e4e935","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["49315de0c"],"source_entry_id":"18.4/changes/032","source_hash":"3de832ddc8bf78b6182f0e1711d3c5ff5baade94f5f8eb4f9d6771b78542be2a","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"95b38df8932c40bbb6eed0884f5ec817fd4ee7218c45df42545da1f44dd8095a","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"},"id":"18.4-4ed3df97c772ff79","matches":[{"id":"17.10-0fb5ea65c461a113","source_entry_id":"17.10/changes/023","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix datum-image comparisons to be insensitive to sign-extension variations","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/032","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix datum-image comparisons to be insensitive to sign-extension variations","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["035c520db","109de35b7","3fda3e12f","622f8b530","94219a73f","a2a0060d5"],"commit_groups":[["035c520db","109de35b7","3fda3e12f","622f8b530","94219a73f","a2a0060d5"]],"commits":["035c520db"],"cves":[],"db_id":"d1a95a788ffc450fd8a8b393d2c3e55d","html":"\u003cp\u003eFix incorrect logic for hashed \u003ccode\u003eIN\u003c/code\u003e/\u003ccode\u003eNOT IN\u003c/code\u003e with non-strict equality operator (Chengpeng Yan) \u003ca href=\"https://postgr.es/c/035c520db\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e","id":"18.4-e5344bf8a6d35197","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.","part":"changes","patch_ids":["73bcd2dbc996c0415640dea74d4f247f"],"relations":[{"evidence":{"patch_ids":["73bcd2dbc996c0415640dea74d4f247f"],"same_day":true,"statement_hash":"f620e21c617639503e22ec199ea3bdfd888287e95b5e026131bfa74e2fd18e5d"},"rule":2,"target":"2a86497013a318262f46769723449b63","type":"equivalent"},{"evidence":{"patch_ids":["73bcd2dbc996c0415640dea74d4f247f"],"same_day":true,"statement_hash":"f620e21c617639503e22ec199ea3bdfd888287e95b5e026131bfa74e2fd18e5d"},"rule":2,"target":"450e4329b437178c4c67084a2ce52024","type":"equivalent"},{"evidence":{"patch_ids":["73bcd2dbc996c0415640dea74d4f247f"],"same_day":true,"statement_hash":"f620e21c617639503e22ec199ea3bdfd888287e95b5e026131bfa74e2fd18e5d"},"rule":2,"target":"6a9e4a1d32172e81ee680d6f0342ca63","type":"equivalent"},{"evidence":{"patch_ids":["73bcd2dbc996c0415640dea74d4f247f"],"same_day":true,"statement_hash":"f620e21c617639503e22ec199ea3bdfd888287e95b5e026131bfa74e2fd18e5d"},"rule":2,"target":"c26aa4cfe9a48bc8f6b4f3924802efa7","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["035c520db"],"source_entry_id":"18.4/changes/033","source_hash":"ffb794be9437535a124258dc5a5a3054bb11a3db6230d2021690f0e0220a79e0","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"f620e21c617639503e22ec199ea3bdfd888287e95b5e026131bfa74e2fd18e5d","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"},"id":"18.4-e5344bf8a6d35197","matches":[{"id":"17.10-c7e5a864f1920ba5","source_entry_id":"17.10/changes/024","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix incorrect logic for hashed IN/NOT IN with non-strict equality operator","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/033","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix incorrect logic for hashed IN/NOT IN with non-strict equality operator","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["580e7be88","8a6f08c0c","a50777680","c97a28618","e1e60f148","f60d25986"],"commit_groups":[["580e7be88","8a6f08c0c","a50777680","c97a28618","e1e60f148","f60d25986"]],"commits":["580e7be88"],"cves":[],"db_id":"606d4464f34532059b31083c8d4b85db","html":"\u003cp\u003eTruncate overly-long locale-specific numeric symbols in \u003ccode\u003eto_char()\u003c/code\u003e (Tom Lane) \u003ca href=\"https://postgr.es/c/580e7be88\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf 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.\u003c/p\u003e","id":"18.4-695d3a73d2ecfb3e","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.","part":"changes","patch_ids":["a55b3cc17f0905d7ae426fd181a6dfc3"],"relations":[{"evidence":{"patch_ids":["a55b3cc17f0905d7ae426fd181a6dfc3"],"same_day":true,"statement_hash":"faa5531634d9cdfe864f4512cf61a4628efe72bf20a627237eac6e0fc2e723b0"},"rule":2,"target":"07daab7dbccbfcc34db05980b3a74098","type":"equivalent"},{"evidence":{"patch_ids":["a55b3cc17f0905d7ae426fd181a6dfc3"],"same_day":true,"statement_hash":"faa5531634d9cdfe864f4512cf61a4628efe72bf20a627237eac6e0fc2e723b0"},"rule":2,"target":"29acc0aac3cc6b0ee03ac19b4559887d","type":"equivalent"},{"evidence":{"patch_ids":["a55b3cc17f0905d7ae426fd181a6dfc3"],"same_day":true,"statement_hash":"faa5531634d9cdfe864f4512cf61a4628efe72bf20a627237eac6e0fc2e723b0"},"rule":2,"target":"7477baaf42cc60c640f8610e0225343b","type":"equivalent"},{"evidence":{"patch_ids":["a55b3cc17f0905d7ae426fd181a6dfc3"],"same_day":true,"statement_hash":"faa5531634d9cdfe864f4512cf61a4628efe72bf20a627237eac6e0fc2e723b0"},"rule":2,"target":"da89f430482b72634ad3d2f296bb5a93","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["580e7be88"],"source_entry_id":"18.4/changes/034","source_hash":"70eb34f88d8f608012378c0560ddedc3d3a33faefc96ac07099ec4ab95e051f1","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"faa5531634d9cdfe864f4512cf61a4628efe72bf20a627237eac6e0fc2e723b0","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()"},"id":"18.4-695d3a73d2ecfb3e","matches":[{"id":"17.10-ead7a4370e3d50c0","source_entry_id":"17.10/changes/025","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Truncate overly-long locale-specific numeric symbols in to_char()","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/034","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Truncate overly-long locale-specific numeric symbols in to_char()","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["00c6e0819","0b196d3db","17f72e037","21a24d709","42383d32d","6cae0c2bd","844bb90d4","a5426dbf8","c2bfeb3bb","d7970e7e9","ea5f0d176","f852c9093"],"commit_groups":[["00c6e0819","0b196d3db","21a24d709","42383d32d","d7970e7e9","ea5f0d176"],["17f72e037","6cae0c2bd","844bb90d4","a5426dbf8","c2bfeb3bb","f852c9093"]],"commits":["00c6e0819","c2bfeb3bb"],"cves":[],"db_id":"12f322f4feb75f55804ad196b114a9d6","html":"\u003cp\u003ePrevent buffer overruns when parsing an affix file for an \u003ccode\u003eIspell\u003c/code\u003e dictionary (Tom Lane) \u003ca href=\"https://postgr.es/c/00c6e0819\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/c2bfeb3bb\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA 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.\u003c/p\u003e","id":"18.4-e6587b3cd0787b2e","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.","part":"changes","patch_ids":["3b2347be1395aa44c1c6ae6a8fa24149","fb61cc9fc6ef6ecc94c4f87d31a648bd"],"relations":[{"evidence":{"patch_ids":["3b2347be1395aa44c1c6ae6a8fa24149","fb61cc9fc6ef6ecc94c4f87d31a648bd"],"same_day":true,"statement_hash":"6442ebdc43f39cc7a336c76cc8f8bcdfb68cc5683190ee35457bd8a1cd9e22d8"},"rule":2,"target":"2b5095497f4832976becc4b644155c51","type":"equivalent"},{"evidence":{"patch_ids":["3b2347be1395aa44c1c6ae6a8fa24149","fb61cc9fc6ef6ecc94c4f87d31a648bd"],"same_day":true,"statement_hash":"6442ebdc43f39cc7a336c76cc8f8bcdfb68cc5683190ee35457bd8a1cd9e22d8"},"rule":2,"target":"5f8b6d695a4f9576cfb99b263e2e4ff7","type":"equivalent"},{"evidence":{"patch_ids":["3b2347be1395aa44c1c6ae6a8fa24149","fb61cc9fc6ef6ecc94c4f87d31a648bd"],"same_day":true,"statement_hash":"6442ebdc43f39cc7a336c76cc8f8bcdfb68cc5683190ee35457bd8a1cd9e22d8"},"rule":2,"target":"cd403cd225ef88fed48df9f593dd683b","type":"equivalent"},{"evidence":{"patch_ids":["3b2347be1395aa44c1c6ae6a8fa24149","fb61cc9fc6ef6ecc94c4f87d31a648bd"],"same_day":true,"statement_hash":"6442ebdc43f39cc7a336c76cc8f8bcdfb68cc5683190ee35457bd8a1cd9e22d8"},"rule":2,"target":"f2129c1b029d4e186640295ff2fd808d","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["00c6e0819","c2bfeb3bb"],"source_entry_id":"18.4/changes/035","source_hash":"26b8c98f5f285541175bbe791e9adc08dd729f507c8744e2c34ae51d9dfb43ea","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"6442ebdc43f39cc7a336c76cc8f8bcdfb68cc5683190ee35457bd8a1cd9e22d8","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"},"id":"18.4-e6587b3cd0787b2e","matches":[{"id":"17.10-666b81e0c79b2b28","source_entry_id":"17.10/changes/026","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Prevent buffer overruns when parsing an affix file for an Ispell dictionary","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/035","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Prevent buffer overruns when parsing an affix file for an Ispell dictionary","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["0fe032e6a","305cf0df0","4da71fc37","8b6c89e37","bfc7dff26","f8736f8bc"],"commit_groups":[["0fe032e6a","305cf0df0","4da71fc37","8b6c89e37","bfc7dff26","f8736f8bc"]],"commits":["bfc7dff26"],"cves":[],"db_id":"511c913495519e0301f1fb895b89e0e3","html":"\u003cp\u003eGuard against integer overflow in calculations of frame start and end positions for window aggregates (Richard Guo) \u003ca href=\"https://postgr.es/c/bfc7dff26\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eVery large user-specified offsets (close to INT64_MAX) could result in errors or incorrect query results.\u003c/p\u003e","id":"18.4-e679f36c64f131bf","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.","part":"changes","patch_ids":["55f185c77388b5ccf5f79078a7a19b0b"],"relations":[{"evidence":{"patch_ids":["55f185c77388b5ccf5f79078a7a19b0b"],"same_day":true,"statement_hash":"84aa1ad98df37853c6497eff68ec71c4a468e09bd91604bc168bf3a8ad45d544"},"rule":2,"target":"8ad5f4df6d3f1b7115577a0c720eb3e0","type":"equivalent"},{"evidence":{"patch_ids":["55f185c77388b5ccf5f79078a7a19b0b"],"same_day":true,"statement_hash":"84aa1ad98df37853c6497eff68ec71c4a468e09bd91604bc168bf3a8ad45d544"},"rule":2,"target":"9a742821f3f95e4a90a5c8c342890d50","type":"equivalent"},{"evidence":{"patch_ids":["55f185c77388b5ccf5f79078a7a19b0b"],"same_day":true,"statement_hash":"84aa1ad98df37853c6497eff68ec71c4a468e09bd91604bc168bf3a8ad45d544"},"rule":2,"target":"cac7bd4fb899dfb735baa61da9c859ec","type":"equivalent"},{"evidence":{"patch_ids":["55f185c77388b5ccf5f79078a7a19b0b"],"same_day":true,"statement_hash":"84aa1ad98df37853c6497eff68ec71c4a468e09bd91604bc168bf3a8ad45d544"},"rule":2,"target":"f1cd95144d4553602b7e2fbfe36961ad","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["bfc7dff26"],"source_entry_id":"18.4/changes/036","source_hash":"7cc0adb14be7a94e57f2517573a111a3e3ebe1c324a0215381ea483c66ba2a2b","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"84aa1ad98df37853c6497eff68ec71c4a468e09bd91604bc168bf3a8ad45d544","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"},"id":"18.4-e679f36c64f131bf","matches":[{"id":"17.10-9cc0aae20d353dbd","source_entry_id":"17.10/changes/027","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","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/036","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","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["14bf2c39e","6582010c8","bb959269e","d6c9432cb"],"commit_groups":[["14bf2c39e","6582010c8","bb959269e","d6c9432cb"]],"commits":["14bf2c39e"],"cves":[],"db_id":"723a8eeb14f51a9627e04c54cff2c321","html":"\u003cp\u003eFix \u003ccode\u003earray_agg_array_combine()\u003c/code\u003e to combine the arrays' null bitmaps correctly (Dmytro Astapov) \u003ca href=\"https://postgr.es/c/14bf2c39e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis mistake resulted in sometimes-incorrect output from parallelized \u003ccode\u003earray_agg(anyarray)\u003c/code\u003e calculations.\u003c/p\u003e","id":"18.4-468cc4bcd201b1ba","identity_text":"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.","part":"changes","patch_ids":["ea7de144946d1e8d4f970b72ca97aad3"],"relations":[{"evidence":{"patch_ids":["ea7de144946d1e8d4f970b72ca97aad3"],"same_day":true,"statement_hash":"3153d0ad054c1a724bee8e6bdd93263c76849c422ce44c5776bb015aec005d04"},"rule":2,"target":"0e5d5bedebe61a4b8b996f87006ba93b","type":"equivalent"},{"evidence":{"patch_ids":["ea7de144946d1e8d4f970b72ca97aad3"],"same_day":true,"statement_hash":"3153d0ad054c1a724bee8e6bdd93263c76849c422ce44c5776bb015aec005d04"},"rule":2,"target":"a8336f214d5ae7c6da31f007fe97cf91","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["14bf2c39e"],"source_entry_id":"18.4/changes/037","source_hash":"f70440a1b0650303bc8248e82662915b1205d9d43392aa926cc38e81d547dafd","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"3153d0ad054c1a724bee8e6bdd93263c76849c422ce44c5776bb015aec005d04","text":"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.","title":"Fix array_agg_array_combine() to combine the arrays' null bitmaps correctly"},"id":"18.4-468cc4bcd201b1ba","matches":[{"id":"17.10-62d51a1802de9407","source_entry_id":"17.10/changes/028","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix array_agg_array_combine() to combine the arrays' null bitmaps correctly","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/037","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix array_agg_array_combine() to combine the arrays' null bitmaps correctly","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["3b35c10a4","5499be332","5941e7f09","6cb307251"],"commit_groups":[["3b35c10a4","5499be332","5941e7f09","6cb307251"]],"commits":["6cb307251"],"cves":[],"db_id":"7fde099d3089697de30b435de5e86e2c","html":"\u003cp\u003eRetry \u003ccode\u003esync_file_range()\u003c/code\u003e if it returns error code \u003ccode\u003eEINTR\u003c/code\u003e (DaeMyung Kang) \u003ca href=\"https://postgr.es/c/6cb307251\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.4-6abb19c703f2cc3c","identity_text":"Retry sync_file_range() if it returns error code EINTR (DaeMyung Kang)","part":"changes","patch_ids":["6860aa5d70c2979dafc25bb7868b4ebf"],"relations":[{"evidence":{"patch_ids":["6860aa5d70c2979dafc25bb7868b4ebf"],"same_day":true,"statement_hash":"5956c28ffd0a101c20228e6e7f9aced284c8ed83dedde4d57ecb4ad6f634b225"},"rule":2,"target":"263733ae017f01e103baa9c76806929c","type":"equivalent"},{"evidence":{"patch_ids":["6860aa5d70c2979dafc25bb7868b4ebf"],"same_day":true,"statement_hash":"5956c28ffd0a101c20228e6e7f9aced284c8ed83dedde4d57ecb4ad6f634b225"},"rule":2,"target":"2d88dc837a682f6290290ff2f8ed8b78","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["6cb307251"],"source_entry_id":"18.4/changes/038","source_hash":"ee9d1c2a9ea475f67bffa117fae0e8b302f29be5558460fa04d6f83f4d0207a5","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"5956c28ffd0a101c20228e6e7f9aced284c8ed83dedde4d57ecb4ad6f634b225","text":"Retry sync_file_range() if it returns error code EINTR (DaeMyung Kang) §","title":"Retry sync_file_range() if it returns error code EINTR"},"id":"18.4-6abb19c703f2cc3c","matches":[{"id":"17.10-9fc5c83ef66b127c","source_entry_id":"17.10/changes/029","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Retry sync_file_range() if it returns error code EINTR","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/038","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Retry sync_file_range() if it returns error code EINTR","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["80156cee0","a4fefb3e0","b081c5b07","c6d3f0585","c7cdcbd3e"],"commit_groups":[["80156cee0","a4fefb3e0","b081c5b07","c6d3f0585","c7cdcbd3e"]],"commits":["b081c5b07"],"cves":[],"db_id":"388698576be55b507a9b7abb256a6450","html":"\u003cp\u003eFix incorrect behavior of \u003ccode\u003epg_stat_reset_single_table_counters()\u003c/code\u003e on a shared catalog (Chao Li) \u003ca href=\"https://postgr.es/c/b081c5b07\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSuch cases had a side-effect of resetting the current database's \u003ccode\u003estat_reset_timestamp\u003c/code\u003e, which was unintended.\u003c/p\u003e","id":"18.4-58b13d376507a808","identity_text":"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.","part":"changes","patch_ids":["236f11c0f7cc166c8c1135c864e37524"],"relations":[{"evidence":{"patch_ids":["236f11c0f7cc166c8c1135c864e37524"],"same_day":true,"statement_hash":"fe3dc0ad7d2fbda95b8fb3c33b60666a7ab7a47f2d3398dd4e2a9cb2ef4c7467"},"rule":2,"target":"09d4f3d68a99c0eb46beb34f51959dbd","type":"equivalent"},{"evidence":{"patch_ids":["236f11c0f7cc166c8c1135c864e37524"],"same_day":true,"statement_hash":"fe3dc0ad7d2fbda95b8fb3c33b60666a7ab7a47f2d3398dd4e2a9cb2ef4c7467"},"rule":2,"target":"6e037b0ab13babc0a57068f559d9947e","type":"equivalent"},{"evidence":{"patch_ids":["236f11c0f7cc166c8c1135c864e37524"],"same_day":true,"statement_hash":"fe3dc0ad7d2fbda95b8fb3c33b60666a7ab7a47f2d3398dd4e2a9cb2ef4c7467"},"rule":2,"target":"78582be8ad9510fda737b311e1159d46","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b081c5b07"],"source_entry_id":"18.4/changes/039","source_hash":"842f38ccff2eac6c788b7628a6eeaa37293ee99c0a37875902dca665146126b5","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"fe3dc0ad7d2fbda95b8fb3c33b60666a7ab7a47f2d3398dd4e2a9cb2ef4c7467","text":"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.","title":"Fix incorrect behavior of pg_stat_reset_single_table_counters() on a shared catalog"},"id":"18.4-58b13d376507a808","matches":[{"id":"17.10-8b259c7f97a0d7e9","source_entry_id":"17.10/changes/030","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix incorrect behavior of pg_stat_reset_single_table_counters() on a shared catalog","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/039","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix incorrect behavior of pg_stat_reset_single_table_counters() on a shared catalog","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["090c4297e","44c8dc280","88d7fdcc9","d052f6c7d"],"commit_groups":[["090c4297e","44c8dc280","88d7fdcc9","d052f6c7d"]],"commits":["44c8dc280"],"cves":[],"db_id":"980b17cc0e380660feb5723048978d0c","html":"\u003cp\u003eUpdate activity statistics when a parallel apply worker is idle (Zhijie Hou) \u003ca href=\"https://postgr.es/c/44c8dc280\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, statistics from a recently-completed transaction might go unreported for long intervals, particularly if the workload is light.\u003c/p\u003e","id":"18.4-c51eded9a9ad369c","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.","part":"changes","patch_ids":["2d9114e9de0545265b46f9271e79774e"],"relations":[{"evidence":{"patch_ids":["2d9114e9de0545265b46f9271e79774e"],"same_day":true,"statement_hash":"1425951cf41b73475715e34b86444749dadef32d8dd753ca05fb84c5dcab7db0"},"rule":2,"target":"677b87203fcf8da98790d6378484a333","type":"equivalent"},{"evidence":{"patch_ids":["2d9114e9de0545265b46f9271e79774e"],"same_day":true,"statement_hash":"1425951cf41b73475715e34b86444749dadef32d8dd753ca05fb84c5dcab7db0"},"rule":2,"target":"96a3e2b2d17bbc2072d29a84e39fe9f0","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["44c8dc280"],"source_entry_id":"18.4/changes/040","source_hash":"0f38a0c7b2916f63a17b15949ea31d283036437e30490f8550f9eee25b66836c","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"1425951cf41b73475715e34b86444749dadef32d8dd753ca05fb84c5dcab7db0","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"},"id":"18.4-c51eded9a9ad369c","matches":[{"id":"17.10-ab22f7a64370fbd6","source_entry_id":"17.10/changes/031","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Update activity statistics when a parallel apply worker is idle","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/040","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Update activity statistics when a parallel apply worker is idle","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["13e20d1c9","77d0e82e5","93ed18720"],"commit_groups":[["13e20d1c9","77d0e82e5","93ed18720"]],"commits":["13e20d1c9"],"cves":[],"db_id":"8b93ba333f257971520839fdfb923dc8","html":"\u003cp\u003eFix \u003cspan\u003e“\u003cspan\u003eno relation entry for relid 0\u003c/span\u003e”\u003c/span\u003e failure while estimating array lengths in set operations (Tender Wang) \u003ca href=\"https://postgr.es/c/13e20d1c9\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.4-9a9061bf537ff043","identity_text":"Fix no relation entry for relid 0 failure while estimating array lengths in set operations (Tender Wang)","part":"changes","patch_ids":["564821c3480587e28f1a951776d143da"],"relations":[{"evidence":{"patch_ids":["564821c3480587e28f1a951776d143da"],"same_day":true,"statement_hash":"79d2c12d4a24236694523bc4108c4ef1ad8487e654635a5140572e534f35ca67"},"rule":2,"target":"767acd748e88add4e0b136661b09348d","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["13e20d1c9"],"source_entry_id":"18.4/changes/041","source_hash":"ecd4d9794c67edfc061e72cc6ae874e0b3d09d0e7aae0513148948a05a1926a2","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"79d2c12d4a24236694523bc4108c4ef1ad8487e654635a5140572e534f35ca67","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"},"id":"18.4-9a9061bf537ff043","matches":[{"id":"17.10-b34c916fe548b623","source_entry_id":"17.10/changes/032","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","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/041","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","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["2b5ba2a0a","c05c3baf1","c3e436b1c","c88ad3a21","de32a01e7","e630f65d0"],"commit_groups":[["2b5ba2a0a","c05c3baf1","c3e436b1c","c88ad3a21","de32a01e7","e630f65d0"]],"commits":["c3e436b1c"],"cves":[],"db_id":"0ae0f8c53b17ca5f253bbab76a0d9b74","html":"\u003cp\u003eFix buffer overread when \u003ccode\u003epglz_decompress()\u003c/code\u003e receives corrupt input (Andrew Dunstan) \u003ca href=\"https://postgr.es/c/c3e436b1c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIt was possible to read a few bytes past the end of the input, which in very unlucky cases might cause a crash.\u003c/p\u003e","id":"18.4-1b7a6be51f8649d8","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.","part":"changes","patch_ids":["c0bb5d07bdfbe114b7578587383a80fa"],"relations":[{"evidence":{"patch_ids":["c0bb5d07bdfbe114b7578587383a80fa"],"same_day":true,"statement_hash":"bd7b2a40bb8d7d7798cf8ecb76df72f44a9455b09e9d2f6b36769b9fa697b84d"},"rule":2,"target":"31b4e32fc9a04113a1aeaa4d2e794a7e","type":"equivalent"},{"evidence":{"patch_ids":["c0bb5d07bdfbe114b7578587383a80fa"],"same_day":true,"statement_hash":"bd7b2a40bb8d7d7798cf8ecb76df72f44a9455b09e9d2f6b36769b9fa697b84d"},"rule":2,"target":"7d77c3cf4d2df5b2b05bab302e7d6447","type":"equivalent"},{"evidence":{"patch_ids":["c0bb5d07bdfbe114b7578587383a80fa"],"same_day":true,"statement_hash":"bd7b2a40bb8d7d7798cf8ecb76df72f44a9455b09e9d2f6b36769b9fa697b84d"},"rule":2,"target":"8f0710244d42d6ab314f2ef4a78fa91d","type":"equivalent"},{"evidence":{"patch_ids":["c0bb5d07bdfbe114b7578587383a80fa"],"same_day":true,"statement_hash":"bd7b2a40bb8d7d7798cf8ecb76df72f44a9455b09e9d2f6b36769b9fa697b84d"},"rule":2,"target":"f313199e743d40f3a6df92ac0387bcfa","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c3e436b1c"],"source_entry_id":"18.4/changes/042","source_hash":"2622fb1e0384f9134f8addee155a77c817d66d712d29b1d6e4192715763b3594","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"bd7b2a40bb8d7d7798cf8ecb76df72f44a9455b09e9d2f6b36769b9fa697b84d","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"},"id":"18.4-1b7a6be51f8649d8","matches":[{"id":"17.10-fc2a0ba457a12efa","source_entry_id":"17.10/changes/033","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix buffer overread when pglz_decompress() receives corrupt input","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/042","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix buffer overread when pglz_decompress() receives corrupt input","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["2478bd5db","2e373785e","3e4955630"],"commit_groups":[["2478bd5db","2e373785e","3e4955630"]],"commits":["3e4955630"],"cves":[],"db_id":"19c77cbe8cf7f7f6073b8df365b35790","html":"\u003cp\u003eFix incremental JSON parser's handling of numeric tokens that cross input buffer boundaries (Andrew Dunstan) \u003ca href=\"https://postgr.es/c/3e4955630\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIt was possible to accept an incorrectly-formatted number, leading to failures later.\u003c/p\u003e","id":"18.4-dd2acc7c0ea39340","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.","part":"changes","patch_ids":["3a87b59bc06c42cccbaad53a59170a0f"],"relations":[{"evidence":{"patch_ids":["3a87b59bc06c42cccbaad53a59170a0f"],"same_day":true,"statement_hash":"e510b6a330131e0a9e306a9599eda0558466f19ce69118716f8d3a5ac91b7463"},"rule":2,"target":"56aacc58e4b3c19869652bc7bccc257f","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["3e4955630"],"source_entry_id":"18.4/changes/043","source_hash":"7f354a831bb7d2c88088a9e7dbc4aedf98fa61903915939d634cc0d68b63f18c","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"e510b6a330131e0a9e306a9599eda0558466f19ce69118716f8d3a5ac91b7463","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"},"id":"18.4-dd2acc7c0ea39340","matches":[{"id":"17.10-4d205143d096f8a7","source_entry_id":"17.10/changes/034","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","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/043","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","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["076bc57fa","9540c0e5d","ffc226ab6"],"commit_groups":[["076bc57fa","9540c0e5d","ffc226ab6"]],"commits":["9540c0e5d"],"cves":[],"db_id":"53b7f65c3e08f9341b47945f095569e8","html":"\u003cp\u003ePrevent bloating relation visibility maps during restore of an incremental backup (Robert Haas) \u003ca href=\"https://postgr.es/c/9540c0e5d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eRestore 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.\u003c/p\u003e","id":"18.4-7eaea7144baecfd7","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.","part":"changes","patch_ids":["738fd594a90796c809e728fbc5651d22"],"relations":[{"evidence":{"patch_ids":["738fd594a90796c809e728fbc5651d22"],"same_day":true,"statement_hash":"8be561d5ad13698eca7d90b5fd9fbde1028f705a3031ab9e786774f2c9f7b3a2"},"rule":2,"target":"8d78dd5d30d4094d87fbfc3de7307fc9","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["9540c0e5d"],"source_entry_id":"18.4/changes/044","source_hash":"a2095c132a2c13d2446246bda6509150086aa1af77f74a38e9c9a8a7a9001a44","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"8be561d5ad13698eca7d90b5fd9fbde1028f705a3031ab9e786774f2c9f7b3a2","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"},"id":"18.4-7eaea7144baecfd7","matches":[{"id":"17.10-1a6869f33820ce4a","source_entry_id":"17.10/changes/035","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Prevent bloating relation visibility maps during restore of an incremental backup","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/044","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Prevent bloating relation visibility maps during restore of an incremental backup","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["03c4f243e","9dda30dd3","dbf217c1c"],"commit_groups":[["03c4f243e","9dda30dd3","dbf217c1c"]],"commits":["03c4f243e"],"cves":[],"db_id":"eedc842000f52b63d80fc16df2a3a7fa","html":"\u003cp\u003eUse C collation, not the database's default collation, in catalog cache lookups on text columns (Jeff Davis) \u003ca href=\"https://postgr.es/c/03c4f243e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis avoids failures in edge cases such as physical replication startup, where there is no identified database so that a default collation cannot be determined.\u003c/p\u003e","id":"18.4-3a216fc3a56d1f2e","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.","part":"changes","patch_ids":["1a030429f091c1d56d52205c2930f3cc"],"relations":[{"evidence":{"patch_ids":["1a030429f091c1d56d52205c2930f3cc"],"same_day":true,"statement_hash":"c93618f8a7ca56819cbbb9cf9df80953c6fe150819de3e1e7fad58e879a5f52f"},"rule":2,"target":"b4e242e2dfdaddd1a84c10f08ab6fdb6","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["03c4f243e"],"source_entry_id":"18.4/changes/045","source_hash":"ca6290e5a73104a965da328f8ab392537a5d88f2b104870bd144639e79684eee","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"c93618f8a7ca56819cbbb9cf9df80953c6fe150819de3e1e7fad58e879a5f52f","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"},"id":"18.4-3a216fc3a56d1f2e","matches":[{"id":"17.10-a4c0aebef3a26164","source_entry_id":"17.10/changes/036","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","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/045","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","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["1362bc33e","15910b1c3","4bed04d39","586f4266f","58c1188a3","94efd308b","acf49bfed","db93032a7"],"commit_groups":[["1362bc33e","4bed04d39","94efd308b"],["15910b1c3","58c1188a3","db93032a7"],["586f4266f","acf49bfed"]],"commits":["58c1188a3","94efd308b","acf49bfed"],"cves":[],"db_id":"e197fe7e68af6fc16360be64080650fb","html":"\u003cp\u003ePrevent stuck slotsync worker processes from blocking promotion of a standby server (Nisha Moond, Ajin Cherian) \u003ca href=\"https://postgr.es/c/58c1188a3\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/acf49bfed\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/94efd308b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA worker process that was vainly waiting for a response from the primary would delay promotion for an unreasonable amount of time.\u003c/p\u003e","id":"18.4-401593c891e36279","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.","part":"changes","patch_ids":["0631393988a6e439ca6c21edde5e08d0","d9eacc799b9f25f84495940918c9855b","f0a73f0938081885d684993c67dca652"],"relations":[{"evidence":{"patch_ids":["0631393988a6e439ca6c21edde5e08d0","d9eacc799b9f25f84495940918c9855b","f0a73f0938081885d684993c67dca652"],"same_day":true,"statement_hash":"86bf0b738194ea614f01e7178f35891e27741d55257e8b4157bf2182cf0b6509"},"rule":2,"target":"299696a41fbafef0ba66bb25a5daba56","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["58c1188a3","94efd308b","acf49bfed"],"source_entry_id":"18.4/changes/046","source_hash":"aaebffec95e506635382bd0e94196d1f16aaf5d2ac954c07ff39f53f2221a160","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"86bf0b738194ea614f01e7178f35891e27741d55257e8b4157bf2182cf0b6509","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"},"id":"18.4-401593c891e36279","matches":[{"id":"17.10-f9ca5e51b9e70665","source_entry_id":"17.10/changes/037","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Prevent stuck slotsync worker processes from blocking promotion of a standby server","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/046","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Prevent stuck slotsync worker processes from blocking promotion of a standby server","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["540fe8fb5","85c17f612","91741b7cb"],"commit_groups":[["540fe8fb5","85c17f612","91741b7cb"]],"commits":["540fe8fb5"],"cves":[],"db_id":"695bd513323417fe3250f7a82dc60ff8","html":"\u003cp\u003eFix excessive log output from idle slotsync worker processes (Zhijie Hou) \u003ca href=\"https://postgr.es/c/540fe8fb5\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.4-59479740d5b1c42c","identity_text":"Fix excessive log output from idle slotsync worker processes (Zhijie Hou)","part":"changes","patch_ids":["fc452e68c97468e4711e1e83f06f17af"],"relations":[{"evidence":{"patch_ids":["fc452e68c97468e4711e1e83f06f17af"],"same_day":true,"statement_hash":"2a2af3205a99361da43475c5da46b1c66376f789f13a1c2ee0f23624cbb849a4"},"rule":2,"target":"823fb36d471b0ef6060bc9363c89e12c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["540fe8fb5"],"source_entry_id":"18.4/changes/047","source_hash":"56513a1c633ce8a47b2cb0bde6139eca65a3e5251dbaeea476d9f7cd3c3265ca","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"2a2af3205a99361da43475c5da46b1c66376f789f13a1c2ee0f23624cbb849a4","text":"Fix excessive log output from idle slotsync worker processes (Zhijie Hou) §","title":"Fix excessive log output from idle slotsync worker processes"},"id":"18.4-59479740d5b1c42c","matches":[{"id":"17.10-f979cb3196409f3b","source_entry_id":"17.10/changes/038","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix excessive log output from idle slotsync worker processes","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/047","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix excessive log output from idle slotsync worker processes","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["1f5b6a5e5","59c139d53","739477345","7cd23aad2","811f3263a","adb7873bb"],"commit_groups":[["1f5b6a5e5","59c139d53","739477345","7cd23aad2","811f3263a","adb7873bb"]],"commits":["adb7873bb"],"cves":[],"db_id":"22646346c25b1d7d6643cd61087c0609","html":"\u003cp\u003eEnsure that tuplestore data structures are internally consistent even after an error (Tom Lane) \u003ca href=\"https://postgr.es/c/adb7873bb\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe code was previously careless about this, which is fine most of the time but is problematic for the tuplestore backing a \u003ccode\u003eWITH HOLD\u003c/code\u003e 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.\u003c/p\u003e","id":"18.4-2024d132beedef06","identity_text":"Ensure that tuplestore data structures are internally consistent even after an error (Tom Lane) The 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.","part":"changes","patch_ids":["d5b0ad2ecd5b574958d883210df966b5"],"relations":[{"evidence":{"patch_ids":["d5b0ad2ecd5b574958d883210df966b5"],"same_day":true,"statement_hash":"01eb563295b1dc8cc7ddc77849a3cd6efe3a0ce73c200fb3aca3280239db80d3"},"rule":2,"target":"4bce4b0b77897bdec13cc979f743e388","type":"equivalent"},{"evidence":{"patch_ids":["d5b0ad2ecd5b574958d883210df966b5"],"same_day":true,"statement_hash":"01eb563295b1dc8cc7ddc77849a3cd6efe3a0ce73c200fb3aca3280239db80d3"},"rule":2,"target":"7a6f561d7317700ce105d1b02cced73b","type":"equivalent"},{"evidence":{"patch_ids":["d5b0ad2ecd5b574958d883210df966b5"],"same_day":true,"statement_hash":"01eb563295b1dc8cc7ddc77849a3cd6efe3a0ce73c200fb3aca3280239db80d3"},"rule":2,"target":"7ecc452c7ec1d9dbb53c7da2da6ff0fb","type":"equivalent"},{"evidence":{"patch_ids":["d5b0ad2ecd5b574958d883210df966b5"],"same_day":true,"statement_hash":"01eb563295b1dc8cc7ddc77849a3cd6efe3a0ce73c200fb3aca3280239db80d3"},"rule":2,"target":"b3f61452eefb1fe329d018b311fb82a7","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["adb7873bb"],"source_entry_id":"18.4/changes/048","source_hash":"5bdc06715aff25d6288e43807c49e045e2800e2d74a17dbcb33513012e39cf63","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"01eb563295b1dc8cc7ddc77849a3cd6efe3a0ce73c200fb3aca3280239db80d3","text":"Ensure that tuplestore data structures are internally consistent even after an error (Tom Lane) § The 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.","title":"Ensure that tuplestore data structures are internally consistent even after an error"},"id":"18.4-2024d132beedef06","matches":[{"id":"17.10-c10485892a0cc1b6","source_entry_id":"17.10/changes/039","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Ensure that tuplestore data structures are internally consistent even after an error","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/048","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Ensure that tuplestore data structures are internally consistent even after an error","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["246c296f0","98e96e579","bf7ecf353","eef1ba704","f42105001","fdce5de55"],"commit_groups":[["246c296f0","98e96e579","bf7ecf353","eef1ba704","f42105001","fdce5de55"]],"commits":["98e96e579"],"cves":[],"db_id":"bf6218705be170d40b881423fbe0391f","html":"\u003cp\u003eFix premature NULL lag reporting in \u003ccode\u003epg_stat_replication\u003c/code\u003e (Shinya Kato) \u003ca href=\"https://postgr.es/c/98e96e579\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe lag columns frequently read as NULL even while replication activity was happening.\u003c/p\u003e","id":"18.4-8789ffc8666b33f9","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.","part":"changes","patch_ids":["7704c6b94c92f272f76de1954c53eb5b"],"relations":[{"evidence":{"patch_ids":["7704c6b94c92f272f76de1954c53eb5b"],"same_day":true,"statement_hash":"bcd10a6c1d43f2b961925210744b26778b15baa46851120a0a4df4d6146ed920"},"rule":2,"target":"5851dbb38f0eb77c8633d934a8c81fbc","type":"equivalent"},{"evidence":{"patch_ids":["7704c6b94c92f272f76de1954c53eb5b"],"same_day":true,"statement_hash":"bcd10a6c1d43f2b961925210744b26778b15baa46851120a0a4df4d6146ed920"},"rule":2,"target":"65eb4d53da31a74e1d2b5ae72a4b3f98","type":"equivalent"},{"evidence":{"patch_ids":["7704c6b94c92f272f76de1954c53eb5b"],"same_day":true,"statement_hash":"bcd10a6c1d43f2b961925210744b26778b15baa46851120a0a4df4d6146ed920"},"rule":2,"target":"8f5d9efb9934b105d69fddf797f34e0b","type":"equivalent"},{"evidence":{"patch_ids":["7704c6b94c92f272f76de1954c53eb5b"],"same_day":true,"statement_hash":"bcd10a6c1d43f2b961925210744b26778b15baa46851120a0a4df4d6146ed920"},"rule":2,"target":"915ec8a085b4d90eb64720a431768f9b","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["98e96e579"],"source_entry_id":"18.4/changes/050","source_hash":"eaaba4794adf71b00e0e8b48b6411961a27dddf2c7f6f550898554fd54f50dad","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"bcd10a6c1d43f2b961925210744b26778b15baa46851120a0a4df4d6146ed920","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"},"id":"18.4-8789ffc8666b33f9","matches":[{"id":"17.10-aef7dca4bced6a82","source_entry_id":"17.10/changes/040","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix premature NULL lag reporting in pg_stat_replication","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/050","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix premature NULL lag reporting in pg_stat_replication","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["4f4025eac","5b3f63a1b","6ef36bb35","b1f14c967","c0ffc725f","ce06b5740"],"commit_groups":[["4f4025eac","5b3f63a1b","6ef36bb35","b1f14c967","c0ffc725f","ce06b5740"]],"commits":["5b3f63a1b"],"cves":[],"db_id":"7f24f05678451ef9707b5c36a7e8d868","html":"\u003cp\u003eAvoid rare flush failure when working with non-WAL-logged GiST indexes (Tomas Vondra) \u003ca href=\"https://postgr.es/c/5b3f63a1b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA non-logged GiST index could nonetheless sometimes produce \u003cspan\u003e“\u003cspan\u003exlog flush request \u003cem\u003e\u003ccode\u003en/nnnn\u003c/code\u003e\u003c/em\u003e is not satisfied\u003c/span\u003e”\u003c/span\u003e errors, due to incorrect selection of a \u003cspan\u003e“\u003cspan\u003efake LSN\u003c/span\u003e”\u003c/span\u003e to represent an insertion point.\u003c/p\u003e","id":"18.4-7270a57d5bd56fee","identity_text":"Avoid rare flush failure when working with non-WAL-logged GiST indexes (Tomas Vondra) A 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.","part":"changes","patch_ids":["1219f2eae7af870fcd0ca6d917389cce"],"relations":[{"evidence":{"patch_ids":["1219f2eae7af870fcd0ca6d917389cce"],"same_day":true,"statement_hash":"d11afd4ede0aa409767b589a5b5e9dcb340b6c781cc05a9ff7edfd8ae5178fd1"},"rule":2,"target":"722f27b43d438fc0b96acc89768d5c59","type":"equivalent"},{"evidence":{"patch_ids":["1219f2eae7af870fcd0ca6d917389cce"],"same_day":true,"statement_hash":"d11afd4ede0aa409767b589a5b5e9dcb340b6c781cc05a9ff7edfd8ae5178fd1"},"rule":2,"target":"83b71f6a6d871542c65ada24311dc7eb","type":"equivalent"},{"evidence":{"patch_ids":["1219f2eae7af870fcd0ca6d917389cce"],"same_day":true,"statement_hash":"d11afd4ede0aa409767b589a5b5e9dcb340b6c781cc05a9ff7edfd8ae5178fd1"},"rule":2,"target":"e347189d3e54dada6ed98ca299883a76","type":"equivalent"},{"evidence":{"patch_ids":["1219f2eae7af870fcd0ca6d917389cce"],"same_day":true,"statement_hash":"d11afd4ede0aa409767b589a5b5e9dcb340b6c781cc05a9ff7edfd8ae5178fd1"},"rule":2,"target":"fdbfdef092c5340666d36a36f384cef5","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["5b3f63a1b"],"source_entry_id":"18.4/changes/052","source_hash":"c12b74818f0a535dec43ac9c95a3e774f625e8ce762249521d73b330e3f6d4cc","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"d11afd4ede0aa409767b589a5b5e9dcb340b6c781cc05a9ff7edfd8ae5178fd1","text":"Avoid rare flush failure when working with non-WAL-logged GiST indexes (Tomas Vondra) § A 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.","title":"Avoid rare flush failure when working with non-WAL-logged GiST indexes"},"id":"18.4-7270a57d5bd56fee","matches":[{"id":"17.10-81df83553a9e021a","source_entry_id":"17.10/changes/041","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Avoid rare flush failure when working with non-WAL-logged GiST indexes","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/052","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Avoid rare flush failure when working with non-WAL-logged GiST indexes","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["0af5e64e9","2543b9ea9","46c93b705","4da2afd01","a0f38604d","eb11d7a91"],"commit_groups":[["0af5e64e9","2543b9ea9","46c93b705","4da2afd01","a0f38604d","eb11d7a91"]],"commits":["a0f38604d"],"cves":[],"db_id":"c0162fa5c8bd731ee869a6a910d5a618","html":"\u003cp\u003eFix underestimate of required size of DSA page maps for odd-size segments (Paul Bunn) \u003ca href=\"https://postgr.es/c/a0f38604d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis miscalculation led to out-of-bounds accesses and hence server crashes.\u003c/p\u003e","id":"18.4-6a31304d211cadfa","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.","part":"changes","patch_ids":["51396541ad50c671641591d5c032f25c"],"relations":[{"evidence":{"patch_ids":["51396541ad50c671641591d5c032f25c"],"same_day":true,"statement_hash":"b77594e65c1a09137763e6965f04edfa079771b8c115cc6bbea72232ff10e97e"},"rule":2,"target":"132eccad33a03f9808709ff243633e21","type":"equivalent"},{"evidence":{"patch_ids":["51396541ad50c671641591d5c032f25c"],"same_day":true,"statement_hash":"b77594e65c1a09137763e6965f04edfa079771b8c115cc6bbea72232ff10e97e"},"rule":2,"target":"6c9b24cf6c2959b6e084b0f1468cc147","type":"equivalent"},{"evidence":{"patch_ids":["51396541ad50c671641591d5c032f25c"],"same_day":true,"statement_hash":"b77594e65c1a09137763e6965f04edfa079771b8c115cc6bbea72232ff10e97e"},"rule":2,"target":"d358ff7daadf000c76becae39274dcc8","type":"equivalent"},{"evidence":{"patch_ids":["51396541ad50c671641591d5c032f25c"],"same_day":true,"statement_hash":"b77594e65c1a09137763e6965f04edfa079771b8c115cc6bbea72232ff10e97e"},"rule":2,"target":"feb50a4056ee0c9561081c3bd1a5fd94","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["a0f38604d"],"source_entry_id":"18.4/changes/053","source_hash":"7634c8ba8f8ffc038896e0b72ea3fe2175a1d44ae6d57fd144afb296e0dc066d","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"b77594e65c1a09137763e6965f04edfa079771b8c115cc6bbea72232ff10e97e","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"},"id":"18.4-6a31304d211cadfa","matches":[{"id":"17.10-530a8cbdc6f714b9","source_entry_id":"17.10/changes/042","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix underestimate of required size of DSA page maps for odd-size segments","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/053","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix underestimate of required size of DSA page maps for odd-size segments","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["0a50ef094","969576dab","ccae90abd","dcd9c06a4","fa3b328e6","fe08113ae"],"commit_groups":[["0a50ef094","ccae90abd","dcd9c06a4"],["969576dab","fa3b328e6","fe08113ae"]],"commits":["0a50ef094","fa3b328e6"],"cves":[],"db_id":"257e52645de77966b485d158daff2049","html":"\u003cp\u003eFix indexing of oldest-multixact arrays in shared memory (Yura Sokolov) \u003ca href=\"https://postgr.es/c/0a50ef094\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/fa3b328e6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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.\u003c/p\u003e","id":"18.4-d3cfc20eaff1d676","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.","part":"changes","patch_ids":["9f4b51556384588dee12dabbaa9a5068","c295c29115de3784af1baea84dd9ddfc"],"relations":[{"evidence":{"patch_ids":["9f4b51556384588dee12dabbaa9a5068","c295c29115de3784af1baea84dd9ddfc"],"same_day":true,"statement_hash":"e8c1956b7f46db612ff4602b13580b3f19536358ea0d47bc73cf87584e556dac"},"rule":2,"target":"440f1367bcb7bd58aa010daa1ed5105b","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["0a50ef094","fa3b328e6"],"source_entry_id":"18.4/changes/054","source_hash":"585061295c9c5bfba8ea8450d973ee3ffcd66eca2322f3d514fcddf1dd3b7dbb","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"e8c1956b7f46db612ff4602b13580b3f19536358ea0d47bc73cf87584e556dac","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"},"id":"18.4-d3cfc20eaff1d676","matches":[{"id":"17.10-cfa55dcb71d57c12","source_entry_id":"17.10/changes/043","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix indexing of oldest-multixact arrays in shared memory","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/054","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix indexing of oldest-multixact arrays in shared memory","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["038c7d4a3","04745ba9c","3b7a6fa15","530b6b02f","83671c0da","f033abc6c"],"commit_groups":[["038c7d4a3","04745ba9c","3b7a6fa15","530b6b02f","83671c0da","f033abc6c"]],"commits":["83671c0da"],"cves":[],"db_id":"e3fcd13894196d38b7fdafd82a39872b","html":"\u003cp\u003eFix possible server crash when processing extended statistics on expressions of extension data types (Michael Paquier) \u003ca href=\"https://postgr.es/c/83671c0da\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eNULL 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.\u003c/p\u003e","id":"18.4-d17ff570c253e2a4","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.","part":"changes","patch_ids":["57808080730ecfb17eedfbeb01bceb92"],"relations":[{"evidence":{"patch_ids":["57808080730ecfb17eedfbeb01bceb92"],"same_day":true,"statement_hash":"0b6cefc1fdc0c8f91af788bfe5a8b6d0b6b4059af142c8779ab898a1590a8d8a"},"rule":2,"target":"11bb9497f3c67aace227015bc936b98e","type":"equivalent"},{"evidence":{"patch_ids":["57808080730ecfb17eedfbeb01bceb92"],"same_day":true,"statement_hash":"0b6cefc1fdc0c8f91af788bfe5a8b6d0b6b4059af142c8779ab898a1590a8d8a"},"rule":2,"target":"1c1afd4ac22d6baac4a29928c824292c","type":"equivalent"},{"evidence":{"patch_ids":["57808080730ecfb17eedfbeb01bceb92"],"same_day":true,"statement_hash":"0b6cefc1fdc0c8f91af788bfe5a8b6d0b6b4059af142c8779ab898a1590a8d8a"},"rule":2,"target":"7060172e893faabd38e47a052f25c75c","type":"equivalent"},{"evidence":{"patch_ids":["57808080730ecfb17eedfbeb01bceb92"],"same_day":true,"statement_hash":"0b6cefc1fdc0c8f91af788bfe5a8b6d0b6b4059af142c8779ab898a1590a8d8a"},"rule":2,"target":"80939c27c6a18cbd33af67b54738ffbb","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["83671c0da"],"source_entry_id":"18.4/changes/056","source_hash":"a6d6eda1706575777e401b70e6374c60ef40a88f3a736b35ba170dbddb62cf83","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"0b6cefc1fdc0c8f91af788bfe5a8b6d0b6b4059af142c8779ab898a1590a8d8a","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"},"id":"18.4-d17ff570c253e2a4","matches":[{"id":"17.10-55b28f30732d7db3","source_entry_id":"17.10/changes/044","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","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/056","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","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["4761f2eee","4abf63c62","a4515c9b4","d942511f0"],"commit_groups":[["4761f2eee","4abf63c62","a4515c9b4","d942511f0"]],"commits":["4abf63c62"],"cves":[],"db_id":"837bd67b8c3f6368b3c27a6551f80927","html":"\u003cp\u003eFix minor memory leaks in ICU-based string processing (Jeff Davis) \u003ca href=\"https://postgr.es/c/4abf63c62\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.4-d03de691fc9de456","identity_text":"Fix minor memory leaks in ICU-based string processing (Jeff Davis)","part":"changes","patch_ids":["6d9d38d08dbad42448b9071321caaf61"],"relations":[{"evidence":{"patch_ids":["6d9d38d08dbad42448b9071321caaf61"],"same_day":true,"statement_hash":"b7a1562c011305e92a0b8937cd9fca1c2e7a7555c23e50eef91b5ced9490aa97"},"rule":2,"target":"50b72add33aaee1a9925c87cbf7716b3","type":"equivalent"},{"evidence":{"patch_ids":["6d9d38d08dbad42448b9071321caaf61"],"same_day":true,"statement_hash":"b7a1562c011305e92a0b8937cd9fca1c2e7a7555c23e50eef91b5ced9490aa97"},"rule":2,"target":"bd584e4f7982ffc4b076ab2f17b9df9c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["4abf63c62"],"source_entry_id":"18.4/changes/058","source_hash":"a9e224936921e1963331dad335fbb68b989592f871716dc81f6ad82e7c37ac94","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"b7a1562c011305e92a0b8937cd9fca1c2e7a7555c23e50eef91b5ced9490aa97","text":"Fix minor memory leaks in ICU-based string processing (Jeff Davis) §","title":"Fix minor memory leaks in ICU-based string processing"},"id":"18.4-d03de691fc9de456","matches":[{"id":"17.10-e802516615666acf","source_entry_id":"17.10/changes/045","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix minor memory leaks in ICU-based string processing","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/058","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix minor memory leaks in ICU-based string processing","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["23cebf672","2d347f2cd","9b43e6793","affdb2dd5","e381843cf"],"commit_groups":[["23cebf672","2d347f2cd","9b43e6793","affdb2dd5","e381843cf"]],"commits":["affdb2dd5"],"cves":[],"db_id":"60187dd7a7a6b60a0c3449316b65aa78","html":"\u003cp\u003eIf the startup process fails, properly shut down other child processes before exiting the postmaster (Ayush Tiwari) \u003ca href=\"https://postgr.es/c/affdb2dd5\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e","id":"18.4-fbb8a60e8a0fb7fa","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.","part":"changes","patch_ids":["336655f61a8e613f6d655ff5a808f10d"],"relations":[{"evidence":{"patch_ids":["336655f61a8e613f6d655ff5a808f10d"],"same_day":true,"statement_hash":"cb4e5d59e127aafd8bb2c9e2c73437dd551d9591dd8c7309ec60a48a3299d4f5"},"rule":2,"target":"1258e1d70ad8d20566f8bef565afb542","type":"equivalent"},{"evidence":{"patch_ids":["336655f61a8e613f6d655ff5a808f10d"],"same_day":true,"statement_hash":"cb4e5d59e127aafd8bb2c9e2c73437dd551d9591dd8c7309ec60a48a3299d4f5"},"rule":2,"target":"2a31a83d114004ec62a45d4511e6eea8","type":"equivalent"},{"evidence":{"patch_ids":["336655f61a8e613f6d655ff5a808f10d"],"same_day":true,"statement_hash":"cb4e5d59e127aafd8bb2c9e2c73437dd551d9591dd8c7309ec60a48a3299d4f5"},"rule":2,"target":"35889e010982e213ace67b19129690cc","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["affdb2dd5"],"source_entry_id":"18.4/changes/059","source_hash":"68c31c19230ddadd1bb75689080bdcd9d4f19cfe5d82a6547e023d3812aca964","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"cb4e5d59e127aafd8bb2c9e2c73437dd551d9591dd8c7309ec60a48a3299d4f5","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"},"id":"18.4-fbb8a60e8a0fb7fa","matches":[{"id":"17.10-ae6a8b961252ec16","source_entry_id":"17.10/changes/046","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","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/059","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","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["0852643e1","1ca385032","77dff5d93","a5f412107","e35e466f6"],"commit_groups":[["0852643e1","1ca385032","77dff5d93","a5f412107","e35e466f6"]],"commits":["0852643e1"],"cves":[],"db_id":"2dd877a931aebbb79cf02748fddc6985","html":"\u003cp\u003eFix race condition between WAL replay of checkpoints and multixact ID creations (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/0852643e1\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA standby server following WAL from a primary of an older minor version could get into a crash-and-restart loop complaining about \u003cspan\u003e“\u003cspan\u003ecould not access status of transaction\u003c/span\u003e”\u003c/span\u003e.\u003c/p\u003e","id":"18.4-b95009e302c19df6","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.","part":"changes","patch_ids":["bc2293c8457ac75a2ee41b1da5cae860"],"relations":[{"evidence":{"patch_ids":["bc2293c8457ac75a2ee41b1da5cae860"],"same_day":true,"statement_hash":"966d18f3bd64c03cfe6fcbf5ad572276df81e74e4f0e0228686357c47c7ba192"},"rule":2,"target":"61f30ae9ddadfa030207bdea7cb12e70","type":"equivalent"},{"evidence":{"patch_ids":["bc2293c8457ac75a2ee41b1da5cae860"],"same_day":true,"statement_hash":"966d18f3bd64c03cfe6fcbf5ad572276df81e74e4f0e0228686357c47c7ba192"},"rule":2,"target":"7656c6c266fb5f623679c473e6534cb4","type":"equivalent"},{"evidence":{"patch_ids":["bc2293c8457ac75a2ee41b1da5cae860"],"same_day":true,"statement_hash":"966d18f3bd64c03cfe6fcbf5ad572276df81e74e4f0e0228686357c47c7ba192"},"rule":2,"target":"85b276d385b6533daa45fb10a83fcdc6","type":"equivalent"},{"evidence":{"patch_ids":["bc2293c8457ac75a2ee41b1da5cae860"],"same_day":true,"statement_hash":"966d18f3bd64c03cfe6fcbf5ad572276df81e74e4f0e0228686357c47c7ba192"},"rule":2,"target":"bdf695af62de33084d77c352623dcee3","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["0852643e1"],"source_entry_id":"18.4/changes/060","source_hash":"ac547c6f2c5e79a65589bd908f8df4b0b44a2c86fdb6cad890d325cd54b6e41d","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"966d18f3bd64c03cfe6fcbf5ad572276df81e74e4f0e0228686357c47c7ba192","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"},"id":"18.4-b95009e302c19df6","matches":[{"id":"17.10-b851403e0c059925","source_entry_id":"17.10/changes/047","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix race condition between WAL replay of checkpoints and multixact ID creations","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/060","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix race condition between WAL replay of checkpoints and multixact ID creations","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["3bf6f22ce","3eb2fecdb","42734f296","6eedb2a5f","82935467a","8ee536c89","980498138","bbbc0888b","d927b4bd9","da21ecf57","f15471464","fa9f2e317"],"commit_groups":[["3bf6f22ce","3eb2fecdb","42734f296","6eedb2a5f","82935467a","bbbc0888b"],["8ee536c89","980498138","d927b4bd9","da21ecf57","f15471464","fa9f2e317"]],"commits":["3eb2fecdb","980498138"],"cves":[],"db_id":"dd2e9c6da8c31f99c801d2fd16385b3c","html":"\u003cp\u003ePrevent indefinite wait in shutdown of a walsender process (Anthonin Bonnefoy) \u003ca href=\"https://postgr.es/c/3eb2fecdb\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/980498138\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAt 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.\u003c/p\u003e","id":"18.4-a9cb192589c0f7aa","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.","part":"changes","patch_ids":["472a5975808282fa6bd581c79c39f9ea","76b367fc789f138e1eeabf0d364392af"],"relations":[{"evidence":{"patch_ids":["472a5975808282fa6bd581c79c39f9ea","76b367fc789f138e1eeabf0d364392af"],"same_day":true,"statement_hash":"82e19a553da5241f427aaa49312a19ba9fb5200bffa8a85355d78e7c64e1a530"},"rule":2,"target":"45420fcd1c11fe55a25c2e6f51f48363","type":"equivalent"},{"evidence":{"patch_ids":["472a5975808282fa6bd581c79c39f9ea","76b367fc789f138e1eeabf0d364392af"],"same_day":true,"statement_hash":"82e19a553da5241f427aaa49312a19ba9fb5200bffa8a85355d78e7c64e1a530"},"rule":2,"target":"58a67f2d4d7fff6342315f22db6849a6","type":"equivalent"},{"evidence":{"patch_ids":["472a5975808282fa6bd581c79c39f9ea","76b367fc789f138e1eeabf0d364392af"],"same_day":true,"statement_hash":"82e19a553da5241f427aaa49312a19ba9fb5200bffa8a85355d78e7c64e1a530"},"rule":2,"target":"a7b932fcfa614135f399c6d16936a3ee","type":"equivalent"},{"evidence":{"patch_ids":["472a5975808282fa6bd581c79c39f9ea","76b367fc789f138e1eeabf0d364392af"],"same_day":true,"statement_hash":"82e19a553da5241f427aaa49312a19ba9fb5200bffa8a85355d78e7c64e1a530"},"rule":2,"target":"f5dd9be5d5ba1e08ae8e1a43cf926484","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["3eb2fecdb","980498138"],"source_entry_id":"18.4/changes/061","source_hash":"30e21260db1c3d5b99950ec0f5dc2e6fdbfa011ede52349a41454054360e4a6e","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"82e19a553da5241f427aaa49312a19ba9fb5200bffa8a85355d78e7c64e1a530","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"},"id":"18.4-a9cb192589c0f7aa","matches":[{"id":"17.10-3ccf02812257acd0","source_entry_id":"17.10/changes/048","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Prevent indefinite wait in shutdown of a walsender process","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/061","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Prevent indefinite wait in shutdown of a walsender process","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["1cf010f21","54537de35","ac3b97db3","c06d1a4ba","ca259b084","f5d1038d9"],"commit_groups":[["1cf010f21","54537de35","ac3b97db3","c06d1a4ba","ca259b084","f5d1038d9"]],"commits":["ac3b97db3"],"cves":[],"db_id":"0ab544ccf54b9ef9d9a67d11e0edd7e6","html":"\u003cp\u003eEnsure that changes to tables' free space maps are persisted during recovery (Alexey Makhmutov) \u003ca href=\"https://postgr.es/c/ac3b97db3\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, 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.\u003c/p\u003e","id":"18.4-97e2910c41fa9a19","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.","part":"changes","patch_ids":["290b85a9a01972ea333ff078f1b803bd"],"relations":[{"evidence":{"patch_ids":["290b85a9a01972ea333ff078f1b803bd"],"same_day":true,"statement_hash":"94dbd19b3ba5c2d1d6d0c3e547d4c2b99593a3f783f7d830b8bd54b62553c5ba"},"rule":2,"target":"0a850a82a0e101c371b76446a16834eb","type":"equivalent"},{"evidence":{"patch_ids":["290b85a9a01972ea333ff078f1b803bd"],"same_day":true,"statement_hash":"94dbd19b3ba5c2d1d6d0c3e547d4c2b99593a3f783f7d830b8bd54b62553c5ba"},"rule":2,"target":"5d55832b6f7b480606ba52039c22d06e","type":"equivalent"},{"evidence":{"patch_ids":["290b85a9a01972ea333ff078f1b803bd"],"same_day":true,"statement_hash":"94dbd19b3ba5c2d1d6d0c3e547d4c2b99593a3f783f7d830b8bd54b62553c5ba"},"rule":2,"target":"d0b2b7eb40b300341a738f0c8f9b9486","type":"equivalent"},{"evidence":{"patch_ids":["290b85a9a01972ea333ff078f1b803bd"],"same_day":true,"statement_hash":"94dbd19b3ba5c2d1d6d0c3e547d4c2b99593a3f783f7d830b8bd54b62553c5ba"},"rule":2,"target":"ef79709e772e43cd7f13cd40fd54ce08","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["ac3b97db3"],"source_entry_id":"18.4/changes/062","source_hash":"b4c7ae8e1632b5ecf778d21be35386e9777e6a942b825bd1a420c044b7e3cc4e","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"94dbd19b3ba5c2d1d6d0c3e547d4c2b99593a3f783f7d830b8bd54b62553c5ba","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"},"id":"18.4-97e2910c41fa9a19","matches":[{"id":"17.10-fe407982706e6121","source_entry_id":"17.10/changes/049","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Ensure that changes to tables' free space maps are persisted during recovery","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/062","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Ensure that changes to tables' free space maps are persisted during recovery","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["5d67549d9","6916f4410","7e4c871f4","c34a280c8","e2688ea5e","f0e3f9732"],"commit_groups":[["5d67549d9","6916f4410","7e4c871f4","c34a280c8","e2688ea5e","f0e3f9732"]],"commits":["e2688ea5e"],"cves":[],"db_id":"c0c7dfbc8d8c6bcae16ae7205d190917","html":"\u003cp\u003eFix crashes in some \u003cspan\u003eecpg\u003c/span\u003e functions when called without any established connection (Shruthi Gowda) \u003ca href=\"https://postgr.es/c/e2688ea5e\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.4-7aa817666dd07903","identity_text":"Fix crashes in some ecpg functions when called without any established connection (Shruthi Gowda)","part":"changes","patch_ids":["c7a6bafc62f4feae4e980b1e35da2b80"],"relations":[{"evidence":{"patch_ids":["c7a6bafc62f4feae4e980b1e35da2b80"],"same_day":true,"statement_hash":"d082bcf56e345df427e58be27130fd3aa6a1679e210b9c2dac559e63adb7e00a"},"rule":2,"target":"7907242716f81b2600bf11b638097726","type":"equivalent"},{"evidence":{"patch_ids":["c7a6bafc62f4feae4e980b1e35da2b80"],"same_day":true,"statement_hash":"d082bcf56e345df427e58be27130fd3aa6a1679e210b9c2dac559e63adb7e00a"},"rule":2,"target":"80c1fd60cd9f0d7c266d99b227c860c1","type":"equivalent"},{"evidence":{"patch_ids":["c7a6bafc62f4feae4e980b1e35da2b80"],"same_day":true,"statement_hash":"d082bcf56e345df427e58be27130fd3aa6a1679e210b9c2dac559e63adb7e00a"},"rule":2,"target":"bdf9527e3b31fa7d5ae8f9823d072d3d","type":"equivalent"},{"evidence":{"patch_ids":["c7a6bafc62f4feae4e980b1e35da2b80"],"same_day":true,"statement_hash":"d082bcf56e345df427e58be27130fd3aa6a1679e210b9c2dac559e63adb7e00a"},"rule":2,"target":"feefd46320fbb1731e40ec3e06323dbb","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["e2688ea5e"],"source_entry_id":"18.4/changes/063","source_hash":"dcf26468595d7c78f1807708270b114aa22c165d1ec52d8150a311fceec78d91","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"d082bcf56e345df427e58be27130fd3aa6a1679e210b9c2dac559e63adb7e00a","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"},"id":"18.4-7aa817666dd07903","matches":[{"id":"17.10-4e8f75e7518f8860","source_entry_id":"17.10/changes/050","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix crashes in some ecpg functions when called without any established connection","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/063","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix crashes in some ecpg functions when called without any established connection","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["01d58d7e3","1590723f0","2640c5ba7","415cc943f","4548e8746","5095f3f4a","78dc9a808","8b198b093","9a42888a3","a01a592b1","ac0accafd","c70f6dc6b","cce939c71","d3bb7841b","f1298a4c2"],"commit_groups":[["01d58d7e3","1590723f0","5095f3f4a","d3bb7841b","f1298a4c2"],["2640c5ba7","415cc943f","4548e8746","78dc9a808","c70f6dc6b"],["8b198b093","9a42888a3","a01a592b1","ac0accafd","cce939c71"]],"commits":["5095f3f4a","78dc9a808","a01a592b1"],"cves":[],"db_id":"2c1767e33fbd2c5b0ad76b3984a83f2d","html":"\u003cp\u003eFix assorted bugs in backup decompression and tar-parsing code (Andrew Dunstan, Tom Lane, Chao Li) \u003ca href=\"https://postgr.es/c/5095f3f4a\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/a01a592b1\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/78dc9a808\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe decompression and tar-file reading code used in \u003cspan\u003epg_basebackup\u003c/span\u003e and \u003cspan\u003epg_verifybackup\u003c/span\u003e 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.\u003c/p\u003e","id":"18.4-3efb2ed246686260","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.","part":"changes","patch_ids":["776d5a67dae4e90312023436a1a121e4","a09bdaf76ce8e50fc1ed232d629496d1","e611dc8dc55e1b7e28e7918dce0a5440"],"relations":[{"evidence":{"patch_ids":["776d5a67dae4e90312023436a1a121e4","a09bdaf76ce8e50fc1ed232d629496d1","e611dc8dc55e1b7e28e7918dce0a5440"],"same_day":true,"statement_hash":"14975a7d452ebd245adc06195cb53e296e97faf277282e3324587b2fcb641829"},"rule":2,"target":"212902cab1e6fcee0bcc358f8fa492ef","type":"equivalent"},{"evidence":{"patch_ids":["776d5a67dae4e90312023436a1a121e4","a09bdaf76ce8e50fc1ed232d629496d1","e611dc8dc55e1b7e28e7918dce0a5440"],"same_day":true,"statement_hash":"14975a7d452ebd245adc06195cb53e296e97faf277282e3324587b2fcb641829"},"rule":2,"target":"34c5828614b646d0ee1635c733748049","type":"equivalent"},{"evidence":{"patch_ids":["776d5a67dae4e90312023436a1a121e4","a09bdaf76ce8e50fc1ed232d629496d1","e611dc8dc55e1b7e28e7918dce0a5440"],"same_day":true,"statement_hash":"14975a7d452ebd245adc06195cb53e296e97faf277282e3324587b2fcb641829"},"rule":2,"target":"bb9e0889e1a5adbf796ceaf3f2bba54a","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["5095f3f4a","78dc9a808","a01a592b1"],"source_entry_id":"18.4/changes/065","source_hash":"cb9c6be5fd1ed810aed5121907e9abee1c0eb6f0b0eaa2df4feb45d2fd127cc8","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"14975a7d452ebd245adc06195cb53e296e97faf277282e3324587b2fcb641829","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"},"id":"18.4-3efb2ed246686260","matches":[{"id":"17.10-608dfcd402c79cc9","source_entry_id":"17.10/changes/051","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix assorted bugs in backup decompression and tar-parsing code","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/065","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix assorted bugs in backup decompression and tar-parsing code","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["1cd783d20","74b4438a7","a4649c50a","b09158cc7"],"commit_groups":[["1cd783d20","74b4438a7","a4649c50a","b09158cc7"]],"commits":["b09158cc7"],"cves":[],"db_id":"498d15925e49297bef5794701969b9e3","html":"\u003cp\u003eIn \u003cspan\u003epg_dumpall\u003c/span\u003e, don't skip role \u003ccode\u003eGRANT\u003c/code\u003es with dangling grantor OIDs (Tom Lane) \u003ca href=\"https://postgr.es/c/b09158cc7\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eInstead, handle such cases by emitting \u003ccode\u003eGRANT\u003c/code\u003e without any \u003ccode\u003eGRANTED BY\u003c/code\u003e 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.\u003c/p\u003e","id":"18.4-4c4f381190f9d053","identity_text":"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.","part":"changes","patch_ids":["be27d62b6c1cd4dc0e48f0fff55be1a3"],"relations":[{"evidence":{"patch_ids":["be27d62b6c1cd4dc0e48f0fff55be1a3"],"same_day":true,"statement_hash":"3b7728d29b36a1645aabd692297c54bf41cba11df9227a8bbeea29920949c298"},"rule":2,"target":"48b5ddf02369d30a0910158589f12b23","type":"equivalent"},{"evidence":{"patch_ids":["be27d62b6c1cd4dc0e48f0fff55be1a3"],"same_day":true,"statement_hash":"3b7728d29b36a1645aabd692297c54bf41cba11df9227a8bbeea29920949c298"},"rule":2,"target":"aaca3c112b54f50cb3d0aef43fa40117","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b09158cc7"],"source_entry_id":"18.4/changes/067","source_hash":"20cdafa4bcad7a1c7702dada4919678945fe5144b57211a2aee7f6c2deb66d58","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"3b7728d29b36a1645aabd692297c54bf41cba11df9227a8bbeea29920949c298","text":"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.","title":"In pg_dumpall, don't skip role GRANTs with dangling grantor OIDs"},"id":"18.4-4c4f381190f9d053","matches":[{"id":"17.10-abb35676e2703512","source_entry_id":"17.10/changes/052","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"In pg_dumpall, don't skip role GRANTs with dangling grantor OIDs","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/067","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"In pg_dumpall, don't skip role GRANTs with dangling grantor OIDs","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["1b2773179","a38ed212f","a60a10338","ad7fc3f1f","c47744ede","e726620d2"],"commit_groups":[["1b2773179","a38ed212f","a60a10338","ad7fc3f1f","c47744ede","e726620d2"]],"commits":["1b2773179"],"cves":[],"db_id":"b441ea3af4b648902039f9d5d3831785","html":"\u003cp\u003eIn \u003cspan\u003epg_upgrade\u003c/span\u003e, take care to use the correct protocol version when connecting to older source servers (Jacob Champion) \u003ca href=\"https://postgr.es/c/1b2773179\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis could be problematic when attempting to upgrade from a pre-2018 server.\u003c/p\u003e","id":"18.4-f5f35647f03db5de","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.","part":"changes","patch_ids":["566020049e5cf4849b3dd9a9935a3aba"],"relations":[{"evidence":{"patch_ids":["566020049e5cf4849b3dd9a9935a3aba"],"same_day":true,"statement_hash":"6ea9a20b0f199ebe33de09e3497f924a73ae542c7d6af134326d0792ad8e087c"},"rule":2,"target":"29ee5ab07783ca431d54fc60a7a68ac6","type":"equivalent"},{"evidence":{"patch_ids":["566020049e5cf4849b3dd9a9935a3aba"],"same_day":true,"statement_hash":"6ea9a20b0f199ebe33de09e3497f924a73ae542c7d6af134326d0792ad8e087c"},"rule":2,"target":"330e067151809e2b5b18a2ce11b3f4a8","type":"equivalent"},{"evidence":{"patch_ids":["566020049e5cf4849b3dd9a9935a3aba"],"same_day":true,"statement_hash":"6ea9a20b0f199ebe33de09e3497f924a73ae542c7d6af134326d0792ad8e087c"},"rule":2,"target":"6e7bc01c77ad0b62b80fffc021e1f621","type":"equivalent"},{"evidence":{"patch_ids":["566020049e5cf4849b3dd9a9935a3aba"],"same_day":true,"statement_hash":"6ea9a20b0f199ebe33de09e3497f924a73ae542c7d6af134326d0792ad8e087c"},"rule":2,"target":"df5ddbd0c6e2f445b5c35f53b9f74046","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["1b2773179"],"source_entry_id":"18.4/changes/068","source_hash":"8350e1a25becbe288b1e0328484e7d60dd9277a9456f597a98cff73be40b3694","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"6ea9a20b0f199ebe33de09e3497f924a73ae542c7d6af134326d0792ad8e087c","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"},"id":"18.4-f5f35647f03db5de","matches":[{"id":"17.10-cf34513657c8c0c2","source_entry_id":"17.10/changes/053","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"In pg_upgrade, take care to use the correct protocol version when connecting to older source servers","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/068","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"In pg_upgrade, take care to use the correct protocol version when connecting to older source servers","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["28c2b7896","8fc45ac5d","bde9ad315","cc774c543","f510577de"],"commit_groups":[["28c2b7896","8fc45ac5d","bde9ad315","cc774c543","f510577de"]],"commits":["bde9ad315"],"cves":[],"db_id":"b41103d47758e1bb2b7b7dfae49365b9","html":"\u003cp\u003eIn \u003ccode\u003econtrib/basic_archive\u003c/code\u003e, allow the archive directory to be missing at startup (Nathan Bossart) \u003ca href=\"https://postgr.es/c/bde9ad315\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, the setting of \u003ccode\u003ebasic_archive.archive_directory\u003c/code\u003e 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.\u003c/p\u003e","id":"18.4-ab15ea8c2f16b1a1","identity_text":"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.","part":"changes","patch_ids":["d1199a3c8097e254072ab83b54c1e1d5"],"relations":[{"evidence":{"patch_ids":["d1199a3c8097e254072ab83b54c1e1d5"],"same_day":true,"statement_hash":"1134bcc987b009966d8cddeefda2e4c96240c13b4f2dc3f1b7e280d8ebf0f2f0"},"rule":2,"target":"1ad9930c22ef55daa7211338a55a1d96","type":"equivalent"},{"evidence":{"patch_ids":["d1199a3c8097e254072ab83b54c1e1d5"],"same_day":true,"statement_hash":"1134bcc987b009966d8cddeefda2e4c96240c13b4f2dc3f1b7e280d8ebf0f2f0"},"rule":2,"target":"616d8fa76e38a5c20f94d74810bf0dfa","type":"equivalent"},{"evidence":{"patch_ids":["d1199a3c8097e254072ab83b54c1e1d5"],"same_day":true,"statement_hash":"1134bcc987b009966d8cddeefda2e4c96240c13b4f2dc3f1b7e280d8ebf0f2f0"},"rule":2,"target":"90e1038fbb68d1913c7ac6d7fe93e376","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["bde9ad315"],"source_entry_id":"18.4/changes/069","source_hash":"8f51f3fd6f254e85baf55a8bd9646bf2e0766f98cd0ce7e799ff2ce137ab807b","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"1134bcc987b009966d8cddeefda2e4c96240c13b4f2dc3f1b7e280d8ebf0f2f0","text":"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.","title":"In contrib/basic_archive, allow the archive directory to be missing at startup"},"id":"18.4-ab15ea8c2f16b1a1","matches":[{"id":"17.10-760c43569faae613","source_entry_id":"17.10/changes/054","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"In contrib/basic_archive, allow the archive directory to be missing at startup","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/069","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"In contrib/basic_archive, allow the archive directory to be missing at startup","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["058710d41","2b993167f","3ed2c7ef7","53a57cae1","b3c2a3d38","c8308a984","d1bd9a7dc"],"commit_groups":[["058710d41","2b993167f","3ed2c7ef7","53a57cae1","d1bd9a7dc"],["b3c2a3d38","c8308a984"]],"commits":["53a57cae1","b3c2a3d38"],"cves":[],"db_id":"64aaf0bd209b1b9e176ded962a3a5b0a","html":"\u003cp\u003eFix \u003ccode\u003econtrib/ltree\u003c/code\u003e to cope when case-folding changes a string's byte length (Jeff Davis) \u003ca href=\"https://postgr.es/c/b3c2a3d38\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/53a57cae1\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, \u003ccode\u003elquery\u003c/code\u003e patterns specifying case-insensitive matching might fail to match labels they should match.\u003c/p\u003e","id":"18.4-3cede858d59bf5c2","identity_text":"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.","part":"changes","patch_ids":["7e19748e0b856cea1d9ea13667371829","9e7c128fe050a45459da3c9572bf888b"],"relations":[{"evidence":{"patch_ids":["7e19748e0b856cea1d9ea13667371829","9e7c128fe050a45459da3c9572bf888b"],"same_day":true,"statement_hash":"c8d7a89f3c07f177066f6fedd62b1119638bbf94ea0046714ce7e210c42a4468"},"rule":2,"target":"88979c94ad494073327481ff0f109ebc","type":"equivalent"},{"evidence":{"patch_ids":["7e19748e0b856cea1d9ea13667371829","9e7c128fe050a45459da3c9572bf888b"],"same_day":true,"statement_hash":"c8d7a89f3c07f177066f6fedd62b1119638bbf94ea0046714ce7e210c42a4468"},"rule":2,"target":"b472005379ddc1793ee9ef6ac751eae2","type":"equivalent"},{"evidence":{"patch_ids":["7e19748e0b856cea1d9ea13667371829","9e7c128fe050a45459da3c9572bf888b"],"same_day":true,"statement_hash":"c8d7a89f3c07f177066f6fedd62b1119638bbf94ea0046714ce7e210c42a4468"},"rule":2,"target":"c90a1fd6362ebfccf11986cdf78fdcbf","type":"equivalent"},{"evidence":{"patch_ids":["7e19748e0b856cea1d9ea13667371829","9e7c128fe050a45459da3c9572bf888b"],"same_day":true,"statement_hash":"c8d7a89f3c07f177066f6fedd62b1119638bbf94ea0046714ce7e210c42a4468"},"rule":2,"target":"e7145d49a5e4620268f44ce6ce59f66b","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["53a57cae1","b3c2a3d38"],"source_entry_id":"18.4/changes/070","source_hash":"c5b29e4136b4dde81189d9123d5790588f1fefd9fda73e26a22a180569ebbd65","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"c8d7a89f3c07f177066f6fedd62b1119638bbf94ea0046714ce7e210c42a4468","text":"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.","title":"Fix contrib/ltree to cope when case-folding changes a string's byte length"},"id":"18.4-3cede858d59bf5c2","matches":[{"id":"17.10-6f3016280c8e2025","source_entry_id":"17.10/changes/055","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Fix contrib/ltree to cope when case-folding changes a string's byte length","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/070","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Fix contrib/ltree to cope when case-folding changes a string's byte length","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["25b02320e","351e59f34","3c74cb576","52edaf9d9","92cf11171","a6d03067f"],"commit_groups":[["25b02320e","351e59f34","3c74cb576","52edaf9d9","92cf11171","a6d03067f"]],"commits":["25b02320e"],"cves":[],"db_id":"5405c5216994c7e3f308af24044493d4","html":"\u003cp\u003eIn \u003ccode\u003econtrib/pg_stat_statements\u003c/code\u003e, don't leak memory if an error occurs while parsing the \u003ccode\u003epgss_query_texts.stat\u003c/code\u003e file (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/25b02320e\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.4-d1fd29b11b780a8b","identity_text":"In contrib/pg_stat_statements, don't leak memory if an error occurs while parsing the pgss_query_texts.stat file (Heikki Linnakangas)","part":"changes","patch_ids":["525c92ce9cbe0762a36b169c9be69fcf"],"relations":[{"evidence":{"patch_ids":["525c92ce9cbe0762a36b169c9be69fcf"],"same_day":true,"statement_hash":"ac5942ed996a5e15c9177f4bd0925874631fd5bf85f5253845cd79fbf3ddf0ad"},"rule":2,"target":"07ffe7eed989081f7577ca43593bd960","type":"equivalent"},{"evidence":{"patch_ids":["525c92ce9cbe0762a36b169c9be69fcf"],"same_day":true,"statement_hash":"ac5942ed996a5e15c9177f4bd0925874631fd5bf85f5253845cd79fbf3ddf0ad"},"rule":2,"target":"2b59e021939b9e9d9f09b01df770c280","type":"equivalent"},{"evidence":{"patch_ids":["525c92ce9cbe0762a36b169c9be69fcf"],"same_day":true,"statement_hash":"ac5942ed996a5e15c9177f4bd0925874631fd5bf85f5253845cd79fbf3ddf0ad"},"rule":2,"target":"98f2c3414fd70c5c98ac19bfad5464b8","type":"equivalent"},{"evidence":{"patch_ids":["525c92ce9cbe0762a36b169c9be69fcf"],"same_day":true,"statement_hash":"ac5942ed996a5e15c9177f4bd0925874631fd5bf85f5253845cd79fbf3ddf0ad"},"rule":2,"target":"e5a91133c6748bd29d99483810ddb96c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["25b02320e"],"source_entry_id":"18.4/changes/072","source_hash":"f3dca59a175138fee4dca1018d8a2aa458f19a90654727612a5d549960f8e664","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"ac5942ed996a5e15c9177f4bd0925874631fd5bf85f5253845cd79fbf3ddf0ad","text":"In contrib/pg_stat_statements, don't leak memory if an error occurs while parsing the pgss_query_texts.stat file (Heikki Linnakangas) §","title":"In contrib/pg_stat_statements, don't leak memory if an error occurs while parsing the pgss_query_texts.stat file"},"id":"18.4-d1fd29b11b780a8b","matches":[{"id":"17.10-c843d842d1a0089b","source_entry_id":"17.10/changes/056","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"In contrib/pg_stat_statements, don't leak memory if an error occurs while parsing the pgss_query_texts.stat file","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/072","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"In contrib/pg_stat_statements, don't leak memory if an error occurs while parsing the pgss_query_texts.stat file","version":"18.4"},{"entry":{"category":"bugfix","commit_aliases":["1352651c2","34c18a225","648818ba3","af8f9248f","c318777da","fd5b36ab1"],"commit_groups":[["1352651c2","34c18a225","648818ba3","af8f9248f","c318777da","fd5b36ab1"]],"commits":["c318777da"],"cves":[],"db_id":"5debbdff219f6645c34f0afc23c6c9a8","html":"\u003cp\u003eIn \u003ccode\u003econtrib/postgres_fdw\u003c/code\u003e, avoid crash due to premature cleanup of a failed connection (Etsuro Fujita) \u003ca href=\"https://postgr.es/c/c318777da\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf 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.\u003c/p\u003e","id":"18.4-78a75773cc77437b","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.","part":"changes","patch_ids":["73eecb88ff1f4197b1eb6900521746ca"],"relations":[{"evidence":{"patch_ids":["73eecb88ff1f4197b1eb6900521746ca"],"same_day":true,"statement_hash":"c7e9961353a3aad5643e55ab0c89f89d4bd050418724e45b79a4a1fb13cd1c48"},"rule":2,"target":"701d8322decc496c951bc0d7ecfdd513","type":"equivalent"},{"evidence":{"patch_ids":["73eecb88ff1f4197b1eb6900521746ca"],"same_day":true,"statement_hash":"c7e9961353a3aad5643e55ab0c89f89d4bd050418724e45b79a4a1fb13cd1c48"},"rule":2,"target":"8c8ea6b283a201d99cb3d8c9f57cd142","type":"equivalent"},{"evidence":{"patch_ids":["73eecb88ff1f4197b1eb6900521746ca"],"same_day":true,"statement_hash":"c7e9961353a3aad5643e55ab0c89f89d4bd050418724e45b79a4a1fb13cd1c48"},"rule":2,"target":"9bcb1c284d9f8abb68fce372f4df9301","type":"equivalent"},{"evidence":{"patch_ids":["73eecb88ff1f4197b1eb6900521746ca"],"same_day":true,"statement_hash":"c7e9961353a3aad5643e55ab0c89f89d4bd050418724e45b79a4a1fb13cd1c48"},"rule":2,"target":"b0783885375212755fb05950c3052a4a","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c318777da"],"source_entry_id":"18.4/changes/073","source_hash":"7370c1e27b16e5685bf55cf6357a6c058a35c4df678be5bec75d4a3d13b7d645","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"c7e9961353a3aad5643e55ab0c89f89d4bd050418724e45b79a4a1fb13cd1c48","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"},"id":"18.4-78a75773cc77437b","matches":[{"id":"17.10-488be0605ad9d4ad","source_entry_id":"17.10/changes/057","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"In contrib/postgres_fdw, avoid crash due to premature cleanup of a failed connection","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/073","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"In contrib/postgres_fdw, avoid crash due to premature cleanup of a failed connection","version":"18.4"},{"entry":{"category":"improvement","commit_aliases":["0465c999e","4c0eab6f0","8a431b6d6","affd929c9","e28fc73d5","f64f62f5b"],"commit_groups":[["0465c999e","4c0eab6f0","8a431b6d6","affd929c9","e28fc73d5","f64f62f5b"]],"commits":["8a431b6d6"],"cves":[],"db_id":"4bebcc2956a5ca291072c22c03407356","html":"\u003cp\u003eUpdate time zone data files to \u003cspan\u003etzdata\u003c/span\u003e release 2026b (Tom Lane) \u003ca href=\"https://postgr.es/c/8a431b6d6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eBritish 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 \u003ccode\u003eMST\u003c/code\u003e 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.\u003c/p\u003e","id":"18.4-a78c59e453b0788d","identity_text":"Update time zone data files to tzdata release 2026b (Tom Lane) British 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.","part":"changes","patch_ids":["30506a0fee43471a4652ed9a4d616395"],"relations":[{"evidence":{"patch_ids":["30506a0fee43471a4652ed9a4d616395"],"same_day":true,"statement_hash":"54d3f56bdf06c07ea93842bb8072e38e1e0d631d40ae890c2e29184e60d57681"},"rule":2,"target":"614039d003cde35ab46fd98561df1111","type":"equivalent"},{"evidence":{"patch_ids":["30506a0fee43471a4652ed9a4d616395"],"same_day":true,"statement_hash":"54d3f56bdf06c07ea93842bb8072e38e1e0d631d40ae890c2e29184e60d57681"},"rule":2,"target":"ae0d24039285853394af147eee246b73","type":"equivalent"},{"evidence":{"patch_ids":["30506a0fee43471a4652ed9a4d616395"],"same_day":true,"statement_hash":"54d3f56bdf06c07ea93842bb8072e38e1e0d631d40ae890c2e29184e60d57681"},"rule":2,"target":"c75239b417c7eb143ce21787698f02df","type":"equivalent"},{"evidence":{"patch_ids":["30506a0fee43471a4652ed9a4d616395"],"same_day":true,"statement_hash":"54d3f56bdf06c07ea93842bb8072e38e1e0d631d40ae890c2e29184e60d57681"},"rule":2,"target":"de255c626ba35a131ca34e075c96784f","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["8a431b6d6"],"source_entry_id":"18.4/changes/074","source_hash":"51485d669ec4724819d65e5254b32119344328adaf7bade39c9fe735e65951eb","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"54d3f56bdf06c07ea93842bb8072e38e1e0d631d40ae890c2e29184e60d57681","text":"Update time zone data files to tzdata release 2026b (Tom Lane) § British 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.","title":"Update time zone data files to tzdata release 2026b"},"id":"18.4-a78c59e453b0788d","matches":[{"id":"17.10-1e6fcd0fa95c5ce6","source_entry_id":"17.10/changes/058","source_url":"/docs/release/17.10/#RELEASE-17-10-CHANGES","title":"Update time zone data files to tzdata release 2026b","version":"17.10"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.4/changes/074","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","title":"Update time zone data files to tzdata release 2026b","version":"18.4"},{"entry":{"category":"security","commit_aliases":["01992176e","20e9dcefd","226e49cbe","2a29b607d","4e1252ee5","4fcccea97","5d47df21e","7082ce248","82fd68801","99f205407","bf3842a64"],"commit_groups":[["01992176e","226e49cbe","2a29b607d","4e1252ee5","5d47df21e","99f205407","bf3842a64"],["20e9dcefd","4fcccea97","7082ce248","82fd68801"]],"commits":["2a29b607d","82fd68801"],"cves":["CVE-2026-6471"],"db_id":"2ed41f6adf451dd977da156f72190023","html":"\u003cp\u003eRestrict logical decoding output plugins to the set specified by a new server parameter \u003ccode\u003eoutput_plugin_libraries\u003c/code\u003e (Jacob Champion) \u003ca href=\"https://postgr.es/c/2a29b607d\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/82fd68801\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, 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.\u003c/p\u003e\n\u003cp\u003eBy default, only the output plugins shipped as part of \u003cspan\u003ePostgreSQL\u003c/span\u003e (\u003ccode\u003epgoutput\u003c/code\u003e and \u003ccode\u003etest_decoding\u003c/code\u003e) are included in \u003ccode\u003eoutput_plugin_libraries\u003c/code\u003e. Installations that rely on other output plugins must add them after updating the server, for example\u003c/p\u003e\n\u003cpre\u003eoutput_plugin_libraries = 'pgoutput, test_decoding, my_trusted_decoder'\n\u003c/pre\u003e\n\u003cp\u003eAdditionally, \u003ccode\u003epg_upgrade --check\u003c/code\u003e will fail if the \u003ccode\u003eoutput_plugin_libraries\u003c/code\u003e 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 \u003cspan\u003epg_upgrade\u003c/span\u003e.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Vladimir Tokarev and Yu Kunpeng for reporting this problem. (CVE-2026-6471)\u003c/p\u003e","id":"18.6-76e8d95ade6e17d6","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)","part":"changes","patch_ids":["29a8e1db1536ed40c71312e7d2015c9e","bcbaedd0455bfc84b87ba56b7f4aba2c"],"relations":[{"evidence":{"patch_ids":["29a8e1db1536ed40c71312e7d2015c9e","bcbaedd0455bfc84b87ba56b7f4aba2c"],"same_day":true,"statement_hash":"66cffd63e622afc809ffcea154c77acb7025871176da7689b08b6db15ff40212"},"rule":2,"target":"549fb97375289bbc21d70209d1e5e9a8","type":"equivalent"},{"evidence":{"patch_ids":["29a8e1db1536ed40c71312e7d2015c9e","bcbaedd0455bfc84b87ba56b7f4aba2c"],"same_day":true,"statement_hash":"66cffd63e622afc809ffcea154c77acb7025871176da7689b08b6db15ff40212"},"rule":2,"target":"7007806ed1d8192364b7ef102e45e7ef","type":"equivalent"},{"evidence":{"patch_ids":["29a8e1db1536ed40c71312e7d2015c9e","bcbaedd0455bfc84b87ba56b7f4aba2c"],"same_day":true,"statement_hash":"66cffd63e622afc809ffcea154c77acb7025871176da7689b08b6db15ff40212"},"rule":2,"target":"b5e7e2e2c6e0c744c28da7990822970a","type":"equivalent"},{"evidence":{"patch_ids":["29a8e1db1536ed40c71312e7d2015c9e","bcbaedd0455bfc84b87ba56b7f4aba2c"],"same_day":true,"statement_hash":"66cffd63e622afc809ffcea154c77acb7025871176da7689b08b6db15ff40212"},"rule":2,"target":"bbf53e61656864929954589e1f777019","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["2a29b607d","82fd68801"],"source_entry_id":"18.6/changes/001","source_hash":"bb65fe803bf799ec945db22c8446c25a0fc57bc240545380b027bcf4cff5e000","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"66cffd63e622afc809ffcea154c77acb7025871176da7689b08b6db15ff40212","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"},"id":"18.6-76e8d95ade6e17d6","matches":[{"id":"17.11-ccab0c809e14d029","source_entry_id":"17.11/changes/001","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Restrict logical decoding output plugins to the set specified by a new server parameter output_plugin_libraries","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/001","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Restrict logical decoding output plugins to the set specified by a new server parameter output_plugin_libraries","version":"18.6"},{"entry":{"category":"security","commit_aliases":["472ef7e4a","49e795414","4c5128ca0","6ca6023ca","7e29eb6f4","7eed42aa8","953be116c","b05cfc693","ba207f58f","ba2a63faf","d0ecee6de","d97b3f58c","e2c48c81f","fe32b10fc"],"commit_groups":[["472ef7e4a","6ca6023ca","7e29eb6f4","b05cfc693","ba207f58f","d0ecee6de","fe32b10fc"],["49e795414","4c5128ca0","7eed42aa8","953be116c","ba2a63faf","d97b3f58c","e2c48c81f"]],"commits":["4c5128ca0","fe32b10fc"],"cves":["CVE-2026-14663"],"db_id":"e8d5337224696bc194016b8a5269940d","html":"\u003cp\u003eFix \u003ccode\u003econtrib/pgcrypto\u003c/code\u003e's PGP encryption to detect unsupported ciphers (Daniel Gustafsson) \u003ca href=\"https://postgr.es/c/fe32b10fc\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/4c5128ca0\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, if OpenSSL rejected the requested cipher (for example, because it is running in FIPS mode, or the legacy provider hasn't been loaded), \u003cspan\u003epgcrypto\u003c/span\u003e failed to notice the failure and simply XOR'd the non-encrypted block with the plaintext, rendering the \u003cspan\u003e“\u003cspan\u003eencryption\u003c/span\u003e”\u003c/span\u003e trivially breakable. This will typically occur with deprecated or non-FIPS cipher algorithms (cipher-algo=blowfish/bf, twofish, cast5, or 3des).\u003c/p\u003e\n\u003cp\u003eBy default, \u003cspan\u003epgcrypto\u003c/span\u003e will now fail to decrypt any messages that were affected in this way. To allow retrieval of such data, a new option \u003ccode\u003eignore-cipher-failure\u003c/code\u003e has been added to \u003ccode\u003epgp_pub_decrypt()\u003c/code\u003e and \u003ccode\u003epgp_sym_decrypt()\u003c/code\u003e. Setting \u003ccode\u003eignore-cipher-failure=1\u003c/code\u003e will restore their previous behavior, allowing the faulty encryption wrapper to be stripped off:\u003c/p\u003e\n\u003cpre\u003epgp_sym_decrypt(encrypted_column, \u003cem\u003e\u003ccode\u003eany key\u003c/code\u003e\u003c/em\u003e, 'ignore-cipher-failure=1')\n\u003c/pre\u003e\n\u003cp\u003eOnce 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 \u003ccode\u003eignore-cipher-failure\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Shishir Sharma for reporting this problem. (CVE-2026-14663)\u003c/p\u003e","id":"18.6-bfaa3421904d3a41","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)","part":"changes","patch_ids":["0c0f3075fa6d42cb4f237a14111f3f86","94579ce6ea64094f97312d8046fcb082"],"relations":[{"evidence":{"patch_ids":["0c0f3075fa6d42cb4f237a14111f3f86","94579ce6ea64094f97312d8046fcb082"],"same_day":true,"statement_hash":"f9b50dfe772a85830e7ce5570ba2e751618ceca0e1ebf0653490632965de190f"},"rule":2,"target":"28125c4ed11f62e12267d5aa58f29ab4","type":"equivalent"},{"evidence":{"patch_ids":["0c0f3075fa6d42cb4f237a14111f3f86","94579ce6ea64094f97312d8046fcb082"],"same_day":true,"statement_hash":"f9b50dfe772a85830e7ce5570ba2e751618ceca0e1ebf0653490632965de190f"},"rule":2,"target":"379745809d65e827e6739e3818394675","type":"equivalent"},{"evidence":{"patch_ids":["0c0f3075fa6d42cb4f237a14111f3f86","94579ce6ea64094f97312d8046fcb082"],"same_day":true,"statement_hash":"f9b50dfe772a85830e7ce5570ba2e751618ceca0e1ebf0653490632965de190f"},"rule":2,"target":"5487cefec946cc3b492ec90f8407bbc0","type":"equivalent"},{"evidence":{"patch_ids":["0c0f3075fa6d42cb4f237a14111f3f86","94579ce6ea64094f97312d8046fcb082"],"same_day":true,"statement_hash":"f9b50dfe772a85830e7ce5570ba2e751618ceca0e1ebf0653490632965de190f"},"rule":2,"target":"a686eb51b6b69a27a6ba670a1473120d","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["4c5128ca0","fe32b10fc"],"source_entry_id":"18.6/changes/002","source_hash":"76c381bb98f96b0d13869dcbf838806af637da86790488eefb0781524c9bb11c","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"f9b50dfe772a85830e7ce5570ba2e751618ceca0e1ebf0653490632965de190f","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"},"id":"18.6-bfaa3421904d3a41","matches":[{"id":"17.11-165fa935d28df7f1","source_entry_id":"17.11/changes/002","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix contrib/pgcrypto's PGP encryption to detect unsupported ciphers","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/002","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix contrib/pgcrypto's PGP encryption to detect unsupported ciphers","version":"18.6"},{"entry":{"category":"security","commit_aliases":["29921259e","2bdfd5cdc","3045a25ba","3fdcfa8f7","46fa1f6f3","5c51ae455","7215c7e96","8cdbabea7","8cf01e213","900894d35","cf754f741","d6ab88d37","db96e87f9","dca6627de"],"commit_groups":[["29921259e","2bdfd5cdc","3045a25ba","3fdcfa8f7","46fa1f6f3","5c51ae455","d6ab88d37"],["7215c7e96","8cdbabea7","8cf01e213","900894d35","cf754f741","db96e87f9","dca6627de"]],"commits":["29921259e","900894d35"],"cves":["CVE-2026-6464"],"db_id":"3c7601286aa0c9239f3cd6933eeddc1f","html":"\u003cp\u003eFix \u003cspan\u003epsql\u003c/span\u003e to skip in-line data following a scripted \u003ccode\u003eCOPY ... FROM STDIN\u003c/code\u003e command, even if the \u003ccode\u003eCOPY\u003c/code\u003e fails before sending \u003ccode\u003ePGRES_COPY_IN\u003c/code\u003e (Tom Lane) \u003ca href=\"https://postgr.es/c/29921259e\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/900894d35\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, if a \u003ccode\u003eCOPY\u003c/code\u003e command failed at startup (for instance, because the target table doesn't exist) \u003cspan\u003epsql\u003c/span\u003e 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 \u003cspan\u003epsql\u003c/span\u003e to recognize syntactically-valid \u003ccode\u003eCOPY ... FROM STDIN\u003c/code\u003e commands and to skip data on its own authority if the server doesn't respond with \u003ccode\u003ePGRES_COPY_IN\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eWhile this fix is unlikely to affect any production SQL scripts, test scripts might intentionally exercise failing \u003ccode\u003eCOPY ... FROM STDIN\u003c/code\u003e commands. Those will need to gain a \u003ccode\u003e\\.\u003c/code\u003e data terminator line after each such command.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Alexander Lakhin for reporting this problem. (CVE-2026-6464)\u003c/p\u003e","id":"18.6-7711e8f6ad16c5dd","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)","part":"changes","patch_ids":["bb5ab12243a3045680f47ff1cb2c8480","ecf5b4358ac3d55d48e5c5a6cf618bc5"],"relations":[{"evidence":{"patch_ids":["bb5ab12243a3045680f47ff1cb2c8480","ecf5b4358ac3d55d48e5c5a6cf618bc5"],"same_day":true,"statement_hash":"76e8147c7ad5a98f52d6ef02172b79adbee8009366c00ae89f0a205215b4b225"},"rule":2,"target":"3fc8822e02c16e254582e2877b732705","type":"equivalent"},{"evidence":{"patch_ids":["bb5ab12243a3045680f47ff1cb2c8480","ecf5b4358ac3d55d48e5c5a6cf618bc5"],"same_day":true,"statement_hash":"76e8147c7ad5a98f52d6ef02172b79adbee8009366c00ae89f0a205215b4b225"},"rule":2,"target":"a4c84c6885a3a330efb43a5e79c7eeca","type":"equivalent"},{"evidence":{"patch_ids":["bb5ab12243a3045680f47ff1cb2c8480","ecf5b4358ac3d55d48e5c5a6cf618bc5"],"same_day":true,"statement_hash":"76e8147c7ad5a98f52d6ef02172b79adbee8009366c00ae89f0a205215b4b225"},"rule":2,"target":"df55d2444f4fc088a4a59341aed77733","type":"equivalent"},{"evidence":{"patch_ids":["bb5ab12243a3045680f47ff1cb2c8480","ecf5b4358ac3d55d48e5c5a6cf618bc5"],"same_day":true,"statement_hash":"76e8147c7ad5a98f52d6ef02172b79adbee8009366c00ae89f0a205215b4b225"},"rule":2,"target":"ea96c547a98f3910bcd150ec7a9bb871","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["29921259e","900894d35"],"source_entry_id":"18.6/changes/003","source_hash":"eecc14b4909d681329da93aaa4d3c4b6db68b34d0fbfa27af7599af1e496d5aa","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"76e8147c7ad5a98f52d6ef02172b79adbee8009366c00ae89f0a205215b4b225","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"},"id":"18.6-7711e8f6ad16c5dd","matches":[{"id":"17.11-8dd81897faaffe37","source_entry_id":"17.11/changes/003","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/003","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","version":"18.6"},{"entry":{"category":"security","commit_aliases":["1f49beef2","37b8f3b0e","60887d348","64a65ead1","7d150b5c9","9e02e2e18","fc933ce00"],"commit_groups":[["1f49beef2","37b8f3b0e","60887d348","64a65ead1","7d150b5c9","9e02e2e18","fc933ce00"]],"commits":["37b8f3b0e"],"cves":["CVE-2026-16239"],"db_id":"5b8818230400246029db8b181a69938c","html":"\u003cp\u003eCross-check the output row type of a portal running \u003ccode\u003eEXECUTE\u003c/code\u003e or \u003ccode\u003eFETCH\u003c/code\u003e (Robert Haas) \u003ca href=\"https://postgr.es/c/37b8f3b0e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eEXECUTE\u003c/code\u003e and \u003ccode\u003eFETCH\u003c/code\u003e 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) and Peter Geoghegan for reporting this problem. (CVE-2026-16239)\u003c/p\u003e","id":"18.6-cdf902a8952d780f","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)","part":"changes","patch_ids":["bca9a8aea055bf40b974631f891c3459"],"relations":[{"evidence":{"patch_ids":["bca9a8aea055bf40b974631f891c3459"],"same_day":true,"statement_hash":"6bfdff724b157ff6ff7a59fd5879e05c524cc0a5a96ac58a33fa9750cc2db073"},"rule":2,"target":"35f9a631aba647241e1c1fe3a3c4c269","type":"equivalent"},{"evidence":{"patch_ids":["bca9a8aea055bf40b974631f891c3459"],"same_day":true,"statement_hash":"6bfdff724b157ff6ff7a59fd5879e05c524cc0a5a96ac58a33fa9750cc2db073"},"rule":2,"target":"3ec84f87545930ce1036d071dad3e665","type":"equivalent"},{"evidence":{"patch_ids":["bca9a8aea055bf40b974631f891c3459"],"same_day":true,"statement_hash":"6bfdff724b157ff6ff7a59fd5879e05c524cc0a5a96ac58a33fa9750cc2db073"},"rule":2,"target":"e2286cb0c701bb465fa540c1d4a45071","type":"equivalent"},{"evidence":{"patch_ids":["bca9a8aea055bf40b974631f891c3459"],"same_day":true,"statement_hash":"6bfdff724b157ff6ff7a59fd5879e05c524cc0a5a96ac58a33fa9750cc2db073"},"rule":2,"target":"e9fc65bf1c23945887e9b1904d08b935","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["37b8f3b0e"],"source_entry_id":"18.6/changes/004","source_hash":"7787b5a3c11e14e37ef4fc1d99970faa5faa1f486bc292127f6a786ec1cc8f4c","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"6bfdff724b157ff6ff7a59fd5879e05c524cc0a5a96ac58a33fa9750cc2db073","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"},"id":"18.6-cdf902a8952d780f","matches":[{"id":"17.11-b9a0ccf8cc602cca","source_entry_id":"17.11/changes/004","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Cross-check the output row type of a portal running EXECUTE or FETCH","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/004","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Cross-check the output row type of a portal running EXECUTE or FETCH","version":"18.6"},{"entry":{"category":"security","commit_aliases":["12a620686","2cf28d1b9","3294ab839","331016322","3d724bf4f","4fafe2380","5dbeb69bc","5fb3c6389","8f64cc83f","b614de487","bef46aed3"],"commit_groups":[["12a620686","3294ab839","3d724bf4f","4fafe2380"],["2cf28d1b9","331016322","5dbeb69bc","5fb3c6389","8f64cc83f","b614de487","bef46aed3"]],"commits":["4fafe2380"],"cves":["CVE-2026-14669"],"db_id":"1b34d3e2b18d75096fd2914d3673446c","html":"\u003cp\u003eFix buffer overrun with long time zone abbreviation in \u003ccode\u003eto_char()\u003c/code\u003e (Tom Lane) \u003ca href=\"https://postgr.es/c/4fafe2380\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis can easily crash the server, and exploits leading to arbitrary code execution have been reported.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e 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)\u003c/p\u003e","id":"18.6-251aba36d837c523","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)","part":"changes","patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9","f6e281e04c97bcdc5fa29a25f60517ca"],"relations":[{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9","f6e281e04c97bcdc5fa29a25f60517ca"],"same_day":true,"statement_hash":"07a38d896c94ef2711ebb1c7c66bf1537f00d81b7488271a922229ab5b8f1962"},"rule":2,"target":"027ccc17f71deb2b38e14fc8cc82dccd","type":"equivalent"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true},"rule":2,"target":"1ba572e4a9f5584ecce320e293d4b258","type":"related"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9","f6e281e04c97bcdc5fa29a25f60517ca"],"same_day":true,"statement_hash":"07a38d896c94ef2711ebb1c7c66bf1537f00d81b7488271a922229ab5b8f1962"},"rule":2,"target":"70897dba323af27792543b2311799668","type":"equivalent"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true},"rule":2,"target":"771fa954f9b22168a0764dc12074dadb","type":"related"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true},"rule":2,"target":"b17ef22f538327cabf0726e1b3f902cc","type":"related"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9","f6e281e04c97bcdc5fa29a25f60517ca"],"same_day":true,"statement_hash":"07a38d896c94ef2711ebb1c7c66bf1537f00d81b7488271a922229ab5b8f1962"},"rule":2,"target":"bf82a2510c4dfe4309435e9bce0ab3a4","type":"equivalent"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true},"rule":2,"target":"bfa74492dd2c8ed5f4b0a4321cb63c85","type":"related"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9","f6e281e04c97bcdc5fa29a25f60517ca"],"same_day":true,"statement_hash":"07a38d896c94ef2711ebb1c7c66bf1537f00d81b7488271a922229ab5b8f1962"},"rule":2,"target":"bfa88fa3d381bbc9b7ee7a8614ea363c","type":"equivalent"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true},"rule":2,"target":"ea24770278021c00f25a8b13bceb2a2c","type":"related"}],"section":"Changes","section_path":["Changes"],"source_commits":["4fafe2380","5dbeb69bc"],"source_entry_id":"18.6/changes/005","source_hash":"08e4bf2c18b6cd512f8d32024d63b2eb56f09338fc780ac9e5dea9a2d705627b","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"07a38d896c94ef2711ebb1c7c66bf1537f00d81b7488271a922229ab5b8f1962","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()"},"id":"18.6-251aba36d837c523","matches":[{"id":"17.11-9aaf551ddc6d8e1b","source_entry_id":"17.11/changes/005","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix buffer overrun with long time zone abbreviation in to_char()","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/005","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix buffer overrun with long time zone abbreviation in to_char()","version":"18.6"},{"entry":{"category":"security","commit_aliases":["127a0673f","3179253c2","343aabf1d","7df2aa8ef","890327639","b7e5c3f63","e91dcfcca"],"commit_groups":[["127a0673f","3179253c2","343aabf1d","7df2aa8ef","890327639","b7e5c3f63","e91dcfcca"]],"commits":["b7e5c3f63"],"cves":["CVE-2026-14664"],"db_id":"31c6d0327b9be4008171a2064e268f6c","html":"\u003cp\u003eFix buffer overrun in regexp match/split functions (Masahiko Sawada) \u003ca href=\"https://postgr.es/c/b7e5c3f63\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf passed invalidly-encoded data, these functions could write past the end of their conversion buffer.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Francesco Verardi for reporting this problem. (CVE-2026-14664)\u003c/p\u003e","id":"18.6-94204615ddc5390c","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)","part":"changes","patch_ids":["0cfa785ead8bfc886613fffe5a36e1bc"],"relations":[{"evidence":{"patch_ids":["0cfa785ead8bfc886613fffe5a36e1bc"],"same_day":true,"statement_hash":"966f554e1e936775481250a24075b22027e89685eec1e0c08a9bfd4f761ad444"},"rule":2,"target":"2dff40febce19283ae38aa647816cd73","type":"equivalent"},{"evidence":{"patch_ids":["0cfa785ead8bfc886613fffe5a36e1bc"],"same_day":true,"statement_hash":"966f554e1e936775481250a24075b22027e89685eec1e0c08a9bfd4f761ad444"},"rule":2,"target":"8e5a5f5c59f91019e7f4f9160ae97951","type":"equivalent"},{"evidence":{"patch_ids":["0cfa785ead8bfc886613fffe5a36e1bc"],"same_day":true,"statement_hash":"966f554e1e936775481250a24075b22027e89685eec1e0c08a9bfd4f761ad444"},"rule":2,"target":"ee22496a80ac478c7a0e734782b86377","type":"equivalent"},{"evidence":{"patch_ids":["0cfa785ead8bfc886613fffe5a36e1bc"],"same_day":true,"statement_hash":"966f554e1e936775481250a24075b22027e89685eec1e0c08a9bfd4f761ad444"},"rule":2,"target":"ee60c1b700f965a0913e70294c9927f5","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b7e5c3f63"],"source_entry_id":"18.6/changes/006","source_hash":"656802ae623d28a3a12751de94a467f10ff76c8f7d87e4aee4c2fe8b1bee118d","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"966f554e1e936775481250a24075b22027e89685eec1e0c08a9bfd4f761ad444","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"},"id":"18.6-94204615ddc5390c","matches":[{"id":"17.11-cb1b743a0208c3c0","source_entry_id":"17.11/changes/006","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix buffer overrun in regexp match/split functions","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/006","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix buffer overrun in regexp match/split functions","version":"18.6"},{"entry":{"category":"security","commit_aliases":["08e812c02","3b925133b","42d333a78","80ce920a5","849da8210","a16c31d39","ac450853d"],"commit_groups":[["08e812c02","3b925133b","42d333a78","80ce920a5","849da8210","a16c31d39","ac450853d"]],"commits":["08e812c02"],"cves":["CVE-2026-18024"],"db_id":"28116a0caca0f02980e6eaa33ad62878","html":"\u003cp\u003eHarden the \u003ccode\u003eascii()\u003c/code\u003e function against invalid input (Michael Paquier) \u003ca href=\"https://postgr.es/c/08e812c02\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eBy 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Hcamael for reporting this problem. (CVE-2026-18024)\u003c/p\u003e","id":"18.6-4a45e658fb69cefb","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)","part":"changes","patch_ids":["55b264296776b9b13ab6e5f986e375f2"],"relations":[{"evidence":{"patch_ids":["55b264296776b9b13ab6e5f986e375f2"],"same_day":true,"statement_hash":"30f93fe9d01d5c3e7f51b7ee86b38f0ddd66109774cc7f5bd732db874c26c1a3"},"rule":2,"target":"12383fa89e42b03b68791e4222af5d42","type":"equivalent"},{"evidence":{"patch_ids":["55b264296776b9b13ab6e5f986e375f2"],"same_day":true,"statement_hash":"30f93fe9d01d5c3e7f51b7ee86b38f0ddd66109774cc7f5bd732db874c26c1a3"},"rule":2,"target":"3fcea79a14fe4f9b97afbae1d619ffdf","type":"equivalent"},{"evidence":{"patch_ids":["55b264296776b9b13ab6e5f986e375f2"],"same_day":true,"statement_hash":"30f93fe9d01d5c3e7f51b7ee86b38f0ddd66109774cc7f5bd732db874c26c1a3"},"rule":2,"target":"5a7d1cc5fb2e41a7a2acbb0c59894992","type":"equivalent"},{"evidence":{"patch_ids":["55b264296776b9b13ab6e5f986e375f2"],"same_day":true,"statement_hash":"30f93fe9d01d5c3e7f51b7ee86b38f0ddd66109774cc7f5bd732db874c26c1a3"},"rule":2,"target":"776c34393ca8da3ea9c128e3d7219ad3","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["08e812c02"],"source_entry_id":"18.6/changes/007","source_hash":"5049ae9ce81738348074ae45e06e63cd9b97bc4cbabd39fbfb981007af3e98b9","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"30f93fe9d01d5c3e7f51b7ee86b38f0ddd66109774cc7f5bd732db874c26c1a3","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"},"id":"18.6-4a45e658fb69cefb","matches":[{"id":"17.11-e6de3d1ea5ee5a52","source_entry_id":"17.11/changes/007","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Harden the ascii() function against invalid input","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/007","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Harden the ascii() function against invalid input","version":"18.6"},{"entry":{"category":"security","commit_aliases":["08454e8b2","57835938f","8d428c6e6","b3d9262bb"],"commit_groups":[["08454e8b2","57835938f","b3d9262bb"],["8d428c6e6"]],"commits":["08454e8b2","8d428c6e6"],"cves":["CVE-2026-16238"],"db_id":"b73333feb74980fc954bc5f235124549","html":"\u003cp\u003eFix multirange type handling in \u003ccode\u003epg_restore_attribute_stats()\u003c/code\u003e (OpenAI Security Research Team) \u003ca href=\"https://postgr.es/c/08454e8b2\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/8d428c6e6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003epg_restore_attribute_stats()\u003c/code\u003e 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-16238)\u003c/p\u003e","id":"18.6-61ef917ba36ebc0f","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)","part":"changes","patch_ids":["d27616df77f838ec6d65ceac3dab4d29","e919d719afc48bf0f48ebde0e7586d45"],"relations":[{"evidence":{"patch_ids":["d27616df77f838ec6d65ceac3dab4d29","e919d719afc48bf0f48ebde0e7586d45"],"same_day":true,"statement_hash":"6c702ad16b71228cee81cbc85de20c25fe06c4ec29202dc0be958c9f409a702d"},"rule":2,"target":"23063a48b3c2ddae3e3c1623fd1552b5","type":"equivalent"},{"evidence":{"patch_ids":["d27616df77f838ec6d65ceac3dab4d29","e919d719afc48bf0f48ebde0e7586d45"],"same_day":true,"statement_hash":"6c702ad16b71228cee81cbc85de20c25fe06c4ec29202dc0be958c9f409a702d"},"rule":2,"target":"7cdf19717697008d9621e1145ea725cc","type":"equivalent"},{"evidence":{"patch_ids":["d27616df77f838ec6d65ceac3dab4d29","e919d719afc48bf0f48ebde0e7586d45"],"same_day":true,"statement_hash":"6c702ad16b71228cee81cbc85de20c25fe06c4ec29202dc0be958c9f409a702d"},"rule":2,"target":"c02d2730726a9bba001c3dcad007a406","type":"equivalent"},{"evidence":{"patch_ids":["d27616df77f838ec6d65ceac3dab4d29","e919d719afc48bf0f48ebde0e7586d45"],"same_day":true,"statement_hash":"6c702ad16b71228cee81cbc85de20c25fe06c4ec29202dc0be958c9f409a702d"},"rule":2,"target":"e8b2ed03b7135b067945fe6134a48d0c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["08454e8b2","8d428c6e6"],"source_entry_id":"18.6/changes/008","source_hash":"2d778012b54a32e71ae2020cc0542b1f6f274071aca48245105476b79eaf8788","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"6c702ad16b71228cee81cbc85de20c25fe06c4ec29202dc0be958c9f409a702d","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()"},"id":"18.6-61ef917ba36ebc0f","matches":[{"id":"17.11-ba8cb69723cdb335","source_entry_id":"17.11/changes/008","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix multirange type handling in pg_restore_attribute_stats()","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/008","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix multirange type handling in pg_restore_attribute_stats()","version":"18.6"},{"entry":{"category":"security","commit_aliases":["005ffaa7f","0d60ee717","0ebf896f4","591192e2e","59205c7e9","8f0c3d2fe","a2cb5a1cf"],"commit_groups":[["005ffaa7f","0d60ee717","0ebf896f4","591192e2e","59205c7e9","8f0c3d2fe","a2cb5a1cf"]],"commits":["a2cb5a1cf"],"cves":["CVE-2026-14668"],"db_id":"97ac47be877760addc2f5b0afd4a077b","html":"\u003cp\u003eMake \u003ccode\u003escalarineqsel()\u003c/code\u003e check that a constant it expects to be of type \u003ccode\u003etid\u003c/code\u003e actually is (Tom Lane) \u003ca href=\"https://postgr.es/c/a2cb5a1cf\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Hcamael for reporting this problem. (CVE-2026-14668)\u003c/p\u003e","id":"18.6-d63d1269e786113b","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)","part":"changes","patch_ids":["de7610ed8a59864556ff1fc7a996e26b"],"relations":[{"evidence":{"patch_ids":["de7610ed8a59864556ff1fc7a996e26b"],"same_day":true,"statement_hash":"9af3f49dfa69a353a456c0aa2751b844ae492634dd94bd7ac2ae7a38d22121ba"},"rule":2,"target":"0c4b36600df59cbe54ae892784279e12","type":"equivalent"},{"evidence":{"patch_ids":["de7610ed8a59864556ff1fc7a996e26b"],"same_day":true,"statement_hash":"9af3f49dfa69a353a456c0aa2751b844ae492634dd94bd7ac2ae7a38d22121ba"},"rule":2,"target":"7cbf7cb5e5571e3fde38e116219b7ff1","type":"equivalent"},{"evidence":{"patch_ids":["de7610ed8a59864556ff1fc7a996e26b"],"same_day":true,"statement_hash":"9af3f49dfa69a353a456c0aa2751b844ae492634dd94bd7ac2ae7a38d22121ba"},"rule":2,"target":"8e21096b01a0beb228febdc9d9b21e1a","type":"equivalent"},{"evidence":{"patch_ids":["de7610ed8a59864556ff1fc7a996e26b"],"same_day":true,"statement_hash":"9af3f49dfa69a353a456c0aa2751b844ae492634dd94bd7ac2ae7a38d22121ba"},"rule":2,"target":"9bd6480c825dec4b7dd7e98d8eca9b8f","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["a2cb5a1cf"],"source_entry_id":"18.6/changes/009","source_hash":"71a628120eaf5daa06fcc85e23c772587ad03074850944dabf62f1513a399b0b","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"9af3f49dfa69a353a456c0aa2751b844ae492634dd94bd7ac2ae7a38d22121ba","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"},"id":"18.6-d63d1269e786113b","matches":[{"id":"17.11-3000fb5c37bacd7b","source_entry_id":"17.11/changes/009","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/009","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","version":"18.6"},{"entry":{"category":"security","commit_aliases":["1e3014f37","23d9ad771","3b2238fbe","4f8b37b6b","7c1a8805a","7c2ba321d","84b6a7a06","8e87bd473","90649b6f8","cb947ca31","dddc8a69f","e25135057","f443d0a0a","fe0b5bd6d"],"commit_groups":[["1e3014f37","3b2238fbe","4f8b37b6b","84b6a7a06","8e87bd473","90649b6f8","dddc8a69f"],["23d9ad771","7c1a8805a","7c2ba321d","cb947ca31","e25135057","f443d0a0a","fe0b5bd6d"]],"commits":["dddc8a69f","e25135057"],"cves":["CVE-2026-14662"],"db_id":"e8daa5e986b5139aa334ffb65fe716c9","html":"\u003cp\u003eHarden \u003ccode\u003etsvector\u003c/code\u003e and \u003ccode\u003etsquery\u003c/code\u003e code against overly long values (both individual lexemes and total vector/query length) (Tom Lane) \u003ca href=\"https://postgr.es/c/e25135057\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/dddc8a69f\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe documented limits were not enforced in all code paths.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Yuhang Wu, Zhenpeng Lin, Zheng Yu, and Hcamael for reporting these problems. (CVE-2026-14662)\u003c/p\u003e","id":"18.6-774bcf033add5976","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)","part":"changes","patch_ids":["5d937de349e172af32f322b84994627c","8594911de53a70a64ff7a92a7e2e7410"],"relations":[{"evidence":{"patch_ids":["5d937de349e172af32f322b84994627c","8594911de53a70a64ff7a92a7e2e7410"],"same_day":true,"statement_hash":"58ee7f5cd2b407484897fe1a7e956c16ce0212b7ffe535ead9c50c21ba819c1e"},"rule":2,"target":"3d26273adc446717f1dd7040f0311025","type":"equivalent"},{"evidence":{"patch_ids":["5d937de349e172af32f322b84994627c","8594911de53a70a64ff7a92a7e2e7410"],"same_day":true,"statement_hash":"58ee7f5cd2b407484897fe1a7e956c16ce0212b7ffe535ead9c50c21ba819c1e"},"rule":2,"target":"728b5628883585075c121bd29db0affe","type":"equivalent"},{"evidence":{"patch_ids":["5d937de349e172af32f322b84994627c","8594911de53a70a64ff7a92a7e2e7410"],"same_day":true,"statement_hash":"58ee7f5cd2b407484897fe1a7e956c16ce0212b7ffe535ead9c50c21ba819c1e"},"rule":2,"target":"aa4dcca3c56a82ca052b2bdbc7e68c1b","type":"equivalent"},{"evidence":{"patch_ids":["5d937de349e172af32f322b84994627c","8594911de53a70a64ff7a92a7e2e7410"],"same_day":true,"statement_hash":"58ee7f5cd2b407484897fe1a7e956c16ce0212b7ffe535ead9c50c21ba819c1e"},"rule":2,"target":"f4f98b5e09530fc0d9eabe85409d03ef","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["dddc8a69f","e25135057"],"source_entry_id":"18.6/changes/010","source_hash":"9634a8c9c802cecb1686784102c75528a5294d81c7a5ed66b0e5c5818f24b1c3","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"58ee7f5cd2b407484897fe1a7e956c16ce0212b7ffe535ead9c50c21ba819c1e","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)"},"id":"18.6-774bcf033add5976","matches":[{"id":"17.11-730aec962ef92894","source_entry_id":"17.11/changes/010","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)","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/010","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)","version":"18.6"},{"entry":{"category":"security","commit_aliases":["2a03f21da","32e0d25d4","42d9749b7","60e7329b9","797e3cc4c","7bd56f7a3","7f0e1aac7","8a40f4b09","8c67c4cf5","92972e815","b417744a7","c7f462838","cf44ff5e6","eb2fa2704"],"commit_groups":[["2a03f21da","32e0d25d4","42d9749b7","60e7329b9","8a40f4b09","c7f462838","eb2fa2704"],["797e3cc4c","7bd56f7a3","7f0e1aac7","8c67c4cf5","92972e815","b417744a7","cf44ff5e6"]],"commits":["2a03f21da","7f0e1aac7"],"cves":["CVE-2026-14679"],"db_id":"4a55b4d9f252330dd0f0f94102631952","html":"\u003cp\u003eFix various places that mistakenly assumed they would not have to deal with more than \u003ccode\u003eFUNC_MAX_ARGS\u003c/code\u003e function arguments (Tom Lane) \u003ca href=\"https://postgr.es/c/7f0e1aac7\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/2a03f21da\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eNotably, the server's actual limit on the number of arguments to an aggregate function is \u003ccode\u003eFUNC_MAX_ARGS - 1\u003c/code\u003e, but the parser failed to enforce that, creating hazards downstream.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Zheng Yu, ylwangtju, and Masahiko Sawada for reporting these problems. (CVE-2026-14679)\u003c/p\u003e","id":"18.6-fe89a6f688a29e60","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)","part":"changes","patch_ids":["9c4aca692d373e760403997525c9e073","ea0a783b3715942dc32c661399220cb1"],"relations":[{"evidence":{"patch_ids":["9c4aca692d373e760403997525c9e073","ea0a783b3715942dc32c661399220cb1"],"same_day":true,"statement_hash":"41c4e79daa1ea65508b91d04fa5138fb9c313606a4ceade697072cb89843941f"},"rule":2,"target":"349adc6ad9cc12d1c04aad6e3d659917","type":"equivalent"},{"evidence":{"patch_ids":["9c4aca692d373e760403997525c9e073","ea0a783b3715942dc32c661399220cb1"],"same_day":true,"statement_hash":"41c4e79daa1ea65508b91d04fa5138fb9c313606a4ceade697072cb89843941f"},"rule":2,"target":"41c6f110168cdb7324811a04a2654cf2","type":"equivalent"},{"evidence":{"patch_ids":["9c4aca692d373e760403997525c9e073","ea0a783b3715942dc32c661399220cb1"],"same_day":true,"statement_hash":"41c4e79daa1ea65508b91d04fa5138fb9c313606a4ceade697072cb89843941f"},"rule":2,"target":"b48c4a1b729ca10627402a86238f5a19","type":"equivalent"},{"evidence":{"patch_ids":["9c4aca692d373e760403997525c9e073","ea0a783b3715942dc32c661399220cb1"],"same_day":true,"statement_hash":"41c4e79daa1ea65508b91d04fa5138fb9c313606a4ceade697072cb89843941f"},"rule":2,"target":"bea7e191e30a8a238690f6d536666b13","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["2a03f21da","7f0e1aac7"],"source_entry_id":"18.6/changes/011","source_hash":"78336166a7234ad10b84a1249d4b43d09a265825e59787c04f3fc43d58a86256","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"41c4e79daa1ea65508b91d04fa5138fb9c313606a4ceade697072cb89843941f","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"},"id":"18.6-fe89a6f688a29e60","matches":[{"id":"17.11-dd9a429d3ce13500","source_entry_id":"17.11/changes/011","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/011","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","version":"18.6"},{"entry":{"category":"security","commit_aliases":["155dacbc5","1aa601b4f","21a00de43","21d8cfb18","4c0c1b2cd","54649de65","722695db1","7f308dd7c","83d0a083f","8f7e35b08","913fe0c31","d6e861e19","e926a9aac","eb9e55297"],"commit_groups":[["155dacbc5","21a00de43","4c0c1b2cd","54649de65","8f7e35b08","e926a9aac","eb9e55297"],["1aa601b4f","21d8cfb18","722695db1","7f308dd7c","83d0a083f","913fe0c31","d6e861e19"]],"commits":["54649de65","722695db1"],"cves":["CVE-2026-14680"],"db_id":"02bb5a11139923dd7f170a94556495c3","html":"\u003cp\u003eReject calls from SQL to functions that take or return type \u003ccode\u003einternal\u003c/code\u003e (Tom Lane) \u003ca href=\"https://postgr.es/c/54649de65\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/722695db1\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe existing defenses against doing this have been shown to be insufficient, so add more explicit checks.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Amy Burnett (OpenAI Codex Security) for reporting this problem. (CVE-2026-14680)\u003c/p\u003e","id":"18.6-a8d1f97d70d85295","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)","part":"changes","patch_ids":["8b623dad3bf883bcb9bd41023fc8f168","b94f9935e7be4a2be88c49eae8a6ae70"],"relations":[{"evidence":{"patch_ids":["8b623dad3bf883bcb9bd41023fc8f168","b94f9935e7be4a2be88c49eae8a6ae70"],"same_day":true,"statement_hash":"713f97bceae2187dec2f42b397097077fb7eec20b6eddb9a6fb32f8878d44f9f"},"rule":2,"target":"42aa2e3353b4536c48a5271f47f0eb90","type":"equivalent"},{"evidence":{"patch_ids":["8b623dad3bf883bcb9bd41023fc8f168","b94f9935e7be4a2be88c49eae8a6ae70"],"same_day":true,"statement_hash":"713f97bceae2187dec2f42b397097077fb7eec20b6eddb9a6fb32f8878d44f9f"},"rule":2,"target":"97ff2029068cd51a1802927b5b54f2d3","type":"equivalent"},{"evidence":{"patch_ids":["8b623dad3bf883bcb9bd41023fc8f168","b94f9935e7be4a2be88c49eae8a6ae70"],"same_day":true,"statement_hash":"713f97bceae2187dec2f42b397097077fb7eec20b6eddb9a6fb32f8878d44f9f"},"rule":2,"target":"b56373871b3aaa929aaba36a65e4eb45","type":"equivalent"},{"evidence":{"patch_ids":["8b623dad3bf883bcb9bd41023fc8f168","b94f9935e7be4a2be88c49eae8a6ae70"],"same_day":true,"statement_hash":"713f97bceae2187dec2f42b397097077fb7eec20b6eddb9a6fb32f8878d44f9f"},"rule":2,"target":"e54c1abdbc2feb1d5c81f31cc4a073f8","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["54649de65","722695db1"],"source_entry_id":"18.6/changes/012","source_hash":"9fc338e9d48ea9fb35714275ed0d3331db14eb450da43f5cebbd900436553e52","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"713f97bceae2187dec2f42b397097077fb7eec20b6eddb9a6fb32f8878d44f9f","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"},"id":"18.6-a8d1f97d70d85295","matches":[{"id":"17.11-ea70ef62a58da283","source_entry_id":"17.11/changes/012","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Reject calls from SQL to functions that take or return type internal","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/012","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Reject calls from SQL to functions that take or return type internal","version":"18.6"},{"entry":{"category":"security","commit_aliases":["6713a6e04","70a3b4e18","75a03c569","7c3367ab5","93b93f28f","a1fa24127","fb6d1ca8d"],"commit_groups":[["6713a6e04","70a3b4e18","75a03c569","7c3367ab5","93b93f28f","a1fa24127","fb6d1ca8d"]],"commits":["a1fa24127"],"cves":["CVE-2026-6469"],"db_id":"4ce18d2a1cf23ef6c7ff55c667d59eae","html":"\u003cp\u003ePreserve the ownership of extended statistics objects when they are rebuilt by \u003ccode\u003eALTER TABLE\u003c/code\u003e (Masahiko Sawada) \u003ca href=\"https://postgr.es/c/a1fa24127\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, the role running \u003ccode\u003eALTER TABLE\u003c/code\u003e gained ownership of such objects, but that seems inappropriate.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Noah Misch for reporting this problem. (CVE-2026-6469)\u003c/p\u003e","id":"18.6-c42539c16ee68f2f","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)","part":"changes","patch_ids":["c847f131eaad282f5fa724ff040f1fc2"],"relations":[{"evidence":{"patch_ids":["c847f131eaad282f5fa724ff040f1fc2"],"same_day":true,"statement_hash":"855872db5602ac9ec63e8c9b362b906eef0f29c2ae3da9a0473220149fc815a6"},"rule":2,"target":"a45d7275fb35413aaeeb017f13dfbf83","type":"equivalent"},{"evidence":{"patch_ids":["c847f131eaad282f5fa724ff040f1fc2"],"same_day":true,"statement_hash":"855872db5602ac9ec63e8c9b362b906eef0f29c2ae3da9a0473220149fc815a6"},"rule":2,"target":"a511c71fb1c56e7bba21699bf176d02f","type":"equivalent"},{"evidence":{"patch_ids":["c847f131eaad282f5fa724ff040f1fc2"],"same_day":true,"statement_hash":"855872db5602ac9ec63e8c9b362b906eef0f29c2ae3da9a0473220149fc815a6"},"rule":2,"target":"ddb05610c858789527b1369d30b4bb1c","type":"equivalent"},{"evidence":{"patch_ids":["c847f131eaad282f5fa724ff040f1fc2"],"same_day":true,"statement_hash":"855872db5602ac9ec63e8c9b362b906eef0f29c2ae3da9a0473220149fc815a6"},"rule":2,"target":"f73abeba4ef827229ec4b724b2dbde1b","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["a1fa24127"],"source_entry_id":"18.6/changes/013","source_hash":"24663e30aeab6ad754d8132d106fe4a7a7973900d0381b17c6a730bc4a47640c","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"855872db5602ac9ec63e8c9b362b906eef0f29c2ae3da9a0473220149fc815a6","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"},"id":"18.6-c42539c16ee68f2f","matches":[{"id":"17.11-50a00c5a01592c04","source_entry_id":"17.11/changes/013","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/013","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","version":"18.6"},{"entry":{"category":"security","commit_aliases":["0ddd9098a","44ea6764b","5981fe370","5e5ea74e3","967acab87","a3832a757","f9729b507"],"commit_groups":[["0ddd9098a","44ea6764b","5981fe370","5e5ea74e3","967acab87","a3832a757","f9729b507"]],"commits":["0ddd9098a"],"cves":["CVE-2026-15741"],"db_id":"57a69063ff0b7f44b253f158536bbc64","html":"\u003cp\u003eWhen deparsing an \u003ccode\u003eEXTRACT()\u003c/code\u003e function call, quote the field name if needed (Nathan Bossart) \u003ca href=\"https://postgr.es/c/0ddd9098a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe parser accepts any string literal as a field name in \u003ccode\u003eEXTRACT()\u003c/code\u003e, deferring validation to execution. If the call is stored and deparsed (for example during \u003cspan\u003epg_dump\u003c/span\u003e), the string body was regurgitated verbatim, allowing SQL injection.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15741)\u003c/p\u003e","id":"18.6-323a1fc7b03b6859","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)","part":"changes","patch_ids":["f0b1d31c8ffb5349b650b0e3b88706ad"],"relations":[{"evidence":{"patch_ids":["f0b1d31c8ffb5349b650b0e3b88706ad"],"same_day":true,"statement_hash":"8fb62033eeb6ede7911fce4b990d20a94bf88226d146867552627bcce9f533ef"},"rule":2,"target":"0b6c8ce7fe6e116e2bb99be5e53dff29","type":"equivalent"},{"evidence":{"patch_ids":["f0b1d31c8ffb5349b650b0e3b88706ad"],"same_day":true,"statement_hash":"8fb62033eeb6ede7911fce4b990d20a94bf88226d146867552627bcce9f533ef"},"rule":2,"target":"46e3e259f29471b862d3a1eeaae97525","type":"equivalent"},{"evidence":{"patch_ids":["f0b1d31c8ffb5349b650b0e3b88706ad"],"same_day":true,"statement_hash":"8fb62033eeb6ede7911fce4b990d20a94bf88226d146867552627bcce9f533ef"},"rule":2,"target":"7c6c8c33a06891c077c2444b81e229fb","type":"equivalent"},{"evidence":{"patch_ids":["f0b1d31c8ffb5349b650b0e3b88706ad"],"same_day":true,"statement_hash":"8fb62033eeb6ede7911fce4b990d20a94bf88226d146867552627bcce9f533ef"},"rule":2,"target":"9677e1d0e314b1250191bf908cc27099","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["0ddd9098a"],"source_entry_id":"18.6/changes/014","source_hash":"b0f3b42c30940539f07658c95026fe3f58860d297a362ca19ea132415bd9848d","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"8fb62033eeb6ede7911fce4b990d20a94bf88226d146867552627bcce9f533ef","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"},"id":"18.6-323a1fc7b03b6859","matches":[{"id":"17.11-2bafbd49437d6dde","source_entry_id":"17.11/changes/014","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"When deparsing an EXTRACT() function call, quote the field name if needed","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/014","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"When deparsing an EXTRACT() function call, quote the field name if needed","version":"18.6"},{"entry":{"category":"security","commit_aliases":["1a358b8f2","24855357c","278053843","2e91f8548","323af0a4e","424fb7160","4fac4c108","53ed5ebd8","57f59ca1d","671359605","6dbedd48b","7a761fe40","7ce056b17","97e277402","a9f6e768a","b6e45b4f8","bb1bc525d","c062734cd","d1c8aa0b0","efdb26072","fd6d3e7e9"],"commit_groups":[["1a358b8f2","278053843","424fb7160","4fac4c108","6dbedd48b","7ce056b17","d1c8aa0b0"],["24855357c","2e91f8548","323af0a4e","97e277402","a9f6e768a","efdb26072","fd6d3e7e9"],["53ed5ebd8","57f59ca1d","671359605","7a761fe40","b6e45b4f8","bb1bc525d","c062734cd"]],"commits":["278053843","2e91f8548","57f59ca1d"],"cves":["CVE-2026-6470"],"db_id":"56232d6e6345f5c09340b72ed581eb4d","html":"\u003cp\u003eCheck for \u003ccode\u003eUSAGE\u003c/code\u003e privilege on data types in places that formerly failed to check that (Nathan Bossart) \u003ca href=\"https://postgr.es/c/2e91f8548\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/57f59ca1d\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/278053843\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eCREATE TYPE AS RANGE\u003c/code\u003e did not check, nor did \u003ccode\u003eALTER TABLE OF\u003c/code\u003e, nor did commands that create stored expressions. These omissions allowed roles without \u003ccode\u003eUSAGE\u003c/code\u003e privilege to nonetheless create objects depending on the type, possibly blocking the type's owner from changing the type later.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Jingzhou Fu for reporting this problem. (CVE-2026-6470)\u003c/p\u003e","id":"18.6-0b5cda175039a2c3","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)","part":"changes","patch_ids":["2470df146b9201b14de19f772c90d867","2de75ceea92e216f0b0f3ec035342d7e","76d1b8b6ad0cee83e43cc4a88d123867"],"relations":[{"evidence":{"patch_ids":["2470df146b9201b14de19f772c90d867","2de75ceea92e216f0b0f3ec035342d7e","76d1b8b6ad0cee83e43cc4a88d123867"],"same_day":true,"statement_hash":"f6ec51b2de1a066951596511e998a5e51ac29a83e3c8e018df4d6e981ebe7068"},"rule":2,"target":"8c93b6ddad829461b98126755a87488f","type":"equivalent"},{"evidence":{"patch_ids":["2470df146b9201b14de19f772c90d867","2de75ceea92e216f0b0f3ec035342d7e","76d1b8b6ad0cee83e43cc4a88d123867"],"same_day":true,"statement_hash":"f6ec51b2de1a066951596511e998a5e51ac29a83e3c8e018df4d6e981ebe7068"},"rule":2,"target":"e50027af5564cb33c0ec80ab0f86e1a9","type":"equivalent"},{"evidence":{"patch_ids":["2470df146b9201b14de19f772c90d867","2de75ceea92e216f0b0f3ec035342d7e","76d1b8b6ad0cee83e43cc4a88d123867"],"same_day":true,"statement_hash":"f6ec51b2de1a066951596511e998a5e51ac29a83e3c8e018df4d6e981ebe7068"},"rule":2,"target":"f2f63cd272a4e4c0c968eacb6779415b","type":"equivalent"},{"evidence":{"patch_ids":["2470df146b9201b14de19f772c90d867","2de75ceea92e216f0b0f3ec035342d7e","76d1b8b6ad0cee83e43cc4a88d123867"],"same_day":true,"statement_hash":"f6ec51b2de1a066951596511e998a5e51ac29a83e3c8e018df4d6e981ebe7068"},"rule":2,"target":"f44708d4a1d626e3b8656335ae598c69","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["278053843","2e91f8548","57f59ca1d"],"source_entry_id":"18.6/changes/015","source_hash":"75e3a152860bf6489cdbd50ff6c57c8551e228583eb60e84a8b6068bf59b58c6","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"f6ec51b2de1a066951596511e998a5e51ac29a83e3c8e018df4d6e981ebe7068","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"},"id":"18.6-0b5cda175039a2c3","matches":[{"id":"17.11-575634f97737603c","source_entry_id":"17.11/changes/015","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/015","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","version":"18.6"},{"entry":{"category":"security","commit_aliases":["0b12f56bf","17b6083db","1974acf23","567286b76","f4174aa84","f5f2da795","ffca23839"],"commit_groups":[["0b12f56bf","17b6083db","1974acf23","567286b76","f4174aa84","f5f2da795","ffca23839"]],"commits":["0b12f56bf"],"cves":["CVE-2026-14666"],"db_id":"0e200ae2afa3db031ffa07314f2deab2","html":"\u003cp\u003eInvalidate role-dependent cached plans after role changes (Ilya Staroverov, Shinya Kato, Nathan Bossart) \u003ca href=\"https://postgr.es/c/0b12f56bf\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eRole 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Ilya Staroverov and Shinya Kato for reporting this problem. (CVE-2026-14666)\u003c/p\u003e","id":"18.6-ad01030c7fc964f1","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)","part":"changes","patch_ids":["7a5d6580a542a5467ce64bfd9ad2b724"],"relations":[{"evidence":{"patch_ids":["7a5d6580a542a5467ce64bfd9ad2b724"],"same_day":true,"statement_hash":"b27f8aace3b388937c6e28c9f1ede652d42059e6b0a2111846c88a4b39769432"},"rule":2,"target":"043b1e2a717a3c7862402faa9c4b1f91","type":"equivalent"},{"evidence":{"patch_ids":["7a5d6580a542a5467ce64bfd9ad2b724"],"same_day":true,"statement_hash":"b27f8aace3b388937c6e28c9f1ede652d42059e6b0a2111846c88a4b39769432"},"rule":2,"target":"49941507efa272e723ff0698b2236a6e","type":"equivalent"},{"evidence":{"patch_ids":["7a5d6580a542a5467ce64bfd9ad2b724"],"same_day":true,"statement_hash":"b27f8aace3b388937c6e28c9f1ede652d42059e6b0a2111846c88a4b39769432"},"rule":2,"target":"652fbbbd4aff8c1d5babff0cde01bc7f","type":"equivalent"},{"evidence":{"patch_ids":["7a5d6580a542a5467ce64bfd9ad2b724"],"same_day":true,"statement_hash":"b27f8aace3b388937c6e28c9f1ede652d42059e6b0a2111846c88a4b39769432"},"rule":2,"target":"c1425f2f64ac014a0d5ac494fbe66faf","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["0b12f56bf"],"source_entry_id":"18.6/changes/016","source_hash":"4b0f6546901b6c865183e9d3201d0ebca911407b1403022f7e39db73d6ef8c30","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"b27f8aace3b388937c6e28c9f1ede652d42059e6b0a2111846c88a4b39769432","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"},"id":"18.6-ad01030c7fc964f1","matches":[{"id":"17.11-43977a837123cada","source_entry_id":"17.11/changes/016","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Invalidate role-dependent cached plans after role changes","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/016","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Invalidate role-dependent cached plans after role changes","version":"18.6"},{"entry":{"category":"security","commit_aliases":["067a64d40","203a48209","3bf185b4b","bf1bb7e29"],"commit_groups":[["067a64d40","203a48209","3bf185b4b","bf1bb7e29"]],"commits":["203a48209"],"cves":["CVE-2026-14681"],"db_id":"deae128594614e84894b8e7a7062759f","html":"\u003cp\u003eReject GSSEncRequest after direct SSL connection (Michael Paquier) \u003ca href=\"https://postgr.es/c/203a48209\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAfter 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 \u003ccode\u003epg_hba\u003c/code\u003e rules. Thus, a \u003ccode\u003epg_hba\u003c/code\u003e policy intending to disallow TLS would not be enforced correctly.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks p4p3r for reporting this problem. (CVE-2026-14681)\u003c/p\u003e","id":"18.6-ed40b113af1a65e3","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)","part":"changes","patch_ids":["0a86d0c924c70e8b47408f823a77a964"],"relations":[{"evidence":{"patch_ids":["0a86d0c924c70e8b47408f823a77a964"],"same_day":true,"statement_hash":"f08040a4f6b5dfe94a4b30090677fd13c199828e108149421fa23eaa60d5f620"},"rule":2,"target":"55da165c3ced2d17689a546cd13a10f8","type":"equivalent"},{"evidence":{"patch_ids":["0a86d0c924c70e8b47408f823a77a964"],"same_day":true,"statement_hash":"f08040a4f6b5dfe94a4b30090677fd13c199828e108149421fa23eaa60d5f620"},"rule":2,"target":"bdd453999af206604b4ae0c623733bc5","type":"equivalent"},{"evidence":{"patch_ids":["0a86d0c924c70e8b47408f823a77a964"],"same_day":true,"statement_hash":"f08040a4f6b5dfe94a4b30090677fd13c199828e108149421fa23eaa60d5f620"},"rule":2,"target":"efca948aece74421d5dff07ca459356e","type":"equivalent"},{"evidence":{"patch_ids":["0a86d0c924c70e8b47408f823a77a964"],"same_day":true,"statement_hash":"f08040a4f6b5dfe94a4b30090677fd13c199828e108149421fa23eaa60d5f620"},"rule":2,"target":"fae551c24851f8412783e17b85987136","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["203a48209"],"source_entry_id":"18.6/changes/017","source_hash":"f4e2864baf55c24b865ce6284f997649fdadecb1671b9173a5b147049484bf3f","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"f08040a4f6b5dfe94a4b30090677fd13c199828e108149421fa23eaa60d5f620","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"},"id":"18.6-ed40b113af1a65e3","matches":[{"id":"17.11-1d103f53312d0305","source_entry_id":"17.11/changes/017","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Reject GSSEncRequest after direct SSL connection","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/017","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Reject GSSEncRequest after direct SSL connection","version":"18.6"},{"entry":{"category":"security","commit_aliases":["4d192fa16","822143c4d","dec60e8ad","fadbe882d","feb8b0182"],"commit_groups":[["4d192fa16","822143c4d","dec60e8ad","fadbe882d","feb8b0182"]],"commits":["822143c4d"],"cves":["CVE-2026-14672"],"db_id":"360618cf2b5023ffb07258f47a407319","html":"\u003cp\u003eMake mock SCRAM authentication secrets more plausible (Nathan Bossart) \u003ca href=\"https://postgr.es/c/822143c4d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf 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 \u003ccode\u003escram_iterations\u003c/code\u003e instead, to make the mock secret look more like the installation's real secrets.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Radim Marek for reporting this problem. (CVE-2026-14672)\u003c/p\u003e","id":"18.6-bb742148aa1ab70a","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)","part":"changes","patch_ids":["b915b0f76ef63e3fd030de3a5e4052c7"],"relations":[{"evidence":{"patch_ids":["b915b0f76ef63e3fd030de3a5e4052c7"],"same_day":true,"statement_hash":"76daff375fab06e676eed2c7ce655a806a67e546c22e89cce3f2506387c91178"},"rule":2,"target":"0b4b5a7457f7fbba0ac49362d4205d94","type":"equivalent"},{"evidence":{"patch_ids":["b915b0f76ef63e3fd030de3a5e4052c7"],"same_day":true,"statement_hash":"76daff375fab06e676eed2c7ce655a806a67e546c22e89cce3f2506387c91178"},"rule":2,"target":"328f985aab0b40a393740fb418be993c","type":"equivalent"},{"evidence":{"patch_ids":["b915b0f76ef63e3fd030de3a5e4052c7"],"same_day":true,"statement_hash":"76daff375fab06e676eed2c7ce655a806a67e546c22e89cce3f2506387c91178"},"rule":2,"target":"465da641b2ad8e32d9b3eff9044cfd21","type":"equivalent"},{"evidence":{"patch_ids":["b915b0f76ef63e3fd030de3a5e4052c7"],"same_day":true,"statement_hash":"76daff375fab06e676eed2c7ce655a806a67e546c22e89cce3f2506387c91178"},"rule":2,"target":"adc5092861582d88d34f6a1b1124f2eb","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["822143c4d"],"source_entry_id":"18.6/changes/018","source_hash":"b6d6fce5b17052a224535f8883fd14426e8400bcc457f265cd697f4f32c9a224","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"76daff375fab06e676eed2c7ce655a806a67e546c22e89cce3f2506387c91178","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"},"id":"18.6-bb742148aa1ab70a","matches":[{"id":"17.11-f319d2c2bdee8718","source_entry_id":"17.11/changes/018","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Make mock SCRAM authentication secrets more plausible","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/018","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Make mock SCRAM authentication secrets more plausible","version":"18.6"},{"entry":{"category":"security","commit_aliases":["39f855e0e","457b8737a","5737110b6","74c59d062","a14ba29b1","c3c830272","c7da85fec"],"commit_groups":[["39f855e0e","457b8737a","5737110b6","74c59d062","a14ba29b1","c3c830272","c7da85fec"]],"commits":["a14ba29b1"],"cves":["CVE-2026-16241"],"db_id":"c7e226410c72dad9c39b76d880e2f2a5","html":"\u003cp\u003eFix out-of-bounds writes in \u003cspan\u003eecpg\u003c/span\u003e applications caused by invalid \u003ccode\u003ebytea\u003c/code\u003e data received from the server (Michael Paquier) \u003ca href=\"https://postgr.es/c/a14ba29b1\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003eecpg\u003c/span\u003e assumed without checking that any \u003ccode\u003ebytea\u003c/code\u003e value must begin with \u003ccode\u003e\\x\u003c/code\u003e. A broken or malicious server might send a string shorter than 2 bytes, resulting in memory clobber in the application.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks ylwangtju for reporting this problem. (CVE-2026-16241)\u003c/p\u003e","id":"18.6-2d9ddb6163eca29a","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)","part":"changes","patch_ids":["eda4e515c03b7210bd33a13cc191c754"],"relations":[{"evidence":{"patch_ids":["eda4e515c03b7210bd33a13cc191c754"],"same_day":true,"statement_hash":"ef3db74c8b626f19d33ecc7d3b8e292c1e11cd1089b59edbc38f72bd729fe946"},"rule":2,"target":"18aec69fea13406451ddcbd0d4c23a88","type":"equivalent"},{"evidence":{"patch_ids":["eda4e515c03b7210bd33a13cc191c754"],"same_day":true,"statement_hash":"ef3db74c8b626f19d33ecc7d3b8e292c1e11cd1089b59edbc38f72bd729fe946"},"rule":2,"target":"4fb7c5910a0436ce3e2bb2ab88b25a87","type":"equivalent"},{"evidence":{"patch_ids":["eda4e515c03b7210bd33a13cc191c754"],"same_day":true,"statement_hash":"ef3db74c8b626f19d33ecc7d3b8e292c1e11cd1089b59edbc38f72bd729fe946"},"rule":2,"target":"7393e9b24b9abe3400e3f04577d58cba","type":"equivalent"},{"evidence":{"patch_ids":["eda4e515c03b7210bd33a13cc191c754"],"same_day":true,"statement_hash":"ef3db74c8b626f19d33ecc7d3b8e292c1e11cd1089b59edbc38f72bd729fe946"},"rule":2,"target":"f5473f236236eb170503879999034ecc","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["a14ba29b1"],"source_entry_id":"18.6/changes/019","source_hash":"bf6d1d41094210cd2ecc127ceb7d2a543ec1b49bae85d8b91a8b744c663c3bbf","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"ef3db74c8b626f19d33ecc7d3b8e292c1e11cd1089b59edbc38f72bd729fe946","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"},"id":"18.6-2d9ddb6163eca29a","matches":[{"id":"17.11-368d04431d80a7fd","source_entry_id":"17.11/changes/019","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/019","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","version":"18.6"},{"entry":{"category":"security","commit_aliases":["0119aa30e","086f6f176","0bfac9e1f","2006fca40","33d0c63fb","71ca694c7","df245c374"],"commit_groups":[["0119aa30e","086f6f176","0bfac9e1f","2006fca40","33d0c63fb","71ca694c7","df245c374"]],"commits":["71ca694c7"],"cves":["CVE-2025-8714","CVE-2026-18408"],"db_id":"36ccc2b6f4b04376dc6bf74ae3d2f6de","html":"\u003cp\u003eDo not do backquote expansion on the argument of \u003cspan\u003epsql\u003c/span\u003e's \u003ccode\u003e\\unrestrict\u003c/code\u003e command (Nathan Bossart) \u003ca href=\"https://postgr.es/c/71ca694c7\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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 \u003cspan\u003epsql\u003c/span\u003e, the exact scenario that CVE-2025-8714 intended to prevent.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Lucas Velgus, Filip Janus, and Daniel Bakker for reporting this problem. (CVE-2026-18408)\u003c/p\u003e","id":"18.6-2227ccac7ef5135c","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)","part":"changes","patch_ids":["061af71132ccdfb4f1bbeed893be595c"],"relations":[{"evidence":{"patch_ids":["061af71132ccdfb4f1bbeed893be595c"],"same_day":true,"statement_hash":"3a14df9ccfd7372d3dac771a23f52e41c3376ea71cf1946e2c9e95f97d2b5d3b"},"rule":2,"target":"49dd1006826cb5f529df97b64194c139","type":"equivalent"},{"evidence":{"patch_ids":["061af71132ccdfb4f1bbeed893be595c"],"same_day":true,"statement_hash":"3a14df9ccfd7372d3dac771a23f52e41c3376ea71cf1946e2c9e95f97d2b5d3b"},"rule":2,"target":"5221242491685338de78e8922e1f353a","type":"equivalent"},{"evidence":{"patch_ids":["061af71132ccdfb4f1bbeed893be595c"],"same_day":true,"statement_hash":"3a14df9ccfd7372d3dac771a23f52e41c3376ea71cf1946e2c9e95f97d2b5d3b"},"rule":2,"target":"56ffc2f53e9a050b5de71327d3cef06f","type":"equivalent"},{"evidence":{"patch_ids":["061af71132ccdfb4f1bbeed893be595c"],"same_day":true,"statement_hash":"3a14df9ccfd7372d3dac771a23f52e41c3376ea71cf1946e2c9e95f97d2b5d3b"},"rule":2,"target":"7a747536f32a440151dcb2b04ac4e968","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["71ca694c7"],"source_entry_id":"18.6/changes/020","source_hash":"70f1f2d332357c2ca128a1dfdb521c31951bc150a0902b355418af50095c6552","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"3a14df9ccfd7372d3dac771a23f52e41c3376ea71cf1946e2c9e95f97d2b5d3b","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"},"id":"18.6-2227ccac7ef5135c","matches":[{"id":"17.11-7f417b32587acff8","source_entry_id":"17.11/changes/020","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Do not do backquote expansion on the argument of psql's \\unrestrict command","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/020","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Do not do backquote expansion on the argument of psql's \\unrestrict command","version":"18.6"},{"entry":{"category":"security","commit_aliases":["13bb73aeb","3299c2ba0","3392cce5c","57aa21f69","71ba5705d","86cd82bf4","c2b16f5d4"],"commit_groups":[["13bb73aeb","3299c2ba0","3392cce5c","57aa21f69","71ba5705d","86cd82bf4","c2b16f5d4"]],"commits":["3392cce5c"],"cves":["CVE-2026-19385"],"db_id":"f91d32a8c03492afba6d7ba835690a32","html":"\u003cp\u003eRemove \u003cspan\u003epg_dump\u003c/span\u003e's assumption that \u003ccode\u003epg_proc\u003c/code\u003e.\u003ccode\u003eprotrftypes\u003c/code\u003e cannot have more than \u003ccode\u003eFUNC_MAX_ARGS\u003c/code\u003e entries (Tom Lane) \u003ca href=\"https://postgr.es/c/3392cce5c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSince there could be entries for both input and output arguments, it's feasible for this array's length to exceed \u003ccode\u003eFUNC_MAX_ARGS\u003c/code\u003e (which constrains only input arguments). Even if that were not so, \u003cspan\u003epg_dump\u003c/span\u003e cannot assume that the server was built with the same value of \u003ccode\u003eFUNC_MAX_ARGS\u003c/code\u003e that it has. An overrun would lead to a memory clobber inside \u003cspan\u003epg_dump\u003c/span\u003e.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Masahiko Sawada for reporting this problem. (CVE-2026-19385)\u003c/p\u003e","id":"18.6-d40f8de8e21a4c6f","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)","part":"changes","patch_ids":["185500373cc27d3d610be991561eb522"],"relations":[{"evidence":{"patch_ids":["185500373cc27d3d610be991561eb522"],"same_day":true,"statement_hash":"0503fb690855a4bf21f955b8b62af71583c422a4e69c4c228faea1f3e3f8b84b"},"rule":2,"target":"5183659937548a24721c52721ce5656b","type":"equivalent"},{"evidence":{"patch_ids":["185500373cc27d3d610be991561eb522"],"same_day":true,"statement_hash":"0503fb690855a4bf21f955b8b62af71583c422a4e69c4c228faea1f3e3f8b84b"},"rule":2,"target":"63fc39b2fe0a2553fb195650ae6915cb","type":"equivalent"},{"evidence":{"patch_ids":["185500373cc27d3d610be991561eb522"],"same_day":true,"statement_hash":"0503fb690855a4bf21f955b8b62af71583c422a4e69c4c228faea1f3e3f8b84b"},"rule":2,"target":"6a0f92cad4fbbfe88adb2be733310a9b","type":"equivalent"},{"evidence":{"patch_ids":["185500373cc27d3d610be991561eb522"],"same_day":true,"statement_hash":"0503fb690855a4bf21f955b8b62af71583c422a4e69c4c228faea1f3e3f8b84b"},"rule":2,"target":"dce6c62e738d4e4801ee4cb45757968f","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["3392cce5c"],"source_entry_id":"18.6/changes/021","source_hash":"94decd765e88345ccbe70faa6e3a61af2c519c0b307c93e6de8a846e22bcba68","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"0503fb690855a4bf21f955b8b62af71583c422a4e69c4c228faea1f3e3f8b84b","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"},"id":"18.6-d40f8de8e21a4c6f","matches":[{"id":"17.11-f6aaa44b60ea5479","source_entry_id":"17.11/changes/021","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/021","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","version":"18.6"},{"entry":{"category":"security","commit_aliases":["2d78c34f8","477a6bdb0","63cb15f40","87c4b8219","8c48cd615","cf4ae7c3b","d7fcfead3"],"commit_groups":[["2d78c34f8","477a6bdb0","63cb15f40","87c4b8219","8c48cd615","cf4ae7c3b","d7fcfead3"]],"commits":["87c4b8219"],"cves":["CVE-2026-14670"],"db_id":"45822fd5bc04f9bc7cd5310ebd922c61","html":"\u003cp\u003eHarden \u003cspan\u003ePL/Perl\u003c/span\u003e against \u003cspan\u003e“\u003cspan\u003etied\u003c/span\u003e”\u003c/span\u003e Perl arrays and hashes (Tom Lane) \u003ca href=\"https://postgr.es/c/87c4b8219\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA 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).\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Hcamael for reporting this problem. (CVE-2026-14670)\u003c/p\u003e","id":"18.6-6d183d795dd4fadd","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)","part":"changes","patch_ids":["5749c355b8bd5a5f2a0f8679d48902f9"],"relations":[{"evidence":{"patch_ids":["5749c355b8bd5a5f2a0f8679d48902f9"],"same_day":true,"statement_hash":"e681b36f925829491afb4aaf1536bea68f7b5021f6e0ea3fdb126ffd69367fa0"},"rule":2,"target":"0caaa5502645631a657b97dc78add8c0","type":"equivalent"},{"evidence":{"patch_ids":["5749c355b8bd5a5f2a0f8679d48902f9"],"same_day":true,"statement_hash":"e681b36f925829491afb4aaf1536bea68f7b5021f6e0ea3fdb126ffd69367fa0"},"rule":2,"target":"59a40e9cc2306d6e115d10b26c7b6d9e","type":"equivalent"},{"evidence":{"patch_ids":["5749c355b8bd5a5f2a0f8679d48902f9"],"same_day":true,"statement_hash":"e681b36f925829491afb4aaf1536bea68f7b5021f6e0ea3fdb126ffd69367fa0"},"rule":2,"target":"bd87bdc33bbf3c2a24631a385372b6ad","type":"equivalent"},{"evidence":{"patch_ids":["5749c355b8bd5a5f2a0f8679d48902f9"],"same_day":true,"statement_hash":"e681b36f925829491afb4aaf1536bea68f7b5021f6e0ea3fdb126ffd69367fa0"},"rule":2,"target":"f0c1fefb4fd60b97ad1a6420db84a85a","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["87c4b8219"],"source_entry_id":"18.6/changes/022","source_hash":"10b1106372761b89d406fd05bbb2541ae14a0d97192d90e5f7a2298a11c3e1c0","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"e681b36f925829491afb4aaf1536bea68f7b5021f6e0ea3fdb126ffd69367fa0","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"},"id":"18.6-6d183d795dd4fadd","matches":[{"id":"17.11-58243a045a5d2555","source_entry_id":"17.11/changes/022","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Harden PL/Perl against “tied” Perl arrays and hashes","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/022","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Harden PL/Perl against “tied” Perl arrays and hashes","version":"18.6"},{"entry":{"category":"security","commit_aliases":["028ee716a","1eb0d5380","776467301","8bbdc0540","a1c1727cb","aff9dac1c","b56cc7deb"],"commit_groups":[["028ee716a","1eb0d5380","776467301","8bbdc0540","a1c1727cb","aff9dac1c","b56cc7deb"]],"commits":["028ee716a"],"cves":["CVE-2026-14677","CVE-2026-6473"],"db_id":"238a2ce678961ff0ad08154da3915f04","html":"\u003cp\u003eFix integer overflows in memory-allocation calculations in \u003cspan\u003ePL/Perl\u003c/span\u003e and \u003cspan\u003ePL/Tcl\u003c/span\u003e (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/028ee716a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks the Tulya Project (Team Dhiutsa, Bitecope Technologies Private Ltd) for reporting this problem. (CVE-2026-14677)\u003c/p\u003e","id":"18.6-16cede7597f41368","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)","part":"changes","patch_ids":["551a41f04d69f180135194c24f4907fb"],"relations":[{"evidence":{"patch_ids":["551a41f04d69f180135194c24f4907fb"],"same_day":true,"statement_hash":"b56f55f83d652a2d7354185c8891454536092c27a727aecc0b21ea91949626f4"},"rule":2,"target":"4cc223998ff4d5b7cf50efd21e2284b1","type":"equivalent"},{"evidence":{"patch_ids":["551a41f04d69f180135194c24f4907fb"],"same_day":true,"statement_hash":"b56f55f83d652a2d7354185c8891454536092c27a727aecc0b21ea91949626f4"},"rule":2,"target":"a110c06ad7fd7a9c4f063b051daf6836","type":"equivalent"},{"evidence":{"patch_ids":["551a41f04d69f180135194c24f4907fb"],"same_day":true,"statement_hash":"b56f55f83d652a2d7354185c8891454536092c27a727aecc0b21ea91949626f4"},"rule":2,"target":"eaeb89e4752f46002fc91e3a83e9f683","type":"equivalent"},{"evidence":{"patch_ids":["551a41f04d69f180135194c24f4907fb"],"same_day":true,"statement_hash":"b56f55f83d652a2d7354185c8891454536092c27a727aecc0b21ea91949626f4"},"rule":2,"target":"f5ff50e89bc960e1e5bac3249477b995","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["028ee716a"],"source_entry_id":"18.6/changes/023","source_hash":"852c6f91848bf90946172edfb621354ea11883c45a93972557c73aaea1ec39d2","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"b56f55f83d652a2d7354185c8891454536092c27a727aecc0b21ea91949626f4","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"},"id":"18.6-16cede7597f41368","matches":[{"id":"17.11-7026dc1b76714418","source_entry_id":"17.11/changes/023","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix integer overflows in memory-allocation calculations in PL/Perl and PL/Tcl","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/023","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix integer overflows in memory-allocation calculations in PL/Perl and PL/Tcl","version":"18.6"},{"entry":{"category":"security","commit_aliases":["0a61fcde0","0fbf785b1","2cc147318","39d792040","557cc7186","e41c72aff","e43e74756"],"commit_groups":[["0a61fcde0","0fbf785b1","2cc147318","39d792040","557cc7186","e41c72aff","e43e74756"]],"commits":["0a61fcde0"],"cves":["CVE-2026-14673"],"db_id":"cb5c4637df879fb88877a760ee0058f9","html":"\u003cp\u003eEnsure that \u003ccode\u003econtrib/amcheck\u003c/code\u003e functions restrict \u003ccode\u003esearch_path\u003c/code\u003e before executing index expressions (Noah Misch) \u003ca href=\"https://postgr.es/c/0a61fcde0\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eBecause amcheck will run such index expressions as the owner of their tables, a caller could potentially hijack \u003ccode\u003esearch_path\u003c/code\u003e-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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Yuelin Wang and Jacob Brazeal for reporting this problem. (CVE-2026-14673)\u003c/p\u003e","id":"18.6-64ea1ee53902ffcc","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)","part":"changes","patch_ids":["5c909624ee89c6ad2350bdeebaf3e414"],"relations":[{"evidence":{"patch_ids":["5c909624ee89c6ad2350bdeebaf3e414"],"same_day":true,"statement_hash":"659077ecd2d4227788959afddf19d4e415449e3189a19ba0beb867937958bff6"},"rule":2,"target":"2c238928eeda3326738ac133c3580936","type":"equivalent"},{"evidence":{"patch_ids":["5c909624ee89c6ad2350bdeebaf3e414"],"same_day":true,"statement_hash":"659077ecd2d4227788959afddf19d4e415449e3189a19ba0beb867937958bff6"},"rule":2,"target":"465e8cabac386aa937b2b97c990e0a0f","type":"equivalent"},{"evidence":{"patch_ids":["5c909624ee89c6ad2350bdeebaf3e414"],"same_day":true,"statement_hash":"659077ecd2d4227788959afddf19d4e415449e3189a19ba0beb867937958bff6"},"rule":2,"target":"9ef4dc62946cbc0407d82f3a9b826f0e","type":"equivalent"},{"evidence":{"patch_ids":["5c909624ee89c6ad2350bdeebaf3e414"],"same_day":true,"statement_hash":"659077ecd2d4227788959afddf19d4e415449e3189a19ba0beb867937958bff6"},"rule":2,"target":"c016d6a0f320dafa02d0585b20842685","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["0a61fcde0"],"source_entry_id":"18.6/changes/024","source_hash":"7ba5e2ae5e38ee0207d070213a63610b01797ed2acef9003492c19568e51fdd1","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"659077ecd2d4227788959afddf19d4e415449e3189a19ba0beb867937958bff6","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"},"id":"18.6-64ea1ee53902ffcc","matches":[{"id":"17.11-ee34ba8ba8f4fa3d","source_entry_id":"17.11/changes/024","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Ensure that contrib/amcheck functions restrict search_path before executing index expressions","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/024","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Ensure that contrib/amcheck functions restrict search_path before executing index expressions","version":"18.6"},{"entry":{"category":"security","commit_aliases":["61481aa0e","62c31b490","74916136f","918683d12","9505175f2","c4d51b627","e88eb4e76"],"commit_groups":[["61481aa0e","62c31b490","74916136f","918683d12","9505175f2","c4d51b627","e88eb4e76"]],"commits":["e88eb4e76"],"cves":["CVE-2026-15742"],"db_id":"1e5eda106e8fd11472d74f91bffc2ff0","html":"\u003cp\u003eFix integer overflows in \u003ccode\u003econtrib/fuzzystrmatch\u003c/code\u003e's \u003ccode\u003elevenshtein()\u003c/code\u003e and \u003ccode\u003elevenshtein_less_equal()\u003c/code\u003e functions (Nathan Bossart) \u003ca href=\"https://postgr.es/c/e88eb4e76\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePassing large cost values to these functions could cause integer overflows, thereby producing nonsensical results, and even causing out-of-bounds writes in some cases.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Ben Morris (in collaboration with Claude and Anthropic Research) for reporting this problem. (CVE-2026-15742)\u003c/p\u003e","id":"18.6-9f4c551d8e885121","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)","part":"changes","patch_ids":["b6a4ec5efdc01505934fe024a8a4270f"],"relations":[{"evidence":{"patch_ids":["b6a4ec5efdc01505934fe024a8a4270f"],"same_day":true,"statement_hash":"f6379cf73e457381cf432fa9add17bfe91f2d96391011c3fe8081ecbbd13eff5"},"rule":2,"target":"24d49d08ad8dddbb2e9b85283621ee67","type":"equivalent"},{"evidence":{"patch_ids":["b6a4ec5efdc01505934fe024a8a4270f"],"same_day":true,"statement_hash":"f6379cf73e457381cf432fa9add17bfe91f2d96391011c3fe8081ecbbd13eff5"},"rule":2,"target":"6cca8c3102c334bca04243a3114f48fe","type":"equivalent"},{"evidence":{"patch_ids":["b6a4ec5efdc01505934fe024a8a4270f"],"same_day":true,"statement_hash":"f6379cf73e457381cf432fa9add17bfe91f2d96391011c3fe8081ecbbd13eff5"},"rule":2,"target":"bc23bdcfa3cae705ffa99474b3b97aae","type":"equivalent"},{"evidence":{"patch_ids":["b6a4ec5efdc01505934fe024a8a4270f"],"same_day":true,"statement_hash":"f6379cf73e457381cf432fa9add17bfe91f2d96391011c3fe8081ecbbd13eff5"},"rule":2,"target":"f41b59ba5bf8ae6184895fe8e7bb8dc1","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["e88eb4e76"],"source_entry_id":"18.6/changes/025","source_hash":"96c67bb1a9ef0c2604ab626734f8e8097c1f3ebea23560d09c5afbd92e7f9683","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"f6379cf73e457381cf432fa9add17bfe91f2d96391011c3fe8081ecbbd13eff5","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"},"id":"18.6-9f4c551d8e885121","matches":[{"id":"17.11-8ee281616fb9fd49","source_entry_id":"17.11/changes/025","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix integer overflows in contrib/fuzzystrmatch's levenshtein() and levenshtein_less_equal() functions","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/025","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix integer overflows in contrib/fuzzystrmatch's levenshtein() and levenshtein_less_equal() functions","version":"18.6"},{"entry":{"category":"security","commit_aliases":["1e2795dde","8a31ffc2d","bb02eba53"],"commit_groups":[["1e2795dde","8a31ffc2d","bb02eba53"]],"commits":["8a31ffc2d"],"cves":["CVE-2026-14676"],"db_id":"e84c1b71b1c15bae4e222a2f72d84864","html":"\u003cp\u003eFix buffer overrun in \u003ccode\u003econtrib/pg_stat_statements\u003c/code\u003e (Álvaro Herrera) \u003ca href=\"https://postgr.es/c/8a31ffc2d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eQuery normalization didn't accurately account for the amount of space the normalized string would require.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Sajeeb Lohani (with TrendAI Zero Day Initiative) and Yuelin Wang for reporting this problem. (CVE-2026-14676)\u003c/p\u003e","id":"18.6-c2bc95cc72b98750","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)","part":"changes","patch_ids":["ff92e3cbebc5005b0bef45f9f1d8d30a"],"relations":[{"evidence":{"patch_ids":["ff92e3cbebc5005b0bef45f9f1d8d30a"],"same_day":true,"statement_hash":"9ccd331655eef445554d4bf3ba5a781e3ca80ec62b9fce48b4cf6f7177789b22"},"rule":2,"target":"29895bb80ed2951a21b387b1a32fd0bf","type":"equivalent"},{"evidence":{"patch_ids":["ff92e3cbebc5005b0bef45f9f1d8d30a"],"same_day":true,"statement_hash":"9ccd331655eef445554d4bf3ba5a781e3ca80ec62b9fce48b4cf6f7177789b22"},"rule":2,"target":"aaa4509a01eb087a7c8dae3d3477599b","type":"equivalent"},{"evidence":{"patch_ids":["ff92e3cbebc5005b0bef45f9f1d8d30a"],"same_day":true,"statement_hash":"9ccd331655eef445554d4bf3ba5a781e3ca80ec62b9fce48b4cf6f7177789b22"},"rule":2,"target":"d7011cf7f02dec0d6f5320d50f1060d7","type":"equivalent"},{"evidence":{"patch_ids":["ff92e3cbebc5005b0bef45f9f1d8d30a"],"same_day":true,"statement_hash":"9ccd331655eef445554d4bf3ba5a781e3ca80ec62b9fce48b4cf6f7177789b22"},"rule":2,"target":"d8f3c95effa66c9d7648ed329303a70e","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["8a31ffc2d"],"source_entry_id":"18.6/changes/026","source_hash":"d2635f488ff4a3302586cb71fa7ddad74aeebf54da30c6109e0319f3e53df0e9","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"9ccd331655eef445554d4bf3ba5a781e3ca80ec62b9fce48b4cf6f7177789b22","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"},"id":"18.6-c2bc95cc72b98750","matches":[{"id":"17.11-881f882c67a9948d","source_entry_id":"17.11/changes/026","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix buffer overrun in contrib/pg_stat_statements","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/026","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix buffer overrun in contrib/pg_stat_statements","version":"18.6"},{"entry":{"category":"security","commit_aliases":["1af08af69","24c88cd39","66c2dbb20","849019a50","a74aa0854","aa7b5815e","c7c82a88c"],"commit_groups":[["1af08af69","24c88cd39","66c2dbb20","849019a50","a74aa0854","aa7b5815e","c7c82a88c"]],"commits":["849019a50"],"cves":["CVE-2026-14678"],"db_id":"0bc10887e786dd035f4571e42ea848b8","html":"\u003cp\u003eFix datatype error in \u003ccode\u003econtrib/pg_trgm\u003c/code\u003e's GiST picksplit function (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/849019a50\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Mehmet D. Ince for reporting this problem. (CVE-2026-14678)\u003c/p\u003e","id":"18.6-b960de4f8267096f","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)","part":"changes","patch_ids":["e6003b6617841df26303992ba1215f03"],"relations":[{"evidence":{"patch_ids":["e6003b6617841df26303992ba1215f03"],"same_day":true,"statement_hash":"b75b9d4c297e71b80fedfe6eeb16417da2cd09f4baa7f5d2b7d3f4d2495f3474"},"rule":2,"target":"007e7b20002c9154a7b78500dad11fde","type":"equivalent"},{"evidence":{"patch_ids":["e6003b6617841df26303992ba1215f03"],"same_day":true,"statement_hash":"b75b9d4c297e71b80fedfe6eeb16417da2cd09f4baa7f5d2b7d3f4d2495f3474"},"rule":2,"target":"1dcffcddaa3ea6a57ebf8bf560e8c531","type":"equivalent"},{"evidence":{"patch_ids":["e6003b6617841df26303992ba1215f03"],"same_day":true,"statement_hash":"b75b9d4c297e71b80fedfe6eeb16417da2cd09f4baa7f5d2b7d3f4d2495f3474"},"rule":2,"target":"b9b08968a5deb7a55558cd0e3c3ecb91","type":"equivalent"},{"evidence":{"patch_ids":["e6003b6617841df26303992ba1215f03"],"same_day":true,"statement_hash":"b75b9d4c297e71b80fedfe6eeb16417da2cd09f4baa7f5d2b7d3f4d2495f3474"},"rule":2,"target":"c1b223f3527ab1382981f7ea6931f7ec","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["849019a50"],"source_entry_id":"18.6/changes/027","source_hash":"80d67ce760ed68d00013270c286690f7d0aa6dd3ecd75d390bacd9e741c74117","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"b75b9d4c297e71b80fedfe6eeb16417da2cd09f4baa7f5d2b7d3f4d2495f3474","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"},"id":"18.6-b960de4f8267096f","matches":[{"id":"17.11-caca197ce0ba4b3f","source_entry_id":"17.11/changes/027","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix datatype error in contrib/pg_trgm's GiST picksplit function","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/027","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix datatype error in contrib/pg_trgm's GiST picksplit function","version":"18.6"},{"entry":{"category":"security","commit_aliases":["1fbe2066d","5b72d0279","66a5146dc","79a506228","a572dd213","b7b513d9a"],"commit_groups":[["1fbe2066d","5b72d0279","66a5146dc","79a506228","a572dd213","b7b513d9a"]],"commits":["79a506228"],"cves":["CVE-2026-14671"],"db_id":"139a1ada6baf2bae757b6a1a97ee7f41","html":"\u003cp\u003eRemove the plan cache in \u003ccode\u003econtrib/refint\u003c/code\u003e (Ayush Tiwari) \u003ca href=\"https://postgr.es/c/79a506228\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis caching behavior has several serious bugs, notably that \u003ccode\u003echeck_foreign_key()\u003c/code\u003e 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Hcamael for reporting this problem. (CVE-2026-14671)\u003c/p\u003e","id":"18.6-2fe39251a9e1874e","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)","part":"changes","patch_ids":["1a32666836cb434aea5b3cbd8282c9f7"],"relations":[{"evidence":{"patch_ids":["1a32666836cb434aea5b3cbd8282c9f7"],"same_day":true,"statement_hash":"b8e6fe77ce440b33c793882e33b84a13458e57df19432239a74f731dbb6496f9"},"rule":2,"target":"0edf0fe6be4ddcafd5c7d27addaa918f","type":"equivalent"},{"evidence":{"patch_ids":["1a32666836cb434aea5b3cbd8282c9f7"],"same_day":true,"statement_hash":"b8e6fe77ce440b33c793882e33b84a13458e57df19432239a74f731dbb6496f9"},"rule":2,"target":"7dbe14e2bbf06d93dd90088eae989b60","type":"equivalent"},{"evidence":{"patch_ids":["1a32666836cb434aea5b3cbd8282c9f7"],"same_day":true,"statement_hash":"b8e6fe77ce440b33c793882e33b84a13458e57df19432239a74f731dbb6496f9"},"rule":2,"target":"aca3bdc694388071f82dcc5eb7deb70d","type":"equivalent"},{"evidence":{"patch_ids":["1a32666836cb434aea5b3cbd8282c9f7"],"same_day":true,"statement_hash":"b8e6fe77ce440b33c793882e33b84a13458e57df19432239a74f731dbb6496f9"},"rule":2,"target":"ddbe7d30f92efca35dca583745e7a91a","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["79a506228"],"source_entry_id":"18.6/changes/028","source_hash":"6e1519ab2f6327b36adc78242481530b3c30efd3dfa202b0fc360b4be1b6fa31","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"b8e6fe77ce440b33c793882e33b84a13458e57df19432239a74f731dbb6496f9","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"},"id":"18.6-2fe39251a9e1874e","matches":[{"id":"17.11-9677b8014f265a17","source_entry_id":"17.11/changes/028","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Remove the plan cache in contrib/refint","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/028","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Remove the plan cache in contrib/refint","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["3704870b2","4ea497a92","7213cbfa0","7d74b2644","894da35b3","cec48686a","f57df2068"],"commit_groups":[["3704870b2","4ea497a92","7213cbfa0","7d74b2644","894da35b3","cec48686a","f57df2068"]],"commits":["4ea497a92"],"cves":[],"db_id":"14a676aedb1f7035485b3957b6cdb1d3","html":"\u003cp\u003eFix mis-handling of asynchronous reads when rescanning an asynchronous Append plan node (Alexander Korotkov, Gleb Kashkin, Etsuro Fujita) \u003ca href=\"https://postgr.es/c/4ea497a92\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWhen 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 \u003ccode\u003epostgres_fdw\u003c/code\u003e 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.\u003c/p\u003e","id":"18.6-ac95828b13f18d05","identity_text":"Fix mis-handling of asynchronous reads when rescanning an asynchronous Append plan node (Alexander Korotkov, Gleb Kashkin, Etsuro Fujita) When 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.","part":"changes","patch_ids":["9c0723170572c08606a9295f60002d24"],"relations":[{"evidence":{"patch_ids":["9c0723170572c08606a9295f60002d24"],"same_day":true,"statement_hash":"63920dc25b666a17f0abbbd9dbd5d73e39729a95414c23162e2eef52f54e0156"},"rule":2,"target":"308bf9c42c99219ddb3217fdf72c3cc2","type":"equivalent"},{"evidence":{"patch_ids":["9c0723170572c08606a9295f60002d24"],"same_day":true,"statement_hash":"63920dc25b666a17f0abbbd9dbd5d73e39729a95414c23162e2eef52f54e0156"},"rule":2,"target":"356859c6db4851d1f22713fc26ca208a","type":"equivalent"},{"evidence":{"patch_ids":["9c0723170572c08606a9295f60002d24"],"same_day":true,"statement_hash":"63920dc25b666a17f0abbbd9dbd5d73e39729a95414c23162e2eef52f54e0156"},"rule":2,"target":"4977c45c15376d01b25828041933e6ed","type":"equivalent"},{"evidence":{"patch_ids":["9c0723170572c08606a9295f60002d24"],"same_day":true,"statement_hash":"63920dc25b666a17f0abbbd9dbd5d73e39729a95414c23162e2eef52f54e0156"},"rule":2,"target":"d3c85d15eab520a6fbdb79e9d5b8db40","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["4ea497a92"],"source_entry_id":"18.6/changes/030","source_hash":"243024c01284f3cf3c5c05a562be2bd035a950664d80808a52db8ec26f9d7c76","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"63920dc25b666a17f0abbbd9dbd5d73e39729a95414c23162e2eef52f54e0156","text":"Fix mis-handling of asynchronous reads when rescanning an asynchronous Append plan node (Alexander Korotkov, Gleb Kashkin, Etsuro Fujita) § When 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.","title":"Fix mis-handling of asynchronous reads when rescanning an asynchronous Append plan node"},"id":"18.6-ac95828b13f18d05","matches":[{"id":"17.11-3e22bb5ab29aa62e","source_entry_id":"17.11/changes/029","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix mis-handling of asynchronous reads when rescanning an asynchronous Append plan node","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/030","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix mis-handling of asynchronous reads when rescanning an asynchronous Append plan node","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["02e69be47","31f2acde5","5190732c9","6098f35f4","709dfd27f","9a0cd8e73","f9282a650"],"commit_groups":[["02e69be47","31f2acde5","5190732c9","6098f35f4","709dfd27f","9a0cd8e73","f9282a650"]],"commits":["02e69be47"],"cves":[],"db_id":"128f5b0ef464d5fb3f9f8de9b62b5b0c","html":"\u003cp\u003eFix error in partition pruning for RANGE-partitioned tables (David Rowley) \u003ca href=\"https://postgr.es/c/02e69be47\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIn some cases the DEFAULT partition would be skipped when it should not be, which could lead to rows missing from query results.\u003c/p\u003e","id":"18.6-1c1bf5522234d430","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.","part":"changes","patch_ids":["07f80c898c23577b927785baf5699ba6"],"relations":[{"evidence":{"patch_ids":["07f80c898c23577b927785baf5699ba6"],"same_day":true,"statement_hash":"e3e0e32dc70a802e15316cd723301dfb9165a361cfaaa3eaebb6138320570c23"},"rule":2,"target":"199c05dd5ca242a1207113d841920d91","type":"equivalent"},{"evidence":{"patch_ids":["07f80c898c23577b927785baf5699ba6"],"same_day":true,"statement_hash":"e3e0e32dc70a802e15316cd723301dfb9165a361cfaaa3eaebb6138320570c23"},"rule":2,"target":"8e616a25980e478e4ba1d40fd43361c9","type":"equivalent"},{"evidence":{"patch_ids":["07f80c898c23577b927785baf5699ba6"],"same_day":true,"statement_hash":"e3e0e32dc70a802e15316cd723301dfb9165a361cfaaa3eaebb6138320570c23"},"rule":2,"target":"b1408f66d7e290909c80f8c2b9d6a6e6","type":"equivalent"},{"evidence":{"patch_ids":["07f80c898c23577b927785baf5699ba6"],"same_day":true,"statement_hash":"e3e0e32dc70a802e15316cd723301dfb9165a361cfaaa3eaebb6138320570c23"},"rule":2,"target":"c03487e8eed72def14469f629495faba","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["02e69be47"],"source_entry_id":"18.6/changes/031","source_hash":"3e9800e0665c2e72616be8e9d68eb5b862ff71271140f5fba3d9feac638d1de7","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"e3e0e32dc70a802e15316cd723301dfb9165a361cfaaa3eaebb6138320570c23","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"},"id":"18.6-1c1bf5522234d430","matches":[{"id":"17.11-ae4f5cd546a7dc28","source_entry_id":"17.11/changes/030","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix error in partition pruning for RANGE-partitioned tables","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/031","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix error in partition pruning for RANGE-partitioned tables","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["13b627a3e","239eabda4","26d6b7dc9","277122036","53470ffba","6fcee189b","9740c68ff"],"commit_groups":[["13b627a3e","239eabda4","26d6b7dc9","277122036","53470ffba","6fcee189b","9740c68ff"]],"commits":["277122036"],"cves":[],"db_id":"ad3ee3744d12ed87e41b743df908a973","html":"\u003cp\u003eFix planner's nullability and strictness checks for \u003ccode\u003e\u003cem\u003e\u003ccode\u003evalue\u003c/code\u003e\u003c/em\u003e IN (\u003cem\u003e\u003ccode\u003earray\u003c/code\u003e\u003c/em\u003e)\u003c/code\u003e expressions (Ayush Tiwari) \u003ca href=\"https://postgr.es/c/277122036\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese 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.\u003c/p\u003e","id":"18.6-7f07d942a2dc7fb3","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.","part":"changes","patch_ids":["df435503db83a1e14391340c77582135"],"relations":[{"evidence":{"patch_ids":["df435503db83a1e14391340c77582135"],"same_day":true,"statement_hash":"2d92bc3cfa84bb56afc5d1f1b3a42de958d5476b1ad5c8eeac46ecc8e878ca25"},"rule":2,"target":"295b1a7da9077453b2e0fd1899e5c7e4","type":"equivalent"},{"evidence":{"patch_ids":["df435503db83a1e14391340c77582135"],"same_day":true,"statement_hash":"2d92bc3cfa84bb56afc5d1f1b3a42de958d5476b1ad5c8eeac46ecc8e878ca25"},"rule":2,"target":"53fcc801e2a78a55196f6122abbd7a01","type":"equivalent"},{"evidence":{"patch_ids":["df435503db83a1e14391340c77582135"],"same_day":true,"statement_hash":"2d92bc3cfa84bb56afc5d1f1b3a42de958d5476b1ad5c8eeac46ecc8e878ca25"},"rule":2,"target":"8c22785dc1e64a0a8f07acd08ee8695d","type":"equivalent"},{"evidence":{"patch_ids":["df435503db83a1e14391340c77582135"],"same_day":true,"statement_hash":"2d92bc3cfa84bb56afc5d1f1b3a42de958d5476b1ad5c8eeac46ecc8e878ca25"},"rule":2,"target":"c4e4aedd211ab9a3cebe71bab9209dff","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["277122036"],"source_entry_id":"18.6/changes/036","source_hash":"59acbe1e0d72123c284eb75137c993aa778cc3317be6c39737ab227966226fcc","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"2d92bc3cfa84bb56afc5d1f1b3a42de958d5476b1ad5c8eeac46ecc8e878ca25","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"},"id":"18.6-7f07d942a2dc7fb3","matches":[{"id":"17.11-0179d9549f7c629e","source_entry_id":"17.11/changes/031","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix planner's nullability and strictness checks for value IN (array) expressions","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/036","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix planner's nullability and strictness checks for value IN (array) expressions","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["0da71d90d","1df9e8d96","21f5e659e","3e1fe25e6","72457f1df","8bc479627","9e40d07e1","b308eb366","cdcec567d","d610d8e8b"],"commit_groups":[["0da71d90d","72457f1df","9e40d07e1","b308eb366","d610d8e8b"],["1df9e8d96","21f5e659e","3e1fe25e6","8bc479627","cdcec567d"]],"commits":["21f5e659e","9e40d07e1"],"cves":[],"db_id":"4f181419572dec31c7f8a0612a21f555","html":"\u003cp\u003eFix incorrect join removal logic (Matheus Alcantara, Richard Guo) \u003ca href=\"https://postgr.es/c/21f5e659e\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/9e40d07e1\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIn 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.\u003c/p\u003e","id":"18.6-8445b59319518d4d","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.","part":"changes","patch_ids":["1e12745a4a72c22047b3d9e8c13b8fb6","dabc0be4437bfea2c9473e4b0cbd7ede"],"relations":[{"evidence":{"patch_ids":["1e12745a4a72c22047b3d9e8c13b8fb6","dabc0be4437bfea2c9473e4b0cbd7ede"],"same_day":true,"statement_hash":"66372d30c157ceb2f0f88f6e5275d315accebe006eebab6de4089f55d7597b5d"},"rule":2,"target":"86a9304ee897d487f2f08fdf6cd5a298","type":"equivalent"},{"evidence":{"patch_ids":["1e12745a4a72c22047b3d9e8c13b8fb6","dabc0be4437bfea2c9473e4b0cbd7ede"],"same_day":true,"statement_hash":"66372d30c157ceb2f0f88f6e5275d315accebe006eebab6de4089f55d7597b5d"},"rule":2,"target":"d46715d5dbb4902eaecdcfe45967fd74","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["21f5e659e","9e40d07e1"],"source_entry_id":"18.6/changes/037","source_hash":"2282060f2cd290842672f0145f4ff5559cbf9d177d487d890edfca94f95af51d","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"66372d30c157ceb2f0f88f6e5275d315accebe006eebab6de4089f55d7597b5d","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"},"id":"18.6-8445b59319518d4d","matches":[{"id":"17.11-8ac984b046b9e22d","source_entry_id":"17.11/changes/032","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix incorrect join removal logic","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/037","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix incorrect join removal logic","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["06e94eccf","11aed8d19","19152e3c2","64778fac7","caebac5f1","cf2bfe073"],"commit_groups":[["06e94eccf","11aed8d19","19152e3c2","64778fac7","caebac5f1","cf2bfe073"]],"commits":["11aed8d19"],"cves":[],"db_id":"b401153415d6c7495b085ccde803a0bc","html":"\u003cp\u003eAdd missed checks for hashability of equality comparisons on container datatypes (arrays, composites, ranges) (Andrei Lepikhov, Tom Lane) \u003ca href=\"https://postgr.es/c/11aed8d19\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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 \u003cspan\u003e“\u003cspan\u003ecould not identify a hash function\u003c/span\u003e”\u003c/span\u003e failures at execution.\u003c/p\u003e","id":"18.6-7bb42265442bdc48","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.","part":"changes","patch_ids":["f162e2041e91d006f552b603fcf44b0b"],"relations":[{"evidence":{"patch_ids":["f162e2041e91d006f552b603fcf44b0b"],"same_day":true,"statement_hash":"b7a7a5b48bc59370b10583c89b44b2318a828907126bcf1f7993377c9815a9e9"},"rule":2,"target":"4de85f9df67410e6ee11d61a4934c2dd","type":"equivalent"},{"evidence":{"patch_ids":["f162e2041e91d006f552b603fcf44b0b"],"same_day":true,"statement_hash":"b7a7a5b48bc59370b10583c89b44b2318a828907126bcf1f7993377c9815a9e9"},"rule":2,"target":"8f291081d50c65368eaa75ffccbfb916","type":"equivalent"},{"evidence":{"patch_ids":["f162e2041e91d006f552b603fcf44b0b"],"same_day":true,"statement_hash":"b7a7a5b48bc59370b10583c89b44b2318a828907126bcf1f7993377c9815a9e9"},"rule":2,"target":"f09d5370fd92cd8394d32a7c6a39f808","type":"equivalent"},{"evidence":{"patch_ids":["f162e2041e91d006f552b603fcf44b0b"],"same_day":true,"statement_hash":"b7a7a5b48bc59370b10583c89b44b2318a828907126bcf1f7993377c9815a9e9"},"rule":2,"target":"f1ae81ec65ad7eceb75ed5e3e0b2c543","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["11aed8d19"],"source_entry_id":"18.6/changes/039","source_hash":"6ad8dd8c985b21b21108124389165bf7327db02422d4aae9a1e764bd8d71d016","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"b7a7a5b48bc59370b10583c89b44b2318a828907126bcf1f7993377c9815a9e9","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)"},"id":"18.6-7bb42265442bdc48","matches":[{"id":"17.11-f6f35a5c24f27bf2","source_entry_id":"17.11/changes/033","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)","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/039","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)","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["842e34efa","a85732162","be63b285e","cf184ec77","d007800f0","fcd58c6d9"],"commit_groups":[["842e34efa","a85732162","be63b285e","cf184ec77","d007800f0","fcd58c6d9"]],"commits":["cf184ec77"],"cves":[],"db_id":"ddf83605232b0de3c591e0caa7a88605","html":"\u003cp\u003eFix mis-optimization of \u003ccode\u003eCOUNT\u003c/code\u003e window functions that have an \u003ccode\u003eEXCLUDE\u003c/code\u003e clause or lack \u003ccode\u003eORDER BY\u003c/code\u003e (Chengpeng Yan, David Rowley) \u003ca href=\"https://postgr.es/c/cf184ec77\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese window functions were treated as monotonic when they should not be, allowing wrong answers to be computed.\u003c/p\u003e","id":"18.6-88417491cf3856e5","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.","part":"changes","patch_ids":["28e51714721f6a824be654de7f6357bc"],"relations":[{"evidence":{"patch_ids":["28e51714721f6a824be654de7f6357bc"],"same_day":true,"statement_hash":"6285e56236281de47720490e02f655ef1c492df7841c118242cef65b8c828aa3"},"rule":2,"target":"28c2612bebf05e287b83343abb5a649a","type":"equivalent"},{"evidence":{"patch_ids":["28e51714721f6a824be654de7f6357bc"],"same_day":true,"statement_hash":"6285e56236281de47720490e02f655ef1c492df7841c118242cef65b8c828aa3"},"rule":2,"target":"40a7c9c1b0ba3bb62e973869e4377d48","type":"equivalent"},{"evidence":{"patch_ids":["28e51714721f6a824be654de7f6357bc"],"same_day":true,"statement_hash":"6285e56236281de47720490e02f655ef1c492df7841c118242cef65b8c828aa3"},"rule":2,"target":"f36b3896971ebb704e9049fa9035f582","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["cf184ec77"],"source_entry_id":"18.6/changes/041","source_hash":"0ea7c716ea749b5741a7bf87e0ccbd8f8674c2d3136b6c921885dd8bb2d28a2c","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"6285e56236281de47720490e02f655ef1c492df7841c118242cef65b8c828aa3","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"},"id":"18.6-88417491cf3856e5","matches":[{"id":"17.11-c7bededba93f5fa4","source_entry_id":"17.11/changes/034","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/041","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","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["18006c1bd","34785a0d5","785289de0","c374f2807","cad17745e","ce6e434ce","fef160d8b"],"commit_groups":[["18006c1bd","34785a0d5","785289de0","c374f2807","cad17745e","ce6e434ce","fef160d8b"]],"commits":["c374f2807"],"cves":[],"db_id":"481ba0dce2331491936d08937b509331","html":"\u003cp\u003eFix \u003ccode\u003eALTER COLUMN ... DROP EXPRESSION\u003c/code\u003e to work when there are multiple levels of partitions (Alberto Piai) \u003ca href=\"https://postgr.es/c/c374f2807\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-14a8792e9a6b6b0c","identity_text":"Fix ALTER COLUMN ... DROP EXPRESSION to work when there are multiple levels of partitions (Alberto Piai)","part":"changes","patch_ids":["eb3e04d63883499b6a42a7149830218b"],"relations":[{"evidence":{"patch_ids":["eb3e04d63883499b6a42a7149830218b"],"same_day":true,"statement_hash":"a9426a4c530fee747811532ad11a1324dac241e961f27f70d5a140fa9110019f"},"rule":2,"target":"3e61c5e7800280c2d75348edca95b482","type":"equivalent"},{"evidence":{"patch_ids":["eb3e04d63883499b6a42a7149830218b"],"same_day":true,"statement_hash":"a9426a4c530fee747811532ad11a1324dac241e961f27f70d5a140fa9110019f"},"rule":2,"target":"644f498dfc902b8478cebc735019df44","type":"equivalent"},{"evidence":{"patch_ids":["eb3e04d63883499b6a42a7149830218b"],"same_day":true,"statement_hash":"a9426a4c530fee747811532ad11a1324dac241e961f27f70d5a140fa9110019f"},"rule":2,"target":"bbd2e283343d80bbe36c5d10b0b7b8d9","type":"equivalent"},{"evidence":{"patch_ids":["eb3e04d63883499b6a42a7149830218b"],"same_day":true,"statement_hash":"a9426a4c530fee747811532ad11a1324dac241e961f27f70d5a140fa9110019f"},"rule":2,"target":"ff8123d6270256da139869a45dd3811f","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c374f2807"],"source_entry_id":"18.6/changes/043","source_hash":"0e0bf3175e90710756985d9f2c44e2fc5d7016f27f682df33d46541780590797","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"a9426a4c530fee747811532ad11a1324dac241e961f27f70d5a140fa9110019f","text":"Fix ALTER COLUMN ... DROP EXPRESSION to work when there are multiple levels of partitions (Alberto Piai) §","title":"Fix ALTER COLUMN ... DROP EXPRESSION to work when there are multiple levels of partitions"},"id":"18.6-14a8792e9a6b6b0c","matches":[{"id":"17.11-aa9ce164073e6fc7","source_entry_id":"17.11/changes/035","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/043","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","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["19e3aa704","1d6c654c8","2b2c2492c","d049a31a4"],"commit_groups":[["19e3aa704","1d6c654c8","2b2c2492c","d049a31a4"]],"commits":["19e3aa704"],"cves":[],"db_id":"5c4182efd803f6d6d6537714c7bd42b7","html":"\u003cp\u003eFix attaching partitions of indexes that are exclusion constraints (Japin Li) \u003ca href=\"https://postgr.es/c/19e3aa704\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eNotably, this oversight broke dump/restore of partitioned exclusion constraints.\u003c/p\u003e","id":"18.6-e8b58d1d4a2ada71","identity_text":"Fix attaching partitions of indexes that are exclusion constraints (Japin Li) Notably, this oversight broke dump/restore of partitioned exclusion constraints.","part":"changes","patch_ids":["32801b307162bd0744d51d9ca6c96a29"],"relations":[{"evidence":{"patch_ids":["32801b307162bd0744d51d9ca6c96a29"],"same_day":true,"statement_hash":"a43e644386fbc7d5b0bbee11dd34413bc9867bd3e1172c28e5ef212327072aab"},"rule":2,"target":"93afcbc160733050810dc157756fa912","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["19e3aa704"],"source_entry_id":"18.6/changes/044","source_hash":"e26997d652381c7f0ed9681bc22f8e68776fa5da18d5bc132c86c3b7e545f464","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"a43e644386fbc7d5b0bbee11dd34413bc9867bd3e1172c28e5ef212327072aab","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"},"id":"18.6-e8b58d1d4a2ada71","matches":[{"id":"17.11-82cead6257dcd50a","source_entry_id":"17.11/changes/036","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix attaching partitions of indexes that are exclusion constraints","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/044","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix attaching partitions of indexes that are exclusion constraints","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["1b17a6e3c","80c7f5467","a69503fb1","a7f7958ab","a8c2547ea","e99fb3262","eada45dd8"],"commit_groups":[["1b17a6e3c","80c7f5467","a69503fb1","a7f7958ab","a8c2547ea","e99fb3262","eada45dd8"]],"commits":["a7f7958ab"],"cves":[],"db_id":"7fcd70e80ad8fcb50e2d2e784c2f096a","html":"\u003cp\u003eDisallow renaming a rule to \u003ccode\u003e_RETURN\u003c/code\u003e (Tom Lane) \u003ca href=\"https://postgr.es/c/a7f7958ab\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThat name is reserved for a view's \u003ccode\u003eON SELECT\u003c/code\u003e rule, but \u003ccode\u003eALTER RULE\u003c/code\u003e allowed renaming other rules to \u003ccode\u003e_RETURN\u003c/code\u003e, causing trouble later.\u003c/p\u003e","id":"18.6-7007f0ab50735ceb","identity_text":"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.","part":"changes","patch_ids":["f0349091818c90f9895303f6c726eb25"],"relations":[{"evidence":{"patch_ids":["f0349091818c90f9895303f6c726eb25"],"same_day":true,"statement_hash":"b2ef150a28cd11b0518b82c8e6876301cd0c2355969ae6477b6742e468bce526"},"rule":2,"target":"3569cc7b8d590ae9ed38d474e4657d07","type":"equivalent"},{"evidence":{"patch_ids":["f0349091818c90f9895303f6c726eb25"],"same_day":true,"statement_hash":"b2ef150a28cd11b0518b82c8e6876301cd0c2355969ae6477b6742e468bce526"},"rule":2,"target":"372d29ed3f3b1d47e4559294d1b39ef0","type":"equivalent"},{"evidence":{"patch_ids":["f0349091818c90f9895303f6c726eb25"],"same_day":true,"statement_hash":"b2ef150a28cd11b0518b82c8e6876301cd0c2355969ae6477b6742e468bce526"},"rule":2,"target":"5937327b4c46721ff43bb1e6390ab869","type":"equivalent"},{"evidence":{"patch_ids":["f0349091818c90f9895303f6c726eb25"],"same_day":true,"statement_hash":"b2ef150a28cd11b0518b82c8e6876301cd0c2355969ae6477b6742e468bce526"},"rule":2,"target":"9cce45b7be8c80c09abfde1a981ce88a","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["a7f7958ab"],"source_entry_id":"18.6/changes/046","source_hash":"42d0bcd76dc5bce27d1905de279a3fe08f17de460d01e4775e689da8679a7bc5","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"b2ef150a28cd11b0518b82c8e6876301cd0c2355969ae6477b6742e468bce526","text":"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.","title":"Disallow renaming a rule to _RETURN"},"id":"18.6-7007f0ab50735ceb","matches":[{"id":"17.11-d462466d836ceca5","source_entry_id":"17.11/changes/037","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Disallow renaming a rule to _RETURN","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/046","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Disallow renaming a rule to _RETURN","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["25e54cec7","9eccdae22","a0daa0b41","b48caa7df","e61d44fde"],"commit_groups":[["25e54cec7","9eccdae22","a0daa0b41","b48caa7df","e61d44fde"]],"commits":["a0daa0b41"],"cves":[],"db_id":"5ac990e6d8ae4f5c9facf9044c23d6c9","html":"\u003cp\u003eFix missing lock release for role membership grants in \u003ccode\u003eDROP OWNED BY\u003c/code\u003e (Jeff Davis) \u003ca href=\"https://postgr.es/c/a0daa0b41\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis oversight resulted in a warning message, followed by retaining a lock on the membership grant until the end of the transaction.\u003c/p\u003e","id":"18.6-b6f7587292fb4dc6","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.","part":"changes","patch_ids":["366a54c27360ab3839f71c858dc847c7"],"relations":[{"evidence":{"patch_ids":["366a54c27360ab3839f71c858dc847c7"],"same_day":true,"statement_hash":"c3d8dda4db627322e27465f2a355faabf29a98b7c4ddfd870cf46d4fa9b704f9"},"rule":2,"target":"0563a596791449f44372e96193722ea2","type":"equivalent"},{"evidence":{"patch_ids":["366a54c27360ab3839f71c858dc847c7"],"same_day":true,"statement_hash":"c3d8dda4db627322e27465f2a355faabf29a98b7c4ddfd870cf46d4fa9b704f9"},"rule":2,"target":"f38a9d64af080b972d55091afa2b7167","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["a0daa0b41"],"source_entry_id":"18.6/changes/047","source_hash":"2aac72ff4aa5ee2955a6053adaa7adbb8f63722691ed0531eec8c26985c5efa3","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"c3d8dda4db627322e27465f2a355faabf29a98b7c4ddfd870cf46d4fa9b704f9","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"},"id":"18.6-b6f7587292fb4dc6","matches":[{"id":"17.11-3e140cc33315fc88","source_entry_id":"17.11/changes/038","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix missing lock release for role membership grants in DROP OWNED BY","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/047","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix missing lock release for role membership grants in DROP OWNED BY","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["45364e496","485527190","96ab9a990","dcda1f07d","eaa561fb6"],"commit_groups":[["45364e496","485527190","96ab9a990","dcda1f07d","eaa561fb6"]],"commits":["45364e496"],"cves":[],"db_id":"9bd2c80a3ef9ebab0fa8c15b085cb9d4","html":"\u003cp\u003eFix failure of \u003ccode\u003eEXPLAIN\u003c/code\u003e when deparsing \u003ccode\u003eSQL/JSON\u003c/code\u003e aggregates (Richard Guo) \u003ca href=\"https://postgr.es/c/45364e496\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSome plan structures resulted in \u003cspan\u003e“\u003cspan\u003einvalid JsonConstructorExpr underlying node type\u003c/span\u003e”\u003c/span\u003e errors.\u003c/p\u003e","id":"18.6-604b807a12c59a87","identity_text":"Fix failure of EXPLAIN when deparsing SQL/JSON aggregates (Richard Guo) Some plan structures resulted in invalid JsonConstructorExpr underlying node type errors.","part":"changes","patch_ids":["60000a6e62ddc3ae0c3b7ef80802ee71"],"relations":[{"evidence":{"patch_ids":["60000a6e62ddc3ae0c3b7ef80802ee71"],"same_day":true,"statement_hash":"6a7283c8b92d0663e05728d26d406516f01a522c2433821f328a072f69e8d6c2"},"rule":2,"target":"76da1bf58091a36c27ddeecb07c72440","type":"equivalent"},{"evidence":{"patch_ids":["60000a6e62ddc3ae0c3b7ef80802ee71"],"same_day":true,"statement_hash":"6a7283c8b92d0663e05728d26d406516f01a522c2433821f328a072f69e8d6c2"},"rule":2,"target":"9796917e37d7742de7735ae20dbc9e8c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["45364e496"],"source_entry_id":"18.6/changes/048","source_hash":"d3a0089d91c98ae5bf10b57ed60f7d442c6dd373660c026c360f1fa30e2703ea","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"6a7283c8b92d0663e05728d26d406516f01a522c2433821f328a072f69e8d6c2","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"},"id":"18.6-604b807a12c59a87","matches":[{"id":"17.11-df483e133aa49926","source_entry_id":"17.11/changes/039","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix failure of EXPLAIN when deparsing SQL/JSON aggregates","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/048","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix failure of EXPLAIN when deparsing SQL/JSON aggregates","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["28269fed6","55adef7ab","5b3712e31","74276e685","9f6fb1191","ac222bea5","e4527519b"],"commit_groups":[["28269fed6","55adef7ab","5b3712e31","74276e685","9f6fb1191","ac222bea5","e4527519b"]],"commits":["e4527519b"],"cves":[],"db_id":"69bafedd5508b393bd3564acfc03f161","html":"\u003cp\u003eFix use of \u003ccode\u003eREINDEX CONCURRENTLY\u003c/code\u003e with a deferred uniqueness constraint (Nitin Motiani) \u003ca href=\"https://postgr.es/c/e4527519b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe transient index copy created during \u003ccode\u003eREINDEX CONCURRENTLY\u003c/code\u003e was incorrectly marked as enforcing immediate uniqueness, causing spurious reports of constraint violation.\u003c/p\u003e","id":"18.6-8283ac4f7a0c7e8e","identity_text":"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.","part":"changes","patch_ids":["aa2c8d3131ec8ded09af11b556aef077"],"relations":[{"evidence":{"patch_ids":["aa2c8d3131ec8ded09af11b556aef077"],"same_day":true,"statement_hash":"783702d713b28b6565831a41c965e36e4f1f58ce03f4dd140c2304c8f02a319e"},"rule":2,"target":"8c14bd88ba60ce9fdffdf9d72dd6da15","type":"equivalent"},{"evidence":{"patch_ids":["aa2c8d3131ec8ded09af11b556aef077"],"same_day":true,"statement_hash":"783702d713b28b6565831a41c965e36e4f1f58ce03f4dd140c2304c8f02a319e"},"rule":2,"target":"cb00c5a92a3128a4094b82f1499aa619","type":"equivalent"},{"evidence":{"patch_ids":["aa2c8d3131ec8ded09af11b556aef077"],"same_day":true,"statement_hash":"783702d713b28b6565831a41c965e36e4f1f58ce03f4dd140c2304c8f02a319e"},"rule":2,"target":"d30d3b7b8ed23c31f3db15911611954c","type":"equivalent"},{"evidence":{"patch_ids":["aa2c8d3131ec8ded09af11b556aef077"],"same_day":true,"statement_hash":"783702d713b28b6565831a41c965e36e4f1f58ce03f4dd140c2304c8f02a319e"},"rule":2,"target":"e5eb6e313eecd9bd0c4062dcd9a34861","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["e4527519b"],"source_entry_id":"18.6/changes/049","source_hash":"20f3eed1649306dfb7a78c54da0e144af4f74021deabbd4d35dedf55e9e7c4cd","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"783702d713b28b6565831a41c965e36e4f1f58ce03f4dd140c2304c8f02a319e","text":"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.","title":"Fix use of REINDEX CONCURRENTLY with a deferred uniqueness constraint"},"id":"18.6-8283ac4f7a0c7e8e","matches":[{"id":"17.11-5f6921ca5abdfb75","source_entry_id":"17.11/changes/040","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix use of REINDEX CONCURRENTLY with a deferred uniqueness constraint","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/049","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix use of REINDEX CONCURRENTLY with a deferred uniqueness constraint","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["0c9cbbfb5","273fe9485","82116023e","8bb935d61","c391375ba","f2ff15e4c"],"commit_groups":[["0c9cbbfb5","273fe9485","82116023e","8bb935d61","c391375ba","f2ff15e4c"]],"commits":["273fe9485"],"cves":[],"db_id":"3a6050c2cb2fe8b496eaa4963a657d6a","html":"\u003cp\u003eFix incorrect NFC recomposition for Hangul U+11A7 (TBASE) (Diego Frias, Michael Paquier) \u003ca href=\"https://postgr.es/c/273fe9485\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis character was treated as a valid T syllable, which it is not, and hence silently swallowed during normalization.\u003c/p\u003e","id":"18.6-bad72301bf213a01","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.","part":"changes","patch_ids":["725250db9eb55dab240d380ece2a835b"],"relations":[{"evidence":{"patch_ids":["725250db9eb55dab240d380ece2a835b"],"same_day":true,"statement_hash":"0790cf6e3b0bbc225a449fee5cfdf5d70b4c6b23cc6777393156d83479c1c717"},"rule":2,"target":"3ca62c531cc3952831a57b828ba3be6f","type":"equivalent"},{"evidence":{"patch_ids":["725250db9eb55dab240d380ece2a835b"],"same_day":true,"statement_hash":"0790cf6e3b0bbc225a449fee5cfdf5d70b4c6b23cc6777393156d83479c1c717"},"rule":2,"target":"955b29dab0dd740875781e1df1992bdc","type":"equivalent"},{"evidence":{"patch_ids":["725250db9eb55dab240d380ece2a835b"],"same_day":true,"statement_hash":"0790cf6e3b0bbc225a449fee5cfdf5d70b4c6b23cc6777393156d83479c1c717"},"rule":2,"target":"aaef9ba320136440f8b0a3ec12c67f23","type":"equivalent"},{"evidence":{"patch_ids":["725250db9eb55dab240d380ece2a835b"],"same_day":true,"statement_hash":"0790cf6e3b0bbc225a449fee5cfdf5d70b4c6b23cc6777393156d83479c1c717"},"rule":2,"target":"b4da21230a332d29b7fdd0c30e5eb1b0","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["273fe9485"],"source_entry_id":"18.6/changes/054","source_hash":"12dfc8fb1740739aa2a2241aafbdc5e41621ac922bf07241fb5d6d9f53cabe3d","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"0790cf6e3b0bbc225a449fee5cfdf5d70b4c6b23cc6777393156d83479c1c717","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)"},"id":"18.6-bad72301bf213a01","matches":[{"id":"17.11-ed1426e8e931d4ba","source_entry_id":"17.11/changes/042","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix incorrect NFC recomposition for Hangul U+11A7 (TBASE)","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/054","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix incorrect NFC recomposition for Hangul U+11A7 (TBASE)","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["1e0458172","3805641cb","89e648498","9234e3337","a7e0e42a2","b32df590c"],"commit_groups":[["1e0458172","3805641cb","89e648498","9234e3337","a7e0e42a2","b32df590c"]],"commits":["89e648498"],"cves":[],"db_id":"347d8e16786f9262348eddb4e4ab7132","html":"\u003cp\u003eAvoid possible truncation of output lexemes in case-insensitive \u003ccode\u003esynonym\u003c/code\u003e dictionaries (Jeff Davis) \u003ca href=\"https://postgr.es/c/89e648498\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf folding to lower case increased the byte length of a lexeme, it was incorrectly truncated to its original byte length when emitted.\u003c/p\u003e","id":"18.6-3c978527782bcd11","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.","part":"changes","patch_ids":["751e547292fa99c95c843d27d6c9593a"],"relations":[{"evidence":{"patch_ids":["751e547292fa99c95c843d27d6c9593a"],"same_day":true,"statement_hash":"c66911e6e36c7126e1b585143d9e9b87d38db4e29cfb38c6987eff4e2c4f70d3"},"rule":2,"target":"0633548b5897af860062f0da29c48e44","type":"equivalent"},{"evidence":{"patch_ids":["751e547292fa99c95c843d27d6c9593a"],"same_day":true,"statement_hash":"c66911e6e36c7126e1b585143d9e9b87d38db4e29cfb38c6987eff4e2c4f70d3"},"rule":2,"target":"3af409a2d71c7fbd1a45975cdba31ea0","type":"equivalent"},{"evidence":{"patch_ids":["751e547292fa99c95c843d27d6c9593a"],"same_day":true,"statement_hash":"c66911e6e36c7126e1b585143d9e9b87d38db4e29cfb38c6987eff4e2c4f70d3"},"rule":2,"target":"a4a88f042e4bc74a3646ee98fc6e3a95","type":"equivalent"},{"evidence":{"patch_ids":["751e547292fa99c95c843d27d6c9593a"],"same_day":true,"statement_hash":"c66911e6e36c7126e1b585143d9e9b87d38db4e29cfb38c6987eff4e2c4f70d3"},"rule":2,"target":"ae43518b0809db4841928b42a3de5142","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["89e648498"],"source_entry_id":"18.6/changes/055","source_hash":"77469b6258132929a06ffd007b2e4038dba19ecf2bf22a1c920ef1c94e3decdd","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"c66911e6e36c7126e1b585143d9e9b87d38db4e29cfb38c6987eff4e2c4f70d3","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"},"id":"18.6-3c978527782bcd11","matches":[{"id":"17.11-a4695342e5fc0fc7","source_entry_id":"17.11/changes/043","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Avoid possible truncation of output lexemes in case-insensitive synonym dictionaries","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/055","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Avoid possible truncation of output lexemes in case-insensitive synonym dictionaries","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["05da336dd","21ffc271d","5e78ebca5","9021c8f3c"],"commit_groups":[["05da336dd","21ffc271d","5e78ebca5","9021c8f3c"]],"commits":["9021c8f3c"],"cves":[],"db_id":"fbf07b5b0ddd47273177153e01d4ca58","html":"\u003cp\u003eDefend against truncated UTF-8 characters in case-conversion logic (Jeff Davis) \u003ca href=\"https://postgr.es/c/9021c8f3c\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-fcede1358593efe6","identity_text":"Defend against truncated UTF-8 characters in case-conversion logic (Jeff Davis)","part":"changes","patch_ids":["70ade08782c5c0086629edb156a1a000"],"relations":[{"evidence":{"patch_ids":["70ade08782c5c0086629edb156a1a000"],"same_day":true,"statement_hash":"b8ea4712aa3d1f59707ea58deb088497b6eb664982552c1833b1fdb40b14fc59"},"rule":2,"target":"6587fa053296846f315df1024b486ffb","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["9021c8f3c"],"source_entry_id":"18.6/changes/056","source_hash":"89b6cc131a56223f184b1fbcb6088e67d57ed12feda80537ab55e794e0c3ac4d","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"b8ea4712aa3d1f59707ea58deb088497b6eb664982552c1833b1fdb40b14fc59","text":"Defend against truncated UTF-8 characters in case-conversion logic (Jeff Davis) §","title":"Defend against truncated UTF-8 characters in case-conversion logic"},"id":"18.6-fcede1358593efe6","matches":[{"id":"17.11-650fe2adca4c15c7","source_entry_id":"17.11/changes/044","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Defend against truncated UTF-8 characters in case-conversion logic","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/056","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Defend against truncated UTF-8 characters in case-conversion logic","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["203e238bb","259b627d5","273a3c776","74d3482f4","8b5580a05","b3f13c032"],"commit_groups":[["203e238bb","259b627d5","273a3c776","74d3482f4","8b5580a05","b3f13c032"]],"commits":["b3f13c032"],"cves":[],"db_id":"1a54434973bf348ac56bbd357db25e7a","html":"\u003cp\u003eFix typo in \u003ccode\u003ehash_record_extended()\u003c/code\u003e (Man Zeng) \u003ca href=\"https://postgr.es/c/b3f13c032\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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 \u003ccode\u003ePG_ARGISNULL(1)\u003c/code\u003e.\u003c/p\u003e","id":"18.6-07aee184fcf9a835","identity_text":"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).","part":"changes","patch_ids":["29a84f83d9835258ff987caab51900d5"],"relations":[{"evidence":{"patch_ids":["29a84f83d9835258ff987caab51900d5"],"same_day":true,"statement_hash":"6a481541d5459f5a423fe86368ee4362d85dac47eaf33158755dd903beff8a30"},"rule":2,"target":"25a4f41e6e86c5076cca107fea29ef1d","type":"equivalent"},{"evidence":{"patch_ids":["29a84f83d9835258ff987caab51900d5"],"same_day":true,"statement_hash":"6a481541d5459f5a423fe86368ee4362d85dac47eaf33158755dd903beff8a30"},"rule":2,"target":"3a78996c251f4fe686fe5fedcd3f9184","type":"equivalent"},{"evidence":{"patch_ids":["29a84f83d9835258ff987caab51900d5"],"same_day":true,"statement_hash":"6a481541d5459f5a423fe86368ee4362d85dac47eaf33158755dd903beff8a30"},"rule":2,"target":"5f9c74e8a3fc194bfa4ae79b3e4f07c7","type":"equivalent"},{"evidence":{"patch_ids":["29a84f83d9835258ff987caab51900d5"],"same_day":true,"statement_hash":"6a481541d5459f5a423fe86368ee4362d85dac47eaf33158755dd903beff8a30"},"rule":2,"target":"ece2673fe4b30003bf5bf840a25f59a4","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b3f13c032"],"source_entry_id":"18.6/changes/057","source_hash":"a922d36a3c1c13dd842a8491ec3c40f6f6563f8e66780fdb65cb475a41ca2c1b","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"6a481541d5459f5a423fe86368ee4362d85dac47eaf33158755dd903beff8a30","text":"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).","title":"Fix typo in hash_record_extended()"},"id":"18.6-07aee184fcf9a835","matches":[{"id":"17.11-f5ccad03da59d5de","source_entry_id":"17.11/changes/045","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix typo in hash_record_extended()","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/057","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix typo in hash_record_extended()","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["28c995948","63e7a0d2c","6c760f6b6","73d63d1c1","dcbc96685"],"commit_groups":[["28c995948","63e7a0d2c","6c760f6b6","73d63d1c1","dcbc96685"]],"commits":["73d63d1c1"],"cves":[],"db_id":"5cf6a04270abb8d2d149dfad435adf07","html":"\u003cp\u003eFix \u003ccode\u003epg_get_publication_tables()\u003c/code\u003e to not fail if a publishable table is dropped concurrently (Bharath Rupireddy) \u003ca href=\"https://postgr.es/c/73d63d1c1\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-07cb6565704cd80c","identity_text":"Fix pg_get_publication_tables() to not fail if a publishable table is dropped concurrently (Bharath Rupireddy)","part":"changes","patch_ids":["d3e55b796cea940a071bce62c2044e17"],"relations":[{"evidence":{"patch_ids":["d3e55b796cea940a071bce62c2044e17"],"same_day":true,"statement_hash":"ab1fb78f736632c66a87ee6397f802a5788855b6c355948e078a57aaab77b53e"},"rule":2,"target":"14c82613c1589216a8ccd71f1db8822e","type":"equivalent"},{"evidence":{"patch_ids":["d3e55b796cea940a071bce62c2044e17"],"same_day":true,"statement_hash":"ab1fb78f736632c66a87ee6397f802a5788855b6c355948e078a57aaab77b53e"},"rule":2,"target":"e740f6073746bb56668a4a47edba21d2","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["73d63d1c1"],"source_entry_id":"18.6/changes/058","source_hash":"048fe358bb679cb48c09cd22d4b797cfcbff48e86771a8cd2a4d0886859d47c2","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"ab1fb78f736632c66a87ee6397f802a5788855b6c355948e078a57aaab77b53e","text":"Fix pg_get_publication_tables() to not fail if a publishable table is dropped concurrently (Bharath Rupireddy) §","title":"Fix pg_get_publication_tables() to not fail if a publishable table is dropped concurrently"},"id":"18.6-07cb6565704cd80c","matches":[{"id":"17.11-a3d6c74423b0a5d4","source_entry_id":"17.11/changes/046","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix pg_get_publication_tables() to not fail if a publishable table is dropped concurrently","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/058","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix pg_get_publication_tables() to not fail if a publishable table is dropped concurrently","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["0115650de","0c06ebf12","2ddc45662","52af6fef4","6de480156","d39b9eed0","e8914ec22"],"commit_groups":[["0115650de","0c06ebf12","2ddc45662","52af6fef4","6de480156","d39b9eed0","e8914ec22"]],"commits":["0c06ebf12"],"cves":[],"db_id":"aca7b7cc0c6297fb6f870b60ad6c6eb2","html":"\u003cp\u003ePrevent \u003ccode\u003esatisfies_hash_partition()\u003c/code\u003e from crashing with \u003ccode\u003eVARIADIC NULL\u003c/code\u003e (Robert Haas) \u003ca href=\"https://postgr.es/c/0c06ebf12\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-8e6a8684fc76928f","identity_text":"Prevent satisfies_hash_partition() from crashing with VARIADIC NULL (Robert Haas)","part":"changes","patch_ids":["a1fff8ec6956e6fe697219d698fc333c"],"relations":[{"evidence":{"patch_ids":["a1fff8ec6956e6fe697219d698fc333c"],"same_day":true,"statement_hash":"2c10eabfd2357642afd00af080282da33e338699d23c4fd63ebce1ed6b5d3de6"},"rule":2,"target":"1fb3283adc95d5350d7e43a295bb846c","type":"equivalent"},{"evidence":{"patch_ids":["a1fff8ec6956e6fe697219d698fc333c"],"same_day":true,"statement_hash":"2c10eabfd2357642afd00af080282da33e338699d23c4fd63ebce1ed6b5d3de6"},"rule":2,"target":"250fe82e174ea43c46f699d38a0bc047","type":"equivalent"},{"evidence":{"patch_ids":["a1fff8ec6956e6fe697219d698fc333c"],"same_day":true,"statement_hash":"2c10eabfd2357642afd00af080282da33e338699d23c4fd63ebce1ed6b5d3de6"},"rule":2,"target":"393be0bc06aa5c29057eb4def7239bd8","type":"equivalent"},{"evidence":{"patch_ids":["a1fff8ec6956e6fe697219d698fc333c"],"same_day":true,"statement_hash":"2c10eabfd2357642afd00af080282da33e338699d23c4fd63ebce1ed6b5d3de6"},"rule":2,"target":"588ad857d225574ba2a655f6d141dfd0","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["0c06ebf12"],"source_entry_id":"18.6/changes/059","source_hash":"23bea444ad424eb33803b0dbca40538305c5da8c5b78995270f51ec10c8249ad","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"2c10eabfd2357642afd00af080282da33e338699d23c4fd63ebce1ed6b5d3de6","text":"Prevent satisfies_hash_partition() from crashing with VARIADIC NULL (Robert Haas) §","title":"Prevent satisfies_hash_partition() from crashing with VARIADIC NULL"},"id":"18.6-8e6a8684fc76928f","matches":[{"id":"17.11-f0697d05fabe6ce7","source_entry_id":"17.11/changes/047","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Prevent satisfies_hash_partition() from crashing with VARIADIC NULL","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/059","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Prevent satisfies_hash_partition() from crashing with VARIADIC NULL","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["0626fbfeb","262cc4df2","b3a86eb6d","c5194139c","ce6bf3cd1","ed5ca5828"],"commit_groups":[["0626fbfeb","262cc4df2","b3a86eb6d","c5194139c","ce6bf3cd1","ed5ca5828"]],"commits":["c5194139c"],"cves":[],"db_id":"7d5a91e54ac5103d6bf03024f3af935e","html":"\u003cp\u003eReport invalid-weight errors more cleanly and consistently in \u003ccode\u003etsvector_filter()\u003c/code\u003e and allied functions (Ewan Young) \u003ca href=\"https://postgr.es/c/c5194139c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIn particular, report weight characters that are not printable ASCII in octal form (\u003ccode\u003e\\\u003cem\u003e\u003ccode\u003ennn\u003c/code\u003e\u003c/em\u003e\u003c/code\u003e), as \u003ccode\u003echarout()\u003c/code\u003e would render them. This avoids possibly producing an invalidly-encoded error message.\u003c/p\u003e","id":"18.6-9981c3dd5925e5fe","identity_text":"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 (\\nnn), as charout() would render them. This avoids possibly producing an invalidly-encoded error message.","part":"changes","patch_ids":["108ef859ecda6eaa371bc79609379d31"],"relations":[{"evidence":{"patch_ids":["108ef859ecda6eaa371bc79609379d31"],"same_day":true,"statement_hash":"b23812182f466ab2843cf43ee7c0e1ecacecfe15dece91513947714713458af8"},"rule":2,"target":"1b9097ec2e33d310c015aacb80137ff1","type":"equivalent"},{"evidence":{"patch_ids":["108ef859ecda6eaa371bc79609379d31"],"same_day":true,"statement_hash":"b23812182f466ab2843cf43ee7c0e1ecacecfe15dece91513947714713458af8"},"rule":2,"target":"4d393fd29403237b560622e62e4ee4e1","type":"equivalent"},{"evidence":{"patch_ids":["108ef859ecda6eaa371bc79609379d31"],"same_day":true,"statement_hash":"b23812182f466ab2843cf43ee7c0e1ecacecfe15dece91513947714713458af8"},"rule":2,"target":"7e8ee08fd9d07b25538b838699962287","type":"equivalent"},{"evidence":{"patch_ids":["108ef859ecda6eaa371bc79609379d31"],"same_day":true,"statement_hash":"b23812182f466ab2843cf43ee7c0e1ecacecfe15dece91513947714713458af8"},"rule":2,"target":"bdf6d20897614c30387f78e16ddf9d3d","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c5194139c"],"source_entry_id":"18.6/changes/060","source_hash":"85f8a7d8c974c413de7e0801013546c6d3e904b56e815556bf19337c42bbe9a6","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"b23812182f466ab2843cf43ee7c0e1ecacecfe15dece91513947714713458af8","text":"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 (\\nnn), as charout() would render them. This avoids possibly producing an invalidly-encoded error message.","title":"Report invalid-weight errors more cleanly and consistently in tsvector_filter() and allied functions"},"id":"18.6-9981c3dd5925e5fe","matches":[{"id":"17.11-39600e2a322b65b2","source_entry_id":"17.11/changes/048","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Report invalid-weight errors more cleanly and consistently in tsvector_filter() and allied functions","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/060","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Report invalid-weight errors more cleanly and consistently in tsvector_filter() and allied functions","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["0b74df66f","0d145be2c","174076601","1d8c72b2e","41876c8d7","4c777d6dd","6c08cbb7a","8bf257aeb","940916549","9618e790c","a17f39aa2","fac26fd41"],"commit_groups":[["0b74df66f","0d145be2c","940916549","9618e790c","a17f39aa2","fac26fd41"],["174076601","1d8c72b2e","41876c8d7","4c777d6dd","6c08cbb7a","8bf257aeb"]],"commits":["0d145be2c","4c777d6dd"],"cves":[],"db_id":"9d61a6c023f441c2a3883f44804564ca","html":"\u003cp\u003eFix mishandling of namespace nodes in \u003ccode\u003expath()\u003c/code\u003e (Michael Paquier) \u003ca href=\"https://postgr.es/c/4c777d6dd\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/0d145be2c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis fix avoids an unexpected \u003cspan\u003e“\u003cspan\u003ecould not copy node\u003c/span\u003e”\u003c/span\u003e error.\u003c/p\u003e","id":"18.6-a9563797105c5be3","identity_text":"Fix mishandling of namespace nodes in xpath() (Michael Paquier) This fix avoids an unexpected could not copy node error.","part":"changes","patch_ids":["702367d070cdeca227ba0e4197a518e9","7df9ed5e8663765f5ca836c89d33f03d"],"relations":[{"evidence":{"patch_ids":["702367d070cdeca227ba0e4197a518e9","7df9ed5e8663765f5ca836c89d33f03d"],"same_day":true,"statement_hash":"2ab954d63190bf0ecdc409c287a734a5049667a3d9db9dc5337f82a35275db37"},"rule":2,"target":"a3cd7c73a5609ef9df5a2f2035307742","type":"equivalent"},{"evidence":{"patch_ids":["702367d070cdeca227ba0e4197a518e9","7df9ed5e8663765f5ca836c89d33f03d"],"same_day":true,"statement_hash":"2ab954d63190bf0ecdc409c287a734a5049667a3d9db9dc5337f82a35275db37"},"rule":2,"target":"c9299f10a2be68af64d82e072893d1fa","type":"equivalent"},{"evidence":{"patch_ids":["702367d070cdeca227ba0e4197a518e9","7df9ed5e8663765f5ca836c89d33f03d"],"same_day":true,"statement_hash":"2ab954d63190bf0ecdc409c287a734a5049667a3d9db9dc5337f82a35275db37"},"rule":2,"target":"d35a51c2f2bcdba360c287240fa92b7a","type":"equivalent"},{"evidence":{"patch_ids":["702367d070cdeca227ba0e4197a518e9","7df9ed5e8663765f5ca836c89d33f03d"],"same_day":true,"statement_hash":"2ab954d63190bf0ecdc409c287a734a5049667a3d9db9dc5337f82a35275db37"},"rule":2,"target":"da05c3ee44af186be3d4b5b7c6f0afe4","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["0d145be2c","4c777d6dd"],"source_entry_id":"18.6/changes/062","source_hash":"46a1a93cf33ad088d8ce016a48b23002f2c9ca6b8eb39cb5d92df14ea571c8bb","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"2ab954d63190bf0ecdc409c287a734a5049667a3d9db9dc5337f82a35275db37","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()"},"id":"18.6-a9563797105c5be3","matches":[{"id":"17.11-aea52062a31be5cf","source_entry_id":"17.11/changes/049","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix mishandling of namespace nodes in xpath()","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/062","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix mishandling of namespace nodes in xpath()","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["5bbc9b300","7b12ae729","84001a04d","90789900b","ab35b8d25","c768637d6"],"commit_groups":[["5bbc9b300","7b12ae729","84001a04d","ab35b8d25"],["90789900b","c768637d6"]],"commits":["84001a04d","90789900b"],"cves":[],"db_id":"e2b61ba2f7f1acf6259668e5028c0d3a","html":"\u003cp\u003eFix \u003ccode\u003ejsonpath\u003c/code\u003e's \u003ccode\u003e.decimal\u003c/code\u003e method to not throw a hard error for incorrect precision or scale (Ewan Young) \u003ca href=\"https://postgr.es/c/84001a04d\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/90789900b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSilent mode should suppress these errors, but failed to.\u003c/p\u003e","id":"18.6-9490e3fbcfd0ff13","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.","part":"changes","patch_ids":["154a264168d2701e57e668c30f8c6672","a933e072e485a711920d54cb328279be"],"relations":[{"evidence":{"patch_ids":["154a264168d2701e57e668c30f8c6672","a933e072e485a711920d54cb328279be"],"same_day":true,"statement_hash":"c504d01401e67b15f04b83edbe81331d59a4135c0f6c1aae9aeea83bf5ceb972"},"rule":2,"target":"151967124db1018c14bba6aaa8fb0531","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["84001a04d","90789900b"],"source_entry_id":"18.6/changes/063","source_hash":"a24f0d483057c78a7d10cc03aacfc3f8214515bbebcd0c3bd866baab53ff26bf","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"c504d01401e67b15f04b83edbe81331d59a4135c0f6c1aae9aeea83bf5ceb972","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"},"id":"18.6-9490e3fbcfd0ff13","matches":[{"id":"17.11-3a52211bf75efb3d","source_entry_id":"17.11/changes/050","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/063","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","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["35d9a6263","60abb3c73","7dd153259","d0acd2535"],"commit_groups":[["35d9a6263","60abb3c73","7dd153259","d0acd2535"]],"commits":["35d9a6263"],"cves":[],"db_id":"2fbf45f00e42445fcae00d71cbf1f0dc","html":"\u003cp\u003eFix NULL-pointer crash when \u003ccode\u003eIS JSON\u003c/code\u003e or similar constructs have an argument that is of string category but lacks a cast to type \u003ccode\u003etext\u003c/code\u003e (Ayush Tiwari) \u003ca href=\"https://postgr.es/c/35d9a6263\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThere are no such data types in core \u003cspan\u003ePostgreSQL\u003c/span\u003e, but the problem is reachable with some extension types.\u003c/p\u003e","id":"18.6-2abf51fa81b5fec1","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.","part":"changes","patch_ids":["96b46719db446e88ef3c60d115404730"],"relations":[{"evidence":{"patch_ids":["96b46719db446e88ef3c60d115404730"],"same_day":true,"statement_hash":"ea987d289e305c0b161cfa39b9d0169ba382dac0fa72d5593a7a281f289b9a70"},"rule":2,"target":"79cd8a83e8bf1bc35f530164bf6860b4","type":"equivalent"},{"evidence":{"patch_ids":["96b46719db446e88ef3c60d115404730"],"same_day":true,"statement_hash":"ea987d289e305c0b161cfa39b9d0169ba382dac0fa72d5593a7a281f289b9a70"},"rule":2,"target":"f8921df2d66db8b26d617c27bddf1db2","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["35d9a6263"],"source_entry_id":"18.6/changes/064","source_hash":"15c4b6ebef3e976580dd4a81a7bddc91381ff8e797fc936f95505c826d0e418e","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"ea987d289e305c0b161cfa39b9d0169ba382dac0fa72d5593a7a281f289b9a70","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"},"id":"18.6-2abf51fa81b5fec1","matches":[{"id":"17.11-b72bd4ebdcd34344","source_entry_id":"17.11/changes/051","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/064","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","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["441e4c8d6","4c75cc786","71cd10cd2","d30bfcbdd"],"commit_groups":[["441e4c8d6","4c75cc786","71cd10cd2","d30bfcbdd"]],"commits":["441e4c8d6"],"cves":[],"db_id":"5ee1791684a43e69ac4ed959f3852d47","html":"\u003cp\u003eEnsure that \u003ccode\u003eSQL/JSON\u003c/code\u003e \u003ccode\u003eON EMPTY / ON ERROR DEFAULT\u003c/code\u003e values are coerced to the correct typmod (Ewan Young) \u003ca href=\"https://postgr.es/c/441e4c8d6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFor example, the declared precision and scale of a \u003ccode\u003enumeric\u003c/code\u003e target column were not applied to the default value.\u003c/p\u003e","id":"18.6-e111e1506709b495","identity_text":"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.","part":"changes","patch_ids":["b9ce697f680c880e4c53a6fd83dff066"],"relations":[{"evidence":{"patch_ids":["b9ce697f680c880e4c53a6fd83dff066"],"same_day":true,"statement_hash":"84e0e04519fd346f18f4cc46eecce1f970b11e003a6a36e9e143044837d8e75e"},"rule":2,"target":"46a8087a2739fb6992db3b87c3ffba3b","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["441e4c8d6"],"source_entry_id":"18.6/changes/065","source_hash":"add98cb9e1f80ee762143f9881e7da06d23f415688008c80539511e301250f57","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"84e0e04519fd346f18f4cc46eecce1f970b11e003a6a36e9e143044837d8e75e","text":"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.","title":"Ensure that SQL/JSON ON EMPTY / ON ERROR DEFAULT values are coerced to the correct typmod"},"id":"18.6-e111e1506709b495","matches":[{"id":"17.11-17dc3fca15a1c17a","source_entry_id":"17.11/changes/052","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/065","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","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["1416f304d","6298a41b4","7746f7492","86f42357c","b4dfae2ff","d782c97e1","fec40878c"],"commit_groups":[["1416f304d","6298a41b4","7746f7492","86f42357c","b4dfae2ff","d782c97e1","fec40878c"]],"commits":["6298a41b4"],"cves":[],"db_id":"ee7676270a36bf258a65c89f89fa44af","html":"\u003cp\u003eAvoid machine-dependent behavior when dividing the smallest possible \u003ccode\u003emoney\u003c/code\u003e value by -1 (Andrey Rachitskiy) \u003ca href=\"https://postgr.es/c/6298a41b4\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-da37578bb1901f30","identity_text":"Avoid machine-dependent behavior when dividing the smallest possible money value by -1 (Andrey Rachitskiy)","part":"changes","patch_ids":["fe8aedb6e19e256e063c5525f5021a96"],"relations":[{"evidence":{"patch_ids":["fe8aedb6e19e256e063c5525f5021a96"],"same_day":true,"statement_hash":"5be6e13596b05605cc072eb289af3ca913d55550b31c1733b3d9a107ef4f6567"},"rule":2,"target":"5ddb2b6ecf3b95db0488f70dff6ce420","type":"equivalent"},{"evidence":{"patch_ids":["fe8aedb6e19e256e063c5525f5021a96"],"same_day":true,"statement_hash":"5be6e13596b05605cc072eb289af3ca913d55550b31c1733b3d9a107ef4f6567"},"rule":2,"target":"606f8159e0d16f836c764d3cf06215f0","type":"equivalent"},{"evidence":{"patch_ids":["fe8aedb6e19e256e063c5525f5021a96"],"same_day":true,"statement_hash":"5be6e13596b05605cc072eb289af3ca913d55550b31c1733b3d9a107ef4f6567"},"rule":2,"target":"ab04f82d05155d2f24611a645ef67570","type":"equivalent"},{"evidence":{"patch_ids":["fe8aedb6e19e256e063c5525f5021a96"],"same_day":true,"statement_hash":"5be6e13596b05605cc072eb289af3ca913d55550b31c1733b3d9a107ef4f6567"},"rule":2,"target":"ad37c4809a78b0946b550655ff98efbb","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["6298a41b4"],"source_entry_id":"18.6/changes/066","source_hash":"74e8b24c99c85d82b80f7175f5a5b42adcb6ced40e77400f70ca339e83b7d28d","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"5be6e13596b05605cc072eb289af3ca913d55550b31c1733b3d9a107ef4f6567","text":"Avoid machine-dependent behavior when dividing the smallest possible money value by -1 (Andrey Rachitskiy) §","title":"Avoid machine-dependent behavior when dividing the smallest possible money value by -1"},"id":"18.6-da37578bb1901f30","matches":[{"id":"17.11-7b7ee8e84aced4b2","source_entry_id":"17.11/changes/053","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Avoid machine-dependent behavior when dividing the smallest possible money value by -1","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/066","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Avoid machine-dependent behavior when dividing the smallest possible money value by -1","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["025228104","4e68b7e29","634a8dcb8","81b1e7916","83336e3ed","dda622edc","df8407d7d"],"commit_groups":[["025228104","4e68b7e29","634a8dcb8","81b1e7916","83336e3ed","dda622edc","df8407d7d"]],"commits":["81b1e7916"],"cves":[],"db_id":"c02824b6af588491530569e4ec99fe1c","html":"\u003cp\u003eFix crash after out-of-memory failure partway through creation of a cache entry for a text search dictionary (Tom Lane) \u003ca href=\"https://postgr.es/c/81b1e7916\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-8f91828547f09bb4","identity_text":"Fix crash after out-of-memory failure partway through creation of a cache entry for a text search dictionary (Tom Lane)","part":"changes","patch_ids":["3c3b45b5ca2c2212b9a36ad4558d619a"],"relations":[{"evidence":{"patch_ids":["3c3b45b5ca2c2212b9a36ad4558d619a"],"same_day":true,"statement_hash":"bba5519e5078b4a32c843646cda9fbb9119cc591d67acb786924d35be185c1e2"},"rule":2,"target":"0c1ad5d57b9bccac58da6089309d8ba7","type":"equivalent"},{"evidence":{"patch_ids":["3c3b45b5ca2c2212b9a36ad4558d619a"],"same_day":true,"statement_hash":"bba5519e5078b4a32c843646cda9fbb9119cc591d67acb786924d35be185c1e2"},"rule":2,"target":"7df44ef8cf990bb0e618cec50c164949","type":"equivalent"},{"evidence":{"patch_ids":["3c3b45b5ca2c2212b9a36ad4558d619a"],"same_day":true,"statement_hash":"bba5519e5078b4a32c843646cda9fbb9119cc591d67acb786924d35be185c1e2"},"rule":2,"target":"b0c7268f189c5a8d74b8439d4bc7c5d9","type":"equivalent"},{"evidence":{"patch_ids":["3c3b45b5ca2c2212b9a36ad4558d619a"],"same_day":true,"statement_hash":"bba5519e5078b4a32c843646cda9fbb9119cc591d67acb786924d35be185c1e2"},"rule":2,"target":"b1fc0de5d2d692ed4af6bcafccb53961","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["81b1e7916"],"source_entry_id":"18.6/changes/067","source_hash":"da086036f61c30030e5480df95ebc5320aafce594ba5114ebc8b25742df3e065","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"bba5519e5078b4a32c843646cda9fbb9119cc591d67acb786924d35be185c1e2","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"},"id":"18.6-8f91828547f09bb4","matches":[{"id":"17.11-84e7ed3f45fec194","source_entry_id":"17.11/changes/054","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix crash after out-of-memory failure partway through creation of a cache entry for a text search dictionary","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/067","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix crash after out-of-memory failure partway through creation of a cache entry for a text search dictionary","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["0fb88979b","330a72052","3fe4062cc","444038bb7","4689ea9ce","5fdea3aa3","cfc720ef4"],"commit_groups":[["0fb88979b","330a72052","3fe4062cc","444038bb7","4689ea9ce","5fdea3aa3","cfc720ef4"]],"commits":["4689ea9ce"],"cves":[],"db_id":"704f65f60aac8a5ed9ba34cc041d5717","html":"\u003cp\u003eFix memory-safety bugs in processing of incorrect ispell/hunspell dictionary files (Andrey Rachitskiy) \u003ca href=\"https://postgr.es/c/4689ea9ce\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-df42fd80a3fef364","identity_text":"Fix memory-safety bugs in processing of incorrect ispell/hunspell dictionary files (Andrey Rachitskiy)","part":"changes","patch_ids":["a2481aa7491246722b292cb1e96c16e2"],"relations":[{"evidence":{"patch_ids":["a2481aa7491246722b292cb1e96c16e2"],"same_day":true,"statement_hash":"188f51f4de54b27a68f6be9927610ed299c71a8aed01714563e401acac778944"},"rule":2,"target":"5e12745b9a23fea83bd8ffdb594c44cb","type":"equivalent"},{"evidence":{"patch_ids":["a2481aa7491246722b292cb1e96c16e2"],"same_day":true,"statement_hash":"188f51f4de54b27a68f6be9927610ed299c71a8aed01714563e401acac778944"},"rule":2,"target":"764e3f0a6b15565637fa481647bae444","type":"equivalent"},{"evidence":{"patch_ids":["a2481aa7491246722b292cb1e96c16e2"],"same_day":true,"statement_hash":"188f51f4de54b27a68f6be9927610ed299c71a8aed01714563e401acac778944"},"rule":2,"target":"77ab5557c03ca1e42e47d51eb237608a","type":"equivalent"},{"evidence":{"patch_ids":["a2481aa7491246722b292cb1e96c16e2"],"same_day":true,"statement_hash":"188f51f4de54b27a68f6be9927610ed299c71a8aed01714563e401acac778944"},"rule":2,"target":"bff681fe60683158629758d3a37c8488","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["4689ea9ce"],"source_entry_id":"18.6/changes/068","source_hash":"71d6a8d23076219ae1c5fcc19a9192f7397d430f00d0743090078b3c95433c02","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"188f51f4de54b27a68f6be9927610ed299c71a8aed01714563e401acac778944","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"},"id":"18.6-df42fd80a3fef364","matches":[{"id":"17.11-ce317c73e36b1b1b","source_entry_id":"17.11/changes/055","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix memory-safety bugs in processing of incorrect ispell/hunspell dictionary files","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/068","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix memory-safety bugs in processing of incorrect ispell/hunspell dictionary files","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["1b0dd0815","3aaefe892","4dfae59a1","4e49f68b7","8021cdceb","c40819ebf","cc3fe7e2a","ce146621f"],"commit_groups":[["1b0dd0815","4dfae59a1","ce146621f"],["3aaefe892","4e49f68b7","8021cdceb","c40819ebf","cc3fe7e2a"]],"commits":["1b0dd0815","3aaefe892"],"cves":[],"db_id":"2b3bc99c3e3caa8f2f62effa65bfd425","html":"\u003cp\u003ePrevent access to other sessions' temporary tables (Jim Jones, Daniil Davydov, Alexander Korotkov) \u003ca href=\"https://postgr.es/c/1b0dd0815\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/3aaefe892\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSome code paths failed to prevent this, leading to silently wrong (inconsistent) results.\u003c/p\u003e","id":"18.6-90e78edb7a08a279","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.","part":"changes","patch_ids":["05c640bb8e2093f6ab8c82eace31d407","78047299bcd9d41b99e91dfc8ff6128f"],"relations":[{"evidence":{"patch_ids":["05c640bb8e2093f6ab8c82eace31d407","78047299bcd9d41b99e91dfc8ff6128f"],"same_day":true,"statement_hash":"bfbfb8f49eb1b9a9eeed9932c828c7ac49f313cc1b97070b91d77b3a11bb80b3"},"rule":2,"target":"446bb0cc48d437fdbe5c1c4d4b77a47b","type":"equivalent"},{"evidence":{"patch_ids":["05c640bb8e2093f6ab8c82eace31d407","78047299bcd9d41b99e91dfc8ff6128f"],"same_day":true,"statement_hash":"bfbfb8f49eb1b9a9eeed9932c828c7ac49f313cc1b97070b91d77b3a11bb80b3"},"rule":2,"target":"c23432cdcb396cd3d3ed58612faea4e6","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["1b0dd0815","3aaefe892"],"source_entry_id":"18.6/changes/069","source_hash":"0cdade44b0c297826d20dc41b61003ae0f4f3817586046a1103471fd0d51fc89","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"bfbfb8f49eb1b9a9eeed9932c828c7ac49f313cc1b97070b91d77b3a11bb80b3","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"},"id":"18.6-90e78edb7a08a279","matches":[{"id":"17.11-712f69030e2d06d3","source_entry_id":"17.11/changes/056","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Prevent access to other sessions' temporary tables","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/069","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Prevent access to other sessions' temporary tables","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["288d4e83f","4cc49cb70","b3331578b","baab3268c"],"commit_groups":[["288d4e83f","4cc49cb70","b3331578b","baab3268c"]],"commits":["4cc49cb70"],"cves":[],"db_id":"b9d8f2a43e4df58e7a17df3fbade9bf4","html":"\u003cp\u003eFix the order in which autovacuum processes databases (Rustam Khamidullin) \u003ca href=\"https://postgr.es/c/4cc49cb70\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIt was unintentionally processing databases from lowest to highest score, when it should be doing the reverse.\u003c/p\u003e","id":"18.6-8f425dbb364b3d86","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.","part":"changes","patch_ids":["42b814ceb732c97aa3c3a526508d3abb"],"relations":[{"evidence":{"patch_ids":["42b814ceb732c97aa3c3a526508d3abb"],"same_day":true,"statement_hash":"c6cdd05a4bedc5971c267480385958b00c43f204b53e4cc0fe52b1e5bf13ea9d"},"rule":2,"target":"7e5aa2c0c13918b50520756d59c3270c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["4cc49cb70"],"source_entry_id":"18.6/changes/071","source_hash":"1fd6e0f3d2162dba796e2b1af675ddaa0591b54062dd8f3eae3648a2fcc25a21","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"c6cdd05a4bedc5971c267480385958b00c43f204b53e4cc0fe52b1e5bf13ea9d","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"},"id":"18.6-8f425dbb364b3d86","matches":[{"id":"17.11-e7e74333c130ff46","source_entry_id":"17.11/changes/057","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix the order in which autovacuum processes databases","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/071","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix the order in which autovacuum processes databases","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["4154a1482","8ad414831","b20c952ce"],"commit_groups":[["4154a1482","8ad414831","b20c952ce"]],"commits":["4154a1482"],"cves":[],"db_id":"7610626b7c4fe5c411f6eaf69975db96","html":"\u003cp\u003eFix memory leak in parallel vacuum worker processes (Baji Shaik) \u003ca href=\"https://postgr.es/c/4154a1482\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eProgress reports from a parallel worker leaked about 1kB per report, with the waste accumulating for the life of the worker process.\u003c/p\u003e","id":"18.6-cf57ab07d77fbdf9","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.","part":"changes","patch_ids":["d49aabf7256557adc98b6cb3284f6aaa"],"relations":[{"evidence":{"patch_ids":["d49aabf7256557adc98b6cb3284f6aaa"],"same_day":true,"statement_hash":"568c6bb4288fdf9897eb84891ce83a70e68203e76785f837606ed060e05d9705"},"rule":2,"target":"12d3079ba949a43359b006c455b1a4d0","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["4154a1482"],"source_entry_id":"18.6/changes/073","source_hash":"eeb4d951de8faa7e6593a2a3defcc579409614caa126d11a39645d0152811604","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"568c6bb4288fdf9897eb84891ce83a70e68203e76785f837606ed060e05d9705","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"},"id":"18.6-cf57ab07d77fbdf9","matches":[{"id":"17.11-94146e86474835ca","source_entry_id":"17.11/changes/058","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix memory leak in parallel vacuum worker processes","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/073","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix memory leak in parallel vacuum worker processes","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["006ac761e","15fd7a3e2","70dad584e","7123abab7","7becb647d","8a045f760","ba5e46329"],"commit_groups":[["006ac761e","15fd7a3e2","70dad584e","7123abab7","7becb647d","8a045f760","ba5e46329"]],"commits":["7becb647d"],"cves":[],"db_id":"5ae3f0e86d0ce40099b20e708d75c4df","html":"\u003cp\u003eHonor query cancel and vacuum delay during GIN index posting-tree cleanup (Paul Kim, Alexander Korotkov) \u003ca href=\"https://postgr.es/c/7becb647d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e","id":"18.6-06642c9e897515be","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.","part":"changes","patch_ids":["5737ead0e5ff1d380903a73cc5289899"],"relations":[{"evidence":{"patch_ids":["5737ead0e5ff1d380903a73cc5289899"],"same_day":true,"statement_hash":"dbe0ee194244f00d3dbdcf97c73698ed65ff34b62bead922d8670ce2d3ad820b"},"rule":2,"target":"409fe91bb94144927c72c3c45b46a6de","type":"equivalent"},{"evidence":{"patch_ids":["5737ead0e5ff1d380903a73cc5289899"],"same_day":true,"statement_hash":"dbe0ee194244f00d3dbdcf97c73698ed65ff34b62bead922d8670ce2d3ad820b"},"rule":2,"target":"49ebdb578d55efc3f72704dda719fc23","type":"equivalent"},{"evidence":{"patch_ids":["5737ead0e5ff1d380903a73cc5289899"],"same_day":true,"statement_hash":"dbe0ee194244f00d3dbdcf97c73698ed65ff34b62bead922d8670ce2d3ad820b"},"rule":2,"target":"814dbd746257f327d953bc1cef61300f","type":"equivalent"},{"evidence":{"patch_ids":["5737ead0e5ff1d380903a73cc5289899"],"same_day":true,"statement_hash":"dbe0ee194244f00d3dbdcf97c73698ed65ff34b62bead922d8670ce2d3ad820b"},"rule":2,"target":"95dd23cd66ca5f13741dbc751bd94f78","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["7becb647d"],"source_entry_id":"18.6/changes/074","source_hash":"49842de8d396c469f5393f32a3ce7fe07babe095a16356733cf2d10be6590697","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"dbe0ee194244f00d3dbdcf97c73698ed65ff34b62bead922d8670ce2d3ad820b","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"},"id":"18.6-06642c9e897515be","matches":[{"id":"17.11-69bd1a00ee81086e","source_entry_id":"17.11/changes/059","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Honor query cancel and vacuum delay during GIN index posting-tree cleanup","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/074","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Honor query cancel and vacuum delay during GIN index posting-tree cleanup","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["126141425","1d4c81ad6","355faed5a","959b7fa2c","c9ea37231","e4ad22eb0","e58192546"],"commit_groups":[["126141425","1d4c81ad6","355faed5a","959b7fa2c","c9ea37231","e4ad22eb0","e58192546"]],"commits":["959b7fa2c"],"cves":[],"db_id":"ae38912b977aee6ba812c2a99322b4ad","html":"\u003cp\u003eFix possible mis-decoding of index tuples during GiST and SP-GiST index-only scans (Peter Geoghegan) \u003ca href=\"https://postgr.es/c/959b7fa2c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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.\u003c/p\u003e","id":"18.6-5a9e09abedfed179","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.","part":"changes","patch_ids":["7ca370d11dfae190ad9f8fa921a2ad3d"],"relations":[{"evidence":{"patch_ids":["7ca370d11dfae190ad9f8fa921a2ad3d"],"same_day":true,"statement_hash":"9efc8088134be1c1e73efd8706fe30257c8c7003aa683976e4455f175426f7c5"},"rule":2,"target":"14d92270ba44127134ec95d6dc3f7106","type":"equivalent"},{"evidence":{"patch_ids":["7ca370d11dfae190ad9f8fa921a2ad3d"],"same_day":true,"statement_hash":"9efc8088134be1c1e73efd8706fe30257c8c7003aa683976e4455f175426f7c5"},"rule":2,"target":"65fae97c05ec4b526543f385b077725a","type":"equivalent"},{"evidence":{"patch_ids":["7ca370d11dfae190ad9f8fa921a2ad3d"],"same_day":true,"statement_hash":"9efc8088134be1c1e73efd8706fe30257c8c7003aa683976e4455f175426f7c5"},"rule":2,"target":"7639c43a8df152827beb0f3c4e7cfc7b","type":"equivalent"},{"evidence":{"patch_ids":["7ca370d11dfae190ad9f8fa921a2ad3d"],"same_day":true,"statement_hash":"9efc8088134be1c1e73efd8706fe30257c8c7003aa683976e4455f175426f7c5"},"rule":2,"target":"fcb9ed65e8420a852359f3e3f6bd54b4","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["959b7fa2c"],"source_entry_id":"18.6/changes/075","source_hash":"d7cc314ea76420e257a538b400aafc8307da56ed29c7aec8ff09e69825fdf64a","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"9efc8088134be1c1e73efd8706fe30257c8c7003aa683976e4455f175426f7c5","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"},"id":"18.6-5a9e09abedfed179","matches":[{"id":"17.11-7b0787620962198f","source_entry_id":"17.11/changes/060","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/075","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","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["0fd5595aa","768ae083e","7a103928a","a2fd8d65a","eabc9a9dd"],"commit_groups":[["0fd5595aa","768ae083e","7a103928a","a2fd8d65a","eabc9a9dd"]],"commits":["eabc9a9dd"],"cves":[],"db_id":"edf9c4cb86d4f9c68eb8b2fe8ad0b5d1","html":"\u003cp\u003eEnsure that the new last block of a bulk-extended table is added to its free space map promptly (Jingtang Zhang) \u003ca href=\"https://postgr.es/c/eabc9a9dd\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAn 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.\u003c/p\u003e","id":"18.6-27ff2778a5384e11","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.","part":"changes","patch_ids":["a01b2fa451eb1e57f308131966fdbfa3"],"relations":[{"evidence":{"patch_ids":["a01b2fa451eb1e57f308131966fdbfa3"],"same_day":true,"statement_hash":"86a67f4007c63f314fcd3fa59706655774d99e6653a04f11b106c0666d4ea725"},"rule":2,"target":"21d26afc1e7bfcc375bff059f0b216d1","type":"equivalent"},{"evidence":{"patch_ids":["a01b2fa451eb1e57f308131966fdbfa3"],"same_day":true,"statement_hash":"86a67f4007c63f314fcd3fa59706655774d99e6653a04f11b106c0666d4ea725"},"rule":2,"target":"5a75bdb8448ae2da9b4ee0c1b6cfc0ec","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["eabc9a9dd"],"source_entry_id":"18.6/changes/076","source_hash":"00108bc91bf3548e985abaaceb15ffddb576d4b6698d11cc22ebd57764038b7c","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"86a67f4007c63f314fcd3fa59706655774d99e6653a04f11b106c0666d4ea725","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"},"id":"18.6-27ff2778a5384e11","matches":[{"id":"17.11-3992304d0ec9fe22","source_entry_id":"17.11/changes/061","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/076","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","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["011eedcdc","ac6a58a70","ef01ca6db"],"commit_groups":[["011eedcdc","ac6a58a70","ef01ca6db"]],"commits":["ac6a58a70"],"cves":[],"db_id":"1c2d5d9905bd8e6369c82b7ef237290e","html":"\u003cp\u003eAvoid possible double-free or infinite error recovery loop in resource cleanup during transaction abort (Tom Lane) \u003ca href=\"https://postgr.es/c/ac6a58a70\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-0c1c452c86d77ab6","identity_text":"Avoid possible double-free or infinite error recovery loop in resource cleanup during transaction abort (Tom Lane)","part":"changes","patch_ids":["952c61c83d0d5caa000ecdb0d8cb575f"],"relations":[{"evidence":{"patch_ids":["952c61c83d0d5caa000ecdb0d8cb575f"],"same_day":true,"statement_hash":"0a5717b9df09bcb1cf776219cba662308d08a453587910b5eb52fcd98913cda4"},"rule":2,"target":"c57cf207c2d63b373be8c9b4e51bf8b0","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["ac6a58a70"],"source_entry_id":"18.6/changes/077","source_hash":"715f023028128f4013b8cb1d6fda903d37d8e3744cb19b6e61bc48873d3a3f0e","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"0a5717b9df09bcb1cf776219cba662308d08a453587910b5eb52fcd98913cda4","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"},"id":"18.6-0c1c452c86d77ab6","matches":[{"id":"17.11-bc733642b8318e02","source_entry_id":"17.11/changes/062","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/077","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","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["4647ac142","4b3bc6b71","9951e3d38","aa80c34c8","f0a831ef3","f25a07b2d"],"commit_groups":[["4647ac142","4b3bc6b71","9951e3d38","aa80c34c8","f0a831ef3","f25a07b2d"]],"commits":["aa80c34c8"],"cves":[],"db_id":"7b3923b1add1cfb8cc243430e7e7769f","html":"\u003cp\u003eWhen creating directories, tolerate concurrent creation of the same directory (Andrew Dunstan, Tom Lane) \u003ca href=\"https://postgr.es/c/aa80c34c8\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-67b85199c3f22fc0","identity_text":"When creating directories, tolerate concurrent creation of the same directory (Andrew Dunstan, Tom Lane)","part":"changes","patch_ids":["be8272a81c28ebdf12c66d1c6ab05685"],"relations":[{"evidence":{"patch_ids":["be8272a81c28ebdf12c66d1c6ab05685"],"same_day":true,"statement_hash":"abc7e610f491a4ce631c4e62316b1f9bd718c7e9e581a2f07ba12774f5db10eb"},"rule":2,"target":"0c17e02f698dc60a4c3ff762796f0a7f","type":"equivalent"},{"evidence":{"patch_ids":["be8272a81c28ebdf12c66d1c6ab05685"],"same_day":true,"statement_hash":"abc7e610f491a4ce631c4e62316b1f9bd718c7e9e581a2f07ba12774f5db10eb"},"rule":2,"target":"268b9e4fbdc7682f30cd928e974932c2","type":"equivalent"},{"evidence":{"patch_ids":["be8272a81c28ebdf12c66d1c6ab05685"],"same_day":true,"statement_hash":"abc7e610f491a4ce631c4e62316b1f9bd718c7e9e581a2f07ba12774f5db10eb"},"rule":2,"target":"467be2f83ba0b7e841b7fca2b8c0a0af","type":"equivalent"},{"evidence":{"patch_ids":["be8272a81c28ebdf12c66d1c6ab05685"],"same_day":true,"statement_hash":"abc7e610f491a4ce631c4e62316b1f9bd718c7e9e581a2f07ba12774f5db10eb"},"rule":2,"target":"b3f796774144a4fd6c7ec84d799fce9c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["aa80c34c8"],"source_entry_id":"18.6/changes/078","source_hash":"7f9cbeb061ab70c91f9d3ab57ff63f17ff4e9749996673f6b9e0507628033ac3","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"abc7e610f491a4ce631c4e62316b1f9bd718c7e9e581a2f07ba12774f5db10eb","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"},"id":"18.6-67b85199c3f22fc0","matches":[{"id":"17.11-13269e0439b17ec9","source_entry_id":"17.11/changes/063","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"When creating directories, tolerate concurrent creation of the same directory","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/078","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"When creating directories, tolerate concurrent creation of the same directory","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["2fbb21170","36b6ed260","3a9909eda","5100bdbd3","5fa137727","c1588f92a","c8cd3d697","d44cd4674","d9bc0d96c","ef3d7b15e","f9d5a52da","fd93ee100"],"commit_groups":[["2fbb21170","3a9909eda","5100bdbd3","5fa137727","c8cd3d697","d9bc0d96c"],["36b6ed260","c1588f92a","d44cd4674","ef3d7b15e","f9d5a52da","fd93ee100"]],"commits":["c8cd3d697","f9d5a52da"],"cves":[],"db_id":"a34abdf13c3a75b01325176fd494ce54","html":"\u003cp\u003ePrevent creation of dangling object dependencies by acquiring a shared lock on any object being depended on (Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/c8cd3d697\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/f9d5a52da\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e","id":"18.6-04ef095d0d14ee39","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.","part":"changes","patch_ids":["6536cf91f14cf539ab4bd08602032b89","aca7f5e76462423a64bce89519f8b4ca"],"relations":[{"evidence":{"patch_ids":["6536cf91f14cf539ab4bd08602032b89","aca7f5e76462423a64bce89519f8b4ca"],"same_day":true,"statement_hash":"aabd3d9b6b1a0460624c086ca1a5f2223aec25bb342c2883b18a435de52ba98c"},"rule":2,"target":"744925e5c1491a9c1e34c5d45e2c5ffd","type":"equivalent"},{"evidence":{"patch_ids":["6536cf91f14cf539ab4bd08602032b89","aca7f5e76462423a64bce89519f8b4ca"],"same_day":true,"statement_hash":"aabd3d9b6b1a0460624c086ca1a5f2223aec25bb342c2883b18a435de52ba98c"},"rule":2,"target":"a9f65b357e29d3c7c477cf734deef532","type":"equivalent"},{"evidence":{"patch_ids":["6536cf91f14cf539ab4bd08602032b89","aca7f5e76462423a64bce89519f8b4ca"],"same_day":true,"statement_hash":"aabd3d9b6b1a0460624c086ca1a5f2223aec25bb342c2883b18a435de52ba98c"},"rule":2,"target":"e1119f78a9d166b823f798e0194d35f4","type":"equivalent"},{"evidence":{"patch_ids":["6536cf91f14cf539ab4bd08602032b89","aca7f5e76462423a64bce89519f8b4ca"],"same_day":true,"statement_hash":"aabd3d9b6b1a0460624c086ca1a5f2223aec25bb342c2883b18a435de52ba98c"},"rule":2,"target":"e811cff0335c3ca435753578de40cbd3","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c8cd3d697","f9d5a52da"],"source_entry_id":"18.6/changes/080","source_hash":"8504063374e840b20b0a001143714b29ff53124b6c9ee7ed57542adbbe725847","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"aabd3d9b6b1a0460624c086ca1a5f2223aec25bb342c2883b18a435de52ba98c","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"},"id":"18.6-04ef095d0d14ee39","matches":[{"id":"17.11-3ecac11b2752e81b","source_entry_id":"17.11/changes/064","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/080","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","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["2aa3c6d1f","2fc3e1b44","5d18105ca","8434c9385","ce3f19e26","d560e730e","e321faaae"],"commit_groups":[["2aa3c6d1f","2fc3e1b44","5d18105ca","8434c9385","ce3f19e26","d560e730e","e321faaae"]],"commits":["d560e730e"],"cves":[],"db_id":"37ab9407c7a4720c042c3c30e616b840","html":"\u003cp\u003eFix race condition in conflict detection for \u003ccode\u003eSERIALIZABLE\u003c/code\u003e isolation mode (Peter Geoghegan) \u003ca href=\"https://postgr.es/c/d560e730e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA conflict could be missed when examining an initially-empty btree index, allowing failure of serializability due to improperly allowing conflicting transactions to commit.\u003c/p\u003e","id":"18.6-020cfc417a109d87","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.","part":"changes","patch_ids":["76d6d81d4ce8e28654632817bbc18838"],"relations":[{"evidence":{"patch_ids":["76d6d81d4ce8e28654632817bbc18838"],"same_day":true,"statement_hash":"08b20f0b0cc877fd90cf1664195b8bfe906cd38aa76d41fb6a77cbb2ead17297"},"rule":2,"target":"03ed91689e7472f3e2b40c0668a9efe6","type":"equivalent"},{"evidence":{"patch_ids":["76d6d81d4ce8e28654632817bbc18838"],"same_day":true,"statement_hash":"08b20f0b0cc877fd90cf1664195b8bfe906cd38aa76d41fb6a77cbb2ead17297"},"rule":2,"target":"06c841c7e97c29498c3c18507b648e43","type":"equivalent"},{"evidence":{"patch_ids":["76d6d81d4ce8e28654632817bbc18838"],"same_day":true,"statement_hash":"08b20f0b0cc877fd90cf1664195b8bfe906cd38aa76d41fb6a77cbb2ead17297"},"rule":2,"target":"8911cf537e3c81e99f223106f705f385","type":"equivalent"},{"evidence":{"patch_ids":["76d6d81d4ce8e28654632817bbc18838"],"same_day":true,"statement_hash":"08b20f0b0cc877fd90cf1664195b8bfe906cd38aa76d41fb6a77cbb2ead17297"},"rule":2,"target":"a69025df57e9873eeee634c6a24b5f52","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["d560e730e"],"source_entry_id":"18.6/changes/081","source_hash":"4935166aff045404d175f6177404bfb76452f17de5687028de3dbd95695df263","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"08b20f0b0cc877fd90cf1664195b8bfe906cd38aa76d41fb6a77cbb2ead17297","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"},"id":"18.6-020cfc417a109d87","matches":[{"id":"17.11-869506b0934d2991","source_entry_id":"17.11/changes/065","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix race condition in conflict detection for SERIALIZABLE isolation mode","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/081","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix race condition in conflict detection for SERIALIZABLE isolation mode","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["159324a73","1a9b1cc18","a651b8a89","cdb9b2830","d79bf7612"],"commit_groups":[["159324a73","1a9b1cc18","a651b8a89","cdb9b2830","d79bf7612"]],"commits":["1a9b1cc18"],"cves":[],"db_id":"52661089ee9f32f8c69e8b167606de61","html":"\u003cp\u003eFix race condition in ProcSignalBarrier code (Masahiko Sawada) \u003ca href=\"https://postgr.es/c/1a9b1cc18\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis error could result in processes getting stuck, typically after reporting \u003cspan\u003e“\u003cspan\u003estill waiting for backend with PID \u003cem\u003e\u003ccode\u003ennnn\u003c/code\u003e\u003c/em\u003e to accept ProcSignalBarrier\u003c/span\u003e”\u003c/span\u003e.\u003c/p\u003e","id":"18.6-814e47a6c0f16883","identity_text":"Fix race condition in ProcSignalBarrier code (Masahiko Sawada) This error could result in processes getting stuck, typically after reporting still waiting for backend with PID nnnn to accept ProcSignalBarrier.","part":"changes","patch_ids":["06cafa4f9024a581dc7df9ac57c28b87"],"relations":[{"evidence":{"patch_ids":["06cafa4f9024a581dc7df9ac57c28b87"],"same_day":true,"statement_hash":"b132ddc69a814c78bb0d80a016bd542d646f004f2e81d83ff063e175b8923180"},"rule":2,"target":"26169dc01cad0326488602b572475378","type":"equivalent"},{"evidence":{"patch_ids":["06cafa4f9024a581dc7df9ac57c28b87"],"same_day":true,"statement_hash":"b132ddc69a814c78bb0d80a016bd542d646f004f2e81d83ff063e175b8923180"},"rule":2,"target":"57a0c23144670659c08e95957bcb21e4","type":"equivalent"},{"evidence":{"patch_ids":["06cafa4f9024a581dc7df9ac57c28b87"],"same_day":true,"statement_hash":"b132ddc69a814c78bb0d80a016bd542d646f004f2e81d83ff063e175b8923180"},"rule":2,"target":"c6eca9eca54620a981882a4c52360d79","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["1a9b1cc18"],"source_entry_id":"18.6/changes/082","source_hash":"26cdfbbb8dcb2c92610b1bef4b41a0c653334588ea11bd982d3d7e9105484329","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"b132ddc69a814c78bb0d80a016bd542d646f004f2e81d83ff063e175b8923180","text":"Fix race condition in ProcSignalBarrier code (Masahiko Sawada) § This error could result in processes getting stuck, typically after reporting “still waiting for backend with PID nnnn to accept ProcSignalBarrier”.","title":"Fix race condition in ProcSignalBarrier code"},"id":"18.6-814e47a6c0f16883","matches":[{"id":"17.11-0e94152c02ef540a","source_entry_id":"17.11/changes/066","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix race condition in ProcSignalBarrier code","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/082","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix race condition in ProcSignalBarrier code","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["12c9b8b42","4e8edf53f","563104523","65d04df60","8007d1185","84b9d6bce","ae08eb168","d489c4439","d5cc6df60","db4d12fc9","e14b4ea4a","e786fb5aa"],"commit_groups":[["12c9b8b42","4e8edf53f","84b9d6bce","db4d12fc9","e14b4ea4a","e786fb5aa"],["563104523","65d04df60","8007d1185","ae08eb168","d489c4439","d5cc6df60"]],"commits":["12c9b8b42","ae08eb168"],"cves":[],"db_id":"5b2fc7485dc383d08b3d68f5272b2a11","html":"\u003cp\u003eFix race conditions when a set of processes that belong to the same lock group exit at the same time (Vlad Lesin) \u003ca href=\"https://postgr.es/c/ae08eb168\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/12c9b8b42\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese errors could lead to PANIC aborts, with messages such as \u003cspan\u003e“\u003cspan\u003elatch already owned\u003c/span\u003e”\u003c/span\u003e. 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.\u003c/p\u003e","id":"18.6-25e5a2422482dd1c","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.","part":"changes","patch_ids":["879e5bd994847bca2264dea6ae8e7636","deebb0acfe2f0b111568661ecf5bdaeb"],"relations":[{"evidence":{"patch_ids":["879e5bd994847bca2264dea6ae8e7636","deebb0acfe2f0b111568661ecf5bdaeb"],"same_day":true,"statement_hash":"8d70122ebcc8b017ec76eed632b4e53a2f4e86497efb77268f99f3855284c592"},"rule":2,"target":"2c46dad30462775a825ad96cfb3ffbdf","type":"equivalent"},{"evidence":{"patch_ids":["879e5bd994847bca2264dea6ae8e7636","deebb0acfe2f0b111568661ecf5bdaeb"],"same_day":true,"statement_hash":"8d70122ebcc8b017ec76eed632b4e53a2f4e86497efb77268f99f3855284c592"},"rule":2,"target":"62cbccb23171427808fec1301b0ac804","type":"equivalent"},{"evidence":{"patch_ids":["879e5bd994847bca2264dea6ae8e7636","deebb0acfe2f0b111568661ecf5bdaeb"],"same_day":true,"statement_hash":"8d70122ebcc8b017ec76eed632b4e53a2f4e86497efb77268f99f3855284c592"},"rule":2,"target":"edd683109ce0095065cd3a04ab6b5136","type":"equivalent"},{"evidence":{"patch_ids":["879e5bd994847bca2264dea6ae8e7636","deebb0acfe2f0b111568661ecf5bdaeb"],"same_day":true,"statement_hash":"8d70122ebcc8b017ec76eed632b4e53a2f4e86497efb77268f99f3855284c592"},"rule":2,"target":"f2fcbfdff352b775c9b16fc62d0649b5","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["12c9b8b42","ae08eb168"],"source_entry_id":"18.6/changes/083","source_hash":"3690c0e45c50bcba3395861167636f0bbdb986d728039e0ebf6dd25961da24f4","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"8d70122ebcc8b017ec76eed632b4e53a2f4e86497efb77268f99f3855284c592","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"},"id":"18.6-25e5a2422482dd1c","matches":[{"id":"17.11-31516fe59eede273","source_entry_id":"17.11/changes/067","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix race conditions when a set of processes that belong to the same lock group exit at the same time","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/083","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix race conditions when a set of processes that belong to the same lock group exit at the same time","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["067213430","10911fde0","4d7feebfb","5174d157a","56bf5fa5d","7edec8b57","9171f77db","b01c31eef","c0d9864f5","d0fb1da21","ed62d26ca","f581fa729"],"commit_groups":[["067213430","4d7feebfb","5174d157a","9171f77db"],["10911fde0","56bf5fa5d","7edec8b57","d0fb1da21"],["b01c31eef","c0d9864f5","ed62d26ca","f581fa729"]],"commits":["4d7feebfb","d0fb1da21","f581fa729"],"cves":[],"db_id":"9fb751cb38bcd179121b328ba031747e","html":"\u003cp\u003eFix WAL logging of operations that clear bits in tables' visibility maps (Melanie Plageman, Andres Freund) \u003ca href=\"https://postgr.es/c/d0fb1da21\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/f581fa729\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/4d7feebfb\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSuch 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.\u003c/p\u003e","id":"18.6-591cce0db8214715","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.","part":"changes","patch_ids":["34adf46d69ca32061b06da3d079a7069","41df06de615aa532015928409cff3d95","892803f446e66b4cc097d23f3797a918"],"relations":[{"evidence":{"patch_ids":["34adf46d69ca32061b06da3d079a7069","41df06de615aa532015928409cff3d95","892803f446e66b4cc097d23f3797a918"],"same_day":true,"statement_hash":"06aadf1e9f9cee9405150393ea42bc91f00a02570025c6028daa277cee57c7f3"},"rule":2,"target":"4def260cbd8a4182ec017b70a81b56f5","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["4d7feebfb","d0fb1da21","f581fa729"],"source_entry_id":"18.6/changes/084","source_hash":"b95470ab8772f7064d787af7fca17722a43fdbb85ec0339e7e7f3a0b846c0f87","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"06aadf1e9f9cee9405150393ea42bc91f00a02570025c6028daa277cee57c7f3","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"},"id":"18.6-591cce0db8214715","matches":[{"id":"17.11-3f8c2715fb02eef2","source_entry_id":"17.11/changes/068","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix WAL logging of operations that clear bits in tables' visibility maps","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/084","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix WAL logging of operations that clear bits in tables' visibility maps","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["18f0de6b8","1d299d6ab","3e8a0c1b0","499d9eabb","8767a10cb","bdcea66f0","d28cdf46e","dfb96277d"],"commit_groups":[["18f0de6b8","3e8a0c1b0","499d9eabb","dfb96277d"],["1d299d6ab","8767a10cb","bdcea66f0","d28cdf46e"]],"commits":["18f0de6b8","1d299d6ab"],"cves":[],"db_id":"3173f4833a6a0aae8a455f45a5a4568e","html":"\u003cp\u003ePrevent WAL summarizer process from getting stuck at a timeline switch (Robert Haas) \u003ca href=\"https://postgr.es/c/18f0de6b8\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/1d299d6ab\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-2ef24f05b5bd445d","identity_text":"Prevent WAL summarizer process from getting stuck at a timeline switch (Robert Haas)","part":"changes","patch_ids":["508495a1aeae90a13092582478007f0c","99c5fedfb753eda3ff5558c646f420a7"],"relations":[{"evidence":{"patch_ids":["508495a1aeae90a13092582478007f0c","99c5fedfb753eda3ff5558c646f420a7"],"same_day":true,"statement_hash":"693f186e16744df775e9c612662444e181a78d71562335513f419c84cb3c35b9"},"rule":2,"target":"6c5349d1b6e45948404ea7876a48dcf9","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["18f0de6b8","1d299d6ab"],"source_entry_id":"18.6/changes/085","source_hash":"875094e4fb85ef4bbd5e3a57e55d80654eef573b8dac8966d60c792eb090e8de","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"693f186e16744df775e9c612662444e181a78d71562335513f419c84cb3c35b9","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"},"id":"18.6-2ef24f05b5bd445d","matches":[{"id":"17.11-aa32892bb54c9a4c","source_entry_id":"17.11/changes/069","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Prevent WAL summarizer process from getting stuck at a timeline switch","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/085","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Prevent WAL summarizer process from getting stuck at a timeline switch","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["16b89ff04","2a04624da","4bff3aa51","8cd687c44","a8ee70bd5","ab5334d8b","b4bd13850","d9b49e5b4","eb4e7224a"],"commit_groups":[["16b89ff04","8cd687c44","b4bd13850","eb4e7224a"],["2a04624da","4bff3aa51","a8ee70bd5","ab5334d8b"],["d9b49e5b4"]],"commits":["4bff3aa51","b4bd13850"],"cves":[],"db_id":"cfd9fb4fa936abb9c7ef216b4854fb3c","html":"\u003cp\u003eFix race with timeline selection in logical decoding during standby promotion (Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/b4bd13850\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/4bff3aa51\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eLogical decoding being performed on the standby could fail with a \u003cspan\u003e“\u003cspan\u003erequested WAL segment has already been removed\u003c/span\u003e”\u003c/span\u003e error. A repeat attempt would succeed, so there was no permanent problem but there was an availability hazard.\u003c/p\u003e","id":"18.6-c988b88dbd957c88","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.","part":"changes","patch_ids":["0baec0cbb6545813886061f478d7fe09","1bbd3b28c72161d54ff8850fb5990a90","afe572d50b5aa93a1a43ac975df96fa6"],"relations":[{"evidence":{"patch_ids":["0baec0cbb6545813886061f478d7fe09","1bbd3b28c72161d54ff8850fb5990a90","afe572d50b5aa93a1a43ac975df96fa6"],"same_day":true,"statement_hash":"b5c88f0e08517e3cf00dd9b3461ec817031530e9f8f05c2cde86c91f4ec8fc51"},"rule":2,"target":"7c127c9b86c4ff620059a798b7b8dda9","type":"equivalent"},{"evidence":{"patch_ids":["0baec0cbb6545813886061f478d7fe09","1bbd3b28c72161d54ff8850fb5990a90","afe572d50b5aa93a1a43ac975df96fa6"],"same_day":true,"statement_hash":"b5c88f0e08517e3cf00dd9b3461ec817031530e9f8f05c2cde86c91f4ec8fc51"},"rule":2,"target":"d6f8670170e47d169eec30b65187d2c4","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["4bff3aa51","b4bd13850","d9b49e5b4"],"source_entry_id":"18.6/changes/086","source_hash":"4d311a1b067d67a29744f1d9c2b459818b0b24040c0f3c40c4d5b6745dec9501","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"b5c88f0e08517e3cf00dd9b3461ec817031530e9f8f05c2cde86c91f4ec8fc51","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"},"id":"18.6-c988b88dbd957c88","matches":[{"id":"17.11-563becf7bc3e6dcf","source_entry_id":"17.11/changes/070","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix race with timeline selection in logical decoding during standby promotion","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/086","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix race with timeline selection in logical decoding during standby promotion","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["065cbfb88","b903d1792","c37b38806","c89499a79","e037a4199","e18b77153"],"commit_groups":[["065cbfb88","b903d1792","c37b38806","c89499a79","e037a4199","e18b77153"]],"commits":["b903d1792"],"cves":[],"db_id":"cd98d8763a77664800622e26ed44bfce","html":"\u003cp\u003eAvoid exposing a WAL receiver's full connection string during timeline jumps (Chao Li) \u003ca href=\"https://postgr.es/c/b903d1792\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe \u003ccode\u003epg_stat_wal_receiver\u003c/code\u003e 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.\u003c/p\u003e","id":"18.6-afb05b61d5152a3a","identity_text":"Avoid exposing a WAL receiver's full connection string during timeline jumps (Chao Li) The 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.","part":"changes","patch_ids":["625ea274df56e79c48b28c2ef1353303"],"relations":[{"evidence":{"patch_ids":["625ea274df56e79c48b28c2ef1353303"],"same_day":true,"statement_hash":"127370516df3531677f14f892409223ad12c32539de2175c8aa26416b2e1cb64"},"rule":2,"target":"25d36b6cd39f40aef2ae629b3189e49c","type":"equivalent"},{"evidence":{"patch_ids":["625ea274df56e79c48b28c2ef1353303"],"same_day":true,"statement_hash":"127370516df3531677f14f892409223ad12c32539de2175c8aa26416b2e1cb64"},"rule":2,"target":"37402bbf4de6b9a68bc1b26a7f9417b9","type":"equivalent"},{"evidence":{"patch_ids":["625ea274df56e79c48b28c2ef1353303"],"same_day":true,"statement_hash":"127370516df3531677f14f892409223ad12c32539de2175c8aa26416b2e1cb64"},"rule":2,"target":"5ea87a1c210c433da8cd395769d7ef5a","type":"equivalent"},{"evidence":{"patch_ids":["625ea274df56e79c48b28c2ef1353303"],"same_day":true,"statement_hash":"127370516df3531677f14f892409223ad12c32539de2175c8aa26416b2e1cb64"},"rule":2,"target":"e4f8b56dcd2aef047beee675ed6d7da6","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b903d1792"],"source_entry_id":"18.6/changes/087","source_hash":"42715f5b7df41b7bf319a6e29de09a5ef0a5673f61fcc5626005832f678be147","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"127370516df3531677f14f892409223ad12c32539de2175c8aa26416b2e1cb64","text":"Avoid exposing a WAL receiver's full connection string during timeline jumps (Chao Li) § The 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.","title":"Avoid exposing a WAL receiver's full connection string during timeline jumps"},"id":"18.6-afb05b61d5152a3a","matches":[{"id":"17.11-1e3e950c5c9035d8","source_entry_id":"17.11/changes/071","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Avoid exposing a WAL receiver's full connection string during timeline jumps","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/087","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Avoid exposing a WAL receiver's full connection string during timeline jumps","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["15f4e3d0c","510a05f07","59759e1a5","871d4f5b6","bf7d19be9","dc3db3a83"],"commit_groups":[["15f4e3d0c","510a05f07","59759e1a5","871d4f5b6","bf7d19be9","dc3db3a83"]],"commits":["dc3db3a83"],"cves":[],"db_id":"29b7d5b8d289c2e83357b4b3887c6ece","html":"\u003cp\u003eUse run-time checks, not just Asserts, to verify the correct number of columns in tuples received during logical replication (Varik Matevosyan) \u003ca href=\"https://postgr.es/c/dc3db3a83\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA 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.\u003c/p\u003e","id":"18.6-842cc1f1f4a2405b","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.","part":"changes","patch_ids":["8665f0efb53857b1f65d3aab55fce701"],"relations":[{"evidence":{"patch_ids":["8665f0efb53857b1f65d3aab55fce701"],"same_day":true,"statement_hash":"ccb9933f82e897841fcc7799b27c7cb46784658d50590f121d691ba4eb1ab215"},"rule":2,"target":"2bec14054822093ac2f6b8e098cf50ef","type":"equivalent"},{"evidence":{"patch_ids":["8665f0efb53857b1f65d3aab55fce701"],"same_day":true,"statement_hash":"ccb9933f82e897841fcc7799b27c7cb46784658d50590f121d691ba4eb1ab215"},"rule":2,"target":"3d36fdfc273db605a521f97942cc7c8b","type":"equivalent"},{"evidence":{"patch_ids":["8665f0efb53857b1f65d3aab55fce701"],"same_day":true,"statement_hash":"ccb9933f82e897841fcc7799b27c7cb46784658d50590f121d691ba4eb1ab215"},"rule":2,"target":"52499b2c374ab99a8520d4e208b224ca","type":"equivalent"},{"evidence":{"patch_ids":["8665f0efb53857b1f65d3aab55fce701"],"same_day":true,"statement_hash":"ccb9933f82e897841fcc7799b27c7cb46784658d50590f121d691ba4eb1ab215"},"rule":2,"target":"b984d160c74d462df46c0818a7351ddb","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["dc3db3a83"],"source_entry_id":"18.6/changes/088","source_hash":"9f31c202910443cee93755001261c06de77951acb16b3fbaa7604fd58b7fb29f","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"ccb9933f82e897841fcc7799b27c7cb46784658d50590f121d691ba4eb1ab215","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"},"id":"18.6-842cc1f1f4a2405b","matches":[{"id":"17.11-83651d53e036fd59","source_entry_id":"17.11/changes/072","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Use run-time checks, not just Asserts, to verify the correct number of columns in tuples received during logical replication","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/088","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Use run-time checks, not just Asserts, to verify the correct number of columns in tuples received during logical replication","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["14810cc0d","26d6c19d0","2a00840e8","819e5b964","a75bd485b","abb582555"],"commit_groups":[["14810cc0d","26d6c19d0","2a00840e8","819e5b964","a75bd485b","abb582555"]],"commits":["abb582555"],"cves":[],"db_id":"1ef980c1780b85528850bbdd9466fa41","html":"\u003cp\u003eClean up quoting of string parameters within constructed replication commands (Tom Lane) \u003ca href=\"https://postgr.es/c/abb582555\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eVarious 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.\u003c/p\u003e","id":"18.6-9e33f830eed35c6f","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.","part":"changes","patch_ids":["32ecc5c79c988e036daa92766ab9c826"],"relations":[{"evidence":{"patch_ids":["32ecc5c79c988e036daa92766ab9c826"],"same_day":true,"statement_hash":"247fbb71eedfaa36fb21d3377adab99beeefb9b4863ba98c464369fe5a6bc0fa"},"rule":2,"target":"492d74031b46a2dbdba89517c2392411","type":"equivalent"},{"evidence":{"patch_ids":["32ecc5c79c988e036daa92766ab9c826"],"same_day":true,"statement_hash":"247fbb71eedfaa36fb21d3377adab99beeefb9b4863ba98c464369fe5a6bc0fa"},"rule":2,"target":"54ed2b1cad03859f062c5ae13dc62693","type":"equivalent"},{"evidence":{"patch_ids":["32ecc5c79c988e036daa92766ab9c826"],"same_day":true,"statement_hash":"247fbb71eedfaa36fb21d3377adab99beeefb9b4863ba98c464369fe5a6bc0fa"},"rule":2,"target":"74c4a1b4a808ecb95dfae29020191080","type":"equivalent"},{"evidence":{"patch_ids":["32ecc5c79c988e036daa92766ab9c826"],"same_day":true,"statement_hash":"247fbb71eedfaa36fb21d3377adab99beeefb9b4863ba98c464369fe5a6bc0fa"},"rule":2,"target":"de678a747a30bf549de927b53ebbc3e7","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["abb582555"],"source_entry_id":"18.6/changes/089","source_hash":"eff14326812c72ae4f764c7f658e5ae7c0bc9c099d1151414e565b9da16e397f","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"247fbb71eedfaa36fb21d3377adab99beeefb9b4863ba98c464369fe5a6bc0fa","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"},"id":"18.6-9e33f830eed35c6f","matches":[{"id":"17.11-f6a7585b485a41e6","source_entry_id":"17.11/changes/073","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Clean up quoting of string parameters within constructed replication commands","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/089","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Clean up quoting of string parameters within constructed replication commands","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["0dbfb8520","2289e65e1","744618346","8c4519c71","acaa100f9","b563fc6bd","c2d34db0a"],"commit_groups":[["0dbfb8520","2289e65e1","744618346","8c4519c71","acaa100f9","b563fc6bd","c2d34db0a"]],"commits":["b563fc6bd"],"cves":[],"db_id":"dc4b173044afd038ad380964a01eea2b","html":"\u003cp\u003eFix logical decoding of empty prepared transactions (Masahiko Sawada) \u003ca href=\"https://postgr.es/c/b563fc6bd\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA prepared transaction that did not cause any decodable updates could result in sending \u003ccode\u003eCOMMIT/ROLLBACK PREPARED\u003c/code\u003e to the output plugin with no preceding \u003ccode\u003ePREPARE\u003c/code\u003e. For the built-in subscriber this breaks replication, and other plugins will probably not like it either.\u003c/p\u003e","id":"18.6-9c7f709d1f862457","identity_text":"Fix logical decoding of empty prepared transactions (Masahiko Sawada) A 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.","part":"changes","patch_ids":["250335f2e4b78140436eb50ee72b3519"],"relations":[{"evidence":{"patch_ids":["250335f2e4b78140436eb50ee72b3519"],"same_day":true,"statement_hash":"c36e39e101cb85a94e4121d8d84d1da47f5f96917db16c284ba7e090b292fe31"},"rule":2,"target":"84b673d7c9ccb6b9e58b7abd3b0c1465","type":"equivalent"},{"evidence":{"patch_ids":["250335f2e4b78140436eb50ee72b3519"],"same_day":true,"statement_hash":"c36e39e101cb85a94e4121d8d84d1da47f5f96917db16c284ba7e090b292fe31"},"rule":2,"target":"a16d1f65cf232982fca81254425fea0a","type":"equivalent"},{"evidence":{"patch_ids":["250335f2e4b78140436eb50ee72b3519"],"same_day":true,"statement_hash":"c36e39e101cb85a94e4121d8d84d1da47f5f96917db16c284ba7e090b292fe31"},"rule":2,"target":"bcdae249049162a8ecdfc761f53a6e97","type":"equivalent"},{"evidence":{"patch_ids":["250335f2e4b78140436eb50ee72b3519"],"same_day":true,"statement_hash":"c36e39e101cb85a94e4121d8d84d1da47f5f96917db16c284ba7e090b292fe31"},"rule":2,"target":"de72e0ac47f2ad5c62da3e86aa9fdd8f","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b563fc6bd"],"source_entry_id":"18.6/changes/090","source_hash":"65090f051bd2f142a8a76bdc7a6d58aa011df73ea204ef53bbbc69a48c3c8fc5","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"c36e39e101cb85a94e4121d8d84d1da47f5f96917db16c284ba7e090b292fe31","text":"Fix logical decoding of empty prepared transactions (Masahiko Sawada) § A 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.","title":"Fix logical decoding of empty prepared transactions"},"id":"18.6-9c7f709d1f862457","matches":[{"id":"17.11-4fcd3ca4da51d952","source_entry_id":"17.11/changes/074","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix logical decoding of empty prepared transactions","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/090","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix logical decoding of empty prepared transactions","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["22af34b98","627605713","8e684ce11","913d3b610","a1ed6a9a0","d2980067b"],"commit_groups":[["22af34b98","627605713","8e684ce11","913d3b610","a1ed6a9a0","d2980067b"]],"commits":["627605713"],"cves":[],"db_id":"7c75fcad7f434b0760cdb29e86f36c46","html":"\u003cp\u003eFix corruption of unlogged sequences after standby promotion (Fujii Masao) \u003ca href=\"https://postgr.es/c/627605713\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, if an unlogged sequence was created on the primary and replicated to a standby, accessing the sequence after promoting the standby could fail with \u003cspan\u003e“\u003cspan\u003ebad magic number in sequence\u003c/span\u003e”\u003c/span\u003e or related errors.\u003c/p\u003e","id":"18.6-a4136eca0096397b","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.","part":"changes","patch_ids":["0c00c75b81c9cf4e2c7dd727d7f47148"],"relations":[{"evidence":{"patch_ids":["0c00c75b81c9cf4e2c7dd727d7f47148"],"same_day":true,"statement_hash":"6ef22cc70bed7a3bdbb01c79c02e183283e72e3ea1060f614fc65f0d30467462"},"rule":2,"target":"04e99de2d6b9c7c2dbe0bac4e30b6b62","type":"equivalent"},{"evidence":{"patch_ids":["0c00c75b81c9cf4e2c7dd727d7f47148"],"same_day":true,"statement_hash":"6ef22cc70bed7a3bdbb01c79c02e183283e72e3ea1060f614fc65f0d30467462"},"rule":2,"target":"1ce08b2128763f685c989c7f545e1b3e","type":"equivalent"},{"evidence":{"patch_ids":["0c00c75b81c9cf4e2c7dd727d7f47148"],"same_day":true,"statement_hash":"6ef22cc70bed7a3bdbb01c79c02e183283e72e3ea1060f614fc65f0d30467462"},"rule":2,"target":"ecc31612cc8e203d9211831d84c3f264","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["627605713"],"source_entry_id":"18.6/changes/091","source_hash":"30d41fa84a95a15e9368578cde5b1e576f99f5b28764feb0fded6f9da9b5faa9","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"6ef22cc70bed7a3bdbb01c79c02e183283e72e3ea1060f614fc65f0d30467462","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"},"id":"18.6-a4136eca0096397b","matches":[{"id":"17.11-bbdd9aa8c76021bc","source_entry_id":"17.11/changes/075","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix corruption of unlogged sequences after standby promotion","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/091","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix corruption of unlogged sequences after standby promotion","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["2cf28d1b9","331016322","5dbeb69bc","5fb3c6389","8f64cc83f","b614de487","bef46aed3"],"commit_groups":[["2cf28d1b9","331016322","5dbeb69bc","5fb3c6389","8f64cc83f","b614de487","bef46aed3"]],"commits":["331016322"],"cves":[],"db_id":"1ba572e4a9f5584ecce320e293d4b258","html":"\u003cp\u003eFix cascading standby reconnect failure after archive fallback (Marco Nenciarini) \u003ca href=\"https://postgr.es/c/331016322\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA cascading standby could fail to reconnect to its upstream standby with \u003cspan\u003e“\u003cspan\u003erequested starting point ... is ahead of the WAL flush position\u003c/span\u003e”\u003c/span\u003e after falling back to archive recovery.\u003c/p\u003e","id":"18.6-e75bd84b8c02b997","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.","part":"changes","patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"relations":[{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true},"rule":2,"target":"027ccc17f71deb2b38e14fc8cc82dccd","type":"related"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true},"rule":2,"target":"1b34d3e2b18d75096fd2914d3673446c","type":"related"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true},"rule":2,"target":"70897dba323af27792543b2311799668","type":"related"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true,"statement_hash":"fb1d8ff1de50924ae1113199938a0ff6d45296b275bab29a749f5176ddbc64ad"},"rule":2,"target":"771fa954f9b22168a0764dc12074dadb","type":"equivalent"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true,"statement_hash":"fb1d8ff1de50924ae1113199938a0ff6d45296b275bab29a749f5176ddbc64ad"},"rule":2,"target":"b17ef22f538327cabf0726e1b3f902cc","type":"equivalent"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true},"rule":2,"target":"bf82a2510c4dfe4309435e9bce0ab3a4","type":"related"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true,"statement_hash":"fb1d8ff1de50924ae1113199938a0ff6d45296b275bab29a749f5176ddbc64ad"},"rule":2,"target":"bfa74492dd2c8ed5f4b0a4321cb63c85","type":"equivalent"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true},"rule":2,"target":"bfa88fa3d381bbc9b7ee7a8614ea363c","type":"related"},{"evidence":{"ambiguous_patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"patch_ids":["8d6dc29f16ca43220ac734ee400f5ee9"],"same_day":true,"statement_hash":"fb1d8ff1de50924ae1113199938a0ff6d45296b275bab29a749f5176ddbc64ad"},"rule":2,"target":"ea24770278021c00f25a8b13bceb2a2c","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["331016322"],"source_entry_id":"18.6/changes/092","source_hash":"5a51be4cd8f245f23d1e5e10bb08538693a17619e15c5a49adfcc92b3d850c4e","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"fb1d8ff1de50924ae1113199938a0ff6d45296b275bab29a749f5176ddbc64ad","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"},"id":"18.6-e75bd84b8c02b997","matches":[{"id":"17.11-8291f394c20dacdc","source_entry_id":"17.11/changes/076","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix cascading standby reconnect failure after archive fallback","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/092","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix cascading standby reconnect failure after archive fallback","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["4a375527a","97b5c5aaa","bec61f593"],"commit_groups":[["4a375527a","97b5c5aaa","bec61f593"]],"commits":["97b5c5aaa"],"cves":[],"db_id":"c7c89eea0ca114afbedbf0cfbae711f9","html":"\u003cp\u003eDo not try to clear \u003ccode\u003epg_database\u003c/code\u003e.\u003ccode\u003edathasloginevt\u003c/code\u003e locally on a standby server (Ayush Tiwari) \u003ca href=\"https://postgr.es/c/97b5c5aaa\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eEvent 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.\u003c/p\u003e","id":"18.6-d53aeb4078876f26","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.","part":"changes","patch_ids":["4ce4f54c8bf735435a0cd83d5e3fd94c"],"relations":[{"evidence":{"patch_ids":["4ce4f54c8bf735435a0cd83d5e3fd94c"],"same_day":true,"statement_hash":"ccdeea440cff75c363fd3daa73d137e4deed890abd48b629fa6387377abac755"},"rule":2,"target":"2652e45990dd9ead74f7cb1a60cd06ae","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["97b5c5aaa"],"source_entry_id":"18.6/changes/094","source_hash":"7dedca87b69ef21715aa2679b45381940636ac8d0716019fb33eca7ea306fdfb","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"ccdeea440cff75c363fd3daa73d137e4deed890abd48b629fa6387377abac755","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"},"id":"18.6-d53aeb4078876f26","matches":[{"id":"17.11-4ea3a29628f7f415","source_entry_id":"17.11/changes/077","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Do not try to clear pg_database.dathasloginevt locally on a standby server","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/094","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Do not try to clear pg_database.dathasloginevt locally on a standby server","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["08458bcae","bdae2c20e","ea834d747"],"commit_groups":[["08458bcae","bdae2c20e","ea834d747"]],"commits":["08458bcae"],"cves":[],"db_id":"3dd18331742596637d053910b38a1f16","html":"\u003cp\u003eAvoid race condition while dropping obsolete replication slots (Xuneng Zhou) \u003ca href=\"https://postgr.es/c/08458bcae\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAn incorrect unlock and log message could occur if another session immediately re-used the dropped slot's shared-memory entry.\u003c/p\u003e","id":"18.6-da8598a35476aae4","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.","part":"changes","patch_ids":["c73474c335bb9d2b86b6bc7565e6f72b"],"relations":[{"evidence":{"patch_ids":["c73474c335bb9d2b86b6bc7565e6f72b"],"same_day":true,"statement_hash":"14c10b585f72cec70dc64da094d3d2d2e80cef7b71ab92442a40f2f70c386a62"},"rule":2,"target":"2724a08367b4dc82b3441236c9f9b14b","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["08458bcae"],"source_entry_id":"18.6/changes/095","source_hash":"cf6d11cd5580220ca35ddb16dd3a29615a1ef8c87cd71658da7e80f82c77be63","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"14c10b585f72cec70dc64da094d3d2d2e80cef7b71ab92442a40f2f70c386a62","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"},"id":"18.6-da8598a35476aae4","matches":[{"id":"17.11-5aeb772ab7b96772","source_entry_id":"17.11/changes/078","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Avoid race condition while dropping obsolete replication slots","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/095","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Avoid race condition while dropping obsolete replication slots","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["080d61f07","51e79222c","968c50845","a4eb59d40","f2081a780","f833c9207"],"commit_groups":[["080d61f07","51e79222c","968c50845","a4eb59d40","f2081a780","f833c9207"]],"commits":["f833c9207"],"cves":[],"db_id":"e7a4717de56195de8e84ae36133e6f25","html":"\u003cp\u003eAvoid race condition while dropping ephemeral replication slots (Zhijie Hou) \u003ca href=\"https://postgr.es/c/f833c9207\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e","id":"18.6-63934e389520e7b8","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.","part":"changes","patch_ids":["a917b168697862cb05827b9e9d804879"],"relations":[{"evidence":{"patch_ids":["a917b168697862cb05827b9e9d804879"],"same_day":true,"statement_hash":"87055d6044521ae3f6b6a74d5c840e75e79be3ee687ddbb92cb366dcb1601282"},"rule":2,"target":"56d06487f4f5f34eaa3c2bcb9a9adcec","type":"equivalent"},{"evidence":{"patch_ids":["a917b168697862cb05827b9e9d804879"],"same_day":true,"statement_hash":"87055d6044521ae3f6b6a74d5c840e75e79be3ee687ddbb92cb366dcb1601282"},"rule":2,"target":"68414efdd4fd28ffb448691fcc350390","type":"equivalent"},{"evidence":{"patch_ids":["a917b168697862cb05827b9e9d804879"],"same_day":true,"statement_hash":"87055d6044521ae3f6b6a74d5c840e75e79be3ee687ddbb92cb366dcb1601282"},"rule":2,"target":"acb52269a9ab57fd523cb58a71e121ec","type":"equivalent"},{"evidence":{"patch_ids":["a917b168697862cb05827b9e9d804879"],"same_day":true,"statement_hash":"87055d6044521ae3f6b6a74d5c840e75e79be3ee687ddbb92cb366dcb1601282"},"rule":2,"target":"f11ac7346f20210841ca22799f957bad","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["f833c9207"],"source_entry_id":"18.6/changes/096","source_hash":"27fbb2571967acc614030a8a722348f6483bb4a253dea242ebe2db84806d008d","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"87055d6044521ae3f6b6a74d5c840e75e79be3ee687ddbb92cb366dcb1601282","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"},"id":"18.6-63934e389520e7b8","matches":[{"id":"17.11-1bc3f286c6ac2176","source_entry_id":"17.11/changes/079","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Avoid race condition while dropping ephemeral replication slots","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/096","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Avoid race condition while dropping ephemeral replication slots","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["422e54e30","b5f7e7569","d140237da","d9cd9b4d7","e3c4e3746","f2acab534"],"commit_groups":[["422e54e30","b5f7e7569","d140237da","d9cd9b4d7","e3c4e3746","f2acab534"]],"commits":["d9cd9b4d7"],"cves":[],"db_id":"9c326b65f30e4f95b13ee3d7fb3dd796","html":"\u003cp\u003eFix stale progress reports during logical replication table synchronization (Shinya Kato) \u003ca href=\"https://postgr.es/c/d9cd9b4d7\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, the \u003ccode\u003epg_stat_progress_copy\u003c/code\u003e view in the subscriber would continue to show the initial \u003ccode\u003eCOPY\u003c/code\u003e operation as active even after the data copy had finished. The stale entry remained visible until synchronization caught up with the publisher.\u003c/p\u003e","id":"18.6-caa7677e59388ffc","identity_text":"Fix stale progress reports during logical replication table synchronization (Shinya Kato) Previously, 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.","part":"changes","patch_ids":["1ad4f3b3d40c3980d4aa9a5a98057761"],"relations":[{"evidence":{"patch_ids":["1ad4f3b3d40c3980d4aa9a5a98057761"],"same_day":true,"statement_hash":"fed32130a83680b56d3331359c775298c978288d1fa6daf4eb73e2b9d60903bb"},"rule":2,"target":"14ad13206c7199257b4a83f16133fde4","type":"equivalent"},{"evidence":{"patch_ids":["1ad4f3b3d40c3980d4aa9a5a98057761"],"same_day":true,"statement_hash":"fed32130a83680b56d3331359c775298c978288d1fa6daf4eb73e2b9d60903bb"},"rule":2,"target":"4b9039b2e6e3f4907e354f148b3975e1","type":"equivalent"},{"evidence":{"patch_ids":["1ad4f3b3d40c3980d4aa9a5a98057761"],"same_day":true,"statement_hash":"fed32130a83680b56d3331359c775298c978288d1fa6daf4eb73e2b9d60903bb"},"rule":2,"target":"63a709580f948ad9f6c1df43e037400c","type":"equivalent"},{"evidence":{"patch_ids":["1ad4f3b3d40c3980d4aa9a5a98057761"],"same_day":true,"statement_hash":"fed32130a83680b56d3331359c775298c978288d1fa6daf4eb73e2b9d60903bb"},"rule":2,"target":"ff38e10dde566b08847e2c27088d3f57","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["d9cd9b4d7"],"source_entry_id":"18.6/changes/097","source_hash":"03488d1c1e96c8bc1674bd25ac9aedc68cabdc4f4873439a3e15274c3791eff1","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"fed32130a83680b56d3331359c775298c978288d1fa6daf4eb73e2b9d60903bb","text":"Fix stale progress reports during logical replication table synchronization (Shinya Kato) § Previously, 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.","title":"Fix stale progress reports during logical replication table synchronization"},"id":"18.6-caa7677e59388ffc","matches":[{"id":"17.11-502303232ec37c57","source_entry_id":"17.11/changes/080","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix stale progress reports during logical replication table synchronization","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/097","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix stale progress reports during logical replication table synchronization","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["55f0a13e9","7cbd80340","a240e8cd2","a8fb98b7b","b70000837","cf7530cf7","e2ad214dd","e2ea6bfed","e7564ee8c","fffa4d870"],"commit_groups":[["55f0a13e9","7cbd80340","b70000837","cf7530cf7","e2ea6bfed","e7564ee8c"],["a240e8cd2","a8fb98b7b","e2ad214dd","fffa4d870"]],"commits":["e2ad214dd","e7564ee8c"],"cves":[],"db_id":"ce88301108e6a4004079448bd7660e3f","html":"\u003cp\u003eClear base backup progress on backup failure (Chao Li) \u003ca href=\"https://postgr.es/c/e7564ee8c\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/e2ad214dd\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously the \u003ccode\u003epg_stat_progress_basebackup\u003c/code\u003e view would continue to show a stale progress entry after a failure, until the replication client disconnected. \u003cspan\u003epg_basebackup\u003c/span\u003e normally disconnects immediately, but other clients might not.\u003c/p\u003e","id":"18.6-0214ccb96b1cfbea","identity_text":"Clear base backup progress on backup failure (Chao Li) Previously 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.","part":"changes","patch_ids":["69213b2b66c0b41b4a5afe802955c74c","9c5e22740fb95d470204bdcf6078ebd3"],"relations":[{"evidence":{"patch_ids":["69213b2b66c0b41b4a5afe802955c74c","9c5e22740fb95d470204bdcf6078ebd3"],"same_day":true,"statement_hash":"90edb0e18fbbfc1f67179ab9512bae516940a5bc615766f8dbd30ebb529a5d9a"},"rule":2,"target":"03d34f5720102ae73e4faeecbb40be16","type":"equivalent"},{"evidence":{"patch_ids":["69213b2b66c0b41b4a5afe802955c74c","9c5e22740fb95d470204bdcf6078ebd3"],"same_day":true,"statement_hash":"90edb0e18fbbfc1f67179ab9512bae516940a5bc615766f8dbd30ebb529a5d9a"},"rule":2,"target":"0ad803b8fa0affc695436e1ce334504b","type":"equivalent"},{"evidence":{"patch_ids":["69213b2b66c0b41b4a5afe802955c74c","9c5e22740fb95d470204bdcf6078ebd3"],"same_day":true,"statement_hash":"90edb0e18fbbfc1f67179ab9512bae516940a5bc615766f8dbd30ebb529a5d9a"},"rule":2,"target":"30cd797665cc3e84a05904b8156ea936","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["e2ad214dd","e7564ee8c"],"source_entry_id":"18.6/changes/098","source_hash":"58ee046a19ef133a53f117bbbc4f8f88e8f077f30cdd7b74543c2a474af22609","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"90edb0e18fbbfc1f67179ab9512bae516940a5bc615766f8dbd30ebb529a5d9a","text":"Clear base backup progress on backup failure (Chao Li) § § Previously 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.","title":"Clear base backup progress on backup failure"},"id":"18.6-0214ccb96b1cfbea","matches":[{"id":"17.11-b156d299eafbb07e","source_entry_id":"17.11/changes/081","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Clear base backup progress on backup failure","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/098","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Clear base backup progress on backup failure","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["1e9e62193","2e0c61aed","39e649d44","5cc59834b","75aca8b93","7c457ea15","850b9218c","8a4f389dd","9e4771825","afb076b29","bf4616b59","e34b1ff5d","fe464e9e6"],"commit_groups":[["1e9e62193","2e0c61aed","5cc59834b","850b9218c","bf4616b59"],["39e649d44","75aca8b93","7c457ea15","8a4f389dd"],["9e4771825","afb076b29","e34b1ff5d","fe464e9e6"]],"commits":["5cc59834b","8a4f389dd","fe464e9e6"],"cves":[],"db_id":"f649a3b052bcad5187adc505673c75c1","html":"\u003cp\u003eFix possible PANIC due to concurrent drop of pgstats entries when \u003ccode\u003etrack_functions\u003c/code\u003e is enabled (Sami Imseih, Michael Paquier) \u003ca href=\"https://postgr.es/c/5cc59834b\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/8a4f389dd\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/fe464e9e6\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-27f3fc55e6505e3a","identity_text":"Fix possible PANIC due to concurrent drop of pgstats entries when track_functions is enabled (Sami Imseih, Michael Paquier)","part":"changes","patch_ids":["11e208c239471e2b9f1cfe6b471d2327","96d4ce4b2cc9952529faad2e7c262657","cd852a41bee86e5a2913a12ac4e43095"],"relations":[{"evidence":{"patch_ids":["11e208c239471e2b9f1cfe6b471d2327","96d4ce4b2cc9952529faad2e7c262657","cd852a41bee86e5a2913a12ac4e43095"],"same_day":true,"statement_hash":"bbf35131dcae001445dbbd0547e54ebeecf3054f9d675a0a951aa59f955018fa"},"rule":2,"target":"4f36f67c7466f2760e401e0630f15a42","type":"equivalent"},{"evidence":{"patch_ids":["11e208c239471e2b9f1cfe6b471d2327","96d4ce4b2cc9952529faad2e7c262657","cd852a41bee86e5a2913a12ac4e43095"],"same_day":true,"statement_hash":"bbf35131dcae001445dbbd0547e54ebeecf3054f9d675a0a951aa59f955018fa"},"rule":2,"target":"7dab11d8d1bb42201bf7693ca895d4ec","type":"equivalent"},{"evidence":{"patch_ids":["11e208c239471e2b9f1cfe6b471d2327","96d4ce4b2cc9952529faad2e7c262657","cd852a41bee86e5a2913a12ac4e43095"],"same_day":true,"statement_hash":"bbf35131dcae001445dbbd0547e54ebeecf3054f9d675a0a951aa59f955018fa"},"rule":2,"target":"becaa982198f0463b739ba15734dbc39","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["5cc59834b","8a4f389dd","fe464e9e6"],"source_entry_id":"18.6/changes/099","source_hash":"81496c00219608c698e6590b77e36c676c02aeee8fe1b3a36263191f5bae09e6","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"bbf35131dcae001445dbbd0547e54ebeecf3054f9d675a0a951aa59f955018fa","text":"Fix possible PANIC due to concurrent drop of pgstats entries when track_functions is enabled (Sami Imseih, Michael Paquier) § § §","title":"Fix possible PANIC due to concurrent drop of pgstats entries when track_functions is enabled"},"id":"18.6-27f3fc55e6505e3a","matches":[{"id":"17.11-ca1b3346f4ca0f86","source_entry_id":"17.11/changes/082","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix possible PANIC due to concurrent drop of pgstats entries when track_functions is enabled","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/099","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix possible PANIC due to concurrent drop of pgstats entries when track_functions is enabled","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["10e20e59e","2fd8d45ec","4069df21b","636bcd6a5","89fc6a7c1","fc9283b21"],"commit_groups":[["10e20e59e","2fd8d45ec","4069df21b","636bcd6a5","89fc6a7c1","fc9283b21"]],"commits":["2fd8d45ec"],"cves":[],"db_id":"69bb916ea3e2500fcf1ca6568c60960f","html":"\u003cp\u003eClean up broken local pgstats entry after failing to obtain space for the corresponding shared hashtable entry (Niall Newman) \u003ca href=\"https://postgr.es/c/2fd8d45ec\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFailure to do this led to a null-pointer dereference the next time the local entry was used.\u003c/p\u003e","id":"18.6-8e68cf04f8d3d622","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.","part":"changes","patch_ids":["073249ed6bcae15bb6d4063aa8558bab"],"relations":[{"evidence":{"patch_ids":["073249ed6bcae15bb6d4063aa8558bab"],"same_day":true,"statement_hash":"c60eb3598315d881be3eccb1a6430b61a597e0457159bd9304d33bd0c753b70e"},"rule":2,"target":"1afc7388a3b74ce2c49cb081c26f6f41","type":"equivalent"},{"evidence":{"patch_ids":["073249ed6bcae15bb6d4063aa8558bab"],"same_day":true,"statement_hash":"c60eb3598315d881be3eccb1a6430b61a597e0457159bd9304d33bd0c753b70e"},"rule":2,"target":"65cb52740b6d4b79d67968be77af89f3","type":"equivalent"},{"evidence":{"patch_ids":["073249ed6bcae15bb6d4063aa8558bab"],"same_day":true,"statement_hash":"c60eb3598315d881be3eccb1a6430b61a597e0457159bd9304d33bd0c753b70e"},"rule":2,"target":"b6f5540e817eacbe3e2ce2803c428998","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["2fd8d45ec"],"source_entry_id":"18.6/changes/100","source_hash":"ae21d24d93211a6397408fa1c2d59a596a32104ae42e7db4a2a7436bcdd24769","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"c60eb3598315d881be3eccb1a6430b61a597e0457159bd9304d33bd0c753b70e","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"},"id":"18.6-8e68cf04f8d3d622","matches":[{"id":"17.11-2a6d1da6de790ba0","source_entry_id":"17.11/changes/083","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Clean up broken local pgstats entry after failing to obtain space for the corresponding shared hashtable entry","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/100","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Clean up broken local pgstats entry after failing to obtain space for the corresponding shared hashtable entry","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["3854f4afc","4015abe14","9b2a6ccc4","d424d06ed","e430ecc59","e520ad34b"],"commit_groups":[["3854f4afc","4015abe14","9b2a6ccc4","d424d06ed","e430ecc59","e520ad34b"]],"commits":["e430ecc59"],"cves":[],"db_id":"51220e5b8d23efc0faab7627c0b277a9","html":"\u003cp\u003eIn \u003cspan\u003ePL/Perl\u003c/span\u003e, avoid NULL pointer dereference crash when working with an invalid \u003ccode\u003ePostgreSQL::InServer::ARRAY\u003c/code\u003e object (Xing Guo) \u003ca href=\"https://postgr.es/c/e430ecc59\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-2efca855d8fe72b9","identity_text":"In PL/Perl, avoid NULL pointer dereference crash when working with an invalid PostgreSQL::InServer::ARRAY object (Xing Guo)","part":"changes","patch_ids":["9f7af30504d68be229b578f1fb298bab"],"relations":[{"evidence":{"patch_ids":["9f7af30504d68be229b578f1fb298bab"],"same_day":true,"statement_hash":"816cdb7f810c7c6b8a9ff3718e2fd5085f754c66d29804028a804f438de99013"},"rule":2,"target":"36209251c760c8062b73654dc7225440","type":"equivalent"},{"evidence":{"patch_ids":["9f7af30504d68be229b578f1fb298bab"],"same_day":true,"statement_hash":"816cdb7f810c7c6b8a9ff3718e2fd5085f754c66d29804028a804f438de99013"},"rule":2,"target":"e8af57b95d1fb94000fded1a07842242","type":"equivalent"},{"evidence":{"patch_ids":["9f7af30504d68be229b578f1fb298bab"],"same_day":true,"statement_hash":"816cdb7f810c7c6b8a9ff3718e2fd5085f754c66d29804028a804f438de99013"},"rule":2,"target":"eeee2b7678fc0f11a7913ff09b05a182","type":"equivalent"},{"evidence":{"patch_ids":["9f7af30504d68be229b578f1fb298bab"],"same_day":true,"statement_hash":"816cdb7f810c7c6b8a9ff3718e2fd5085f754c66d29804028a804f438de99013"},"rule":2,"target":"f143e0fa28a7dd57f718edca2aebc331","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["e430ecc59"],"source_entry_id":"18.6/changes/102","source_hash":"10bb4cf365e34eae6176aeba278f76d048007603b3a16c65aa6f0fa3bcc7f7cb","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"816cdb7f810c7c6b8a9ff3718e2fd5085f754c66d29804028a804f438de99013","text":"In PL/Perl, avoid NULL pointer dereference crash when working with an invalid PostgreSQL::InServer::ARRAY object (Xing Guo) §","title":"In PL/Perl, avoid NULL pointer dereference crash when working with an invalid PostgreSQL::InServer::ARRAY object"},"id":"18.6-2efca855d8fe72b9","matches":[{"id":"17.11-df7c413d42462d43","source_entry_id":"17.11/changes/084","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/102","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","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["0b7719f74","12bff46ff","309dc4526","3dc59c173","53482fcb9","8612f0b7c","e92f23bde"],"commit_groups":[["0b7719f74","12bff46ff","3dc59c173","53482fcb9","8612f0b7c","e92f23bde"],["309dc4526"]],"commits":["53482fcb9"],"cves":[],"db_id":"c6334af88dcf8bb00a0c24becb0804c2","html":"\u003cp\u003eIn \u003cspan\u003ePL/Python\u003c/span\u003e, properly check for errors when working with sequence and mapping objects (Richard Guo) \u003ca href=\"https://postgr.es/c/53482fcb9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, a broken object or an unhandled exception could result in a NULL pointer dereference crash.\u003c/p\u003e","id":"18.6-728c054c41aaf74d","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.","part":"changes","patch_ids":["82aeda458da615307371e8d49ed0abdd","a96949fcfb8c6bac8cc1705ad8aa548e"],"relations":[{"evidence":{"patch_ids":["82aeda458da615307371e8d49ed0abdd","a96949fcfb8c6bac8cc1705ad8aa548e"],"same_day":true,"statement_hash":"33d469b3040d6c202f91bb0448f11a09e5ddae64c76bb00e48ee5634543c64ee"},"rule":2,"target":"1bcdb1bad2833f07d4dbdd7f3fd25692","type":"equivalent"},{"evidence":{"patch_ids":["82aeda458da615307371e8d49ed0abdd","a96949fcfb8c6bac8cc1705ad8aa548e"],"same_day":true,"statement_hash":"33d469b3040d6c202f91bb0448f11a09e5ddae64c76bb00e48ee5634543c64ee"},"rule":2,"target":"5ee9ccfc012c4ede5db692562772a752","type":"equivalent"},{"evidence":{"patch_ids":["82aeda458da615307371e8d49ed0abdd","a96949fcfb8c6bac8cc1705ad8aa548e"],"same_day":true,"statement_hash":"33d469b3040d6c202f91bb0448f11a09e5ddae64c76bb00e48ee5634543c64ee"},"rule":2,"target":"7c536b903c2b846285e39de4051f4dda","type":"equivalent"},{"evidence":{"patch_ids":["82aeda458da615307371e8d49ed0abdd","a96949fcfb8c6bac8cc1705ad8aa548e"],"same_day":true,"statement_hash":"33d469b3040d6c202f91bb0448f11a09e5ddae64c76bb00e48ee5634543c64ee"},"rule":2,"target":"c7d8f5074aecff2a6209080fb7907c5d","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["309dc4526","53482fcb9"],"source_entry_id":"18.6/changes/103","source_hash":"c779f97703863e26c6b6c406b53da7e717ecf8ef2e2938a212dac1d15ff7c366","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"33d469b3040d6c202f91bb0448f11a09e5ddae64c76bb00e48ee5634543c64ee","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"},"id":"18.6-728c054c41aaf74d","matches":[{"id":"17.11-bf867cbb1ebe32c7","source_entry_id":"17.11/changes/085","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"In PL/Python, properly check for errors when working with sequence and mapping objects","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/103","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"In PL/Python, properly check for errors when working with sequence and mapping objects","version":"18.6"},{"entry":{"category":"improvement","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"],"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"]],"commits":["2167302b7","27761c015","87c3a79ea","bb0a54518"],"cves":[],"db_id":"9168ca39fb7c001030f5bfbd2405a57c","html":"\u003cp\u003eIn \u003cspan\u003elibpq\u003c/span\u003e, always drain all pending bytes from the SSL or GSS decryption buffer during \u003ccode\u003epqReadData()\u003c/code\u003e (Jacob Champion) \u003ca href=\"https://postgr.es/c/2167302b7\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/bb0a54518\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/27761c015\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/87c3a79ea\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis avoids edge cases where \u003cspan\u003elibpq\u003c/span\u003e or its calling application waits for more data to arrive on the socket, but actually all the data has already arrived.\u003c/p\u003e","id":"18.6-99e20888b0a13dd7","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.","part":"changes","patch_ids":["0b824057774a76b143d700730eb3e762","cc43f5c943c90e1a9e72f73b95bcd867","dd46de527b9a0334591039f236b5d00d","fdc82cd35935c0be303512dba39e65fe"],"relations":[{"evidence":{"patch_ids":["0b824057774a76b143d700730eb3e762","cc43f5c943c90e1a9e72f73b95bcd867","dd46de527b9a0334591039f236b5d00d","fdc82cd35935c0be303512dba39e65fe"],"same_day":true,"statement_hash":"8034e64e929755fda7f40131432f08c549be661e2525d6f7be6b5192313374be"},"rule":2,"target":"06f569df58220f97a2f065dcabd4567f","type":"equivalent"},{"evidence":{"patch_ids":["0b824057774a76b143d700730eb3e762","cc43f5c943c90e1a9e72f73b95bcd867","dd46de527b9a0334591039f236b5d00d","fdc82cd35935c0be303512dba39e65fe"],"same_day":true,"statement_hash":"8034e64e929755fda7f40131432f08c549be661e2525d6f7be6b5192313374be"},"rule":2,"target":"964e3e4ad6311992f04c2399fc930719","type":"equivalent"},{"evidence":{"patch_ids":["0b824057774a76b143d700730eb3e762","cc43f5c943c90e1a9e72f73b95bcd867","dd46de527b9a0334591039f236b5d00d","fdc82cd35935c0be303512dba39e65fe"],"same_day":true,"statement_hash":"8034e64e929755fda7f40131432f08c549be661e2525d6f7be6b5192313374be"},"rule":2,"target":"c77eeb650517090fade53e3cf3d24d00","type":"equivalent"},{"evidence":{"patch_ids":["0b824057774a76b143d700730eb3e762","cc43f5c943c90e1a9e72f73b95bcd867","dd46de527b9a0334591039f236b5d00d","fdc82cd35935c0be303512dba39e65fe"],"same_day":true,"statement_hash":"8034e64e929755fda7f40131432f08c549be661e2525d6f7be6b5192313374be"},"rule":2,"target":"f60154c0b7e3d0ae2ae39034edcdc2c1","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["2167302b7","27761c015","87c3a79ea","bb0a54518"],"source_entry_id":"18.6/changes/104","source_hash":"ae71f0d838a63f4577ab24237e763fb0ed2276579a52d8ba784b464f53b9dce1","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"8034e64e929755fda7f40131432f08c549be661e2525d6f7be6b5192313374be","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()"},"id":"18.6-99e20888b0a13dd7","matches":[{"id":"17.11-ece298bedf647a6a","source_entry_id":"17.11/changes/086","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()","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/104","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()","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["0f63b74a4","1b79c8d1a","8d516d2b9","b1ab4bc52","e0511883c","e4183c667"],"commit_groups":[["0f63b74a4","1b79c8d1a","8d516d2b9","b1ab4bc52","e0511883c","e4183c667"]],"commits":["b1ab4bc52"],"cves":[],"db_id":"c1e7d9148740f6776370a4a75311e436","html":"\u003cp\u003eAllow \u003cspan\u003elibpq\u003c/span\u003e to accept ParameterDescription messages exceeding 30000 bytes (Ning Sun) \u003ca href=\"https://postgr.es/c/b1ab4bc52\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, this message type was not among those that \u003cspan\u003elibpq\u003c/span\u003e'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.\u003c/p\u003e","id":"18.6-524638e22a952ee0","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.","part":"changes","patch_ids":["b6b26c4c8b27c2138732ea0f070c591b"],"relations":[{"evidence":{"patch_ids":["b6b26c4c8b27c2138732ea0f070c591b"],"same_day":true,"statement_hash":"2bf8dba03893ccac611f0c0a15dfeaa8cb7ed7f18e2fbb58d26e630ffd77a548"},"rule":2,"target":"5ebbe0622604b80c5219c1c82f7d9aca","type":"equivalent"},{"evidence":{"patch_ids":["b6b26c4c8b27c2138732ea0f070c591b"],"same_day":true,"statement_hash":"2bf8dba03893ccac611f0c0a15dfeaa8cb7ed7f18e2fbb58d26e630ffd77a548"},"rule":2,"target":"7b36888afdccf5778f4b3d9b3f4d4b19","type":"equivalent"},{"evidence":{"patch_ids":["b6b26c4c8b27c2138732ea0f070c591b"],"same_day":true,"statement_hash":"2bf8dba03893ccac611f0c0a15dfeaa8cb7ed7f18e2fbb58d26e630ffd77a548"},"rule":2,"target":"96f87cdaa195bfc8af2e374fe5cd785d","type":"equivalent"},{"evidence":{"patch_ids":["b6b26c4c8b27c2138732ea0f070c591b"],"same_day":true,"statement_hash":"2bf8dba03893ccac611f0c0a15dfeaa8cb7ed7f18e2fbb58d26e630ffd77a548"},"rule":2,"target":"97c44cf1d7b9b31d86691416921a75e4","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["b1ab4bc52"],"source_entry_id":"18.6/changes/107","source_hash":"9743df9bec312c0248fa3bbdd40827d03f169c1af78432f1e9df9d53f0a077ae","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"2bf8dba03893ccac611f0c0a15dfeaa8cb7ed7f18e2fbb58d26e630ffd77a548","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"},"id":"18.6-524638e22a952ee0","matches":[{"id":"17.11-a3c4e49ff3e57eff","source_entry_id":"17.11/changes/087","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Allow libpq to accept ParameterDescription messages exceeding 30000 bytes","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/107","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Allow libpq to accept ParameterDescription messages exceeding 30000 bytes","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["081434b0f","4484165b0","4d4b73cfd","9e8fd9f7a","bfeddcf09","fe8c0a762"],"commit_groups":[["081434b0f","4484165b0","4d4b73cfd","9e8fd9f7a","bfeddcf09","fe8c0a762"]],"commits":["081434b0f"],"cves":[],"db_id":"aa20c63216e98c98f035fa86491b5b30","html":"\u003cp\u003eReject multiple descriptor header items in \u003cspan\u003eecpg\u003c/span\u003e's \u003ccode\u003eGET/SET DESCRIPTOR\u003c/code\u003e statements (Masashi Kamura) \u003ca href=\"https://postgr.es/c/081434b0f\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously the grammar allowed this syntax, but broken C code was generated. Adjust the grammar and the documentation to allow only one header item.\u003c/p\u003e","id":"18.6-f7ec4316771ce1eb","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.","part":"changes","patch_ids":["4f4dddcf40354c994e2b6668a43af20d"],"relations":[{"evidence":{"patch_ids":["4f4dddcf40354c994e2b6668a43af20d"],"same_day":true,"statement_hash":"e3bda298ded00b77261ba1c76b32c15895630f65da4a428ed88a0e425a4414cb"},"rule":2,"target":"2d1814d3627bd7de23f302bac9690b77","type":"equivalent"},{"evidence":{"patch_ids":["4f4dddcf40354c994e2b6668a43af20d"],"same_day":true,"statement_hash":"e3bda298ded00b77261ba1c76b32c15895630f65da4a428ed88a0e425a4414cb"},"rule":2,"target":"d5ef1996d66a6c71b921d8881446c413","type":"equivalent"},{"evidence":{"patch_ids":["4f4dddcf40354c994e2b6668a43af20d"],"same_day":true,"statement_hash":"e3bda298ded00b77261ba1c76b32c15895630f65da4a428ed88a0e425a4414cb"},"rule":2,"target":"e7657a963bd66274d46d2b5a9e11a18a","type":"equivalent"},{"evidence":{"patch_ids":["4f4dddcf40354c994e2b6668a43af20d"],"same_day":true,"statement_hash":"e3bda298ded00b77261ba1c76b32c15895630f65da4a428ed88a0e425a4414cb"},"rule":2,"target":"f619d880f7a5f55846623a2af12abad1","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["081434b0f"],"source_entry_id":"18.6/changes/109","source_hash":"8fd091c57d1ece6fac2c371b58e204e819ec5818de477c5e0736e1b023f750f2","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"e3bda298ded00b77261ba1c76b32c15895630f65da4a428ed88a0e425a4414cb","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"},"id":"18.6-f7ec4316771ce1eb","matches":[{"id":"17.11-4edba097ad3499b7","source_entry_id":"17.11/changes/088","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Reject multiple descriptor header items in ecpg's GET/SET DESCRIPTOR statements","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/109","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Reject multiple descriptor header items in ecpg's GET/SET DESCRIPTOR statements","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["022ba5c61","07a6c262b","1edbe6695","3d0d6741d","a4ca91ea1","efd885d05"],"commit_groups":[["022ba5c61","07a6c262b","1edbe6695","3d0d6741d","a4ca91ea1","efd885d05"]],"commits":["07a6c262b"],"cves":[],"db_id":"8c98433b203fc9f697cb6dfef2f22a70","html":"\u003cp\u003eMake line widths match in \u003cspan\u003epsql\u003c/span\u003e's expanded aligned output format (Pavel Stehule) \u003ca href=\"https://postgr.es/c/07a6c262b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWhen the table's data rows are narrower than the record header lines, widen the data rows to match the headers, avoiding unsightly output.\u003c/p\u003e","id":"18.6-e95d42c0b0a749e2","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.","part":"changes","patch_ids":["e1ed38dd6fb22dc6b3c388c344a54963"],"relations":[{"evidence":{"patch_ids":["e1ed38dd6fb22dc6b3c388c344a54963"],"same_day":true,"statement_hash":"bfb36185dbcab5e46aea9291f19969eb343ad3998992659ae2d4c88cea80e5d6"},"rule":2,"target":"58d0bf8b8ffb214d0f6ab86e01e2ee4d","type":"equivalent"},{"evidence":{"patch_ids":["e1ed38dd6fb22dc6b3c388c344a54963"],"same_day":true,"statement_hash":"bfb36185dbcab5e46aea9291f19969eb343ad3998992659ae2d4c88cea80e5d6"},"rule":2,"target":"6a176afe78ae457a5f2e20281e68c1c8","type":"equivalent"},{"evidence":{"patch_ids":["e1ed38dd6fb22dc6b3c388c344a54963"],"same_day":true,"statement_hash":"bfb36185dbcab5e46aea9291f19969eb343ad3998992659ae2d4c88cea80e5d6"},"rule":2,"target":"6d353eb0c8713cda0665ed6128c86dc7","type":"equivalent"},{"evidence":{"patch_ids":["e1ed38dd6fb22dc6b3c388c344a54963"],"same_day":true,"statement_hash":"bfb36185dbcab5e46aea9291f19969eb343ad3998992659ae2d4c88cea80e5d6"},"rule":2,"target":"73be9a684058fbdc9b8dd586127fd52a","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["07a6c262b"],"source_entry_id":"18.6/changes/111","source_hash":"2d580be2068a246a98a192e4b40e46fe642aeb2c0d2fea17a0d81119c971db75","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"bfb36185dbcab5e46aea9291f19969eb343ad3998992659ae2d4c88cea80e5d6","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"},"id":"18.6-e95d42c0b0a749e2","matches":[{"id":"17.11-410e9178511c3bd6","source_entry_id":"17.11/changes/089","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Make line widths match in psql's expanded aligned output format","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/111","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Make line widths match in psql's expanded aligned output format","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["38afc3dcb","41949c6f3","4e19081da","77aeca802","844bc718a","e6e8a3078","f2d6cf880"],"commit_groups":[["38afc3dcb","41949c6f3","4e19081da","77aeca802","844bc718a","e6e8a3078","f2d6cf880"]],"commits":["f2d6cf880"],"cves":[],"db_id":"141d0e312a20156d1cd7aa5beaa39b84","html":"\u003cp\u003eFix \u003cspan\u003epsql\u003c/span\u003e's privilege check for showing database size in \u003ccode\u003e\\l+\u003c/code\u003e (Christoph Berg) \u003ca href=\"https://postgr.es/c/f2d6cf880\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe underlying server function permits users who have \u003ccode\u003epg_read_all_stats\u003c/code\u003e privileges to see the sizes of all databases, even if they lack \u003ccode\u003eCONNECT\u003c/code\u003e privilege. But \u003cspan\u003epsql\u003c/span\u003e was unaware of that provision and would not call the function unless the user has \u003ccode\u003eCONNECT\u003c/code\u003e privilege.\u003c/p\u003e","id":"18.6-f01251105c93da4a","identity_text":"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.","part":"changes","patch_ids":["987969fa30d6f3f33766c7242f782fcc"],"relations":[{"evidence":{"patch_ids":["987969fa30d6f3f33766c7242f782fcc"],"same_day":true,"statement_hash":"52d0973776d5fe7f0ea2f39f5e8746a9acc9f7423229f4d6af57f5fe0d5f77e6"},"rule":2,"target":"8b38bff9895db96300585ebb983568e8","type":"equivalent"},{"evidence":{"patch_ids":["987969fa30d6f3f33766c7242f782fcc"],"same_day":true,"statement_hash":"52d0973776d5fe7f0ea2f39f5e8746a9acc9f7423229f4d6af57f5fe0d5f77e6"},"rule":2,"target":"e7c613c24d691b769e31df57d0463965","type":"equivalent"},{"evidence":{"patch_ids":["987969fa30d6f3f33766c7242f782fcc"],"same_day":true,"statement_hash":"52d0973776d5fe7f0ea2f39f5e8746a9acc9f7423229f4d6af57f5fe0d5f77e6"},"rule":2,"target":"f02d8966daabdbd36db1126f9327767d","type":"equivalent"},{"evidence":{"patch_ids":["987969fa30d6f3f33766c7242f782fcc"],"same_day":true,"statement_hash":"52d0973776d5fe7f0ea2f39f5e8746a9acc9f7423229f4d6af57f5fe0d5f77e6"},"rule":2,"target":"fb027e827736bff10cc532003be6bcee","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["f2d6cf880"],"source_entry_id":"18.6/changes/113","source_hash":"76fc25f23c99dc4482bf43dfc62acad6dd6958269504ce0077e7451c61767bdb","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"52d0973776d5fe7f0ea2f39f5e8746a9acc9f7423229f4d6af57f5fe0d5f77e6","text":"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.","title":"Fix psql's privilege check for showing database size in \\l+"},"id":"18.6-f01251105c93da4a","matches":[{"id":"17.11-3336152e1ee6addb","source_entry_id":"17.11/changes/090","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix psql's privilege check for showing database size in \\l+","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/113","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix psql's privilege check for showing database size in \\l+","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["2d44bb900","355a4fcf9","558e0de6d","598af79b1","6d4ca6de9","c25737c89","f9afdb6d1"],"commit_groups":[["2d44bb900","355a4fcf9","558e0de6d","598af79b1","6d4ca6de9","c25737c89","f9afdb6d1"]],"commits":["598af79b1"],"cves":[],"db_id":"a6e56de07c090ea331a5f798b3fa0d29","html":"\u003cp\u003eFix \u003cspan\u003epsql\u003c/span\u003e's tab completion for \u003ccode\u003e\\df\u003c/code\u003e to consider procedures too (Erik Wienhold) \u003ca href=\"https://postgr.es/c/598af79b1\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-34779a676e9c08fc","identity_text":"Fix psql's tab completion for \\df to consider procedures too (Erik Wienhold)","part":"changes","patch_ids":["42dfbce6e4e3f60c61e074ef2e0a152b"],"relations":[{"evidence":{"patch_ids":["42dfbce6e4e3f60c61e074ef2e0a152b"],"same_day":true,"statement_hash":"1e5b0a22566f92da2ff5281d6974022db425423987f69e22a54af6a299da7e4c"},"rule":2,"target":"2e71a63a423fe753a49907fea3f3f726","type":"equivalent"},{"evidence":{"patch_ids":["42dfbce6e4e3f60c61e074ef2e0a152b"],"same_day":true,"statement_hash":"1e5b0a22566f92da2ff5281d6974022db425423987f69e22a54af6a299da7e4c"},"rule":2,"target":"9de93d1e22001ece7792c285e354eead","type":"equivalent"},{"evidence":{"patch_ids":["42dfbce6e4e3f60c61e074ef2e0a152b"],"same_day":true,"statement_hash":"1e5b0a22566f92da2ff5281d6974022db425423987f69e22a54af6a299da7e4c"},"rule":2,"target":"b7650aff43943bf8882b3a2f849f6bee","type":"equivalent"},{"evidence":{"patch_ids":["42dfbce6e4e3f60c61e074ef2e0a152b"],"same_day":true,"statement_hash":"1e5b0a22566f92da2ff5281d6974022db425423987f69e22a54af6a299da7e4c"},"rule":2,"target":"df69b2e9f052d92dfefda54eacbfc1ea","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["598af79b1"],"source_entry_id":"18.6/changes/114","source_hash":"9124d04d66e089430c2b51bc59f8324c460e79feb7188fd61ffe68f450c6f621","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"1e5b0a22566f92da2ff5281d6974022db425423987f69e22a54af6a299da7e4c","text":"Fix psql's tab completion for \\df to consider procedures too (Erik Wienhold) §","title":"Fix psql's tab completion for \\df to consider procedures too"},"id":"18.6-34779a676e9c08fc","matches":[{"id":"17.11-774191cf1146f3bf","source_entry_id":"17.11/changes/091","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix psql's tab completion for \\df to consider procedures too","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/114","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix psql's tab completion for \\df to consider procedures too","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["52b3e7001","61f8a85a5","6432a4cd6","98dd6c204","f18fcd9a4"],"commit_groups":[["52b3e7001","61f8a85a5","6432a4cd6","98dd6c204","f18fcd9a4"]],"commits":["98dd6c204"],"cves":[],"db_id":"44b28e2d798edbd4039b847c6dd86848","html":"\u003cp\u003eFix thread-safety bug in \u003cspan\u003epgbench\u003c/span\u003e (Fujii Masao) \u003ca href=\"https://postgr.es/c/98dd6c204\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWhen \u003cspan\u003epgbench\u003c/span\u003e runs with multiple threads and the \u003ccode\u003e--verbose-errors\u003c/code\u003e option, different threads could attempt to use the same buffer to construct error messages, leading to corrupted log output.\u003c/p\u003e","id":"18.6-d444b0e88b717a34","identity_text":"Fix thread-safety bug in pgbench (Fujii Masao) When 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.","part":"changes","patch_ids":["4117d7222a31fc591ad7eac0024a0f9f"],"relations":[{"evidence":{"patch_ids":["4117d7222a31fc591ad7eac0024a0f9f"],"same_day":true,"statement_hash":"954c7afe7c6b0058837dfdb334f6d992ca7c956e2e82c888bfb65248ea13fcaf"},"rule":2,"target":"4e32c3e5a2bb416ea303c286b1df2858","type":"equivalent"},{"evidence":{"patch_ids":["4117d7222a31fc591ad7eac0024a0f9f"],"same_day":true,"statement_hash":"954c7afe7c6b0058837dfdb334f6d992ca7c956e2e82c888bfb65248ea13fcaf"},"rule":2,"target":"5b099ea0ec4e743ffb1348250e4fbe06","type":"equivalent"},{"evidence":{"patch_ids":["4117d7222a31fc591ad7eac0024a0f9f"],"same_day":true,"statement_hash":"954c7afe7c6b0058837dfdb334f6d992ca7c956e2e82c888bfb65248ea13fcaf"},"rule":2,"target":"9fc066b4de5fcf91012835e6ddbc1b32","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["98dd6c204"],"source_entry_id":"18.6/changes/115","source_hash":"e6aedd0eb0f7424224cb1fd8581477605d7c08b7f44191b8d45ab9aef9a01a18","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"954c7afe7c6b0058837dfdb334f6d992ca7c956e2e82c888bfb65248ea13fcaf","text":"Fix thread-safety bug in pgbench (Fujii Masao) § When 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.","title":"Fix thread-safety bug in pgbench"},"id":"18.6-d444b0e88b717a34","matches":[{"id":"17.11-700eeda11277f3b9","source_entry_id":"17.11/changes/092","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix thread-safety bug in pgbench","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/115","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix thread-safety bug in pgbench","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["090ce6934","994f770a0","d36b72894"],"commit_groups":[["090ce6934","994f770a0","d36b72894"]],"commits":["d36b72894"],"cves":[],"db_id":"c27420aa9b3b249ab663f9b3b7619204","html":"\u003cp\u003eIn \u003cspan\u003epg_combinebackup\u003c/span\u003e, prevent infinite loop if the source file is shorter than expected (Peter Eisentraut) \u003ca href=\"https://postgr.es/c/d36b72894\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-0a368cc2731c2f99","identity_text":"In pg_combinebackup, prevent infinite loop if the source file is shorter than expected (Peter Eisentraut)","part":"changes","patch_ids":["0ba00e2ae3a5e83df9d4302186a61a05"],"relations":[{"evidence":{"patch_ids":["0ba00e2ae3a5e83df9d4302186a61a05"],"same_day":true,"statement_hash":"761861ecd47105adace712b27a89e3d3f71b32c7571c4e3a163697a77fad30a7"},"rule":2,"target":"0de6b21246ca038db28e1d7e7a8c33a5","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["d36b72894"],"source_entry_id":"18.6/changes/116","source_hash":"e32f0075646e4a9ef32c93d9a5abb89c84e7398c492390d99d563ba6792484be","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"761861ecd47105adace712b27a89e3d3f71b32c7571c4e3a163697a77fad30a7","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"},"id":"18.6-0a368cc2731c2f99","matches":[{"id":"17.11-17e93d8574cb6937","source_entry_id":"17.11/changes/093","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"In pg_combinebackup, prevent infinite loop if the source file is shorter than expected","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/116","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"In pg_combinebackup, prevent infinite loop if the source file is shorter than expected","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["12d000488","196b4b5ae","c03784a21"],"commit_groups":[["12d000488","196b4b5ae","c03784a21"]],"commits":["196b4b5ae"],"cves":[],"db_id":"b3b32d95005620db1dde6737c217ff79","html":"\u003cp\u003eFix cleanup of publisher-side objects after errors in \u003cspan\u003epg_createsubscriber\u003c/span\u003e (Nisha Moond) \u003ca href=\"https://postgr.es/c/196b4b5ae\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWhen \u003cspan\u003epg_createsubscriber\u003c/span\u003e 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.\u003c/p\u003e","id":"18.6-280913453570aa34","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.","part":"changes","patch_ids":["294a0298249f9d0b66c918ec534fd2fa"],"relations":[{"evidence":{"patch_ids":["294a0298249f9d0b66c918ec534fd2fa"],"same_day":true,"statement_hash":"0b52e9786bbf3135e7724a4cd772716beafec6c0f4a214b285af87f0fd2ba380"},"rule":2,"target":"a5c36038d3fc8268a2ecbdc5f6d205fc","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["196b4b5ae"],"source_entry_id":"18.6/changes/117","source_hash":"57682237b6273967edf6e0db2bced108af4544c26854c821f2753f04470bee76","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"0b52e9786bbf3135e7724a4cd772716beafec6c0f4a214b285af87f0fd2ba380","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"},"id":"18.6-280913453570aa34","matches":[{"id":"17.11-48e3e90ffcc9370a","source_entry_id":"17.11/changes/094","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix cleanup of publisher-side objects after errors in pg_createsubscriber","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/117","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix cleanup of publisher-side objects after errors in pg_createsubscriber","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["263d1e6df","5552a15a3","89b4b3ae3","9590dcfca","ba9833a75","ddd12d1a5"],"commit_groups":[["263d1e6df","5552a15a3","89b4b3ae3","9590dcfca","ba9833a75","ddd12d1a5"]],"commits":["89b4b3ae3"],"cves":[],"db_id":"739e2a6e3be37fb134a81099033e7b88","html":"\u003cp\u003eUse the source cluster's group-read file permissions for \u003cspan\u003epg_recvlogical\u003c/span\u003e output files (Fujii Masao) \u003ca href=\"https://postgr.es/c/89b4b3ae3\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003epg_recvlogical\u003c/span\u003e was documented to behave this way, but it never actually enabled group-read.\u003c/p\u003e","id":"18.6-ccc1d394ba38511a","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.","part":"changes","patch_ids":["afbffd5094352bc11bf18ec699c42866"],"relations":[{"evidence":{"patch_ids":["afbffd5094352bc11bf18ec699c42866"],"same_day":true,"statement_hash":"76c08921b60501e09bdf60cd197949c5372599c542dc2702bad076644bfb808e"},"rule":2,"target":"46627f579bf31b5d6613ea2ead9a438c","type":"equivalent"},{"evidence":{"patch_ids":["afbffd5094352bc11bf18ec699c42866"],"same_day":true,"statement_hash":"76c08921b60501e09bdf60cd197949c5372599c542dc2702bad076644bfb808e"},"rule":2,"target":"5e9c0809074f8046eb23cf8c625f723d","type":"equivalent"},{"evidence":{"patch_ids":["afbffd5094352bc11bf18ec699c42866"],"same_day":true,"statement_hash":"76c08921b60501e09bdf60cd197949c5372599c542dc2702bad076644bfb808e"},"rule":2,"target":"7c4fc2d9507cff650a6e11a00319e316","type":"equivalent"},{"evidence":{"patch_ids":["afbffd5094352bc11bf18ec699c42866"],"same_day":true,"statement_hash":"76c08921b60501e09bdf60cd197949c5372599c542dc2702bad076644bfb808e"},"rule":2,"target":"f4924985d224acc909a53983f158ebbe","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["89b4b3ae3"],"source_entry_id":"18.6/changes/118","source_hash":"c7707d5c1907b9f8589f22c46145c7e026130a40f4b4d3662c264143afee593b","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"76c08921b60501e09bdf60cd197949c5372599c542dc2702bad076644bfb808e","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"},"id":"18.6-ccc1d394ba38511a","matches":[{"id":"17.11-7a66a4f0ad5abf3d","source_entry_id":"17.11/changes/095","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/118","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","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["4284476c0","897e79486","8abb8a155","af09b18cb","c89a1ca01","da1eff08a"],"commit_groups":[["4284476c0","897e79486","8abb8a155","af09b18cb","c89a1ca01","da1eff08a"]],"commits":["897e79486"],"cves":[],"db_id":"2d507c3ecfdc88b0a54eabbb1a06a7e0","html":"\u003cp\u003eIn \u003ccode\u003econtrib/amcheck\u003c/code\u003e, handle short-header varlena datums correctly (Andrey Borodin) \u003ca href=\"https://postgr.es/c/897e79486\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis error could result in doing excess work while verifying a btree index, but seems not to have had any worse consequences.\u003c/p\u003e","id":"18.6-83d0b073d364f75c","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.","part":"changes","patch_ids":["d7fc6f8977003129b1104cd80d7d07dc"],"relations":[{"evidence":{"patch_ids":["d7fc6f8977003129b1104cd80d7d07dc"],"same_day":true,"statement_hash":"e472f473c1b1497e339e1735040e13130df76e2534eb81a81dc2b51327126c5d"},"rule":2,"target":"3b8c851869278523310ddb5e0cf66c28","type":"equivalent"},{"evidence":{"patch_ids":["d7fc6f8977003129b1104cd80d7d07dc"],"same_day":true,"statement_hash":"e472f473c1b1497e339e1735040e13130df76e2534eb81a81dc2b51327126c5d"},"rule":2,"target":"45cd63fac27296a03920e2ac709b0ed6","type":"equivalent"},{"evidence":{"patch_ids":["d7fc6f8977003129b1104cd80d7d07dc"],"same_day":true,"statement_hash":"e472f473c1b1497e339e1735040e13130df76e2534eb81a81dc2b51327126c5d"},"rule":2,"target":"cdde56de8d6ffe6162fb47b834f39528","type":"equivalent"},{"evidence":{"patch_ids":["d7fc6f8977003129b1104cd80d7d07dc"],"same_day":true,"statement_hash":"e472f473c1b1497e339e1735040e13130df76e2534eb81a81dc2b51327126c5d"},"rule":2,"target":"e3d3da7d18247e58916c107812921cf0","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["897e79486"],"source_entry_id":"18.6/changes/123","source_hash":"152b36f3a586a937cd005dd3f18e0bbbd573f79cc40dff4a2e1213c59f38f760","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"e472f473c1b1497e339e1735040e13130df76e2534eb81a81dc2b51327126c5d","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"},"id":"18.6-83d0b073d364f75c","matches":[{"id":"17.11-43173bad4eaa1b27","source_entry_id":"17.11/changes/096","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"In contrib/amcheck, handle short-header varlena datums correctly","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/123","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"In contrib/amcheck, handle short-header varlena datums correctly","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["1e1d07792","255bce448","7d3448961","98dd4406f","a47005f0b","d215d2cc2","d569ccd40"],"commit_groups":[["1e1d07792","255bce448","7d3448961","98dd4406f","a47005f0b","d215d2cc2","d569ccd40"]],"commits":["1e1d07792"],"cves":[],"db_id":"4d9e91353135c760e8823c0cd0ef6409","html":"\u003cp\u003eIn \u003ccode\u003econtrib/btree_gist\u003c/code\u003e, fix \u003ccode\u003eNaN\u003c/code\u003e handling in the \u003ccode\u003efloat4\u003c/code\u003e and \u003ccode\u003efloat8\u003c/code\u003e opclasses (Bill Kim, Tom Lane) \u003ca href=\"https://postgr.es/c/1e1d07792\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eComparisons, as well as the GiST penalty and distance functions, did not account for \u003ccode\u003eNaN\u003c/code\u003e and would give the wrong answer when handed one. It is recommended to reindex \u003ccode\u003ebtree_gist\u003c/code\u003e indexes on float columns after installing this update, if there is any possibility that there are \u003ccode\u003eNaN\u003c/code\u003e entries in those columns.\u003c/p\u003e","id":"18.6-f1427fb43b6c1e77","identity_text":"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.","part":"changes","patch_ids":["a41ef98054d9fc11255ff2e1ac2b8d7f"],"relations":[{"evidence":{"patch_ids":["a41ef98054d9fc11255ff2e1ac2b8d7f"],"same_day":true,"statement_hash":"faf27e09f191a40fa7cb700d40946951864bfacf5baac3f0510ba15d921d9788"},"rule":2,"target":"4cd8eba009b82559add8c3ec81c4961d","type":"equivalent"},{"evidence":{"patch_ids":["a41ef98054d9fc11255ff2e1ac2b8d7f"],"same_day":true,"statement_hash":"faf27e09f191a40fa7cb700d40946951864bfacf5baac3f0510ba15d921d9788"},"rule":2,"target":"b7dd35efd818ab32c6cd15f0eb30fcbe","type":"equivalent"},{"evidence":{"patch_ids":["a41ef98054d9fc11255ff2e1ac2b8d7f"],"same_day":true,"statement_hash":"faf27e09f191a40fa7cb700d40946951864bfacf5baac3f0510ba15d921d9788"},"rule":2,"target":"b9df41b379c5302bb94ed660170eb547","type":"equivalent"},{"evidence":{"patch_ids":["a41ef98054d9fc11255ff2e1ac2b8d7f"],"same_day":true,"statement_hash":"faf27e09f191a40fa7cb700d40946951864bfacf5baac3f0510ba15d921d9788"},"rule":2,"target":"eacc61a61a6ef9f06eeceda6f5a96384","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["1e1d07792"],"source_entry_id":"18.6/changes/124","source_hash":"3389079cb64adc93caa2505b62c87e58e61ca1e10b80392c67a4cee8db9e9e3a","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"faf27e09f191a40fa7cb700d40946951864bfacf5baac3f0510ba15d921d9788","text":"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.","title":"In contrib/btree_gist, fix NaN handling in the float4 and float8 opclasses"},"id":"18.6-f1427fb43b6c1e77","matches":[{"id":"17.11-62f2c81188559a68","source_entry_id":"17.11/changes/097","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"In contrib/btree_gist, fix NaN handling in the float4 and float8 opclasses","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/124","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"In contrib/btree_gist, fix NaN handling in the float4 and float8 opclasses","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["0663382c9","12c519207","286f9a3ce","86992769e","8f2a1b3d3","eef644e57","fc6649abe"],"commit_groups":[["0663382c9","12c519207","286f9a3ce","86992769e","8f2a1b3d3","eef644e57","fc6649abe"]],"commits":["12c519207"],"cves":[],"db_id":"6a17d9b57b1644e479653b086d9a3d5b","html":"\u003cp\u003eIn \u003ccode\u003econtrib/btree_gist\u003c/code\u003e, fix searches using a not-equal operator (Ayush Tiwari) \u003ca href=\"https://postgr.es/c/12c519207\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFor variable-length data types, the code for scanning non-leaf index pages applied the wrong comparison function, leading to wrong results and potentially crashes.\u003c/p\u003e","id":"18.6-ba3d35f49ebe5363","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.","part":"changes","patch_ids":["515eccc8717dfd3bf829ad309ee292d4"],"relations":[{"evidence":{"patch_ids":["515eccc8717dfd3bf829ad309ee292d4"],"same_day":true,"statement_hash":"2be1ae243cd8ebc1e8e722c0adfd189a77f8b7ec2ce84c5f76afc7ac0990135a"},"rule":2,"target":"635407feb25f134fd4b583a750d226fd","type":"equivalent"},{"evidence":{"patch_ids":["515eccc8717dfd3bf829ad309ee292d4"],"same_day":true,"statement_hash":"2be1ae243cd8ebc1e8e722c0adfd189a77f8b7ec2ce84c5f76afc7ac0990135a"},"rule":2,"target":"72b13e01606442471a1d73d64267d5db","type":"equivalent"},{"evidence":{"patch_ids":["515eccc8717dfd3bf829ad309ee292d4"],"same_day":true,"statement_hash":"2be1ae243cd8ebc1e8e722c0adfd189a77f8b7ec2ce84c5f76afc7ac0990135a"},"rule":2,"target":"b8f3ffff9bd8249a29d2857d5a2613d1","type":"equivalent"},{"evidence":{"patch_ids":["515eccc8717dfd3bf829ad309ee292d4"],"same_day":true,"statement_hash":"2be1ae243cd8ebc1e8e722c0adfd189a77f8b7ec2ce84c5f76afc7ac0990135a"},"rule":2,"target":"c540681583edc5cf717591e5bf65da83","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["12c519207"],"source_entry_id":"18.6/changes/126","source_hash":"f473dbeeef45f9192ac0fd0459f12bff57152d3ed6af68df7b93c96933c434cd","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"2be1ae243cd8ebc1e8e722c0adfd189a77f8b7ec2ce84c5f76afc7ac0990135a","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"},"id":"18.6-ba3d35f49ebe5363","matches":[{"id":"17.11-bb79dbfaaf4bd7a5","source_entry_id":"17.11/changes/098","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"In contrib/btree_gist, fix searches using a not-equal operator","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/126","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"In contrib/btree_gist, fix searches using a not-equal operator","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["1f6b2295f","3df0b7755","4efef9d18","4fbbabb0a","60a1d712a","639fff511","a6f23c3ad","b0f3465b6","c0f17b04d","d65cf6f80","da82fbb8f","e3b7a43fa"],"commit_groups":[["1f6b2295f","4efef9d18","4fbbabb0a","60a1d712a","c0f17b04d","d65cf6f80"],["3df0b7755","639fff511","a6f23c3ad","b0f3465b6","da82fbb8f","e3b7a43fa"]],"commits":["d65cf6f80","e3b7a43fa"],"cves":[],"db_id":"e84c01132f8e26fec06fb2c24d693754","html":"\u003cp\u003eFix unguarded recursion and loops in \u003ccode\u003econtrib/hstore_plperl\u003c/code\u003e, \u003ccode\u003econtrib/jsonb_plperl\u003c/code\u003e, and \u003ccode\u003econtrib/jsonb_plpython\u003c/code\u003e (Aleksander Alekseev) \u003ca href=\"https://postgr.es/c/e3b7a43fa\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/d65cf6f80\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePrevent stack overflow when dealing with deeply nested \u003ccode\u003ejsonb\u003c/code\u003e values, and allow interruption of the infinite loop caused when attempting to dereference circular chains of Perl object references.\u003c/p\u003e","id":"18.6-3bbe012702953660","identity_text":"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.","part":"changes","patch_ids":["06d3f82c811dcdc72352268391913b6d","d2e482ea690658ce247d390c41c898b7"],"relations":[{"evidence":{"patch_ids":["06d3f82c811dcdc72352268391913b6d","d2e482ea690658ce247d390c41c898b7"],"same_day":true,"statement_hash":"7097b151e48a64281451cfa04b6e3d236b5b30fd3c3c7d17dc03685399c5d1a3"},"rule":2,"target":"595e055e71880ae192e2de47f74a1291","type":"equivalent"},{"evidence":{"patch_ids":["06d3f82c811dcdc72352268391913b6d","d2e482ea690658ce247d390c41c898b7"],"same_day":true,"statement_hash":"7097b151e48a64281451cfa04b6e3d236b5b30fd3c3c7d17dc03685399c5d1a3"},"rule":2,"target":"94eaadfc76909fd86106e4f1ca7ca2ff","type":"equivalent"},{"evidence":{"patch_ids":["06d3f82c811dcdc72352268391913b6d","d2e482ea690658ce247d390c41c898b7"],"same_day":true,"statement_hash":"7097b151e48a64281451cfa04b6e3d236b5b30fd3c3c7d17dc03685399c5d1a3"},"rule":2,"target":"e764a2169f298518893448497eb58f37","type":"equivalent"},{"evidence":{"patch_ids":["06d3f82c811dcdc72352268391913b6d","d2e482ea690658ce247d390c41c898b7"],"same_day":true,"statement_hash":"7097b151e48a64281451cfa04b6e3d236b5b30fd3c3c7d17dc03685399c5d1a3"},"rule":2,"target":"f6efa9b4ffedab334fa7ffa327afa7eb","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["d65cf6f80","e3b7a43fa"],"source_entry_id":"18.6/changes/129","source_hash":"81b7f0f415195e0494dd86d9173418b2ec8748068be845c22ec549a8569b82e2","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"7097b151e48a64281451cfa04b6e3d236b5b30fd3c3c7d17dc03685399c5d1a3","text":"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.","title":"Fix unguarded recursion and loops in contrib/hstore_plperl, contrib/jsonb_plperl, and contrib/jsonb_plpython"},"id":"18.6-3bbe012702953660","matches":[{"id":"17.11-f475bfd70799c254","source_entry_id":"17.11/changes/099","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/129","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","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["273be484a","524cc0f63","702a6d5f6","94b57ab54","a96b051a9","e7544c518"],"commit_groups":[["273be484a","524cc0f63","702a6d5f6","94b57ab54","a96b051a9","e7544c518"]],"commits":["e7544c518"],"cves":[],"db_id":"531f88cd6dd693227e011632166ae87b","html":"\u003cp\u003eFix missed release of statistics catcache entry in \u003ccode\u003econtrib/intarray\u003c/code\u003e (Man Zeng) \u003ca href=\"https://postgr.es/c/e7544c518\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis oversight led to warnings like \u003cspan\u003e“\u003cspan\u003eresource was not closed: cache pg_statistic\u003c/span\u003e”\u003c/span\u003e.\u003c/p\u003e","id":"18.6-69c78fae0c5ccd69","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.","part":"changes","patch_ids":["ed91737595bc2b3f155e28dcd1a2eea2"],"relations":[{"evidence":{"patch_ids":["ed91737595bc2b3f155e28dcd1a2eea2"],"same_day":true,"statement_hash":"f94e4dacb87f6c952276d56347322f0e3b34e2c00c7f4e555ef6c2806632dec3"},"rule":2,"target":"29b63a7300df9efc4d5ac1e96dc34cb7","type":"equivalent"},{"evidence":{"patch_ids":["ed91737595bc2b3f155e28dcd1a2eea2"],"same_day":true,"statement_hash":"f94e4dacb87f6c952276d56347322f0e3b34e2c00c7f4e555ef6c2806632dec3"},"rule":2,"target":"2c29490e6377bc8f4bb49b5d5ca76323","type":"equivalent"},{"evidence":{"patch_ids":["ed91737595bc2b3f155e28dcd1a2eea2"],"same_day":true,"statement_hash":"f94e4dacb87f6c952276d56347322f0e3b34e2c00c7f4e555ef6c2806632dec3"},"rule":2,"target":"441b437853466f13724bc66579a3d9c5","type":"equivalent"},{"evidence":{"patch_ids":["ed91737595bc2b3f155e28dcd1a2eea2"],"same_day":true,"statement_hash":"f94e4dacb87f6c952276d56347322f0e3b34e2c00c7f4e555ef6c2806632dec3"},"rule":2,"target":"a4dfb26ea114f9668f1e953f8895f530","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["e7544c518"],"source_entry_id":"18.6/changes/130","source_hash":"68153d5159c3c6ada0f6a07d899814308d69aa1ba7d4318b10ec41562e2e416c","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"f94e4dacb87f6c952276d56347322f0e3b34e2c00c7f4e555ef6c2806632dec3","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"},"id":"18.6-69c78fae0c5ccd69","matches":[{"id":"17.11-c1417114cda9dd52","source_entry_id":"17.11/changes/100","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix missed release of statistics catcache entry in contrib/intarray","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/130","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix missed release of statistics catcache entry in contrib/intarray","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["1bec6b1c1","3f3280491","aca944e33","c391c00d9","c3e36a9a5","f528a5606"],"commit_groups":[["1bec6b1c1","3f3280491","aca944e33","c391c00d9","c3e36a9a5","f528a5606"]],"commits":["c3e36a9a5"],"cves":[],"db_id":"888fddf9fe911dead6a68c55c98b9295","html":"\u003cp\u003eIn \u003ccode\u003econtrib/ltree\u003c/code\u003e, fix integer overflow in comparisons (Ayush Tiwari) \u003ca href=\"https://postgr.es/c/c3e36a9a5\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eltree\u003c/code\u003e 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.\u003c/p\u003e","id":"18.6-b2444fb7d252ecb2","identity_text":"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.","part":"changes","patch_ids":["81c4c385ffbd98f111a552cae708d804"],"relations":[{"evidence":{"patch_ids":["81c4c385ffbd98f111a552cae708d804"],"same_day":true,"statement_hash":"c38e1cee6bb8614366f4396766b59cb9e1991d5646798456e57e0b3b5c284883"},"rule":2,"target":"48fe7f3222eda75ec840ab2668d55093","type":"equivalent"},{"evidence":{"patch_ids":["81c4c385ffbd98f111a552cae708d804"],"same_day":true,"statement_hash":"c38e1cee6bb8614366f4396766b59cb9e1991d5646798456e57e0b3b5c284883"},"rule":2,"target":"708292f2ccdab3377b60d76cdaa5a7e5","type":"equivalent"},{"evidence":{"patch_ids":["81c4c385ffbd98f111a552cae708d804"],"same_day":true,"statement_hash":"c38e1cee6bb8614366f4396766b59cb9e1991d5646798456e57e0b3b5c284883"},"rule":2,"target":"f0507c88031aeac9ab37c3874a1e91d1","type":"equivalent"},{"evidence":{"patch_ids":["81c4c385ffbd98f111a552cae708d804"],"same_day":true,"statement_hash":"c38e1cee6bb8614366f4396766b59cb9e1991d5646798456e57e0b3b5c284883"},"rule":2,"target":"faeb6c3b8ab3db22ba871dc683772018","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["c3e36a9a5"],"source_entry_id":"18.6/changes/131","source_hash":"539609c22eddb85033f73068fec4c6fc7090af0cd27f3e4cc988f4498dc5ed25","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"c38e1cee6bb8614366f4396766b59cb9e1991d5646798456e57e0b3b5c284883","text":"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.","title":"In contrib/ltree, fix integer overflow in comparisons"},"id":"18.6-b2444fb7d252ecb2","matches":[{"id":"17.11-390646d2843a7323","source_entry_id":"17.11/changes/101","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"In contrib/ltree, fix integer overflow in comparisons","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/131","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"In contrib/ltree, fix integer overflow in comparisons","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["020426268","2aa6be6e6","80bb0ebcc"],"commit_groups":[["020426268","2aa6be6e6","80bb0ebcc"]],"commits":["020426268"],"cves":[],"db_id":"a3a95ce55c5a9796ab6c6450441f3aab","html":"\u003cp\u003eIn \u003ccode\u003econtrib/pgcrypto\u003c/code\u003e, avoid double-free crash after encountering an error while using an OSSLCipher object (Yuelin Wang) \u003ca href=\"https://postgr.es/c/020426268\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-794d5c13d1ec54d8","identity_text":"In contrib/pgcrypto, avoid double-free crash after encountering an error while using an OSSLCipher object (Yuelin Wang)","part":"changes","patch_ids":["0fc20fc5da6cc2df460972dea4bc66d3"],"relations":[{"evidence":{"patch_ids":["0fc20fc5da6cc2df460972dea4bc66d3"],"same_day":true,"statement_hash":"e754a4cc9f54f8e9075d7eb90cc11678eab6addc3270a282ab92b5e46a8111cc"},"rule":2,"target":"d0d6e890b41eab7e420c2fcbe5f1ef9a","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["020426268"],"source_entry_id":"18.6/changes/132","source_hash":"62a490cb890259e475d3ea5658bff0c45139063437eae9ae3a658a2876f49d15","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"e754a4cc9f54f8e9075d7eb90cc11678eab6addc3270a282ab92b5e46a8111cc","text":"In contrib/pgcrypto, avoid double-free crash after encountering an error while using an OSSLCipher object (Yuelin Wang) §","title":"In contrib/pgcrypto, avoid double-free crash after encountering an error while using an OSSLCipher object"},"id":"18.6-794d5c13d1ec54d8","matches":[{"id":"17.11-5451045e11a327c3","source_entry_id":"17.11/changes/102","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"In contrib/pgcrypto, avoid double-free crash after encountering an error while using an OSSLCipher object","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/132","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"In contrib/pgcrypto, avoid double-free crash after encountering an error while using an OSSLCipher object","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["0bcf19c9e","193a4ded9","1eda3eb07","2b09f8a91","51f63ba2b","daf8bc7d4"],"commit_groups":[["0bcf19c9e","193a4ded9","1eda3eb07","2b09f8a91","51f63ba2b","daf8bc7d4"]],"commits":["2b09f8a91"],"cves":[],"db_id":"34c6abdf99153564a44d057cfe4b6dac","html":"\u003cp\u003eFix array overrun in \u003ccode\u003econtrib/pg_surgery\u003c/code\u003e's \u003ccode\u003eheap_force_kill\u003c/code\u003e and \u003ccode\u003eheap_force_freeze\u003c/code\u003e functions (Michael Paquier) \u003ca href=\"https://postgr.es/c/2b09f8a91\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAttempting to change a TID whose offset number equals MaxHeapTuplesPerPage wrote one byte past the end of the allocated array, potentially crashing the server.\u003c/p\u003e","id":"18.6-2f1813bf59f642ea","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.","part":"changes","patch_ids":["eb798217c4bf865d1840668bc6612f6d"],"relations":[{"evidence":{"patch_ids":["eb798217c4bf865d1840668bc6612f6d"],"same_day":true,"statement_hash":"0c283cf21db62b067b9adc880d22c26404e9404758237c1adc833a4aa35981ae"},"rule":2,"target":"68b2c21176cad03670e2c5de5fd39431","type":"equivalent"},{"evidence":{"patch_ids":["eb798217c4bf865d1840668bc6612f6d"],"same_day":true,"statement_hash":"0c283cf21db62b067b9adc880d22c26404e9404758237c1adc833a4aa35981ae"},"rule":2,"target":"bfda1df269b11b96600aa8d604c7a26a","type":"equivalent"},{"evidence":{"patch_ids":["eb798217c4bf865d1840668bc6612f6d"],"same_day":true,"statement_hash":"0c283cf21db62b067b9adc880d22c26404e9404758237c1adc833a4aa35981ae"},"rule":2,"target":"dd33ec95e198e9db76b741cb251151f9","type":"equivalent"},{"evidence":{"patch_ids":["eb798217c4bf865d1840668bc6612f6d"],"same_day":true,"statement_hash":"0c283cf21db62b067b9adc880d22c26404e9404758237c1adc833a4aa35981ae"},"rule":2,"target":"f14b53949f2fa5150ed94f6fdbc3af9e","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["2b09f8a91"],"source_entry_id":"18.6/changes/134","source_hash":"0d8617c88bd69699f61f86b4d43593b97925e36eb860f4273481eca4654d97d7","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"0c283cf21db62b067b9adc880d22c26404e9404758237c1adc833a4aa35981ae","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"},"id":"18.6-2f1813bf59f642ea","matches":[{"id":"17.11-e5e220ac4d63838b","source_entry_id":"17.11/changes/103","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix array overrun in contrib/pg_surgery's heap_force_kill and heap_force_freeze functions","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/134","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix array overrun in contrib/pg_surgery's heap_force_kill and heap_force_freeze functions","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["19f0391df","1b6c99d96","1f24c8237","346fbdcc2","395700f48","e9d53cf45","eb28b6f24"],"commit_groups":[["19f0391df","1b6c99d96","1f24c8237","346fbdcc2","395700f48","e9d53cf45","eb28b6f24"]],"commits":["19f0391df"],"cves":[],"db_id":"15bef4f690bc1f9d9deab62cf46941cd","html":"\u003cp\u003eIn \u003ccode\u003econtrib/pg_surgery\u003c/code\u003e, avoid infinite loop with TID arrays having more than 64K elements (Andrey Rachitskiy) \u003ca href=\"https://postgr.es/c/19f0391df\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-e307258545af5090","identity_text":"In contrib/pg_surgery, avoid infinite loop with TID arrays having more than 64K elements (Andrey Rachitskiy)","part":"changes","patch_ids":["eee9eeea4b735f7e05d2171f399f90b7"],"relations":[{"evidence":{"patch_ids":["eee9eeea4b735f7e05d2171f399f90b7"],"same_day":true,"statement_hash":"61e49310bab6315f2a6361f60f0c6a990b1ae003c54c69d1fffe69de809cb046"},"rule":2,"target":"4a05d2d19e5e7e6511185becc5206900","type":"equivalent"},{"evidence":{"patch_ids":["eee9eeea4b735f7e05d2171f399f90b7"],"same_day":true,"statement_hash":"61e49310bab6315f2a6361f60f0c6a990b1ae003c54c69d1fffe69de809cb046"},"rule":2,"target":"a5a79735a400ca2b0ff1eb682f488482","type":"equivalent"},{"evidence":{"patch_ids":["eee9eeea4b735f7e05d2171f399f90b7"],"same_day":true,"statement_hash":"61e49310bab6315f2a6361f60f0c6a990b1ae003c54c69d1fffe69de809cb046"},"rule":2,"target":"d01853553d7520acbac484e63be9b7ae","type":"equivalent"},{"evidence":{"patch_ids":["eee9eeea4b735f7e05d2171f399f90b7"],"same_day":true,"statement_hash":"61e49310bab6315f2a6361f60f0c6a990b1ae003c54c69d1fffe69de809cb046"},"rule":2,"target":"ff158bb4d522b01e710f1a52fc58ebac","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["19f0391df"],"source_entry_id":"18.6/changes/135","source_hash":"6fcdfb5c70607b17ca3b702f66f28ff227ed11b400c8577205a7e95ba55305a7","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"61e49310bab6315f2a6361f60f0c6a990b1ae003c54c69d1fffe69de809cb046","text":"In contrib/pg_surgery, avoid infinite loop with TID arrays having more than 64K elements (Andrey Rachitskiy) §","title":"In contrib/pg_surgery, avoid infinite loop with TID arrays having more than 64K elements"},"id":"18.6-e307258545af5090","matches":[{"id":"17.11-79d5c27db04cf496","source_entry_id":"17.11/changes/104","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","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/135","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","version":"18.6"},{"entry":{"category":"security","commit_aliases":["1de0a711d","611756948","6b4de201e","77b2d18e9","eb93f10e2","ed0c4d5af"],"commit_groups":[["1de0a711d","611756948","6b4de201e","77b2d18e9","eb93f10e2","ed0c4d5af"]],"commits":["ed0c4d5af"],"cves":["CVE-2026-6637"],"db_id":"1404c503877f8a1f5c524fd84656cf87","html":"\u003cp\u003eAvoid NULL-pointer dereference in \u003ccode\u003econtrib/refint\u003c/code\u003e's \u003ccode\u003echeck_foreign_key()\u003c/code\u003e (Ayush Tiwari) \u003ca href=\"https://postgr.es/c/ed0c4d5af\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIn 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.\u003c/p\u003e","id":"18.6-8573bd52d03d8b3e","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.","part":"changes","patch_ids":["47510ee01f1ec9c76e280af528461da2"],"relations":[{"evidence":{"patch_ids":["47510ee01f1ec9c76e280af528461da2"],"same_day":true,"statement_hash":"95ffa03f4949f1fbe65efb454898eb0f8b9358951a8110fcc4b0547102b37374"},"rule":2,"target":"220e195253d94eac399969a628bda519","type":"equivalent"},{"evidence":{"patch_ids":["47510ee01f1ec9c76e280af528461da2"],"same_day":true,"statement_hash":"95ffa03f4949f1fbe65efb454898eb0f8b9358951a8110fcc4b0547102b37374"},"rule":2,"target":"4a53f44037d5d1ea5b714eb8d91567ee","type":"equivalent"},{"evidence":{"patch_ids":["47510ee01f1ec9c76e280af528461da2"],"same_day":true,"statement_hash":"95ffa03f4949f1fbe65efb454898eb0f8b9358951a8110fcc4b0547102b37374"},"rule":2,"target":"98b367e0c42416fd78e2312f81ec66e2","type":"equivalent"},{"evidence":{"patch_ids":["47510ee01f1ec9c76e280af528461da2"],"same_day":true,"statement_hash":"95ffa03f4949f1fbe65efb454898eb0f8b9358951a8110fcc4b0547102b37374"},"rule":2,"target":"a4fcc13dcc4b7cf6a5470b40915f7de5","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["ed0c4d5af"],"source_entry_id":"18.6/changes/136","source_hash":"1057a22e1c5d835fbe3ab3dedae9abbb24679f457e5b5af6ae2f572a15177513","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"95ffa03f4949f1fbe65efb454898eb0f8b9358951a8110fcc4b0547102b37374","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()"},"id":"18.6-8573bd52d03d8b3e","matches":[{"id":"17.11-3c3f973709d9fe9a","source_entry_id":"17.11/changes/105","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Avoid NULL-pointer dereference in contrib/refint's check_foreign_key()","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/136","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Avoid NULL-pointer dereference in contrib/refint's check_foreign_key()","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["0004cab4d","0e1f1ed15","504ca0513","58b91fc73","b3aa2083a","bcbbd070d"],"commit_groups":[["0004cab4d","0e1f1ed15","504ca0513","58b91fc73","b3aa2083a","bcbbd070d"]],"commits":["0004cab4d"],"cves":[],"db_id":"de74a54f9ab1b5032316a8f4cb4edf58","html":"\u003cp\u003eFix \u003ccode\u003econtrib/seg\u003c/code\u003e to print segments with \u003ccode\u003e~\u003c/code\u003e certainty indicators correctly (Ewan Young) \u003ca href=\"https://postgr.es/c/0004cab4d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eDue to a typo, \u003ccode\u003eseg_out()\u003c/code\u003e did not print a \u003ccode\u003e~\u003c/code\u003e certainty indicator attached to a segment's upper boundary. Worse, if the lower boundary had \u003ccode\u003e~\u003c/code\u003e while the upper boundary had no indicator, the upper boundary was not printed at all, incorrectly converting the value into an open interval.\u003c/p\u003e","id":"18.6-387ff665922d6204","identity_text":"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.","part":"changes","patch_ids":["e2313cef86571289890e86a92fd291b0"],"relations":[{"evidence":{"patch_ids":["e2313cef86571289890e86a92fd291b0"],"same_day":true,"statement_hash":"23b42c58c9ee43c9366b0c8bcd51fa7f6a5f8128a44a1177cc58f3f91513f308"},"rule":2,"target":"0092f0106b4cbebadc3657eda9991c9e","type":"equivalent"},{"evidence":{"patch_ids":["e2313cef86571289890e86a92fd291b0"],"same_day":true,"statement_hash":"23b42c58c9ee43c9366b0c8bcd51fa7f6a5f8128a44a1177cc58f3f91513f308"},"rule":2,"target":"4479ff440be61a73b062dfc1c959faf7","type":"equivalent"},{"evidence":{"patch_ids":["e2313cef86571289890e86a92fd291b0"],"same_day":true,"statement_hash":"23b42c58c9ee43c9366b0c8bcd51fa7f6a5f8128a44a1177cc58f3f91513f308"},"rule":2,"target":"f181fe24877ee46b04e858490e6a289b","type":"equivalent"},{"evidence":{"patch_ids":["e2313cef86571289890e86a92fd291b0"],"same_day":true,"statement_hash":"23b42c58c9ee43c9366b0c8bcd51fa7f6a5f8128a44a1177cc58f3f91513f308"},"rule":2,"target":"f63e408806c4f80aa07b2f3f4200fd07","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["0004cab4d"],"source_entry_id":"18.6/changes/137","source_hash":"86e9b8749c97077d90db0dbf1d2eb20b55d8a11d0d9cb5d26e215073c1f7db48","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"23b42c58c9ee43c9366b0c8bcd51fa7f6a5f8128a44a1177cc58f3f91513f308","text":"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.","title":"Fix contrib/seg to print segments with ~ certainty indicators correctly"},"id":"18.6-387ff665922d6204","matches":[{"id":"17.11-f8ebcb7cb6568363","source_entry_id":"17.11/changes/106","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix contrib/seg to print segments with ~ certainty indicators correctly","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/137","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix contrib/seg to print segments with ~ certainty indicators correctly","version":"18.6"},{"entry":{"category":"bugfix","commit_aliases":["18955d412","4a49ab289","91b57eade","9d33a5a80","bc5775149","f3f901a53"],"commit_groups":[["18955d412","4a49ab289","91b57eade","9d33a5a80","bc5775149","f3f901a53"]],"commits":["91b57eade"],"cves":[],"db_id":"fd09f75c1b17c508bb1667d2e8243417","html":"\u003cp\u003eFix crash with namespace nodes in \u003ccode\u003econtrib/xml2\u003c/code\u003e's \u003ccode\u003expath_nodeset()\u003c/code\u003e function (Andrey Chernyy, Michael Paquier) \u003ca href=\"https://postgr.es/c/91b57eade\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-de0be6584b43dd98","identity_text":"Fix crash with namespace nodes in contrib/xml2's xpath_nodeset() function (Andrey Chernyy, Michael Paquier)","part":"changes","patch_ids":["8c64b7d500b48c68b6c001ce703e5a7a"],"relations":[{"evidence":{"patch_ids":["8c64b7d500b48c68b6c001ce703e5a7a"],"same_day":true,"statement_hash":"564064da4d754c14b74429277ee8c70cec905cb6c0898171524ca51bb511cd9e"},"rule":2,"target":"2953470186ae43261dceb65dc846a8ae","type":"equivalent"},{"evidence":{"patch_ids":["8c64b7d500b48c68b6c001ce703e5a7a"],"same_day":true,"statement_hash":"564064da4d754c14b74429277ee8c70cec905cb6c0898171524ca51bb511cd9e"},"rule":2,"target":"32f92901accbc8994883d1e03fd0af26","type":"equivalent"},{"evidence":{"patch_ids":["8c64b7d500b48c68b6c001ce703e5a7a"],"same_day":true,"statement_hash":"564064da4d754c14b74429277ee8c70cec905cb6c0898171524ca51bb511cd9e"},"rule":2,"target":"d967526895b7f276004e82823a346cb6","type":"equivalent"},{"evidence":{"patch_ids":["8c64b7d500b48c68b6c001ce703e5a7a"],"same_day":true,"statement_hash":"564064da4d754c14b74429277ee8c70cec905cb6c0898171524ca51bb511cd9e"},"rule":2,"target":"edc2de68fd585e179939afe22f49f6bb","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["91b57eade"],"source_entry_id":"18.6/changes/138","source_hash":"9996c2e7a29a9068cc7a5efd483950a9f070ec8e84e7ba20d0c1cb497c144290","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"564064da4d754c14b74429277ee8c70cec905cb6c0898171524ca51bb511cd9e","text":"Fix crash with namespace nodes in contrib/xml2's xpath_nodeset() function (Andrey Chernyy, Michael Paquier) §","title":"Fix crash with namespace nodes in contrib/xml2's xpath_nodeset() function"},"id":"18.6-de0be6584b43dd98","matches":[{"id":"17.11-104bc8853d14d256","source_entry_id":"17.11/changes/107","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix crash with namespace nodes in contrib/xml2's xpath_nodeset() function","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/138","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Fix crash with namespace nodes in contrib/xml2's xpath_nodeset() function","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["086652c02","27cf3b5af","89d243d52","8bcabfcce","c7f70fa1b","fb8befa7b"],"commit_groups":[["086652c02","27cf3b5af","89d243d52","8bcabfcce","c7f70fa1b","fb8befa7b"]],"commits":["27cf3b5af"],"cves":[],"db_id":"c3287f3d7329f9fd4fb1dead8c819569","html":"\u003cp\u003eSupport building \u003cspan\u003ePostgreSQL\u003c/span\u003e with OpenSSL 4 (Daniel Gustafsson) \u003ca href=\"https://postgr.es/c/27cf3b5af\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-48c6d3c86320b73f","identity_text":"Support building PostgreSQL with OpenSSL 4 (Daniel Gustafsson)","part":"changes","patch_ids":["17c49f696c0a31900846c5a8c98eebd4"],"relations":[{"evidence":{"patch_ids":["17c49f696c0a31900846c5a8c98eebd4"],"same_day":true,"statement_hash":"c7b934d532c3b5d79d29d9130c3ab4f97028c3c1aa16422bb9101d84ad828729"},"rule":2,"target":"10ee20e58ffd04daecf6e5f030162c87","type":"equivalent"},{"evidence":{"patch_ids":["17c49f696c0a31900846c5a8c98eebd4"],"same_day":true,"statement_hash":"c7b934d532c3b5d79d29d9130c3ab4f97028c3c1aa16422bb9101d84ad828729"},"rule":2,"target":"3814ca74f63c29149528542a43ad21c5","type":"equivalent"},{"evidence":{"patch_ids":["17c49f696c0a31900846c5a8c98eebd4"],"same_day":true,"statement_hash":"c7b934d532c3b5d79d29d9130c3ab4f97028c3c1aa16422bb9101d84ad828729"},"rule":2,"target":"5205dd7058f572a69fe179e448446706","type":"equivalent"},{"evidence":{"patch_ids":["17c49f696c0a31900846c5a8c98eebd4"],"same_day":true,"statement_hash":"c7b934d532c3b5d79d29d9130c3ab4f97028c3c1aa16422bb9101d84ad828729"},"rule":2,"target":"5a9bafbcf49a80b12f21e542e3bae026","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["27cf3b5af"],"source_entry_id":"18.6/changes/139","source_hash":"9be69421adf563ef48c8b372b32c2e4d99c30d055115c7dd160eb2613d7ce3d6","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"c7b934d532c3b5d79d29d9130c3ab4f97028c3c1aa16422bb9101d84ad828729","text":"Support building PostgreSQL with OpenSSL 4 (Daniel Gustafsson) §","title":"Support building PostgreSQL with OpenSSL 4"},"id":"18.6-48c6d3c86320b73f","matches":[{"id":"17.11-f6b857a06e35de57","source_entry_id":"17.11/changes/108","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Support building PostgreSQL with OpenSSL 4","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/139","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Support building PostgreSQL with OpenSSL 4","version":"18.6"},{"entry":{"category":"improvement","commit_aliases":["3c16aa293","5f67124fa","669438aed","6ca405938","796c275a0","812cc1a73","af7be5672"],"commit_groups":[["3c16aa293","5f67124fa","669438aed","6ca405938","796c275a0","812cc1a73","af7be5672"]],"commits":["5f67124fa"],"cves":[],"db_id":"5d6e219dd117842cc9b25b660af47952","html":"\u003cp\u003eUpdate time zone data files to \u003cspan\u003etzdata\u003c/span\u003e release 2026c (Tom Lane) \u003ca href=\"https://postgr.es/c/5f67124fa\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAlberta (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 \u003ccode\u003eCST\u003c/code\u003e from that time forward. That seems likely to change, but it's unclear what new abbreviation will be used.\u003c/p\u003e\n\u003cp\u003eMorocco (Africa/Casablanca) will move to permanent UTC+00, without daylight saving time transitions, on 2026-09-20.\u003c/p\u003e","id":"18.6-d9abf44820fbecc5","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.","part":"changes","patch_ids":["b4e9971495e6df3bcbb5661de594cfb5"],"relations":[{"evidence":{"patch_ids":["b4e9971495e6df3bcbb5661de594cfb5"],"same_day":true,"statement_hash":"db30f9e9494e81ad745b38acebea395f96ce2c6e6fd0e722f568326a3b8491a7"},"rule":2,"target":"163da88262eec7e167bed3e56a48dcc3","type":"equivalent"},{"evidence":{"patch_ids":["b4e9971495e6df3bcbb5661de594cfb5"],"same_day":true,"statement_hash":"db30f9e9494e81ad745b38acebea395f96ce2c6e6fd0e722f568326a3b8491a7"},"rule":2,"target":"6c00ccb389c691ec829366a2dd6d8fd7","type":"equivalent"},{"evidence":{"patch_ids":["b4e9971495e6df3bcbb5661de594cfb5"],"same_day":true,"statement_hash":"db30f9e9494e81ad745b38acebea395f96ce2c6e6fd0e722f568326a3b8491a7"},"rule":2,"target":"ae8d1b295c148a9982765709cf1583a9","type":"equivalent"},{"evidence":{"patch_ids":["b4e9971495e6df3bcbb5661de594cfb5"],"same_day":true,"statement_hash":"db30f9e9494e81ad745b38acebea395f96ce2c6e6fd0e722f568326a3b8491a7"},"rule":2,"target":"afb53916a223205ed20435542f0bacc1","type":"equivalent"}],"section":"Changes","section_path":["Changes"],"source_commits":["5f67124fa"],"source_entry_id":"18.6/changes/140","source_hash":"b5d88332184a238e737bbc48bbbe3050925043c34b0b9fca1b100be6365fb68c","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"db30f9e9494e81ad745b38acebea395f96ce2c6e6fd0e722f568326a3b8491a7","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"},"id":"18.6-d9abf44820fbecc5","matches":[{"id":"17.11-8abc326e9afc0d23","source_entry_id":"17.11/changes/109","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Update time zone data files to tzdata release 2026c","version":"17.11"}],"method":"commits","reason":"already_in_source","source_entry_id":"18.6/changes/140","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","title":"Update time zone data files to tzdata release 2026c","version":"18.6"}],"from_release":{"age_days":91,"build":"17.11","changes_count":109,"compatibility_count":0,"content_hash":"f74d21ad6247b97678eefe3bead018fa4ee58db3a76e7c54b095617c6f080c7e","date":"2026-08-13","date_text":"2026-08-13","doc_git":"","doc_loaded_at":"2026-09-25T02:22:44.760693","entry_count":109,"eol":"2029-11-08","eol_date":"2029-11-08","label":"17.11","major":"17","manual":"17","manual_build":"17.11","manual_url":"/docs/17/release-17-11.html","migration_html":"\u003cp\u003eA dump/restore is not required for those running 17.X.\u003c/p\u003e\n\u003cp\u003eHowever, the first three security entries below describe configuration adjustments and data cleanups that you may need to make after updating.\u003c/p\u003e\n\u003cp\u003eAlso, if you use \u003ccode\u003econtrib/btree_gist\u003c/code\u003e or \u003ccode\u003econtrib/ltree\u003c/code\u003e, you may need to reindex indexes made with those extensions; see the relevant entries below.\u003c/p\u003e\n\u003cp\u003eAlso, if you are upgrading from a version earlier than 17.6, see \u003ca href=\"/docs/17/release-17-6.html\" title=\"E.6. Release 17.6\"\u003eSection E.6\u003c/a\u003e.\u003c/p\u003e","minor":11,"placeholder":false,"source_as_of":"","source_url":"/docs/release/17.11/","status":"stable","status_label":"Supported","support_days":1092,"supported":true,"version":"17.11"},"groups":[{"age_days":91,"build":"18.6","changes_count":140,"compatibility_count":0,"content_hash":"575a5072ec6e2481991ad0b4cdb89c632870708db9b883a92a47d5e531533bab","date":"2026-08-13","date_text":"2026-08-13","doc_git":"","doc_loaded_at":"2026-09-25T02:22:44.760693","entries":[{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["1232f7a08","5707d7517","d4420a972"],"commit_groups":[["1232f7a08","5707d7517","d4420a972"]],"commits":["d4420a972"],"cves":[],"db_id":"2bea73c0e3659c8ea68597bc29d434fd","html":"\u003cp\u003eEnsure that parallel GIN index builds update the table's \u003ccode\u003epg_class\u003c/code\u003e.\u003ccode\u003ereltuples\u003c/code\u003e value correctly (Jan Nidzwetzki, Tomas Vondra) \u003ca href=\"https://postgr.es/c/d4420a972\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA parallel worker could report an uninitialized value for the number of rows it processed, leading to a bogus value for \u003ccode\u003ereltuples\u003c/code\u003e, 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 \u003ccode\u003eANALYZE\u003c/code\u003e command, or creation of another index, will be needed to reset \u003ccode\u003ereltuples\u003c/code\u003e to the correct value. If you have any tables with GIN indexes, it's recommended to check to see if their \u003ccode\u003ereltuples\u003c/code\u003e entries look sane. A query such as this may be helpful:\u003c/p\u003e\n\u003cpre\u003eSELECT 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\u003c/pre\u003e","id":"18.6-771506a0ec518830","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;","part":"changes","patch_ids":["3ba1d61fdeb3854b8d7595ad4bc67069"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["d4420a972"],"source_entry_id":"18.6/changes/029","source_hash":"42d01e124a3d70ce5a6d4df2a04917ae62cfd6ff67c4928b7730b4452367807c","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"5febee3004e16621892415adb2d6ad17f0f816a84f510b674120400b485b14ac","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","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["1ef917e3a","b43f8aa4c","bba4e095d"],"commit_groups":[["1ef917e3a","b43f8aa4c"],["bba4e095d"]],"commits":["1ef917e3a","bba4e095d"],"cves":[],"db_id":"2b8134603cff445d9ecd4c835cbe2a6e","html":"\u003cp\u003eCorrectly update foreign-data-wrapper state in a ModifyTable plan node after pruning result relations (Ayush Tiwari, Rafia Sabih) \u003ca href=\"https://postgr.es/c/1ef917e3a\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/bba4e095d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, 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.\u003c/p\u003e","id":"18.6-1cf05c7dcd8bb2fd","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.","part":"changes","patch_ids":["46e6b35613de84cd63addb686c943afb","7972012e2e1068ee15bfecc0258e4f2a"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["1ef917e3a","bba4e095d"],"source_entry_id":"18.6/changes/032","source_hash":"9097b4cd39a85f24d5f6c0e2fa3135319dd9d272e7e93aca7e7e9932563698d2","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"c3f25655c3d5080eb4703b55d0bbd7dd434df2bff0f889c492e293272595f57d","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","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["4908225be","7048e50f8","8e0c25275"],"commit_groups":[["4908225be","7048e50f8","8e0c25275"]],"commits":["4908225be"],"cves":[],"db_id":"fbbb19f32ec43a1cb37d29840b3ffba1","html":"\u003cp\u003eFix missed concurrent update in \u003ccode\u003eUPDATE\u003c/code\u003e with \u003ccode\u003eRETURNING OLD\u003c/code\u003e on a table that has a \u003ccode\u003eBEFORE UPDATE\u003c/code\u003e trigger (Dean Rasheed) \u003ca href=\"https://postgr.es/c/4908225be\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf the target row was concurrently updated, then at isolation level \u003ccode\u003eREAD COMMITTED\u003c/code\u003e any \u003ccode\u003eOLD\u003c/code\u003e values in \u003ccode\u003eRETURNING\u003c/code\u003e 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).\u003c/p\u003e","id":"18.6-4a48d24c7f8eeec1","identity_text":"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).","part":"changes","patch_ids":["ba9cbda53c7ab8bd59e73bf84160ded4"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["4908225be"],"source_entry_id":"18.6/changes/033","source_hash":"b761e87f81a802b4cdb47ed7bd4e83b79a60f4a2bbf726d3415f48af1496e5e4","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"aea68a315f610feeca9a2fad2bcebca8668a9368972950c35281611fd541da43","text":"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).","title":"Fix missed concurrent update in UPDATE with RETURNING OLD on a table that has a BEFORE UPDATE trigger","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["60826a352","a71a348ed","f70acc8a2"],"commit_groups":[["60826a352","a71a348ed","f70acc8a2"]],"commits":["f70acc8a2"],"cves":[],"db_id":"b86d64491c7200dcd007d54d6a962628","html":"\u003cp\u003eFix hash join performance issue when there are multiple join keys and many NULL values (David Rowley) \u003ca href=\"https://postgr.es/c/f70acc8a2\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eNull-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.\u003c/p\u003e","id":"18.6-a0aeb22946500334","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.","part":"changes","patch_ids":["697f23d3ba44fd5f0f409f3e57d332b0"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["f70acc8a2"],"source_entry_id":"18.6/changes/034","source_hash":"a2215a6115900b68d1877c40187dbb0cf3142d42635ac903a285d313f595979c","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"9cb938e6d1f9c4bd4956e1e17c2a8c000498ab703f9836c62d8937f30c3dfeaf","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","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["79c65b9d9","9108fed3e"],"commit_groups":[["79c65b9d9","9108fed3e"]],"commits":["9108fed3e"],"cves":[],"db_id":"79eb93008caad05e495b986eed1eb67c","html":"\u003cp\u003eFix parsing of parenthesized \u003ccode\u003eOLD\u003c/code\u003e/\u003ccode\u003eNEW\u003c/code\u003e in \u003ccode\u003eRETURNING\u003c/code\u003e expressions (Marko Grujic) \u003ca href=\"https://postgr.es/c/9108fed3e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eExpressions such as \u003ccode\u003e(old).colname\u003c/code\u003e and \u003ccode\u003e(old).*\u003c/code\u003e were mis-handled, effectively converting them to \u003ccode\u003eNEW\u003c/code\u003e references.\u003c/p\u003e","id":"18.6-c5b329365b75d540","identity_text":"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.","part":"changes","patch_ids":["4c43aac234add994672d46a55527fdbf"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["9108fed3e"],"source_entry_id":"18.6/changes/035","source_hash":"c6a8a9fbeafe11c6131fb7a5a843ce5f2eceee4f1af9a2196cc1927a5814db55","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"ec910567dfb23a9d7844fbbba2a2c51eb550d149387df0ae3a4a4222bb4c3f01","text":"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.","title":"Fix parsing of parenthesized OLD/NEW in RETURNING expressions","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["18105e6db","9a60f295b","aae47813a","d68576bcf","e02526795"],"commit_groups":[["18105e6db","aae47813a","d68576bcf"],["9a60f295b","e02526795"]],"commits":["18105e6db","e02526795"],"cves":[],"db_id":"7287a2439ac16ed2b13a58ded903d600","html":"\u003cp\u003eClean up PlaceHolderVars more thoroughly during join removal (Richard Guo, Arne Roland) \u003ca href=\"https://postgr.es/c/e02526795\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/18105e6db\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis fix corrects various edge cases that could trip assertions or result in incorrect plans.\u003c/p\u003e","id":"18.6-86d838ba82cd928b","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.","part":"changes","patch_ids":["dad98679fdb945f46899a1cf96a43235","efd98d1529cbbfc26850e87cacb3d2d3"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["18105e6db","e02526795"],"source_entry_id":"18.6/changes/038","source_hash":"7baeb4799ba10a67535a51042cb67368e6f775deb642040394941009b4d2631c","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"8ac2ba046ee3e00a0a68bc894a425dc73015f576c3ed6cc93d8f10f0a991adec","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","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["44fb59fc6","98d5d7ee6","fe5d62951"],"commit_groups":[["44fb59fc6","98d5d7ee6","fe5d62951"]],"commits":["fe5d62951"],"cves":[],"db_id":"8a5302ba87723cdae5cab329b237ef44","html":"\u003cp\u003eAvoid pushing \u003ccode\u003eWHERE\u003c/code\u003e clauses down past a grouping step that has a different equivalence rule (Richard Guo) \u003ca href=\"https://postgr.es/c/fe5d62951\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA 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.\u003c/p\u003e","id":"18.6-671435cc27948d1c","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.","part":"changes","patch_ids":["797e4b8a009ec7e54b9f5e0d46c255b2"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["fe5d62951"],"source_entry_id":"18.6/changes/040","source_hash":"48b740a410e4123a116a78b26c3c7594ce144c3b75195fbc3b847e3990659bc6","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"06dd2db2f4d9fa1b243241abc89c3c8c94b969cacd2dee10ca07caa830e7c4e4","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","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["5fd1c3f28","b574fec00"],"commit_groups":[["5fd1c3f28","b574fec00"]],"commits":["5fd1c3f28"],"cves":[],"db_id":"d6878f50541a70b023c90d9e051b3fb6","html":"\u003cp\u003eAvoid \u003cspan\u003e“\u003cspan\u003ecache lookup failed for collation 0\u003c/span\u003e”\u003c/span\u003e error when planner looks up statistics for a column of type \u003ccode\u003e\"char\"\u003c/code\u003e (Feng Wu) \u003ca href=\"https://postgr.es/c/5fd1c3f28\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-e9b3bdb4cdd524a5","identity_text":"Avoid cache lookup failed for collation 0 error when planner looks up statistics for a column of type \"char\" (Feng Wu)","part":"changes","patch_ids":["aea4547f9be1d54480260af7050fe78c"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["5fd1c3f28"],"source_entry_id":"18.6/changes/042","source_hash":"dd4b08a6595545a2c1c1ff9ec924de615c5f6c84d431b29d58a62baf63592d29","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"c280be416f006943228456cda29cfb50069cc80bdb27fe6737fe18248d002388","text":"Avoid “cache lookup failed for collation 0” error when planner looks up statistics for a column of type \"char\" (Feng Wu) §","title":"Avoid “cache lookup failed for collation 0” error when planner looks up statistics for a column of type \"char\"","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["41247cdf6","d8b5d87e5"],"commit_groups":[["41247cdf6","d8b5d87e5"]],"commits":["41247cdf6"],"cves":[],"db_id":"7f94bd8f2b3eaf108733e19761f28b5c","html":"\u003cp\u003ePrevent setting \u003ccode\u003eNO INHERIT\u003c/code\u003e on partitioned \u003ccode\u003eNOT NULL\u003c/code\u003e constraints via \u003ccode\u003eALTER CONSTRAINT\u003c/code\u003e (Andreas Karlsson) \u003ca href=\"https://postgr.es/c/41247cdf6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eNOT NULL\u003c/code\u003e constraints on partitioned tables are supposed to be inherited by all partitions, and therefore must not be marked \u003ccode\u003eNO INHERIT\u003c/code\u003e. This rule was correctly enforced by constraint creation, but not by \u003ccode\u003eALTER TABLE ... ALTER CONSTRAINT\u003c/code\u003e.\u003c/p\u003e","id":"18.6-b5bc23b2ba1a7eec","identity_text":"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.","part":"changes","patch_ids":["bf2253b466db4457c0859fe6a2584679"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["41247cdf6"],"source_entry_id":"18.6/changes/045","source_hash":"0601f5b0e3d77a5ffcfbcba09f3f3dcbd5535739b32c8f3325eb9893d808dbca","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"ce6fffbf1beb8c7b56093e97c9b54cab8422e5f127c4c6ebe3d89431038aba0f","text":"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.","title":"Prevent setting NO INHERIT on partitioned NOT NULL constraints via ALTER CONSTRAINT","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["42b7ff3aa","51652c42d","54d5947ef","99775b388","a99bd8d58","d6ffcae32"],"commit_groups":[["42b7ff3aa","51652c42d","54d5947ef"],["99775b388","a99bd8d58","d6ffcae32"]],"commits":["51652c42d","a99bd8d58"],"cves":[],"db_id":"d3cce82763a46bec6558823f526096ae","html":"\u003cp\u003eFix \u003ccode\u003eLIKE\u003c/code\u003e matching with nondeterministic collations and backslashes (Nitin Motiani, Tom Lane) \u003ca href=\"https://postgr.es/c/a99bd8d58\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/51652c42d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWhen using a nondeterministic collation, \u003ccode\u003eLIKE\u003c/code\u003e mishandled an escaped backslash (\u003ccode\u003e\\\\\u003c/code\u003e), 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.\u003c/p\u003e","id":"18.6-99dd4ced91d2437b","identity_text":"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.","part":"changes","patch_ids":["42e518e106517fa6c599c068344cdcc4","f06fdeb7d5c2c1ca22a3727e6c57386b"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["51652c42d","a99bd8d58"],"source_entry_id":"18.6/changes/050","source_hash":"8053f101d3b3b3a24a71b0da4963bb9ccc1dee666d0f88129be89f8cf5e9d3c1","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"e18a833d191731a4c5d47cd2d7f022d5acf10e11b8701241a22b6f63a41510a8","text":"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.","title":"Fix LIKE matching with nondeterministic collations and backslashes","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["2d7808e6f","67cf73ddb","d0bb49e61"],"commit_groups":[["2d7808e6f","67cf73ddb","d0bb49e61"]],"commits":["d0bb49e61"],"cves":[],"db_id":"753e54987dcf92d3f495233f193ef239","html":"\u003cp\u003eFix \u003ccode\u003eLIKE\u003c/code\u003e/regex optimization for indexscan with exact-match pattern (Jelte Fennema-Nio) \u003ca href=\"https://postgr.es/c/d0bb49e61\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eRefactoring for \u003ccode\u003eLIKE\u003c/code\u003e with non-deterministic collations accidentally broke the optimization for converting a \u003ccode\u003eLIKE\u003c/code\u003e 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 \u003cspan\u003epsql\u003c/span\u003e's \u003ccode\u003e\\d \u003cem\u003e\u003ccode\u003etablename\u003c/code\u003e\u003c/em\u003e\u003c/code\u003e command much slower.\u003c/p\u003e","id":"18.6-5d12ae4d78fa8033","identity_text":"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 tablename command much slower.","part":"changes","patch_ids":["54018fbe657a62243f1d69e443acc9f5"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["d0bb49e61"],"source_entry_id":"18.6/changes/051","source_hash":"5a44a696271b577cddcb781f5f9685b07ed794e99ca025610139ddf026577fde","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"221ab631be4dde5f6e7bd8b02b6811e63a505d1f7cf2eee944bcec8f7d145e60","text":"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 tablename command much slower.","title":"Fix LIKE/regex optimization for indexscan with exact-match pattern","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["011384ba4","0de744cd5","49a712f32","55ea76426","5f003855e","8acfaa12a","b594efe52","fd2b89854"],"commit_groups":[["011384ba4","0de744cd5","49a712f32","55ea76426","8acfaa12a","b594efe52","fd2b89854"],["5f003855e"]],"commits":["011384ba4","5f003855e"],"cves":[],"db_id":"eb74da46a95f0db0c15adface2feaffa","html":"\u003cp\u003eFix matching of localized month/day names in \u003ccode\u003eto_date()\u003c/code\u003e (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/011384ba4\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/5f003855e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe matching logic misbehaved in cases where case-folding changes the byte length of the string.\u003c/p\u003e","id":"18.6-937d0b3149314116","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.","part":"changes","patch_ids":["34110329d25e6401c920fba619dc5a15","b8ca654311e23485845960b9d01e76fc"],"related_changes":[{"db_id":"b0d8986fede0f1216361d5a43a076e4e","evidence":{"patch_ids":["b8ca654311e23485845960b9d01e76fc"],"same_day":true,"statement_hash":"ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"},"kind":"related","label":"17.11","source_url":"/docs/release/17.11/#RELEASE-17-11-CHANGES","title":"Fix matching of localized month/day names in to_date()","url":"/docs/compare/?release=17.11#17.11-8557fc5fb2204540","version":"17.11"},{"db_id":"08bd69e7cd8f7b8bd4623958f924ac19","evidence":{"patch_ids":["b8ca654311e23485845960b9d01e76fc"],"same_day":true,"statement_hash":"ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"},"kind":"related","label":"16.15","source_url":"/docs/release/16.15/#RELEASE-16-15-CHANGES","title":"Fix matching of localized month/day names in to_date()","url":"/docs/compare/?release=16.15#16.15-6af7d41f64cafafa","version":"16.15"},{"db_id":"0800233346f3a252c62d9a6f579d5573","evidence":{"patch_ids":["b8ca654311e23485845960b9d01e76fc"],"same_day":true,"statement_hash":"ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"},"kind":"related","label":"15.19","source_url":"/docs/release/15.19/#id-1.11.6.6.5","title":"Fix matching of localized month/day names in to_date()","url":"/docs/compare/?release=15.19#15.19-a96cc8b4c22ffe2e","version":"15.19"},{"db_id":"d3800c6695b429dd746c574f0d0d93e5","evidence":{"patch_ids":["b8ca654311e23485845960b9d01e76fc"],"same_day":true,"statement_hash":"ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"},"kind":"related","label":"14.24","source_url":"/docs/release/14.24/#id-1.11.6.6.6","title":"Fix matching of localized month/day names in to_date()","url":"/docs/compare/?release=14.24#14.24-8ab3e783a00643a8","version":"14.24"}],"relations":[{"evidence":{"patch_ids":["b8ca654311e23485845960b9d01e76fc"],"same_day":true,"statement_hash":"ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"},"rule":2,"target":"0800233346f3a252c62d9a6f579d5573","type":"related"},{"evidence":{"patch_ids":["b8ca654311e23485845960b9d01e76fc"],"same_day":true,"statement_hash":"ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"},"rule":2,"target":"08bd69e7cd8f7b8bd4623958f924ac19","type":"related"},{"evidence":{"patch_ids":["b8ca654311e23485845960b9d01e76fc"],"same_day":true,"statement_hash":"ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"},"rule":2,"target":"b0d8986fede0f1216361d5a43a076e4e","type":"related"},{"evidence":{"patch_ids":["b8ca654311e23485845960b9d01e76fc"],"same_day":true,"statement_hash":"ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da"},"rule":2,"target":"d3800c6695b429dd746c574f0d0d93e5","type":"related"}],"section":"Changes","section_path":["Changes"],"source_commits":["011384ba4","5f003855e"],"source_entry_id":"18.6/changes/052","source_hash":"9fe2ae50e9bfc4ced876406d6b2428ee94aab62e6e58788cfe5038327a31c0c3","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"ef6d4c6554fba5da9f815beec3f0b6e84e2334ba9bd093035db08b8e3c61e1da","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()","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["28d498e28","368693689","66ec24276"],"commit_groups":[["28d498e28","368693689","66ec24276"]],"commits":["66ec24276"],"cves":[],"db_id":"b26cb5804188e11182113acfa2af2f06","html":"\u003cp\u003eCorrect case-folding rules for Greek final sigma (Jeff Davis) \u003ca href=\"https://postgr.es/c/66ec24276\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf the string is preceded only by Case Ignorable characters, don't consider it to be a final sigma. This only affects the built-in \u003ccode\u003epg_unicode_fast\u003c/code\u003e locale.\u003c/p\u003e","id":"18.6-e4b72f9a6fc1a4a4","identity_text":"Correct case-folding rules for Greek final sigma (Jeff Davis) If 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.","part":"changes","patch_ids":["1194cd191de15fbe8bba89681ad47d4f"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["66ec24276"],"source_entry_id":"18.6/changes/053","source_hash":"89b5c46c4733b4076a027d5c599960f5478741668ea5f7bcdef1b17a83461c17","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"9ed6169c6ff51444837f797efaede7d8883cd9cba60472cbf5129bc51729553f","text":"Correct case-folding rules for Greek final sigma (Jeff Davis) § If 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.","title":"Correct case-folding rules for Greek final sigma","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["2a933deaa","7575215e0","c31b0fca0"],"commit_groups":[["2a933deaa","7575215e0","c31b0fca0"]],"commits":["c31b0fca0"],"cves":[],"db_id":"4ba47e1101fe0dc93dfdf09978a397f7","html":"\u003cp\u003eReject out-of-range timestamp shift values in \u003ccode\u003euuidv7()\u003c/code\u003e (Baji Shaik) \u003ca href=\"https://postgr.es/c/c31b0fca0\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e","id":"18.6-54da379f0b9b3e5e","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.","part":"changes","patch_ids":["98b79989c57e289aff70a4f3cb8d7680"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["c31b0fca0"],"source_entry_id":"18.6/changes/061","source_hash":"02eb6fc1f39bf79a5e9ad65d69a91d28ac6cdc3b2f7832b8811f2fd6ad0fff1f","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"30752f07a027de559876959a4bd468e260cc47a4bc30f24960ea23366b39f35e","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()","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["da6874635","ed8050370"],"commit_groups":[["da6874635","ed8050370"]],"commits":["ed8050370"],"cves":[],"db_id":"fdb4c4b82ee3d59d1982ef4cb1f2f0f8","html":"\u003cp\u003ePrevent \u003cspan\u003e“\u003cspan\u003eno empty local buffer available\u003c/span\u003e”\u003c/span\u003e errors during temporary table access (Melanie Plageman) \u003ca href=\"https://postgr.es/c/ed8050370\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eLimit the number of local buffers that the read streaming mechanism is allowed to use. Previously, a large value of \u003ccode\u003eeffective_io_concurrency\u003c/code\u003e could allow a single stream to use all the buffers, resulting in failure.\u003c/p\u003e","id":"18.6-d9671d1ad39e8c30","identity_text":"Prevent no empty local buffer available errors during temporary table access (Melanie Plageman) Limit 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.","part":"changes","patch_ids":["e9321701f611ce406a35624c7852e55d"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["ed8050370"],"source_entry_id":"18.6/changes/070","source_hash":"eea40f81f27d58cd717745f20b9ba263701124698ee98272324b76b841964ec9","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"323a6fc70b6374b70a2d5b8caebf92b3650ad3bd87152ba5e49dea1f6f5a78ae","text":"Prevent “no empty local buffer available” errors during temporary table access (Melanie Plageman) § Limit 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.","title":"Prevent “no empty local buffer available” errors during temporary table access","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["112c26838","55d01a10f","585181e07","69800557c","7c25cdb1e","fd90c3221"],"commit_groups":[["112c26838","585181e07","fd90c3221"],["55d01a10f","69800557c","7c25cdb1e"]],"commits":["585181e07","7c25cdb1e"],"cves":[],"db_id":"76e68f03af84d570f09339ccddb5ec37","html":"\u003cp\u003eRestore full use of shared buffer pool in \u003ccode\u003eVACUUM\u003c/code\u003e's wraparound failsafe mode (Melanie Plageman) \u003ca href=\"https://postgr.es/c/585181e07\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/7c25cdb1e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAn ordinary \u003ccode\u003eVACUUM\u003c/code\u003e 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.\u003c/p\u003e","id":"18.6-732f82763dbae3c0","identity_text":"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.","part":"changes","patch_ids":["1fc4d5a35015217cd94108fd4bd6d947","92ef90f96599873178ce78032e30cbe9"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["585181e07","7c25cdb1e"],"source_entry_id":"18.6/changes/072","source_hash":"6f1301b14ed11056046aad98d40511bc44e939608e1e6c09060adde68d5f6bbe","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"5041354134b66b31841763d6cb312cb27def4c034a45ad9239094c97892a9b35","text":"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.","title":"Restore full use of shared buffer pool in VACUUM's wraparound failsafe mode","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["dc5116780","e9692de1d"],"commit_groups":[["dc5116780","e9692de1d"]],"commits":["e9692de1d"],"cves":[],"db_id":"5d966088a095e18332fc3fae2df8943c","html":"\u003cp\u003eFix JIT-compiled tuple deconstruction code to account correctly for virtual generated columns (David Rowley) \u003ca href=\"https://postgr.es/c/e9692de1d\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-33623243926bee4f","identity_text":"Fix JIT-compiled tuple deconstruction code to account correctly for virtual generated columns (David Rowley)","part":"changes","patch_ids":["5b06ca9ccac80b782c6215117ad2b6f3"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["e9692de1d"],"source_entry_id":"18.6/changes/079","source_hash":"d8b6408afef1a01cea4ed9e7255b21a66f6a2269a77fb40199d08aed00ee87a7","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"108a7033ad22cb766018c23cec70aac4e45d29f7e41fbdfe619f05d9039da69e","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","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["311e66df9","7673dfe77","b59783502"],"commit_groups":[["311e66df9","7673dfe77","b59783502"]],"commits":["311e66df9"],"cves":[],"db_id":"ca322b7422c7864dcfe83a827441f183","html":"\u003cp\u003ePrevent accepting hot-standby connections before WAL replay has reached a consistent database state (Nikhil Sontakke) \u003ca href=\"https://postgr.es/c/311e66df9\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-fe809e2024f47bd3","identity_text":"Prevent accepting hot-standby connections before WAL replay has reached a consistent database state (Nikhil Sontakke)","part":"changes","patch_ids":["c006640df5f2be4c0af354adc9b3739e"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["311e66df9"],"source_entry_id":"18.6/changes/093","source_hash":"8b317869ae141be91e8dec8efd1716dafab967ff2900378e9d1e5e1a60e43286","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"c2216840c8e764a88ae341a1741319888a2b275d882def3b439922ca5a525ddc","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","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["13f940b4b","3048e8130"],"commit_groups":[["13f940b4b","3048e8130"]],"commits":["13f940b4b"],"cves":[],"db_id":"eb60b9ab1b9e4814af98c8013ccaaefc","html":"\u003cp\u003eAvoid recording incorrect I/O operation statistics after a failed read or write (Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/13f940b4b\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-62f8d7fac7e94f66","identity_text":"Avoid recording incorrect I/O operation statistics after a failed read or write (Bertrand Drouvot)","part":"changes","patch_ids":["51ef28bcac96b451b9c22362030f5034"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["13f940b4b"],"source_entry_id":"18.6/changes/101","source_hash":"8c2ec8b48869b5269106dca7f2cac2aa798943ce27c0456e0988651fa1953022","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"1ee5c678ab1708424e1e440c9385d800ef55fb4ff8fab375174baaad825421f1","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","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["676bf48e1","6b46a5d1b","8380013cd"],"commit_groups":[["676bf48e1","6b46a5d1b","8380013cd"]],"commits":["6b46a5d1b"],"cves":[],"db_id":"702619bca4eafa5ec897c54c44899700","html":"\u003cp\u003eImprove \u003cspan\u003elibpq\u003c/span\u003e's handling of out-of-memory conditions (Anthonin Bonnefoy) \u003ca href=\"https://postgr.es/c/6b46a5d1b\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-1ca0e17d82442acb","identity_text":"Improve libpq's handling of out-of-memory conditions (Anthonin Bonnefoy)","part":"changes","patch_ids":["ac21c3ce2ae02e085ed3866481058001"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["6b46a5d1b"],"source_entry_id":"18.6/changes/105","source_hash":"38431992340fffe07fa78ab8d91ba4e891f245a36569221cb9ed86b13074c4bf","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"eec6ec640464f740117d7e235a58f7b9f7d0ab46f08ef5a5d2037538eab150c9","text":"Improve libpq's handling of out-of-memory conditions (Anthonin Bonnefoy) §","title":"Improve libpq's handling of out-of-memory conditions","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["0766bc57e","b22b61905","dd5eca055"],"commit_groups":[["0766bc57e","b22b61905","dd5eca055"]],"commits":["dd5eca055"],"cves":[],"db_id":"fd5dcb29b0fd1252d10a21b8c0cdcb8c","html":"\u003cp\u003eFix \u003cspan\u003elibpq\u003c/span\u003e's trace facility to print new-style BackendKeyData and CancelRequest messages correctly (Anthonin Bonnefoy) \u003ca href=\"https://postgr.es/c/dd5eca055\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-2070f350641c3bd5","identity_text":"Fix libpq's trace facility to print new-style BackendKeyData and CancelRequest messages correctly (Anthonin Bonnefoy)","part":"changes","patch_ids":["c7d629e80647c3be8fd73079d8a1b5ce"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["dd5eca055"],"source_entry_id":"18.6/changes/106","source_hash":"5f13cf168ff8b4075ae64e38a62713e18f734eca0e447ebefd908379324afed9","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"f7529c3c3921210742bad5f01a4dc3306780887b530249441e741d2209b3e067","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","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["7f5e0b22e","917fdbc63"],"commit_groups":[["7f5e0b22e","917fdbc63"]],"commits":["917fdbc63"],"cves":[],"db_id":"3efdef76585f7653700d42263bf2fcd4","html":"\u003cp\u003eFix null-pointer crash in \u003cspan\u003eecpg\u003c/span\u003e compiler (Jehan-Guillaume de Rorthais) \u003ca href=\"https://postgr.es/c/917fdbc63\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003eecpg\u003c/span\u003e failed on a \u003ccode\u003eDECLARE\u003c/code\u003e section containing a union nested inside a struct.\u003c/p\u003e","id":"18.6-7aa882d7346d6ba9","identity_text":"Fix null-pointer crash in ecpg compiler (Jehan-Guillaume de Rorthais) ecpg failed on a DECLARE section containing a union nested inside a struct.","part":"changes","patch_ids":["4f49070aa0244314298c6e53b2ca3663"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["917fdbc63"],"source_entry_id":"18.6/changes/108","source_hash":"0b2598c72b6398d45e95b27238d52a344421e109b788b5775ec2bc0b0f1c4fd3","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"73d8bc20ea111e6babb09147ca348cbbc92d82d0ad4603e1379ed894c6013189","text":"Fix null-pointer crash in ecpg compiler (Jehan-Guillaume de Rorthais) § ecpg failed on a DECLARE section containing a union nested inside a struct.","title":"Fix null-pointer crash in ecpg compiler","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["1e9bc4074","d21604e17"],"commit_groups":[["1e9bc4074","d21604e17"]],"commits":["1e9bc4074"],"cves":[],"db_id":"72a7f65480654f93eac8950b0559cbc0","html":"\u003cp\u003eFix issues with deferred errors in pipeline mode in \u003cspan\u003epsql\u003c/span\u003e (Michael Paquier) \u003ca href=\"https://postgr.es/c/1e9bc4074\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003epsql\u003c/span\u003e 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.\u003c/p\u003e","id":"18.6-37072fc5e593b9ae","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.","part":"changes","patch_ids":["fd3b0e71a3f8eb28e4ab3713dc100752"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["1e9bc4074"],"source_entry_id":"18.6/changes/110","source_hash":"0b6a251cbdd63ef30c411a5700968044736d26485b0b2c00c8ca1c01814cb13e","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"9b5d97f70333cd1039a7854f6dd2a1fd15944a41f9681c94182b6c05e41f7ed4","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","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["e04910a9a","e0c641ebb"],"commit_groups":[["e04910a9a","e0c641ebb"]],"commits":["e0c641ebb"],"cves":[],"db_id":"da4e14855386a41b1b007342405420fd","html":"\u003cp\u003eEnforce the intended upper limit for \u003cspan\u003epsql\u003c/span\u003e's special variable \u003ccode\u003eWATCH_INTERVAL\u003c/code\u003e (Sven Klemm, Daniel Gustafsson) \u003ca href=\"https://postgr.es/c/e0c641ebb\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf a too-large value was given, \u003cspan\u003epsql\u003c/span\u003e reported an error but applied the setting anyway.\u003c/p\u003e","id":"18.6-f4ed56f70dce1993","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.","part":"changes","patch_ids":["89fd801900bdac240cfcf7a7e686b427"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["e0c641ebb"],"source_entry_id":"18.6/changes/112","source_hash":"ab27f170112801ffa643398355061630ad04b9a25cfe9388df28aace143d3e11","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"642fd9555fa98a6c5630f67a94fa38617df76e4b28a80be73c949d4f69a344f4","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","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["0dd93de69","42ffdedcf","477efef08","ae39bd23c"],"commit_groups":[["0dd93de69","42ffdedcf"],["477efef08","ae39bd23c"]],"commits":["42ffdedcf","477efef08"],"cves":[],"db_id":"ec56aefa8b1230926a58d37ee31c1974","html":"\u003cp\u003eFix inconsistent behavior of \u003cspan\u003epg_restore\u003c/span\u003e with \u003ccode\u003e--statistics\u003c/code\u003e or \u003ccode\u003e--statistics-only\u003c/code\u003e (Chao Li, Michael Paquier) \u003ca href=\"https://postgr.es/c/42ffdedcf\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/477efef08\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWhen combined with other selective-restore options such as \u003ccode\u003e--schema\u003c/code\u003e, these options failed to restore the expected items, unlike \u003cspan\u003epg_dump\u003c/span\u003e with similar options.\u003c/p\u003e","id":"18.6-5e4a18698665afbd","identity_text":"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.","part":"changes","patch_ids":["23528d57fa6b8e93bbc4085e322c3a16","585fd7a6a1c8fb7d359e7696ae5c9036"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["42ffdedcf","477efef08"],"source_entry_id":"18.6/changes/119","source_hash":"2f735e665d48f5621e42b45aadc7897b37b9d5cfac2bdff2abaa34acc4f2914d","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"49ec3bc6d2ca19fc4494e1c248eb47cf2974fc96b5ea5b35c22d65a400e1a990","text":"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.","title":"Fix inconsistent behavior of pg_restore with --statistics or --statistics-only","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["7e085aabd","d2cea6306"],"commit_groups":[["7e085aabd","d2cea6306"]],"commits":["7e085aabd"],"cves":[],"db_id":"a508819f0cd2f3814bc2c3070f5f9bcb","html":"\u003cp\u003eFix \u003ccode\u003evacuumdb --missing-stats-only\u003c/code\u003e to ignore partitioned expression indexes (Baji Shaik) \u003ca href=\"https://postgr.es/c/7e085aabd\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, \u003cspan\u003evacuumdb\u003c/span\u003e would always attempt to \u003ccode\u003eANALYZE\u003c/code\u003e the partitioned table, accomplishing nothing since statistics are never created for partitioned indexes, only for their leaf indexes.\u003c/p\u003e","id":"18.6-159528afc9012599","identity_text":"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.","part":"changes","patch_ids":["4240972938f6b727b9c3afb7db256e7f"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["7e085aabd"],"source_entry_id":"18.6/changes/120","source_hash":"2a9bab9b5ef6ceed3a27a6d9cc371bc06c29fefbabb414181173326806d21eaf","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"d6b7dea0a810f8f989f969924d9f140e8c262ad79e5ce437c44240fe9086c126","text":"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.","title":"Fix vacuumdb --missing-stats-only to ignore partitioned expression indexes","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["12c32bbc8","389bd4c5b"],"commit_groups":[["12c32bbc8","389bd4c5b"]],"commits":["12c32bbc8"],"cves":[],"db_id":"a235ce1f79e91e8c29f992a04c38c0cb","html":"\u003cp\u003eIn \u003ccode\u003econtrib/amcheck\u003c/code\u003e, fix failure to report corruption of a btree metapage's \u003ccode\u003eallequalimage\u003c/code\u003e flag (Chao Li) \u003ca href=\"https://postgr.es/c/12c32bbc8\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-cb44e3b45014a3e4","identity_text":"In contrib/amcheck, fix failure to report corruption of a btree metapage's allequalimage flag (Chao Li)","part":"changes","patch_ids":["2e4cb447d88b8071d1cff1786b93723f"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["12c32bbc8"],"source_entry_id":"18.6/changes/121","source_hash":"d8601d714bc15658e9ee9e49b0efd8c042ab916c39bdc9d9b1fdfd11485a6947","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"ac30562981396990cd5820957e553598ded7456dc47ad4339afb6b62de628d15","text":"In contrib/amcheck, fix failure to report corruption of a btree metapage's allequalimage flag (Chao Li) §","title":"In contrib/amcheck, fix failure to report corruption of a btree metapage's allequalimage flag","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["1f8ab91c1","80cfd8aef","e939332c6"],"commit_groups":[["1f8ab91c1","80cfd8aef","e939332c6"]],"commits":["1f8ab91c1"],"cves":[],"db_id":"454cdc2db92dfb4e8f7196d6dda27a28","html":"\u003cp\u003eIn \u003ccode\u003econtrib/amcheck\u003c/code\u003e, fix query-lifespan memory leak while verifying a GIN index (Kirill Reshke) \u003ca href=\"https://postgr.es/c/1f8ab91c1\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.6-3b91fe80edf88a17","identity_text":"In contrib/amcheck, fix query-lifespan memory leak while verifying a GIN index (Kirill Reshke)","part":"changes","patch_ids":["21110d48c29396c2e4c5957c57b81507"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["1f8ab91c1"],"source_entry_id":"18.6/changes/122","source_hash":"901f5ee678dc754c8308afd39326a2d9000956927796d9753370e1266b06b575","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"d80d872dd78a4e0ed360096ae3e5ad9c0c6ded22c4417298383456624ac7476c","text":"In contrib/amcheck, fix query-lifespan memory leak while verifying a GIN index (Kirill Reshke) §","title":"In contrib/amcheck, fix query-lifespan memory leak while verifying a GIN index","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["11cb9c431","558c4ea9a","a9fa6c69e"],"commit_groups":[["11cb9c431","558c4ea9a","a9fa6c69e"]],"commits":["558c4ea9a"],"cves":[],"db_id":"3bd318bf985f65f08e4de889f9f7dc63","html":"\u003cp\u003eIn \u003ccode\u003econtrib/btree_gist\u003c/code\u003e, fix sorting of \u003ccode\u003ebit\u003c/code\u003e/\u003ccode\u003evarbit\u003c/code\u003e entries during GiST index construction (Tom Lane) \u003ca href=\"https://postgr.es/c/558c4ea9a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eValues of bit types were sorted as though they were \u003ccode\u003ebytea\u003c/code\u003es, 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 \u003ccode\u003ebtree_gist\u003c/code\u003e indexes on bit columns after installing this update.\u003c/p\u003e","id":"18.6-abc27a01f64c06e0","identity_text":"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.","part":"changes","patch_ids":["b1435c9263f45de040aa91c540d81bc4"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["558c4ea9a"],"source_entry_id":"18.6/changes/125","source_hash":"6919d8dbfe9b26d45a07162cc17efe9fccc0dbcb73cb5ce1a228db4bb3a492cb","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"2511024258be5eb09455cef6a97b8c951e38d2d4f39f80e6c5c02bdcc59a85d5","text":"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.","title":"In contrib/btree_gist, fix sorting of bit/varbit entries during GiST index construction","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["130396e6c","5f5165e2f","88d7748d2","97f6fc10f"],"commit_groups":[["130396e6c","5f5165e2f"],["88d7748d2","97f6fc10f"]],"commits":["130396e6c","88d7748d2"],"cves":[],"db_id":"063f2bffd0990ef3fcf1cfb885de863c","html":"\u003cp\u003eIn \u003ccode\u003econtrib/dblink\u003c/code\u003e and \u003ccode\u003econtrib/postgres_fdw\u003c/code\u003e, ensure that a user-mapping setting for \u003ccode\u003euse_scram_passthrough\u003c/code\u003e overrides one for a foreign server (Matheus Alcantara) \u003ca href=\"https://postgr.es/c/88d7748d2\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/130396e6c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously the precedence went the other way, but that is inconsistent with the behavior of other foreign-table options.\u003c/p\u003e","id":"18.6-3e71696a57ffc6a1","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.","part":"changes","patch_ids":["b1b74b0cc1463725747a8653fc6f9171","bd57ecb015393dce39ef90b46d9e0490"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["130396e6c","88d7748d2"],"source_entry_id":"18.6/changes/127","source_hash":"dbd1d91619b17788c51ca8c36aeebec53d14f2020589b52c793e5a750ad59f83","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"db8d7ee5007bfdda5824537bec6f7ef8dab92f90ad711e9f78d654634734b9ce","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","variants":[],"version":"18.6"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["cd777e27e","e2b881340"],"commit_groups":[["cd777e27e","e2b881340"]],"commits":["cd777e27e"],"cves":[],"db_id":"fcf062a479f1adf951f0e01ba9085269","html":"\u003cp\u003eReject setting \u003ccode\u003euse_scram_passthrough\u003c/code\u003e on \u003ccode\u003econtrib/dblink\u003c/code\u003e foreign-data wrappers (Matheus Alcantara) \u003ca href=\"https://postgr.es/c/cd777e27e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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).\u003c/p\u003e","id":"18.6-ff5e4d8a0c43e0de","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).","part":"changes","patch_ids":["42c3eee21590032a02c95eee1fb701ea"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["cd777e27e"],"source_entry_id":"18.6/changes/128","source_hash":"70de6bc6d249294e8fdeab1a24f46b7dd7ba562fcc13795d138d7ee697b1aa0f","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"901c22f80f76bf023745d17a817b1d44b8d41905f41f65deeb6c657adf7865a9","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","variants":[],"version":"18.6"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["3bf2cb225","dac36601f"],"commit_groups":[["3bf2cb225","dac36601f"]],"commits":["3bf2cb225"],"cves":[],"db_id":"deeb54842607dd110ef702b21efa1e40","html":"\u003cp\u003eFix out-of-bounds access in \u003ccode\u003econtrib/pg_prewarm\u003c/code\u003e's autoprewarm worker (Matheus Alcantara) \u003ca href=\"https://postgr.es/c/3bf2cb225\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe code tried to fetch a value from one past the end of an array, risking a segfault.\u003c/p\u003e","id":"18.6-4e6978b69317c416","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.","part":"changes","patch_ids":["b8e5ecd5e13f4cc5d49f2b89c1f08c28"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["3bf2cb225"],"source_entry_id":"18.6/changes/133","source_hash":"4fe07e991a81e828486f77914f9731842bee8fceb0d84b70e025b680b9f06924","source_url":"/docs/release/18.6/#RELEASE-18-6-CHANGES","statement_hash":"78dd0ea4ace46cf7dd61d2a6c030af907036f2e92bdfeaf6006e3958c5b09372","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","variants":[],"version":"18.6"}],"entry_count":140,"eol":"2030-11-14","eol_date":"2030-11-14","label":"18.6","major":"18","manual":"18","manual_build":"18.6","manual_url":"/docs/18/release-18-6.html","migration_html":"\u003cp\u003eA dump/restore is not required for those running 18.X.\u003c/p\u003e\n\u003cp\u003eHowever, the first three security entries below describe configuration adjustments and data cleanups that you may need to make after updating.\u003c/p\u003e\n\u003cp\u003eAlso, if you have any GIN indexes, see the changelog entry below about possibly-corrupt \u003ccode\u003ereltuples\u003c/code\u003e values for their tables.\u003c/p\u003e\n\u003cp\u003eAlso, if you use \u003ccode\u003econtrib/btree_gist\u003c/code\u003e or \u003ccode\u003econtrib/ltree\u003c/code\u003e, you may need to reindex indexes made with those extensions; see the relevant entries below.\u003c/p\u003e\n\u003cp\u003eAlso, if you are upgrading from a version earlier than 18.2, see \u003ca href=\"/docs/18/release-18-2.html\" title=\"E.4. Release 18.2\"\u003eSection E.4\u003c/a\u003e.\u003c/p\u003e","minor":6,"placeholder":false,"source_as_of":"","source_url":"/docs/release/18.6/","status":"stable","status_label":"Supported","support_days":1463,"supported":true,"version":"18.6"},{"age_days":182,"build":"18.4","changes_count":74,"compatibility_count":0,"content_hash":"5a493ad50c657f9f1d75227f03f55e685a5c3b253f73bbfbf0f5849ce14a1328","date":"2026-05-14","date_text":"2026-05-14","doc_git":"","doc_loaded_at":"2026-09-25T02:22:44.760693","entries":[{"also_in":[],"category":"security","category_label":"Security","commit_aliases":["661095c40","6d6348f03"],"commit_groups":[["661095c40","6d6348f03"]],"commits":["661095c40"],"cves":["CVE-2026-6575"],"db_id":"ce14ae2a212d2d178a6aba00d5dd585b","html":"\u003cp\u003eDetect faulty input when restoring attribute MCV statistics (Michael Paquier) \u003ca href=\"https://postgr.es/c/661095c40\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe statistics restore functions were insufficiently careful about validating most-common-value statistics, and would accept values that could crash the planner later on.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Jeroen Gui for reporting this problem. (CVE-2026-6575)\u003c/p\u003e","id":"18.4-b66bfac9ca625fe0","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)","part":"changes","patch_ids":["14b76df22d84c41c9cd0c4bba781d01d"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["661095c40"],"source_entry_id":"18.4/changes/006","source_hash":"2ed57c28e3aa4cbc7c04ba7942002bce58bb97ccc26a76547ddb32caf7c1ce65","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"d9012182ea9860adfbb2bc765d8e5b34569eadbd1aa9127209aa68e3c78fe1f0","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","variants":[],"version":"18.4"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["8e8b2bef7","c1408956e"],"commit_groups":[["8e8b2bef7","c1408956e"]],"commits":["8e8b2bef7"],"cves":[],"db_id":"43a62fc09aea76b18f3d3f019ecc7d49","html":"\u003cp\u003eImprove planner's matching of partition key columns to sub-query outputs (Richard Guo) \u003ca href=\"https://postgr.es/c/8e8b2bef7\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eStrip 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.\u003c/p\u003e","id":"18.4-fcf247ac879d30ab","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.","part":"changes","patch_ids":["ddbca8eddff456bfa8f4cca750f65073"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["8e8b2bef7"],"source_entry_id":"18.4/changes/017","source_hash":"04cfa65c27a90398206b1ff4221c2fa00dc5946461f9188c0da94f7471717161","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"d93745d6ff9d6631eb0626d27278a8e4a41b1ec44b9ae76802033575d6e229b5","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","variants":[],"version":"18.4"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["07b7a964d","e8b9d6497"],"commit_groups":[["07b7a964d","e8b9d6497"]],"commits":["e8b9d6497"],"cves":[],"db_id":"cd64c18c4400ba2e91f7b9a9fe576c95","html":"\u003cp\u003eFix self-join removal to handle join clauses that are bare boolean columns, e.g. \u003ccode\u003eON t1.boolcol\u003c/code\u003e (Andrei Lepikhov, Tender Wang, Alexander Korotkov) \u003ca href=\"https://postgr.es/c/e8b9d6497\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously such a case led to a \u003cspan\u003e“\u003cspan\u003eno relation entry for relid \u003cem\u003e\u003ccode\u003eN\u003c/code\u003e\u003c/em\u003e\u003c/span\u003e”\u003c/span\u003e error.\u003c/p\u003e","id":"18.4-7be51988e3e04ad1","identity_text":"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.","part":"changes","patch_ids":["8838bdccbd267233e5836d34efe63bca"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["e8b9d6497"],"source_entry_id":"18.4/changes/018","source_hash":"2fac75fa91378eb7633bd98dcbd88a8df9e733d521d2d434eac920e920c67264","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"6c534106629f4fee4301716f0637e75339e859c0041786eca50df72f28803a4a","text":"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.","title":"Fix self-join removal to handle join clauses that are bare boolean columns, e.g. ON t1.boolcol","variants":[],"version":"18.4"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["5548a969b","f3d03fbd5"],"commit_groups":[["5548a969b","f3d03fbd5"]],"commits":["f3d03fbd5"],"cves":[],"db_id":"3f76215c13ea5064220f47e2c19cde4d","html":"\u003cp\u003eFix \u003ccode\u003eUPDATE/DELETE ... WHERE CURRENT OF\u003c/code\u003e to work on tables with virtual generated columns (Satyanarayana Narlapuram, Dean Rasheed) \u003ca href=\"https://postgr.es/c/f3d03fbd5\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.4-1abd3ad38cf43108","identity_text":"Fix UPDATE/DELETE ... WHERE CURRENT OF to work on tables with virtual generated columns (Satyanarayana Narlapuram, Dean Rasheed)","part":"changes","patch_ids":["2e93fe13908a3975c9028e49ebb12afd"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["f3d03fbd5"],"source_entry_id":"18.4/changes/019","source_hash":"8851a234da2c4938b90db20b9cfc1794bc427c88ada73079206819a5129c705d","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"8255b67bf43bcabfa174f276d4479baa06674782acc81bdbc0db446661776080","text":"Fix UPDATE/DELETE ... WHERE CURRENT OF to work on tables with virtual generated columns (Satyanarayana Narlapuram, Dean Rasheed) §","title":"Fix UPDATE/DELETE ... WHERE CURRENT OF to work on tables with virtual generated columns","variants":[],"version":"18.4"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["783425175","cf38dedf6"],"commit_groups":[["783425175","cf38dedf6"]],"commits":["cf38dedf6"],"cves":[],"db_id":"e00a8ab631baca6c94ae7f0c2f524e18","html":"\u003cp\u003eFix expansion of virtual generated columns in \u003ccode\u003eEXCLUDED\u003c/code\u003e column references in \u003ccode\u003eINSERT ... ON CONFLICT\u003c/code\u003e (Satyanarayana Narlapuram, Dean Rasheed) \u003ca href=\"https://postgr.es/c/cf38dedf6\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.4-e9b3c3a674a28f06","identity_text":"Fix expansion of virtual generated columns in EXCLUDED column references in INSERT ... ON CONFLICT (Satyanarayana Narlapuram, Dean Rasheed)","part":"changes","patch_ids":["96409b335e92e81a0ad7e9d07596457f"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["cf38dedf6"],"source_entry_id":"18.4/changes/020","source_hash":"be1a35672d14cacee410846ce4acaa5338fc0c0a71f139695ee8b9b3c161e9c1","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"3cd0fa9459302b604a5636b1271133e42985d8545e87063df0c7054409263afc","text":"Fix expansion of virtual generated columns in EXCLUDED column references in INSERT ... ON CONFLICT (Satyanarayana Narlapuram, Dean Rasheed) §","title":"Fix expansion of virtual generated columns in EXCLUDED column references in INSERT ... ON CONFLICT","variants":[],"version":"18.4"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["570e2fcc0","cceb9c18a"],"commit_groups":[["570e2fcc0","cceb9c18a"]],"commits":["cceb9c18a"],"cves":[],"db_id":"10809b505e53f4caa2198df75ce3f735","html":"\u003cp\u003eFix spurious \u003cspan\u003e“\u003cspan\u003eindexes on virtual generated columns are not supported\u003c/span\u003e”\u003c/span\u003e errors (Robert Haas) \u003ca href=\"https://postgr.es/c/cceb9c18a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eCreation of an expression index could sometimes incorrectly report this error.\u003c/p\u003e","id":"18.4-61f1172fd1f6b603","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.","part":"changes","patch_ids":["bada2bc45007a3aca1d5b8712ebf2e04"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["cceb9c18a"],"source_entry_id":"18.4/changes/022","source_hash":"e8ac75ceb5a337d641a8170260673923d297cef2ecbba9406f19e8a55ad0722a","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"98a3d07fd5c51c5e159270aa6be7f88c123bf9cdcaacda474b4b39e5bc976e87","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","variants":[],"version":"18.4"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["6958077ce","e7975f1c0"],"commit_groups":[["6958077ce","e7975f1c0"]],"commits":["6958077ce"],"cves":[],"db_id":"43d9f06131caf2ef064630aca69efdf9","html":"\u003cp\u003eFix \u003ccode\u003eALTER TABLE ... SET NOT NULL\u003c/code\u003e to invoke object-access hook functions only after completing the catalog change (Artur Zakirov) \u003ca href=\"https://postgr.es/c/6958077ce\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.4-655416f730344aaf","identity_text":"Fix ALTER TABLE ... SET NOT NULL to invoke object-access hook functions only after completing the catalog change (Artur Zakirov)","part":"changes","patch_ids":["990e77b758464c6ca9482318179aabfa"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["6958077ce"],"source_entry_id":"18.4/changes/027","source_hash":"2343653094cbe32fe9406267b47d59179b0533c48ae6b3228174ab1fccea3b2d","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"ff18dd9e4aa149d33d3c8c705b416cef35c9189351368c8e7cca71a867b80ceb","text":"Fix ALTER TABLE ... SET NOT NULL to invoke object-access hook functions only after completing the catalog change (Artur Zakirov) §","title":"Fix ALTER TABLE ... SET NOT NULL to invoke object-access hook functions only after completing the catalog change","variants":[],"version":"18.4"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["2497dac55","5db5e3396"],"commit_groups":[["2497dac55","5db5e3396"]],"commits":["5db5e3396"],"cves":[],"db_id":"a7d8bafa2e67763a273d0c70d25876b1","html":"\u003cp\u003eFix loss of deferrability of foreign-key triggers (Yasuo Honda) \u003ca href=\"https://postgr.es/c/5db5e3396\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, a foreign key defined as \u003ccode\u003eDEFERRABLE INITIALLY DEFERRED\u003c/code\u003e would behave as \u003ccode\u003eNOT DEFERRABLE\u003c/code\u003e after being set to \u003ccode\u003eNOT ENFORCED\u003c/code\u003e status and then back to \u003ccode\u003eENFORCED\u003c/code\u003e.\u003c/p\u003e\n\u003cp\u003eIf you have a foreign key with this problem, it can be repaired (after installing this update) by again setting it to \u003ccode\u003eNOT ENFORCED\u003c/code\u003e and then back to \u003ccode\u003eENFORCED\u003c/code\u003e.\u003c/p\u003e","id":"18.4-757e8def6f28d551","identity_text":"Fix loss of deferrability of foreign-key triggers (Yasuo Honda) Previously, 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.","part":"changes","patch_ids":["a8b6899ab6bee4e9606c8611a5125b62"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["5db5e3396"],"source_entry_id":"18.4/changes/029","source_hash":"3ec02fd26d09bc6bfdbfe84c8fa62b365d06ee44c8304dd7574747870153dd2c","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"448682b444cc8d8e557814b1258bf854a09a519e4a50147eb30083b336d17345","text":"Fix loss of deferrability of foreign-key triggers (Yasuo Honda) § Previously, 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.","title":"Fix loss of deferrability of foreign-key triggers","variants":[],"version":"18.4"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["49f3cb453","4edd6036d"],"commit_groups":[["49f3cb453","4edd6036d"]],"commits":["49f3cb453"],"cves":[],"db_id":"7d6269513e48aefe9bdc3b0584b31529","html":"\u003cp\u003eFix \u003ccode\u003eWITHOUT OVERLAPS\u003c/code\u003e to allow domains (Jian He) \u003ca href=\"https://postgr.es/c/49f3cb453\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ccode\u003eUNIQUE/PRIMARY KEY ... WITHOUT OVERLAPS\u003c/code\u003e requires the no-overlap column to be a range or multirange, but it should allow a domain over such a type too.\u003c/p\u003e","id":"18.4-14749769518877d7","identity_text":"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.","part":"changes","patch_ids":["3fdf3834e29b4ddc0a9e5f011d5c8e13"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["49f3cb453"],"source_entry_id":"18.4/changes/030","source_hash":"5d736c6b9e17ace81f0e08e079ab89be5c2ec52f36404d213fd068342c662670","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"5c1cebbc5d901be819d5086acd99b9d83c7842859f6297a3e039acd57d9e78ee","text":"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.","title":"Fix WITHOUT OVERLAPS to allow domains","variants":[],"version":"18.4"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["882bdcf9f","93b76db0a"],"commit_groups":[["882bdcf9f","93b76db0a"]],"commits":["882bdcf9f"],"cves":[],"db_id":"39dad3fa894462363882bb2d00c79508","html":"\u003cp\u003eMake the \u003ccode\u003epg_aios\u003c/code\u003e system view's \u003ccode\u003epid\u003c/code\u003e column show NULL not 0 when an entry has no owning process (ChangAo Chen) \u003ca href=\"https://postgr.es/c/882bdcf9f\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.4-31b8f4fb84eb2442","identity_text":"Make the pg_aios system view's pid column show NULL not 0 when an entry has no owning process (ChangAo Chen)","part":"changes","patch_ids":["8ca5fe936a75e5b38c4cfccb843dddc3"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["882bdcf9f"],"source_entry_id":"18.4/changes/049","source_hash":"053f0c15c56221d792a8bc6e819e078c37d06ffcd6fad01b4d7eba8bf23036fc","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"cc6f01a65e56c6feb082e44429011c8c3b0dd89109143b4ab80e997a56f5cd89","text":"Make the pg_aios system view's pid column show NULL not 0 when an entry has no owning process (ChangAo Chen) §","title":"Make the pg_aios system view's pid column show NULL not 0 when an entry has no owning process","variants":[],"version":"18.4"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["1e71970d2","748d871b7"],"commit_groups":[["1e71970d2","748d871b7"]],"commits":["1e71970d2"],"cves":[],"db_id":"98b5ca4b1ed9b2c07fdfe2cdb0d69c16","html":"\u003cp\u003eFix under-allocation of shared memory used for parallel btree index scans (Siddharth Kothari) \u003ca href=\"https://postgr.es/c/1e71970d2\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIn edge cases this could result in a server crash.\u003c/p\u003e","id":"18.4-21b3ff02e00fea31","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.","part":"changes","patch_ids":["2fc6e3250377e522a3426425b060e9c3"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["1e71970d2"],"source_entry_id":"18.4/changes/051","source_hash":"1ef3d6cea990bd1dcf9ef51cc71e396b6f1f0d1befdde45495a99af305979d45","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"2e4818f716b54a67ca93894bb2763fe0ec497edda3ec9887d07fefe174034d01","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","variants":[],"version":"18.4"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["730c98d03","f7dc17aa9"],"commit_groups":[["730c98d03","f7dc17aa9"]],"commits":["730c98d03"],"cves":[],"db_id":"2c27166fac4a8166cbff771308e483d6","html":"\u003cp\u003eFix array overrun when too many \u003ccode\u003eEXPLAIN\u003c/code\u003e extension options are installed (Joel Jacobson) \u003ca href=\"https://postgr.es/c/730c98d03\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.4-d741c04b8ba8da80","identity_text":"Fix array overrun when too many EXPLAIN extension options are installed (Joel Jacobson)","part":"changes","patch_ids":["efc29acce3ca9d8d3fb120451fc4ca89"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["730c98d03"],"source_entry_id":"18.4/changes/055","source_hash":"ea69eb0828bdee04a674f3b776844e6dff7c83bd57f6d7ef5a5c4540d17a8965","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"42fcf730871baa06f879abc92e1e12cf88021a9dda4d2b9e0b2a8c87fc865f1f","text":"Fix array overrun when too many EXPLAIN extension options are installed (Joel Jacobson) §","title":"Fix array overrun when too many EXPLAIN extension options are installed","variants":[],"version":"18.4"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["98616ac18","c2c1962a6"],"commit_groups":[["98616ac18","c2c1962a6"]],"commits":["c2c1962a6"],"cves":[],"db_id":"5e752b46c1ad98780f84af438311a30a","html":"\u003cp\u003eCorrectly display join alias Vars that are used in \u003ccode\u003eGROUP BY\u003c/code\u003e (Tom Lane) \u003ca href=\"https://postgr.es/c/c2c1962a6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIn views containing queries like \u003ccode\u003eSELECT ... t1 LEFT JOIN t2 USING (x) GROUP BY x\u003c/code\u003e, the \u003ccode\u003eGROUP BY\u003c/code\u003e clause could be displayed incorrectly by deparsing, leading to dump/restore failures. Failures occurred only if \u003ccode\u003et1.x\u003c/code\u003e and \u003ccode\u003et2.x\u003c/code\u003e were not of identical data types and \u003ccode\u003et1.x\u003c/code\u003e was the side that required an implicit coercion.\u003c/p\u003e","id":"18.4-2e1bb29db6fa2e3f","identity_text":"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.","part":"changes","patch_ids":["2d3aaa978f866519aa59acaca75c71f2"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["c2c1962a6"],"source_entry_id":"18.4/changes/057","source_hash":"e25f43132041c8331aa38d774ae07a2fd81bfe116cb26d8ccd59e8d808123022","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"4a8c2b1c074d7fe26de3844d355cf9e0a5da9523b99517433394f5399b4d0af3","text":"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.","title":"Correctly display join alias Vars that are used in GROUP BY","variants":[],"version":"18.4"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["698eae7db","bc30c704a"],"commit_groups":[["698eae7db","bc30c704a"]],"commits":["698eae7db"],"cves":[],"db_id":"cfbe37010505dabb9d8718a926fa7918","html":"\u003cp\u003eHarden tar-file parsing logic against archives it can't handle (Tom Lane) \u003ca href=\"https://postgr.es/c/698eae7db\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe tar-file reading code used in \u003cspan\u003epg_basebackup\u003c/span\u003e and \u003cspan\u003epg_verifybackup\u003c/span\u003e 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 \u003cspan\u003ePostgreSQL\u003c/span\u003e code, but it can be an issue if the input has been generated by some other \u003cspan\u003etar\u003c/span\u003e program.\u003c/p\u003e","id":"18.4-927c209bb0a436cf","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.","part":"changes","patch_ids":["ce75739c3a49f201e6f23d201ae3df1f"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["698eae7db"],"source_entry_id":"18.4/changes/064","source_hash":"578b25b94ff8020a981a088d55d8d16dfbcf6e5b8065316d692942d65af1a5bc","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"b88cecc4f1e07d97baf49826b0e6852cf61b8c4b3817c2da613355e317b533cd","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","variants":[],"version":"18.4"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["c3c8b63d7","d0833fdae"],"commit_groups":[["c3c8b63d7","d0833fdae"]],"commits":["c3c8b63d7"],"cves":[],"db_id":"591d57aec1d925b713bf09e1f3edaa5f","html":"\u003cp\u003eIn \u003cspan\u003epg_dump\u003c/span\u003e, preserve \u003ccode\u003eNO INHERIT\u003c/code\u003e property of \u003ccode\u003eNOT NULL\u003c/code\u003e constraints (Jian He) \u003ca href=\"https://postgr.es/c/c3c8b63d7\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSome cases missed printing the \u003ccode\u003eNO INHERIT\u003c/code\u003e clause.\u003c/p\u003e","id":"18.4-cc6458aa3ad5fac1","identity_text":"In pg_dump, preserve NO INHERIT property of NOT NULL constraints (Jian He) Some cases missed printing the NO INHERIT clause.","part":"changes","patch_ids":["e01ed1747be4b6914a87beb807da9e49"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["c3c8b63d7"],"source_entry_id":"18.4/changes/066","source_hash":"81eaadc3cf62b2e54dc3aa7d65c0af39028ad328d20366be8107d0a5da94b98c","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"5926bb02f2dcb74f96be6f74033a817ad65190a139029a48a6cd4ad5bd0bf132","text":"In pg_dump, preserve NO INHERIT property of NOT NULL constraints (Jian He) § Some cases missed printing the NO INHERIT clause.","title":"In pg_dump, preserve NO INHERIT property of NOT NULL constraints","variants":[],"version":"18.4"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["059cf7f58","6723d462d"],"commit_groups":[["059cf7f58","6723d462d"]],"commits":["6723d462d"],"cves":[],"db_id":"a966a7e34390a814b0814712e4a00fdb","html":"\u003cp\u003eFix mis-structured output from \u003ccode\u003econtrib/pg_overexplain\u003c/code\u003e's \u003ccode\u003eRANGE_TABLE\u003c/code\u003e option (Satyanarayana Narlapuram) \u003ca href=\"https://postgr.es/c/6723d462d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSome fields were misplaced in JSON, YAML, and XML formats, resulting in structurally invalid output.\u003c/p\u003e","id":"18.4-7eed4fd6e0f7af4c","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.","part":"changes","patch_ids":["7fbc73f17a809373752c95effd8e6508"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["6723d462d"],"source_entry_id":"18.4/changes/071","source_hash":"29c20b68392e7cfc54d80f25d77055ad68bce244a0febb29053ed40d82d3d99d","source_url":"/docs/release/18.4/#RELEASE-18-4-CHANGES","statement_hash":"58504c6ef9233ef351280878eed22065a06df00f1c6e2baf450c3f48ff8a566a","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","variants":[],"version":"18.4"}],"entry_count":74,"eol":"2030-11-14","eol_date":"2030-11-14","label":"18.4","major":"18","manual":"18","manual_build":"18.6","manual_url":"/docs/18/release-18-4.html","migration_html":"\u003cp\u003eA dump/restore is not required for those running 18.X.\u003c/p\u003e\n\u003cp\u003eHowever, if you are upgrading from a version earlier than 18.2, see \u003ca href=\"/docs/18/release-18-2.html\" title=\"E.4. Release 18.2\"\u003eSection E.4\u003c/a\u003e.\u003c/p\u003e","minor":4,"placeholder":false,"source_as_of":"","source_url":"/docs/release/18.4/","status":"stable","status_label":"Supported","support_days":1463,"supported":true,"version":"18.4"},{"age_days":259,"build":"18.3","changes_count":9,"compatibility_count":0,"content_hash":"0818a2beffd0714ee0bc46a9c4d50bb727030a489b1fd4d7a5774592f6c607cb","date":"2026-02-26","date_text":"2026-02-26","doc_git":"","doc_loaded_at":"2026-09-25T02:22:44.760693","entries":[{"also_in":[],"category":"security","category_label":"Security","commit_aliases":["041e02e6a","18bcdb75d"],"commit_groups":[["041e02e6a","18bcdb75d"]],"commits":["041e02e6a"],"cves":["CVE-2026-2007"],"db_id":"bba76daa4b2c3aa3dad7cb3348361627","html":"\u003cp\u003eFix oversight in the fix for CVE-2026-2007 (Zsolt Parragi) \u003ca href=\"https://postgr.es/c/041e02e6a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf the \u003cspan\u003e“\u003cspan\u003ebounds\u003c/span\u003e”\u003c/span\u003e array needed to be expanded, because the input contained more trigrams than the initial guess, \u003ccode\u003egenerate_trgm_only\u003c/code\u003e didn't return the modified array pointer to its caller. That would lead to incorrect output from \u003ccode\u003estrict_word_similarity()\u003c/code\u003e 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.\u003c/p\u003e","id":"18.3-760673c96f02dc6a","identity_text":"Fix oversight in the fix for CVE-2026-2007 (Zsolt Parragi) If 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.","part":"changes","patch_ids":["5746d160c61038943aab7567edcfacd5"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["041e02e6a"],"source_entry_id":"18.3/changes/003","source_hash":"b353c8f16f7cf05d4c8ce29c2e27cb990261f851a19bb5942a3636d3c0e0eb06","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","statement_hash":"aeb227836e4937f484397599f9cfd2ab0c9663370769305feeb631f1ea2c1bbf","text":"Fix oversight in the fix for CVE-2026-2007 (Zsolt Parragi) § If 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.","title":"Fix oversight in the fix for CVE-2026-2007","variants":[],"version":"18.3"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["2f6ee7b38","759b03b24"],"commit_groups":[["2f6ee7b38"],["759b03b24"]],"commits":["2f6ee7b38"],"cves":[],"db_id":"b0676672ef3eccce4bfc53495f6c6dc3","html":"\u003cp\u003eFix the volatility marking of \u003ccode\u003ejson_strip_nulls()\u003c/code\u003e and \u003ccode\u003ejsonb_strip_nulls()\u003c/code\u003e (Andrew Dunstan) \u003ca href=\"https://postgr.es/c/2f6ee7b38\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese 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 \u003cspan\u003epg_upgrade\u003c/span\u003e'd to 18.3 or later). However it will not help existing clusters made using 18.0 through 18.2.\u003c/p\u003e\n\u003cp\u003eIf this mistake affects your usage of these functions, the recommended fix for an existing cluster is a manual catalog update. As superuser, perform\u003c/p\u003e\n\u003cpre\u003eUPDATE pg_catalog.pg_proc SET provolatile = 'i' WHERE oid IN ('3261','3262');\n\u003c/pre\u003e\n\u003cp\u003ein each affected database. Update \u003ccode\u003etemplate0\u003c/code\u003e and \u003ccode\u003etemplate1\u003c/code\u003e as well, so that databases made in future will have the fix.\u003c/p\u003e","id":"18.3-2fc407c7b5f1163b","identity_text":"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. If this mistake affects your usage of these functions, the recommended fix for an existing cluster is a manual catalog update. As superuser, perform UPDATE pg_catalog.pg_proc SET provolatile = 'i' WHERE oid IN ('3261','3262'); in each affected database. Update template0 and template1 as well, so that databases made in future will have the fix.","part":"changes","patch_ids":["3a0025921520001b45028dce4cf6545c","3c779614e5f31760b4d0ff66997fdc12"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["2f6ee7b38","759b03b24"],"source_entry_id":"18.3/changes/004","source_hash":"69cd62e964905e515097310ffca11c4981f7e1a31ce586fae8c7446405c7e7fd","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","statement_hash":"ea52638885fce4815a12bef2616101dc58e758e28f6544ac1d5ed498078d7721","text":"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. If this mistake affects your usage of these functions, the recommended fix for an existing cluster is a manual catalog update. As superuser, perform UPDATE pg_catalog.pg_proc SET provolatile = 'i' WHERE oid IN ('3261','3262'); in each affected database. Update template0 and template1 as well, so that databases made in future will have the fix.","title":"Fix the volatility marking of json_strip_nulls() and jsonb_strip_nulls()","variants":[],"version":"18.3"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["0eeffd31b","8d9a97e0b"],"commit_groups":[["0eeffd31b","8d9a97e0b"]],"commits":["8d9a97e0b"],"cves":[],"db_id":"d4784548a1f32ea6f8bd918343dcdb09","html":"\u003cp\u003eAvoid name collisions between user-written constraints and automatically-named \u003ccode\u003eNOT NULL\u003c/code\u003e constraints (Laurenz Albe) \u003ca href=\"https://postgr.es/c/8d9a97e0b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAs of version 18, \u003ccode\u003eNOT NULL\u003c/code\u003e constraints have full-fledged \u003ccode\u003epg_constraint\u003c/code\u003e entries, and therefore require names. The logic for choosing a name for an unnamed \u003ccode\u003eNOT NULL\u003c/code\u003e constraint failed to avoid conflicts with user-written constraints elsewhere in the same \u003ccode\u003eCREATE TABLE\u003c/code\u003e statement.\u003c/p\u003e","id":"18.3-0f7d74b3efc6c659","identity_text":"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.","part":"changes","patch_ids":["c17004a9d75adab1b627cac20c7716b1"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["8d9a97e0b"],"source_entry_id":"18.3/changes/006","source_hash":"39458dc6a2571ebb70095b8c7716b51af2fe99d225b57860fddba4da475bde38","source_url":"/docs/release/18.3/#RELEASE-18-3-CHANGES","statement_hash":"fd81cebb242019e1085e6af82a15875472cff42d16d84f62d9fa32656c8c4aca","text":"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.","title":"Avoid name collisions between user-written constraints and automatically-named NOT NULL constraints","variants":[],"version":"18.3"}],"entry_count":9,"eol":"2030-11-14","eol_date":"2030-11-14","label":"18.3","major":"18","manual":"18","manual_build":"18.6","manual_url":"/docs/18/release-18-3.html","migration_html":"\u003cp\u003eA dump/restore is not required for those running 18.X.\u003c/p\u003e\n\u003cp\u003eHowever, if you are upgrading from a version earlier than 18.2, see \u003ca href=\"/docs/18/release-18-2.html\" title=\"E.4. Release 18.2\"\u003eSection E.4\u003c/a\u003e.\u003c/p\u003e","minor":3,"placeholder":false,"source_as_of":"","source_url":"/docs/release/18.3/","status":"stable","status_label":"Supported","support_days":1463,"supported":true,"version":"18.3"},{"age_days":273,"build":"18.2","changes_count":75,"compatibility_count":0,"content_hash":"1d2dec04037af9cd68f78d36ee7a89e7bc992fd283b7c29da493c2ca2c7cdd02","date":"2026-02-12","date_text":"2026-02-12","doc_git":"","doc_loaded_at":"2026-09-25T02:22:44.760693","entries":[{"also_in":[],"category":"security","category_label":"Security","commit_aliases":["00896ddaf","18548681d","54598670f","e0965fb1a"],"commit_groups":[["00896ddaf","e0965fb1a"],["18548681d","54598670f"]],"commits":["18548681d","e0965fb1a"],"cves":["CVE-2026-2007"],"db_id":"95fa609ca10598fcbb0e28380f59c52b","html":"\u003cp\u003eHarden \u003ccode\u003econtrib/pg_trgm\u003c/code\u003e against changes in string lowercasing behavior (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/e0965fb1a\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/18548681d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFix 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.\u003c/p\u003e\n\u003cp\u003eThe \u003cspan\u003ePostgreSQL\u003c/span\u003e Project thanks Heikki Linnakangas for reporting this problem. (CVE-2026-2007)\u003c/p\u003e","id":"18.2-c06546179f64c96f","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)","part":"changes","patch_ids":["5701670e8636f3ad6e90ece759b0f13c","58324894c92d02a2d347ffa71bcabd58"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["18548681d","e0965fb1a"],"source_entry_id":"18.2/changes/005","source_hash":"4ca1b05495d40ac64500fd5b28f5325eae1f38a331b7a0742faa0c82d591ebed","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"842194f3cb8ebb43fc2cf44a76c56bf4cdf698c126f74cd0b634e06ad05f42e6","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","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["7f007e4a0","806555e30","8993bf099"],"commit_groups":[["7f007e4a0","806555e30"],["8993bf099"]],"commits":["806555e30","8993bf099"],"cves":[],"db_id":"f1aaa470ec2427a3bbea9a8b789e4da3","html":"\u003cp\u003eFix inconsistent case-insensitive matching in \u003ccode\u003econtrib/ltree\u003c/code\u003e (Jeff Davis) \u003ca href=\"https://postgr.es/c/806555e30\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/8993bf099\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIndex-related routines in \u003ccode\u003eltree\u003c/code\u003e 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.\u003c/p\u003e\n\u003cp\u003eTo fix, change the code to use case-folding with the database's default collation. This change will require reindexing indexes on \u003ccode\u003eltree\u003c/code\u003e 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.\u003c/p\u003e","id":"18.2-8107ada0cc1987cf","identity_text":"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.","part":"changes","patch_ids":["20bcd119c7a5ccd8d6c5b2cbec82a03f","91c3e917f6a5ec72c88bfb372b71316e"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["806555e30","8993bf099"],"source_entry_id":"18.2/changes/006","source_hash":"293c30e613b4d435169de45a9fb1127d910bf354fdcf42643453ef65f1940336","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"bf596476471b4eb2b843395c81da162031723bd1b8e69d43b32ae7afc01863fb","text":"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.","title":"Fix inconsistent case-insensitive matching in contrib/ltree","variants":[],"version":"18.2"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["492a69e14","96e2af605"],"commit_groups":[["492a69e14","96e2af605"]],"commits":["492a69e14"],"cves":[],"db_id":"56dc21c3cd2fff96c529ae9b2f971e88","html":"\u003cp\u003eWhen using \u003ccode\u003eALTER TABLE ... ADD CONSTRAINT\u003c/code\u003e 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) \u003ca href=\"https://postgr.es/c/492a69e14\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-bffed45d64e86015","identity_text":"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)","part":"changes","patch_ids":["ad511117ad108627aac3bc33ba669536"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["492a69e14"],"source_entry_id":"18.2/changes/007","source_hash":"801bf7f08770f729a2298f661ae3b3e5239f7907db1365e7ea819e16d06ae28a","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"8a1913dbe2937a6cc326c741017e415951638e48685efb1731d90b2f92245875","text":"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) §","title":"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","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["889676a0d","f335457e8"],"commit_groups":[["889676a0d","f335457e8"]],"commits":["f335457e8"],"cves":[],"db_id":"caf0b499119457e7b5f32e7812786e45","html":"\u003cp\u003eFix incorrect pruning of rowmarks belonging to non-relation rangetable entries, such as subqueries (Dean Rasheed) \u003ca href=\"https://postgr.es/c/f335457e8\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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.\u003c/p\u003e","id":"18.2-5cdbe1aab8d4d9b3","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.","part":"changes","patch_ids":["cc7499fdc74374d0838681b0e4e6cbce"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["f335457e8"],"source_entry_id":"18.2/changes/010","source_hash":"95c63c924f06095199dadafd4b211e2cb34c79ddccf7c381c757e7449284fd4f","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"1302bad0f15fa4ccc1f2e489bbe7c15b86ea748af40600dd43abfa98cb1694f5","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","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["75609fded","bdc5dedfc"],"commit_groups":[["75609fded","bdc5dedfc"]],"commits":["bdc5dedfc"],"cves":[],"db_id":"d51cc67df421ce0b185e4351a475c98c","html":"\u003cp\u003eFix expression evaluation bug for a sub-select within an array subscript (Andres Freund) \u003ca href=\"https://postgr.es/c/bdc5dedfc\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-76075de65b93bee4","identity_text":"Fix expression evaluation bug for a sub-select within an array subscript (Andres Freund)","part":"changes","patch_ids":["5908ce8e0da90c8b77e7a7d38c3e1377"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["bdc5dedfc"],"source_entry_id":"18.2/changes/012","source_hash":"cc7d39b69e97d5475b6643118ea3c371f3d8748bd98ed00644a2d6c2e2e83bce","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"2125e6ce990cf454284474b773e9091e1c42ad8ba7465f081da4fd84ee20d578","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","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["18b349315","6dfce8420"],"commit_groups":[["18b349315","6dfce8420"]],"commits":["18b349315"],"cves":[],"db_id":"6b7eab2a0410d798bfe50ae7628ef2dc","html":"\u003cp\u003eFix text substring search for non-deterministic collations (Laurenz Albe) \u003ca href=\"https://postgr.es/c/18b349315\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWhen using a non-deterministic collation, we failed to detect a match occurring at the very end of the searched string.\u003c/p\u003e","id":"18.2-ae79adaf8f257b64","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.","part":"changes","patch_ids":["ea38b18c588f3f94f7b67f3c7c313412"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["18b349315"],"source_entry_id":"18.2/changes/013","source_hash":"d0c98fcaf9a96ad1be16714c11aab51affff7efb750446d6d233191c575718d6","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"310b7de794986202c641c1b8c3d90b363fa90fb99c78c23f1c7cff31b4f4747b","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","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["325808cac","382ce9cb7"],"commit_groups":[["325808cac","382ce9cb7"]],"commits":["382ce9cb7"],"cves":[],"db_id":"bc2a159eaf3974e7716604942064c56f","html":"\u003cp\u003eFix planner error with set-returning functions and grouping sets (Richard Guo) \u003ca href=\"https://postgr.es/c/382ce9cb7\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWhen 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 \u003cspan\u003e“\u003cspan\u003evariable not found in subplan target list\u003c/span\u003e”\u003c/span\u003e.\u003c/p\u003e","id":"18.2-649e6794b398ddbb","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.","part":"changes","patch_ids":["eeb8feeb82fe026545fa79e36fe8e45a"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["382ce9cb7"],"source_entry_id":"18.2/changes/015","source_hash":"bfe0c00a4c0bd63be1d00cedf698d85b72a12a918ad78e6380acde776206dc0e","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"1c3b6e833fd7b899cf7ef68c26c207cfe9f1fd37cce060a0ea001c22d4e52b17","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","variants":[],"version":"18.2"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["34740b90b","7650eabb6"],"commit_groups":[["34740b90b","7650eabb6"]],"commits":["7650eabb6"],"cves":[],"db_id":"9b5a3307e8e1098ff8eef8ca23427644","html":"\u003cp\u003eAvoid incorrect optimization when a subquery's grouping clause contains a volatile or set-returning function (Richard Guo) \u003ca href=\"https://postgr.es/c/7650eabb6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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 \u003ccode\u003eWHERE\u003c/code\u003e/\u003ccode\u003eHAVING\u003c/code\u003e clauses.\u003c/p\u003e","id":"18.2-6765d768956aae6e","identity_text":"Avoid incorrect optimization when a subquery's grouping clause contains a volatile or set-returning function (Richard Guo) The 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.","part":"changes","patch_ids":["a57bfe9b17a406dcabee6035042eee67"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["7650eabb6"],"source_entry_id":"18.2/changes/016","source_hash":"ab9c80987ac3a97add7ebc6bf2a3e7915a82f69bbf712cb57a5c1d38f722a237","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"38a215b6ea2052b022eeb01f4141057758fbd647538154244b177bbeaea77912","text":"Avoid incorrect optimization when a subquery's grouping clause contains a volatile or set-returning function (Richard Guo) § The 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.","title":"Avoid incorrect optimization when a subquery's grouping clause contains a volatile or set-returning function","variants":[],"version":"18.2"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["559f9e90d","7e9f852a7"],"commit_groups":[["559f9e90d","7e9f852a7"]],"commits":["7e9f852a7"],"cves":[],"db_id":"1fd583db09b5d4f529a7cc73d10d9b3e","html":"\u003cp\u003eLook through PlaceHolderVar nodes when searching for statistics about an expression (Richard Guo) \u003ca href=\"https://postgr.es/c/7e9f852a7\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis change allows the planner to find relevant statistics about expressions pulled up from subqueries or used in \u003ccode\u003eGROUP BY\u003c/code\u003e, 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 \u003cspan\u003ePostgreSQL\u003c/span\u003e version 18 made PlaceHolderVars more common than before, so make the change to avoid plan regressions in affected cases.\u003c/p\u003e","id":"18.2-746d4217820b0179","identity_text":"Look through PlaceHolderVar nodes when searching for statistics about an expression (Richard Guo) This 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.","part":"changes","patch_ids":["a2b0342c9a69df2baecdd5b03c45ecdb"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["7e9f852a7"],"source_entry_id":"18.2/changes/017","source_hash":"2e3fe0c0b9544928ab0db692c8afc782b0d2fe59c6e0976a7e3fc982e6453423","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"37469dabc76b94c5c696a16261f7cc8e3a46334e6d787ceca0d2b3b1fbe08e65","text":"Look through PlaceHolderVar nodes when searching for statistics about an expression (Richard Guo) § This 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.","title":"Look through PlaceHolderVar nodes when searching for statistics about an expression","variants":[],"version":"18.2"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["ad66f705f","b4cf74420"],"commit_groups":[["ad66f705f","b4cf74420"]],"commits":["b4cf74420"],"cves":[],"db_id":"210a202963ef31d2c268f29448660f49","html":"\u003cp\u003eLook through no-op PlaceHolderVar nodes when matching expressions to indexes (Richard Guo) \u003ca href=\"https://postgr.es/c/b4cf74420\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eBecause \u003cspan\u003ePostgreSQL\u003c/span\u003e 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.\u003c/p\u003e","id":"18.2-0677f3efa6183aff","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.","part":"changes","patch_ids":["53d01d1a3c53c6464ef09ecc976ee332"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["b4cf74420"],"source_entry_id":"18.2/changes/018","source_hash":"a22a975a62936995e5c733505e5cb2413d8e0ffe0fc8ea23bab714f1ed47ce58","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"499947e9b2731bd734d2d41a7fb4749ea9665bdf69c9076c6227ba0edaaa6c0c","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","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["bf5b13a8a","ed931377a"],"commit_groups":[["bf5b13a8a","ed931377a"]],"commits":["bf5b13a8a"],"cves":[],"db_id":"94eedc608f36ae44537859b8b9484ab3","html":"\u003cp\u003eFix planner's conversion of \u003ccode\u003eOR\u003c/code\u003e clauses to ScalarArrayOp index conditions (Tender Wang, Tom Lane) \u003ca href=\"https://postgr.es/c/bf5b13a8a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe code did not handle RelabelType nodes correctly, and could generate invalid expressions or fail to perform a valid conversion.\u003c/p\u003e","id":"18.2-df3239546e44b0cd","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.","part":"changes","patch_ids":["1c449b40bb86e705289bfa79952a34a2"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["bf5b13a8a"],"source_entry_id":"18.2/changes/019","source_hash":"3ed87fea3bb1e7df63b1e9929de9df6e3de1977345d1ad50cab3a41567b78a13","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"4613d2cb8f7f4c9cb614a7c8886084608316d9fe5c1bbb70ce9149628a5849c7","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","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["db14dcdec","eee71a66c"],"commit_groups":[["db14dcdec","eee71a66c"]],"commits":["eee71a66c"],"cves":[],"db_id":"8bb71f9af38e5b5860817aa7de5e1ab4","html":"\u003cp\u003eUse the correct ordering function in parallel GIN index builds (Tomas Vondra) \u003ca href=\"https://postgr.es/c/eee71a66c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe 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.\u003c/p\u003e","id":"18.2-f25edebc3313b2e9","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.","part":"changes","patch_ids":["aa226fd5175b721e5e2259a6364ccac6"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["eee71a66c"],"source_entry_id":"18.2/changes/022","source_hash":"973146437be60c25c40e87f556a60ea70c774a8c9dfe17423d4113036c477198","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"318cfc6b1c80caebb91eb100312a972bee87e50eb8e5e2b385370bf2723cca6d","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","variants":[],"version":"18.2"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["9c3caad02","e217dc748"],"commit_groups":[["9c3caad02","e217dc748"]],"commits":["9c3caad02"],"cves":[],"db_id":"45a5eeb2bacd1dedc1490b8ffff62798","html":"\u003cp\u003eConsider grouping expressions when computing a query ID hash (Jian He) \u003ca href=\"https://postgr.es/c/9c3caad02\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, two queries that were the same except in \u003ccode\u003eGROUP BY\u003c/code\u003e expressions would be merged by \u003ccode\u003econtrib/pg_stat_statements\u003c/code\u003e and other users of query IDs.\u003c/p\u003e","id":"18.2-c776aad9e4397483","identity_text":"Consider grouping expressions when computing a query ID hash (Jian He) Previously, 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.","part":"changes","patch_ids":["a0cecf69ec7964724911302c6fa3a07b"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["9c3caad02"],"source_entry_id":"18.2/changes/025","source_hash":"eedb6675ae097912d0f81eba48a312b4aa303e1482d75a2413f5694c61799ab8","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"e34d8ff79a2989809c11d3caf91cddcce955ac35372061609057c466eb42a6a8","text":"Consider grouping expressions when computing a query ID hash (Jian He) § Previously, 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.","title":"Consider grouping expressions when computing a query ID hash","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["7f1b3a4ce","807764990"],"commit_groups":[["7f1b3a4ce","807764990"]],"commits":["7f1b3a4ce"],"cves":[],"db_id":"d7b9af6aba344aaf3e300ba043f6e676","html":"\u003cp\u003eFix race condition in async I/O code (Andres Freund) \u003ca href=\"https://postgr.es/c/7f1b3a4ce\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIt was possible for the result code of an asynchronous I/O operation to be overwritten before it was fetched.\u003c/p\u003e","id":"18.2-f5298e917912b5f8","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.","part":"changes","patch_ids":["eadaff6d2b44dde4bfed1267e5de7286"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["7f1b3a4ce"],"source_entry_id":"18.2/changes/030","source_hash":"5af700db1614d279fcb4fcebf26c8689988d0b9bde5b133a056adcd4a9552070","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"1ed0580c38ed15716eec1bf553a375fa0748d46936276494503831223d421a84","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","variants":[],"version":"18.2"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["3fccbd94c","9796c4f56"],"commit_groups":[["3fccbd94c","9796c4f56"]],"commits":["9796c4f56"],"cves":[],"db_id":"a4a4627ccc48db9aa301be1c008e8e7a","html":"\u003cp\u003eAvoid failure of NUMA status views when a page has been swapped out (Tomas Vondra) \u003ca href=\"https://postgr.es/c/9796c4f56\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-41d3c4fc60b60873","identity_text":"Avoid failure of NUMA status views when a page has been swapped out (Tomas Vondra)","part":"changes","patch_ids":["c1934fec3a67006ff496ce9fb844191b"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["9796c4f56"],"source_entry_id":"18.2/changes/038","source_hash":"38d4ca5996782890ca2a8d47c302f2fba325fe4e6d025da506c9c1c097171cfe","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"981fce7d7bf6866f425cbf1dc7f0d13d35e9addf7428a9dce5e55e3c69b9c85d","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","variants":[],"version":"18.2"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["482e98ac4","599336c64"],"commit_groups":[["482e98ac4","599336c64"]],"commits":["482e98ac4"],"cves":[],"db_id":"f1a5fdf26515c807e56ed1d6de014dd1","html":"\u003cp\u003eAvoid \u003cspan\u003e“\u003cspan\u003eoperation not permitted\u003c/span\u003e”\u003c/span\u003e errors when querying NUMA page status with older libnuma versions (Tomas Vondra) \u003ca href=\"https://postgr.es/c/482e98ac4\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-33eb39d50d6770e0","identity_text":"Avoid operation not permitted errors when querying NUMA page status with older libnuma versions (Tomas Vondra)","part":"changes","patch_ids":["639b15538137cdc707818eaccc7bb5ba"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["482e98ac4"],"source_entry_id":"18.2/changes/039","source_hash":"10794498f6ae24d9bfbee4b67ef15fa1893a35ad5b80ba4d3f628c72faed942c","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"d7f2ab1d3fb2329282928f089cffff62ce9cd74b3faa5a45573d6cf600c28439","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","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["3e83bdd35","6a5170755","6d969ca68","db4eba152"],"commit_groups":[["3e83bdd35","6a5170755"],["6d969ca68","db4eba152"]],"commits":["6a5170755","db4eba152"],"cves":[],"db_id":"a44abc9297ae39cc8abcc977a7a85ce4","html":"\u003cp\u003eFix aarch64-specific code to build with old (RHEL7-era) system header files (Tom Lane) \u003ca href=\"https://postgr.es/c/db4eba152\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/6a5170755\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-af5fc26e8f8168d4","identity_text":"Fix aarch64-specific code to build with old (RHEL7-era) system header files (Tom Lane)","part":"changes","patch_ids":["2792ee2090bd3b24ee2601afc2231214","341f355bf2e1a82a85b3bc4ddacd7e41"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["6a5170755","db4eba152"],"source_entry_id":"18.2/changes/054","source_hash":"529bcd93c047b2ef7eec0c93454effdb7bf1dc30a7e787b9cdc4b0f1eba54689","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"029c7334d68c62bf885d8809ad4d9b0c95dcd9472fff890d2839cbdcfca4b7eb","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","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["640772c6d","85d5bd308"],"commit_groups":[["640772c6d","85d5bd308"]],"commits":["640772c6d"],"cves":[],"db_id":"d68ab5c932a807f00f02a3ef1979ea8e","html":"\u003cp\u003eFix incorrect configure probe for \u003ccode\u003eio_uring_queue_init_mem()\u003c/code\u003e (Masahiko Sawada) \u003ca href=\"https://postgr.es/c/640772c6d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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.\u003c/p\u003e","id":"18.2-86262bb2b8fa68fb","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.","part":"changes","patch_ids":["31cbb2c33e39c0e4ef28cc6890ff10f4"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["640772c6d"],"source_entry_id":"18.2/changes/055","source_hash":"ad451119c2c42159d919470bd46bbc04ff30fcfd36273c4c496e4e04cd4a44a7","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"d8fc17387f6344b93284d7852d2f78ec8e602fcb2a9c3aaa1c5d271b3ab58ea4","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()","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["4e1376900","c5c808f9b"],"commit_groups":[["4e1376900","c5c808f9b"]],"commits":["4e1376900"],"cves":[],"db_id":"3ed7d34c9f1f44d7f12b3cdf5be71fdb","html":"\u003cp\u003eFix \u003cspan\u003epsql\u003c/span\u003e's tab completion for \u003ccode\u003eVACUUM\u003c/code\u003e option values (Yugo Nagata) \u003ca href=\"https://postgr.es/c/4e1376900\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-208ee506bc091a4e","identity_text":"Fix psql's tab completion for VACUUM option values (Yugo Nagata)","part":"changes","patch_ids":["47fa51099f2042bb10fa2d4100d596e6"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["4e1376900"],"source_entry_id":"18.2/changes/060","source_hash":"795aa4c4f95ee4028ff6a69e46104986349ec281dfd541dc14835862cb9cdc7a","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"484a8e0d2d168721774297ba19d5a5bf75c0ddb8133cd526f01eca3a45220bf6","text":"Fix psql's tab completion for VACUUM option values (Yugo Nagata) §","title":"Fix psql's tab completion for VACUUM option values","variants":[],"version":"18.2"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["4b77282f2","d42735b1e"],"commit_groups":[["4b77282f2","d42735b1e"]],"commits":["d42735b1e"],"cves":[],"db_id":"0856ce3b7218500bf5dbe52cdc233e9f","html":"\u003cp\u003eIn \u003cspan\u003epsql\u003c/span\u003e command prompts, do not show a value for \u003ccode\u003e%P\u003c/code\u003e (pipeline status) when there is no server connection (Chao Li) \u003ca href=\"https://postgr.es/c/d42735b1e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis makes \u003ccode\u003e%P\u003c/code\u003e act like other prompt escape sequences whose values depend on the active connection.\u003c/p\u003e","id":"18.2-33c3f1c7bab6b68d","identity_text":"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.","part":"changes","patch_ids":["693bff41453365dddf860360cb11e561"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["d42735b1e"],"source_entry_id":"18.2/changes/061","source_hash":"c12e03620468521702d6bd8dcc133365a028c92b4c8a1403dc325a5fa1efbb80","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"272361171af0f32c0153740896cdb38602e94f6913109737c20a6f445a8d851e","text":"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.","title":"In psql command prompts, do not show a value for %P (pipeline status) when there is no server connection","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["39d555576","56e1f5010","5d1f5079a","7a485bd64"],"commit_groups":[["39d555576","7a485bd64"],["56e1f5010","5d1f5079a"]],"commits":["39d555576","56e1f5010"],"cves":[],"db_id":"6a88db926279b2de84f76189b0b7b586","html":"\u003cp\u003eFix \u003cspan\u003epg_dump\u003c/span\u003e's logic for collecting sequence values (Nathan Bossart) \u003ca href=\"https://postgr.es/c/39d555576\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/56e1f5010\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003epg_dump\u003c/span\u003e 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, \u003cspan\u003epg_dump\u003c/span\u003e emitted incorrect values rather than failing as expected.\u003c/p\u003e","id":"18.2-4719d9fbda426b6b","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.","part":"changes","patch_ids":["09260790fdc4775cb78273043d8cf1be","eaea0ffb838affab367b400e8c79884f"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["39d555576","56e1f5010"],"source_entry_id":"18.2/changes/062","source_hash":"37f2d4cc5be5c650e6934efeddfac614410556bf5d2ba2916471c87b81d6781e","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"ce18d8cd7ca3634349a95b8901669acb169663943174c58ace92a87d8eb5a4ae","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","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["61c78e1f4","ec0da9b89"],"commit_groups":[["61c78e1f4","ec0da9b89"]],"commits":["61c78e1f4"],"cves":[],"db_id":"2edcdf4c426f73af4c504d84d937d988","html":"\u003cp\u003eFix potentially-incorrect quoting of \u003ccode\u003eoauth_validator_libraries\u003c/code\u003e values by \u003cspan\u003epg_dump\u003c/span\u003e (ChangAo Chen) \u003ca href=\"https://postgr.es/c/61c78e1f4\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003epg_dump\u003c/span\u003e applied the wrong quoting rule if it needed to dump a value of this setting.\u003c/p\u003e","id":"18.2-f023cfdc0ce6569e","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.","part":"changes","patch_ids":["862047a17a76ec23fcd2672f659199b1"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["61c78e1f4"],"source_entry_id":"18.2/changes/063","source_hash":"b70c2051bd8c92a107757fad0742c202ef62cfffe67c8c80e96122f38bd6cf65","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"d589bfa7906038771b189bb28737cfa67b315269b47561f913b9ac6b9a230781","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","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["3f83de20b","580b5c2f3"],"commit_groups":[["3f83de20b","580b5c2f3"]],"commits":["580b5c2f3"],"cves":[],"db_id":"2a469e87e461518ff6a0c895df4011c4","html":"\u003cp\u003eFix excessive memory allocation in \u003ccode\u003econtrib/pg_buffercache\u003c/code\u003e (David Geier) \u003ca href=\"https://postgr.es/c/580b5c2f3\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe code allocated twice as much memory as it needed for NUMA page status.\u003c/p\u003e","id":"18.2-78621868f8a48d3e","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.","part":"changes","patch_ids":["68296f37cd0ce327bf140bb0b4bfe511"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["580b5c2f3"],"source_entry_id":"18.2/changes/071","source_hash":"88873f3cec0f4d824b5d7ec01e5819d140fc5921a33dd96de5c0410e14d7329b","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"1042007c5ddc717af06afcddccb20c95b2ab0127baff1887603f236846d07dd3","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","variants":[],"version":"18.2"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["3304e97b1","5d95219fa"],"commit_groups":[["3304e97b1","5d95219fa"]],"commits":["3304e97b1"],"cves":[],"db_id":"91440dc09c962461aba340bf8d013706","html":"\u003cp\u003eAvoid crash in \u003ccode\u003econtrib/pg_stat_statements\u003c/code\u003e when an \u003ccode\u003eIN\u003c/code\u003e list contains both constants and non-constant expressions (Sami Imseih) \u003ca href=\"https://postgr.es/c/3304e97b1\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.2-88be8c9b8608cbbe","identity_text":"Avoid crash in contrib/pg_stat_statements when an IN list contains both constants and non-constant expressions (Sami Imseih)","part":"changes","patch_ids":["7630dbbb9eb7bf6a2e8bb27d523e2b17"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["3304e97b1"],"source_entry_id":"18.2/changes/074","source_hash":"d9db972c28c90a40ba525627189a32e20fa74e1597314455dcadf45500b27791","source_url":"/docs/release/18.2/#RELEASE-18-2-CHANGES","statement_hash":"d25646826d953ef8261159e709f96e95efd7d1f356853de68cc892f611ebcbea","text":"Avoid crash in contrib/pg_stat_statements when an IN list contains both constants and non-constant expressions (Sami Imseih) §","title":"Avoid crash in contrib/pg_stat_statements when an IN list contains both constants and non-constant expressions","variants":[],"version":"18.2"}],"entry_count":75,"eol":"2030-11-14","eol_date":"2030-11-14","label":"18.2","major":"18","manual":"18","manual_build":"18.6","manual_url":"/docs/18/release-18-2.html","migration_html":"\u003cp\u003eA dump/restore is not required for those running 18.X.\u003c/p\u003e\n\u003cp\u003eHowever, if you have any indexes on \u003ccode\u003eltree\u003c/code\u003e columns, it may be necessary to reindex them after updating. See the sixth changelog entry below.\u003c/p\u003e","minor":2,"placeholder":false,"source_as_of":"","source_url":"/docs/release/18.2/","status":"stable","status_label":"Supported","support_days":1463,"supported":true,"version":"18.2"},{"age_days":364,"build":"18.1","changes_count":53,"compatibility_count":0,"content_hash":"37f4be50ffa6dd05ff6bba94d65415e84618983e53724f0712b560222d8f2990","date":"2025-11-13","date_text":"2025-11-13","doc_git":"","doc_loaded_at":"2026-09-25T02:22:44.760693","entries":[{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["18d261409","40c242830","ee49f2cf4"],"commit_groups":[["18d261409","40c242830"],["ee49f2cf4"]],"commits":["40c242830","ee49f2cf4"],"cves":[],"db_id":"64d7741972b458081894d24da0374395","html":"\u003cp\u003eAvoid incorrect optimization of variable-free \u003ccode\u003eHAVING\u003c/code\u003e clauses with grouping sets (Richard Guo) \u003ca href=\"https://postgr.es/c/40c242830\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/ee49f2cf4\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-3c477bf7c9a2885e","identity_text":"Avoid incorrect optimization of variable-free HAVING clauses with grouping sets (Richard Guo)","part":"changes","patch_ids":["2c0ae04ea0e784fc2d17c8ab38e5cd41","50b322963c6b58d35aea2955fcfea34f"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["40c242830","ee49f2cf4"],"source_entry_id":"18.1/changes/004","source_hash":"ad359f03b7b74d8a0a552d70b1b2cf5e247a06f8ad1e5b8356baf8e55e4d2baf","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"40b106b47db0974b5bea1bdc63c90189e253c1958fd7ff025f370ad6794518ba","text":"Avoid incorrect optimization of variable-free HAVING clauses with grouping sets (Richard Guo) § §","title":"Avoid incorrect optimization of variable-free HAVING clauses with grouping sets","variants":[],"version":"18.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["257ee7834","ef6168baf"],"commit_groups":[["257ee7834","ef6168baf"]],"commits":["ef6168baf"],"cves":[],"db_id":"ed09728e7057ba0bd58174091cf36572","html":"\u003cp\u003eDo not use parallelism in hash right semi joins (Richard Guo) \u003ca href=\"https://postgr.es/c/ef6168baf\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe case does not work reliably due to a race condition in updating the join's shared hash table.\u003c/p\u003e","id":"18.1-dbb02ab568ba9c9d","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.","part":"changes","patch_ids":["f3845afa0fdccbe6d8cbb30c204eadc5"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["ef6168baf"],"source_entry_id":"18.1/changes/005","source_hash":"39312baafff0331dc6e11307f7638efa4a10bda18328fc33401949b670dd2c7a","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"3f17b0b718491fbba177f4509a3ce7371c9be8208074eb0f788005239524f671","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","variants":[],"version":"18.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["500f64636","c1777f2d6"],"commit_groups":[["500f64636","c1777f2d6"]],"commits":["500f64636"],"cves":[],"db_id":"805d87830e137872aeddda00e5eb47fa","html":"\u003cp\u003eAvoid possible division-by-zero when creating ordered-append plans (Richard Guo) \u003ca href=\"https://postgr.es/c/500f64636\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis mistake could result in incorrect selection of the cheapest path, or in an assertion failure in debug builds.\u003c/p\u003e","id":"18.1-5ec2ebf5e9d409d9","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.","part":"changes","patch_ids":["9414b4063f9e09aec7dbfc033ff0d56c"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["500f64636"],"source_entry_id":"18.1/changes/006","source_hash":"05094dbe1a52e137262c79803f4a98e69d7150808221f3286b1687f51db2a39b","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"9ab1c92995e5dc19b2f8430a87e9fe9e0f7b8dac32500b13b471acc4c3e4632a","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","variants":[],"version":"18.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["35e53b684","74197bdc8"],"commit_groups":[["35e53b684","74197bdc8"]],"commits":["74197bdc8"],"cves":[],"db_id":"48e2cdd93edf3d7841847a6e50d6cef2","html":"\u003cp\u003eFix planner failure with index types that can do ordered access but not index-only scans (Maxime Schoemans) \u003ca href=\"https://postgr.es/c/74197bdc8\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis oversight resulted in errors like \u003cspan\u003e“\u003cspan\u003eno data returned for index-only scan\u003c/span\u003e”\u003c/span\u003e. The case does not arise with any in-core index type, but some extensions encountered the problem.\u003c/p\u003e","id":"18.1-c0b31ef03ca6b8d1","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.","part":"changes","patch_ids":["cccb634623d2b8f1ee8f5067fca472e2"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["74197bdc8"],"source_entry_id":"18.1/changes/007","source_hash":"57874e5db38d38966d2b710cf21e5580b67abd8ab00c1e2cd67449f3d5a529a0","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"24cae600a957284e060515856c041bc697d4b1ccf9e6f631f35d5bdbade1bc28","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","variants":[],"version":"18.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["a26b753a0","c98dffcb7"],"commit_groups":[["a26b753a0","c98dffcb7"]],"commits":["a26b753a0"],"cves":[],"db_id":"e3a6863618f309db1f698b4f2fcc8973","html":"\u003cp\u003eAvoid possible out-of-memory or \u003cspan\u003e“\u003cspan\u003einvalid memory alloc request size\u003c/span\u003e”\u003c/span\u003e failures during parallel GIN index build (Tomas Vondra) \u003ca href=\"https://postgr.es/c/a26b753a0\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-37c61345d3eacb08","identity_text":"Avoid possible out-of-memory or invalid memory alloc request size failures during parallel GIN index build (Tomas Vondra)","part":"changes","patch_ids":["2cfdabaf231689f023ac206f2d6e0d32"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["a26b753a0"],"source_entry_id":"18.1/changes/009","source_hash":"fb8079b2782c06b6778225c99b5fd0371cff81d513d4d0cff5381c5dacf27249","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"5743d4aa1ec81c0d062d02b160bfecf8805fd2e5abb8be2006065e2655b7797e","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","variants":[],"version":"18.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["0b6a02f03","5c0a20003"],"commit_groups":[["0b6a02f03","5c0a20003"]],"commits":["0b6a02f03"],"cves":[],"db_id":"e70ede7bd5583f381bf465e783e34002","html":"\u003cp\u003eFix rare crash when processing hashed \u003ccode\u003eGROUPING SETS\u003c/code\u003e queries (David Rowley) \u003ca href=\"https://postgr.es/c/0b6a02f03\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-86469df42b03e324","identity_text":"Fix rare crash when processing hashed GROUPING SETS queries (David Rowley)","part":"changes","patch_ids":["1c5627dd3234f4c77c310d7fcec4806f"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["0b6a02f03"],"source_entry_id":"18.1/changes/013","source_hash":"cc577384085b9efd2f083bd967ec65d06ee8023c468f527337a797ad834fcc5e","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"aaf9819b0b8a5d95eaa44966037d6f0f416829e205ff02c52bbbbb49ed82e79b","text":"Fix rare crash when processing hashed GROUPING SETS queries (David Rowley) §","title":"Fix rare crash when processing hashed GROUPING SETS queries","variants":[],"version":"18.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["aa151022e","b85c4700f"],"commit_groups":[["aa151022e","b85c4700f"]],"commits":["aa151022e"],"cves":[],"db_id":"a3653066758eab729f75956e87c77d7e","html":"\u003cp\u003eRepair faulty hash-table-size-choosing logic in hash joins (Tomas Vondra) \u003ca href=\"https://postgr.es/c/aa151022e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eHash joins sometimes used more memory than intended, or failed to divide it in an efficient way.\u003c/p\u003e","id":"18.1-595b80f1b57139d2","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.","part":"changes","patch_ids":["e7109e998d0ab28d4a07d7656b59c540"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["aa151022e"],"source_entry_id":"18.1/changes/014","source_hash":"2f1f77c5b58aad4080d3f53a2ed5a3111544020d333a1a2c3c94f1a0b67b0fff","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"673e758ffe8bfaad06735b49302d3951f81c17011e37608c1152b407bc0c3e5b","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","variants":[],"version":"18.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["15d7dded0","688dc6299","c8af5019b"],"commit_groups":[["15d7dded0"],["688dc6299","c8af5019b"]],"commits":["15d7dded0","c8af5019b"],"cves":[],"db_id":"994046ec35e4309bd0a13d4c68e9f1d1","html":"\u003cp\u003eImprove relation lookup logic in statistics manipulation functions (Nathan Bossart) \u003ca href=\"https://postgr.es/c/c8af5019b\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/15d7dded0\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eFix \u003ccode\u003epg_restore_relation_stats()\u003c/code\u003e, \u003ccode\u003epg_clear_relation_stats()\u003c/code\u003e, \u003ccode\u003epg_restore_attribute_stats()\u003c/code\u003e, and \u003ccode\u003epg_clear_attribute_stats()\u003c/code\u003e to check privileges before acquiring lock on the target relation rather than after.\u003c/p\u003e","id":"18.1-db784857980e4eb2","identity_text":"Improve relation lookup logic in statistics manipulation functions (Nathan Bossart) Fix 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.","part":"changes","patch_ids":["4003c14332c687be30fc03d4af31da84","4da2341fff5b72181492769ab6d6fa07"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["15d7dded0","c8af5019b"],"source_entry_id":"18.1/changes/015","source_hash":"f8bd59218ac4b34b3ee565d68c5695004386bd084e04b43b9b6021087ca2e7ac","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"44114a78e01aa87c025a8c38bf3fab478ad80fcca0d566de78a5c814a859cbd4","text":"Improve relation lookup logic in statistics manipulation functions (Nathan Bossart) § § Fix 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.","title":"Improve relation lookup logic in statistics manipulation functions","variants":[],"version":"18.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["1296dcf18","905e932f0"],"commit_groups":[["1296dcf18","905e932f0"]],"commits":["1296dcf18"],"cves":[],"db_id":"a0c4022eb806e7bff85e5e4f45d350da","html":"\u003cp\u003eFix crash during EvalPlanQual rechecks on partitioned tables (David Rowley, Amit Langote) \u003ca href=\"https://postgr.es/c/1296dcf18\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-4fabed399ac5f947","identity_text":"Fix crash during EvalPlanQual rechecks on partitioned tables (David Rowley, Amit Langote)","part":"changes","patch_ids":["cfaa90e1fdcf18ac6f3f0eafaf77ada8"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["1296dcf18"],"source_entry_id":"18.1/changes/017","source_hash":"2bb2eab84c9d0aef8280d0f562760f0381fcab6030475f916b6ae62ee941d8c4","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"9669bf1f77810bf9ebd51d3fc0ea281b8ca1e3a90f20cee99402fbc39242eea5","text":"Fix crash during EvalPlanQual rechecks on partitioned tables (David Rowley, Amit Langote) §","title":"Fix crash during EvalPlanQual rechecks on partitioned tables","variants":[],"version":"18.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["cf8be0225","d9ffc2729"],"commit_groups":[["cf8be0225","d9ffc2729"]],"commits":["d9ffc2729"],"cves":[],"db_id":"1cc2ad2f1d77c84c94244519b7c21f49","html":"\u003cp\u003ePrevent setting a column as identity if it has a not-null constraint but the constraint is marked as invalid (Jian He) \u003ca href=\"https://postgr.es/c/d9ffc2729\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIdentity columns must be not-null, but the check for that missed this edge case.\u003c/p\u003e","id":"18.1-8cabd69c2fc9923e","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.","part":"changes","patch_ids":["98b878ffaecd78024f87c7da5729ffae"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["d9ffc2729"],"source_entry_id":"18.1/changes/022","source_hash":"2363f4d7bfd86ce33ae953ccf4e4c56d7128d64840b12913cbbdb8adf4dc9418","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"eb006304791e8ea1548b9c4a7928a374c1b1a1f0d2a2219dc90b3744065f5b53","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","variants":[],"version":"18.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["3ebea75f9","d115de9d8"],"commit_groups":[["3ebea75f9","d115de9d8"]],"commits":["3ebea75f9"],"cves":[],"db_id":"f3a09ba6d76319872cf3c57dfe3cbb7f","html":"\u003cp\u003eRe-establish special case for \u003ccode\u003eC\u003c/code\u003e collation in locale setup (Jeff Davis) \u003ca href=\"https://postgr.es/c/3ebea75f9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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 \u003cspan\u003ePostgreSQL\u003c/span\u003e code, but some extensions were broken.\u003c/p\u003e","id":"18.1-33661c84650917d0","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.","part":"changes","patch_ids":["8a35575852644cce7c43988f09a72271"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["3ebea75f9"],"source_entry_id":"18.1/changes/034","source_hash":"5967144f5a9ac390e5f43e37e44136126f8a69ddef70fa46672228f341690c6e","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"a7ae6078a0c5cd7c2be592c68fcd68fe554b04a4788ec782c9e11a5f99e01b1d","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","variants":[],"version":"18.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["16edc1b94","b1635c166"],"commit_groups":[["16edc1b94","b1635c166"]],"commits":["b1635c166"],"cves":[],"db_id":"a68f0a28f777789fc34dd952b7f61778","html":"\u003cp\u003eIn \u003ccode\u003econtrib/pg_stat_statements\u003c/code\u003e, avoid crash when two or more constants are marked as having the same location in the SQL statement text (Sami Imseih, Dmitry Dolgov) \u003ca href=\"https://postgr.es/c/b1635c166\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.1-a7e88dbb0ea69eea","identity_text":"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)","part":"changes","patch_ids":["c4d097e6702d0a18bda4d1a8bbc618cf"],"related_changes":[],"relations":[],"section":"Changes","section_path":["Changes"],"source_commits":["b1635c166"],"source_entry_id":"18.1/changes/050","source_hash":"e65713e607c506b7563eb27872a7beba8b3701ef14558d32ca8b3bac3df1388e","source_url":"/docs/release/18.1/#RELEASE-18-1-CHANGES","statement_hash":"1bddbef944aed8861f456de07c83405980becf4c45f4baebf912d6a5864ba3ca","text":"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) §","title":"In contrib/pg_stat_statements, avoid crash when two or more constants are marked as having the same location in the SQL statement text","variants":[],"version":"18.1"}],"entry_count":53,"eol":"2030-11-14","eol_date":"2030-11-14","label":"18.1","major":"18","manual":"18","manual_build":"18.6","manual_url":"/docs/18/release-18-1.html","migration_html":"\u003cp\u003eA dump/restore is not required for those running 18.X.\u003c/p\u003e","minor":1,"placeholder":false,"source_as_of":"","source_url":"/docs/release/18.1/","status":"stable","status_label":"Supported","support_days":1463,"supported":true,"version":"18.1"},{"age_days":413,"build":"18.0","changes_count":199,"compatibility_count":11,"content_hash":"18846b73e34c6c5402520e411e973c0a253591050c63dbc366a66ce751e0aeaa","date":"2025-09-25","date_text":"2025-09-25","doc_git":"","doc_loaded_at":"2026-09-25T02:22:44.760693","entries":[{"also_in":[],"category":"compatibility","category_label":"Compatibility","commit_aliases":["04bec894a04"],"commit_groups":[["04bec894a04"]],"commits":["04bec894a04"],"cves":[],"db_id":"f3c7465886914cc33d3dae8014f0ac38","html":"\u003cp\u003eChange \u003ca href=\"/docs/18/app-initdb.html\" title=\"initdb\"\u003e\u003cspan\u003e\u003cspan\u003einitdb\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e default to enable data checksums (Greg Sabino Mullane) \u003ca href=\"https://postgr.es/c/04bec894a04\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eChecksums can be disabled with the new \u003cspan\u003einitdb\u003c/span\u003e option \u003ccode\u003e--no-data-checksums\u003c/code\u003e. \u003ca href=\"/docs/18/pgupgrade.html\" title=\"pg_upgrade\"\u003e\u003cspan\u003e\u003cspan\u003epg_upgrade\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e requires matching cluster checksum settings, so this new option can be useful to upgrade non-checksum old clusters.\u003c/p\u003e","id":"18.0-a8fa82432892119f","identity_text":"Change app-initdb default to enable data checksums (Greg Sabino Mullane) Checksums can be disabled with the new initdb option --no-data-checksums. pgupgrade requires matching cluster checksum settings, so this new option can be useful to upgrade non-checksum old clusters.","part":"migration","patch_ids":["f78286ddb1f2e6833c76c4a8351542bf"],"related_changes":[{"db_id":"db70c584fb64d9f59231adb14744b4a2","evidence":{"patch_ids":["f78286ddb1f2e6833c76c4a8351542bf"],"same_day":true},"kind":"related","label":"18.0","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-APPS","title":"Change initdb to default to enabling checksums","url":"/docs/compare/?release=18.0#18.0-d9b49042b8f09224","version":"18.0"}],"relations":[{"evidence":{"patch_ids":["f78286ddb1f2e6833c76c4a8351542bf"],"same_day":true},"rule":2,"target":"db70c584fb64d9f59231adb14744b4a2","type":"related"}],"section":"Compatibility","section_path":["Compatibility"],"source_commits":["04bec894a04"],"source_entry_id":"18.0/migration/001","source_hash":"ab496434d25411703b78d251977a161d4f481117f9a61c9a5ed39e5056795861","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","statement_hash":"8b50759677598fe7ea5e5a6df6d0083c36bbd43c74224fd00ca0fd9966a22f2f","text":"Change initdb default to enable data checksums (Greg Sabino Mullane) § Checksums 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.","title":"Change initdb default to enable data checksums","variants":[],"version":"18.0"},{"also_in":[],"category":"compatibility","category_label":"Compatibility","commit_aliases":["d7674c9fa"],"commit_groups":[["d7674c9fa"]],"commits":["d7674c9fa"],"cves":[],"db_id":"2343bc4fd897605d6495c765dfdc2774","html":"\u003cp\u003eChange time zone abbreviation handling (Tom Lane) \u003ca href=\"https://postgr.es/c/d7674c9fa\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe system will now favor the current session's time zone abbreviations before checking the server variable \u003ca href=\"/docs/18/runtime-config-client.html#GUC-TIMEZONE-ABBREVIATIONS\"\u003etimezone_abbreviations\u003c/a\u003e. Previously \u003ccode\u003etimezone_abbreviations\u003c/code\u003e was checked first.\u003c/p\u003e","id":"18.0-d328de9397b5e0d5","identity_text":"Change time zone abbreviation handling (Tom Lane) The system will now favor the current session's time zone abbreviations before checking the server variable guc-timezone-abbreviations . Previously timezone_abbreviations was checked first.","part":"migration","patch_ids":["4fb970b4bd6121eaf0178066f8ea909c"],"related_changes":[],"relations":[],"section":"Compatibility","section_path":["Compatibility"],"source_commits":["d7674c9fa"],"source_entry_id":"18.0/migration/002","source_hash":"ec9a6dbcae9b0cc2ac417b00bc0d62968e91e82fe34d0a8e1e8e63e896b46d5f","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","statement_hash":"f8a25067db2d336959a2f40c8130ac1d55dcd167e4db04c3249bec7147a49eb8","text":"Change time zone abbreviation handling (Tom Lane) § The system will now favor the current session's time zone abbreviations before checking the server variable timezone_abbreviations. Previously timezone_abbreviations was checked first.","title":"Change time zone abbreviation handling","variants":[],"version":"18.0"},{"also_in":[],"category":"compatibility","category_label":"Compatibility","commit_aliases":["db6a4a985"],"commit_groups":[["db6a4a985"]],"commits":["db6a4a985"],"cves":[],"db_id":"30aed22a7b379bfc7e845b051d348d35","html":"\u003cp\u003eDeprecate \u003ca href=\"/docs/18/auth-password.html\" title=\"20.5. Password Authentication\"\u003eMD5 password\u003c/a\u003e authentication (Nathan Bossart) \u003ca href=\"https://postgr.es/c/db6a4a985\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSupport for MD5 passwords will be removed in a future major version release. \u003ca href=\"/docs/18/sql-createrole.html\" title=\"CREATE ROLE\"\u003e\u003cspan\u003eCREATE ROLE\u003c/span\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/sql-alterrole.html\" title=\"ALTER ROLE\"\u003e\u003cspan\u003eALTER ROLE\u003c/span\u003e\u003c/a\u003e now emit deprecation warnings when setting MD5 passwords. These warnings can be disabled by setting the \u003ca href=\"/docs/18/runtime-config-connection.html#GUC-MD5-PASSWORD-WARNINGS\"\u003emd5_password_warnings\u003c/a\u003e parameter to \u003ccode\u003eoff\u003c/code\u003e.\u003c/p\u003e","id":"18.0-5b8f3e9c493f3cfc","identity_text":"Deprecate MD5 password authentication (Nathan Bossart) Support for MD5 passwords will be removed in a future major version release. sql-createrole and sql-alterrole now emit deprecation warnings when setting MD5 passwords. These warnings can be disabled by setting the guc-md5-password-warnings parameter to off.","part":"migration","patch_ids":["8c3ab652b8b1dc2fd0afe67ca881830c"],"related_changes":[],"relations":[],"section":"Compatibility","section_path":["Compatibility"],"source_commits":["db6a4a985"],"source_entry_id":"18.0/migration/003","source_hash":"a3c1406a89e6567a01f463dc017332ee26f86f6513954e4242d41228f630b354","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","statement_hash":"680efa648cd65a0e690a37b96731050a958a0690ae89e623a11e01e1a072488e","text":"Deprecate MD5 password authentication (Nathan Bossart) § Support 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.","title":"Deprecate MD5 password authentication","variants":[],"version":"18.0"},{"also_in":[],"category":"compatibility","category_label":"Compatibility","commit_aliases":["62ddf7ee9"],"commit_groups":[["62ddf7ee9"]],"commits":["62ddf7ee9"],"cves":[],"db_id":"c27156e947f09ff22df4dce5613e8f4c","html":"\u003cp\u003eChange \u003ca href=\"/docs/18/sql-vacuum.html\" title=\"VACUUM\"\u003e\u003cspan\u003eVACUUM\u003c/span\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/sql-analyze.html\" title=\"ANALYZE\"\u003e\u003cspan\u003eANALYZE\u003c/span\u003e\u003c/a\u003e to process the inheritance children of a parent (Michael Harris) \u003ca href=\"https://postgr.es/c/62ddf7ee9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe previous behavior can be performed by using the new \u003ccode\u003eONLY\u003c/code\u003e option.\u003c/p\u003e","id":"18.0-c84ca88e6e5518a9","identity_text":"Change sql-vacuum and sql-analyze to process the inheritance children of a parent (Michael Harris) The previous behavior can be performed by using the new ONLY option.","part":"migration","patch_ids":["29279fd7549098871f985b99df60e141"],"related_changes":[{"db_id":"94f45240a0275d0638838beebe665ece","evidence":{"patch_ids":["29279fd7549098871f985b99df60e141"],"same_day":true},"kind":"related","label":"18.0","source_url":"/docs/release/18.0/#RELEASE-18-UTILITY","title":"Allow VACUUM and ANALYZE to process partitioned tables without processing their children","url":"/docs/compare/?release=18.0#18.0-f2283e0ad8b607f4","version":"18.0"}],"relations":[{"evidence":{"patch_ids":["29279fd7549098871f985b99df60e141"],"same_day":true},"rule":2,"target":"94f45240a0275d0638838beebe665ece","type":"related"}],"section":"Compatibility","section_path":["Compatibility"],"source_commits":["62ddf7ee9"],"source_entry_id":"18.0/migration/004","source_hash":"e38aa345a14711d367987f4fa89c4779eea36ec33d38f095e55fe5cee251a237","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","statement_hash":"76658321347e57068ed0f32921beaf67fdfe6744b563a2f78d0f84beb89c3ac3","text":"Change VACUUM and ANALYZE to process the inheritance children of a parent (Michael Harris) § The previous behavior can be performed by using the new ONLY option.","title":"Change VACUUM and ANALYZE to process the inheritance children of a parent","variants":[],"version":"18.0"},{"also_in":[],"category":"compatibility","category_label":"Compatibility","commit_aliases":["770233748","da8a4c166"],"commit_groups":[["770233748"],["da8a4c166"]],"commits":["770233748","da8a4c166"],"cves":[],"db_id":"4f7cd257e4ad009f611f0caf979d438e","html":"\u003cp\u003ePrevent \u003ca href=\"/docs/18/sql-copy.html\" title=\"COPY\"\u003e\u003ccode\u003eCOPY FROM\u003c/code\u003e\u003c/a\u003e from treating \u003ccode\u003e\\.\u003c/code\u003e as an end-of-file marker when reading \u003cacronym\u003eCSV\u003c/acronym\u003e files (Daniel Vérité, Tom Lane) \u003ca href=\"https://postgr.es/c/770233748\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/da8a4c166\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003ca href=\"/docs/18/app-psql.html\" title=\"psql\"\u003e\u003cspan\u003e\u003cspan\u003epsql\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e will still treat \u003ccode\u003e\\.\u003c/code\u003e as an end-of-file marker when reading \u003cacronym\u003eCSV\u003c/acronym\u003e files from \u003ccode\u003eSTDIN\u003c/code\u003e. Older \u003cspan\u003epsql\u003c/span\u003e clients connecting to \u003cspan\u003ePostgreSQL\u003c/span\u003e 18 servers might experience \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-META-COMMANDS-COPY\"\u003e\u003ccode\u003e\\copy\u003c/code\u003e\u003c/a\u003e problems. This release also enforces that \u003ccode\u003e\\.\u003c/code\u003e must appear alone on a line.\u003c/p\u003e","id":"18.0-dea78a5140a83ea5","identity_text":"Prevent COPY FROM from treating \\. as an end-of-file marker when reading CSV files (Daniel Vérité, Tom Lane) app-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.","part":"migration","patch_ids":["0d4f992d2be4de6ff4cd458ccb95eca4","1ea23822f2f40fda5f44f0d3d8abc20f"],"related_changes":[],"relations":[],"section":"Compatibility","section_path":["Compatibility"],"source_commits":["770233748","da8a4c166"],"source_entry_id":"18.0/migration/005","source_hash":"fea2a46c290c3f9965df10b2e76f7a4d57cffc9ed5493f2366fa39775ad33fe9","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","statement_hash":"e79e11d3871e9ef0892573cfab7e0f55552a205043d862b2e9724ee4c69f4016","text":"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.","title":"Prevent COPY FROM from treating \\. as an end-of-file marker when reading CSV files","variants":[],"version":"18.0"},{"also_in":[],"category":"compatibility","category_label":"Compatibility","commit_aliases":["e2bab2d79"],"commit_groups":[["e2bab2d79"]],"commits":["e2bab2d79"],"cves":[],"db_id":"8118dd69602467d30fb6a9609bba6b70","html":"\u003cp\u003eDisallow unlogged partitioned tables (Michael Paquier) \u003ca href=\"https://postgr.es/c/e2bab2d79\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously \u003ca href=\"/docs/18/sql-altertable.html\" title=\"ALTER TABLE\"\u003e\u003ccode\u003eALTER TABLE SET [UN]LOGGED\u003c/code\u003e\u003c/a\u003e did nothing, and the creation of an unlogged partitioned table did not cause its children to be unlogged.\u003c/p\u003e","id":"18.0-c367683bb470a5d2","identity_text":"Disallow unlogged partitioned tables (Michael Paquier) Previously ALTER TABLE SET [UN]LOGGED did nothing, and the creation of an unlogged partitioned table did not cause its children to be unlogged.","part":"migration","patch_ids":["04e8ab00f8915683a43dd6f436a5c79b"],"related_changes":[],"relations":[],"section":"Compatibility","section_path":["Compatibility"],"source_commits":["e2bab2d79"],"source_entry_id":"18.0/migration/006","source_hash":"2a426f3624dd193ed36b9a5f8e99a1c2b6a654ba9a342e2deb4f460d5d74d69c","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","statement_hash":"3b9bcae38ba730024eb2f2277a64804c55d104dbf649268784801db61ef784c1","text":"Disallow unlogged partitioned tables (Michael Paquier) § Previously ALTER TABLE SET [UN]LOGGED did nothing, and the creation of an unlogged partitioned table did not cause its children to be unlogged.","title":"Disallow unlogged partitioned tables","variants":[],"version":"18.0"},{"also_in":[],"category":"compatibility","category_label":"Compatibility","commit_aliases":["01463e1cc"],"commit_groups":[["01463e1cc"]],"commits":["01463e1cc"],"cves":[],"db_id":"ae8521434650fe5524c9fcaa38acac84","html":"\u003cp\u003eExecute \u003ccode\u003eAFTER\u003c/code\u003e \u003ca href=\"/docs/18/triggers.html\" title=\"Chapter 37. Triggers\"\u003etriggers\u003c/a\u003e as the role that was active when trigger events were queued (Laurenz Albe) \u003ca href=\"https://postgr.es/c/01463e1cc\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously such triggers were run as the role that was active at trigger execution time (e.g., at \u003ca href=\"/docs/18/sql-commit.html\" title=\"COMMIT\"\u003e\u003cspan\u003eCOMMIT\u003c/span\u003e\u003c/a\u003e). This is significant for cases where the role is changed between queue time and transaction commit.\u003c/p\u003e","id":"18.0-0d2c2c2259abf618","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.","part":"migration","patch_ids":["917ba717810e74a1c7c638690cf0f5eb"],"related_changes":[],"relations":[],"section":"Compatibility","section_path":["Compatibility"],"source_commits":["01463e1cc"],"source_entry_id":"18.0/migration/007","source_hash":"f10785acbe9b26f28a8c98e9a00c1d2a4e8afa8c0b7f7291f990211dfc079f53","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","statement_hash":"f0612c07183e11ac71073f5d359d3b0a521ebcc0822d94befe83c23059d03016","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","variants":[],"version":"18.0"},{"also_in":[],"category":"compatibility","category_label":"Compatibility","commit_aliases":["fefa76f70"],"commit_groups":[["fefa76f70"]],"commits":["fefa76f70"],"cves":[],"db_id":"421b9236b8ba45e9981de4acb0936336","html":"\u003cp\u003eRemove non-functional support for rule privileges in \u003ca href=\"/docs/18/sql-grant.html\" title=\"GRANT\"\u003e\u003cspan\u003eGRANT\u003c/span\u003e\u003c/a\u003e/\u003ca href=\"/docs/18/sql-revoke.html\" title=\"REVOKE\"\u003e\u003cspan\u003eREVOKE\u003c/span\u003e\u003c/a\u003e (Fujii Masao) \u003ca href=\"https://postgr.es/c/fefa76f70\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese have been non-functional since \u003cspan\u003ePostgreSQL\u003c/span\u003e 8.2.\u003c/p\u003e","id":"18.0-607cc591e9d82ae8","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.","part":"migration","patch_ids":["1a39a92752613c9674e39e99f119c2de"],"related_changes":[],"relations":[],"section":"Compatibility","section_path":["Compatibility"],"source_commits":["fefa76f70"],"source_entry_id":"18.0/migration/008","source_hash":"db08cd3d3ddd023cec8d6165fd052ba6e7d655cc958d6c238b6f02af024dc1a1","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","statement_hash":"9a9f6ec57f00ae867aca818ec5c55d43899650a49ee6ab2ce0bed4d154bb41b9","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","variants":[],"version":"18.0"},{"also_in":[],"category":"compatibility","category_label":"Compatibility","commit_aliases":["f0d112759"],"commit_groups":[["f0d112759"]],"commits":["f0d112759"],"cves":[],"db_id":"af948e47866b03a70707df9bf672d482","html":"\u003cp\u003eRemove column \u003ca href=\"/docs/18/view-pg-backend-memory-contexts.html\" title=\"53.5. pg_backend_memory_contexts\"\u003e\u003ccode\u003epg_backend_memory_contexts\u003c/code\u003e\u003c/a\u003e.\u003ccode\u003eparent\u003c/code\u003e (Melih Mutlu) \u003ca href=\"https://postgr.es/c/f0d112759\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is no longer needed since \u003ccode\u003epg_backend_memory_contexts\u003c/code\u003e.\u003ccode\u003epath\u003c/code\u003e was added.\u003c/p\u003e","id":"18.0-558a645d00b3f47b","identity_text":"Remove column pg_backend_memory_contexts.parent (Melih Mutlu) This is no longer needed since pg_backend_memory_contexts.path was added.","part":"migration","patch_ids":["91a2e8e9299edf53c184627b3cf053e7"],"related_changes":[],"relations":[],"section":"Compatibility","section_path":["Compatibility"],"source_commits":["f0d112759"],"source_entry_id":"18.0/migration/009","source_hash":"3348da5b519f14fb93b5b2c6235af20ce3d744fa55889ab04d496724498b7727","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","statement_hash":"a4dc378426b8f016478b991a4d989f716af959a3b360b65d527ec7fd450acb6b","text":"Remove column pg_backend_memory_contexts.parent (Melih Mutlu) § This is no longer needed since pg_backend_memory_contexts.path was added.","title":"Remove column pg_backend_memory_contexts.parent","variants":[],"version":"18.0"},{"also_in":[],"category":"compatibility","category_label":"Compatibility","commit_aliases":["32d3ed816","706cbed35","d9e03864b"],"commit_groups":[["32d3ed816"],["706cbed35"],["d9e03864b"]],"commits":["32d3ed816","706cbed35","d9e03864b"],"cves":[],"db_id":"b8c57d935d8b183f9ee20e7477f90abd","html":"\u003cp\u003eChange \u003ccode\u003epg_backend_memory_contexts\u003c/code\u003e.\u003ccode\u003elevel\u003c/code\u003e and \u003ca href=\"/docs/18/functions-admin.html#FUNCTIONS-ADMIN-SIGNAL-TABLE\" title=\"Table 9.96. Server Signaling Functions\"\u003e\u003ccode\u003epg_log_backend_memory_contexts()\u003c/code\u003e\u003c/a\u003e to be one-based (Melih Mutlu, Atsushi Torikoshi, David Rowley, Fujii Masao) \u003ca href=\"https://postgr.es/c/32d3ed816\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/d9e03864b\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/706cbed35\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese were previously zero-based.\u003c/p\u003e","id":"18.0-3bddcb1c02f74659","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.","part":"migration","patch_ids":["3d61500ab7649ba207c5b4742ce83946","845864cc388c5f840e08c3fdf9f3032a","eaa8db2e49e44f9880c123bf159cab42"],"related_changes":[{"db_id":"7ed5d279df474d7ce518a2cd605d091d","evidence":{"patch_ids":["eaa8db2e49e44f9880c123bf159cab42"],"same_day":true},"kind":"related","label":"18.0","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","title":"Add column pg_backend_memory_contexts.path to show memory context parents","url":"/docs/compare/?release=18.0#18.0-f9c2e124d8a94a20","version":"18.0"}],"relations":[{"evidence":{"patch_ids":["eaa8db2e49e44f9880c123bf159cab42"],"same_day":true},"rule":2,"target":"7ed5d279df474d7ce518a2cd605d091d","type":"related"}],"section":"Compatibility","section_path":["Compatibility"],"source_commits":["32d3ed816","706cbed35","d9e03864b"],"source_entry_id":"18.0/migration/010","source_hash":"50bbd1729e746a694a3df7d491e7ab79d0b57696ebbb5127fdc124520b03ee7c","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","statement_hash":"c56bfdda9e9b110545ab282f1be71da486fd1e7af030b2a5c125fe4d37560c98","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","variants":[],"version":"18.0"},{"also_in":[],"category":"compatibility","category_label":"Compatibility","commit_aliases":["fb1a18810f0"],"commit_groups":[["fb1a18810f0"]],"commits":["fb1a18810f0"],"cves":[],"db_id":"14f7ec96f489178a5ba54f0173a2002a","html":"\u003cp\u003eChange \u003ca href=\"/docs/18/textsearch.html\" title=\"Chapter 12. Full Text Search\"\u003efull text search\u003c/a\u003e to use the default collation provider of the cluster to read configuration files and dictionaries, rather than always using libc (Peter Eisentraut) \u003ca href=\"https://postgr.es/c/fb1a18810f0\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eClusters 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 \u003ca href=\"/docs/18/pgtrgm.html\" title=\"F.35. pg_trgm — support for similarity of text using trigram matching\"\u003epg_trgm\u003c/a\u003e extension. When upgrading such clusters using \u003ca href=\"/docs/18/pgupgrade.html\" title=\"pg_upgrade\"\u003e\u003cspan\u003e\u003cspan\u003epg_upgrade\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e, it is recommended to reindex all indexes related to full-text search and \u003cspan\u003epg_trgm\u003c/span\u003e after the upgrade.\u003c/p\u003e","id":"18.0-63b962f0125472b6","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.","part":"migration","patch_ids":["d34589a0ca33552be8913ecb392dc365"],"related_changes":[],"relations":[],"section":"Compatibility","section_path":["Compatibility"],"source_commits":["fb1a18810f0"],"source_entry_id":"18.0/migration/011","source_hash":"e3ce56b4fc2a72cd171306a24ddd0b8daecb530f1409e98a57781871e32f9519","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","statement_hash":"0d016706c1da5d040bed5653360eaa27ed050c9172ff53f737e1221153008011","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["fc069a3a6"],"commit_groups":[["fc069a3a6"]],"commits":["fc069a3a6"],"cves":[],"db_id":"e93aac468afc7b983da5961bc89a6570","html":"\u003cp\u003eAutomatically remove some unnecessary table self-joins (Andrey Lepikhov, Alexander Kuzmenkov, Alexander Korotkov, Alena Rybakina) \u003ca href=\"https://postgr.es/c/fc069a3a6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis optimization can be disabled using server variable \u003ca href=\"/docs/18/runtime-config-query.html#GUC-ENABLE-SELF-JOIN-ELIMINATION\"\u003eenable_self_join_elimination\u003c/a\u003e.\u003c/p\u003e","id":"18.0-680d6a94e6af24a0","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 .","part":"changes","patch_ids":["f4668f24b918872b344ea179b57163cf"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["fc069a3a6"],"source_entry_id":"18.0/changes/001","source_hash":"40c3196e66530b1ad6c86357db78c6683c075a289ecc4fdc11ccdd15d42dafad","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"235c5aa78ae11057e82ffcaba18192f08d816b80c7a4abeb2ccab576de5173f7","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["c0962a113"],"commit_groups":[["c0962a113"]],"commits":["c0962a113"],"cves":[],"db_id":"764cb613ec29b5df2b6d0d9987768083","html":"\u003cp\u003eConvert some \u003ca href=\"/docs/18/functions-comparisons.html#FUNCTIONS-COMPARISONS-IN-SCALAR\" title=\"9.25.1. IN\"\u003e\u003ccode\u003eIN (VALUES ...)\u003c/code\u003e\u003c/a\u003e to \u003ccode\u003ex = ANY ...\u003c/code\u003e for better optimizer statistics (Alena Rybakina, Andrei Lepikhov) \u003ca href=\"https://postgr.es/c/c0962a113\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-d841fa8566ba0e41","identity_text":"Convert some IN (VALUES ...) to x = ANY ... for better optimizer statistics (Alena Rybakina, Andrei Lepikhov)","part":"changes","patch_ids":["f3ef498af7484884fe0fe8d3179d0691"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["c0962a113"],"source_entry_id":"18.0/changes/002","source_hash":"4ba957892aa6172c1ba4d6e4d5242417072a25fa5fb19f26aa2cb93b5cdcea82","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"1994faf6d5d15f3e4a7dbff5aa1cd8f7f3f12341dfdeacdf6a2f1f84be69c14b","text":"Convert some IN (VALUES ...) to x = ANY ... for better optimizer statistics (Alena Rybakina, Andrei Lepikhov) §","title":"Convert some IN (VALUES ...) to x = ANY ... for better optimizer statistics","variants":[],"version":"18.0"},{"also_in":[],"category":"performance","category_label":"Performance","commit_aliases":["ae4569161"],"commit_groups":[["ae4569161"]],"commits":["ae4569161"],"cves":[],"db_id":"2e05a47011ecefd0b4eb07547cc72835","html":"\u003cp\u003eAllow transforming \u003ca href=\"/docs/18/functions-logical.html\" title=\"9.1. Logical Operators\"\u003e\u003ccode\u003eOR\u003c/code\u003e\u003c/a\u003e-clauses to arrays for faster index processing (Alexander Korotkov, Andrey Lepikhov) \u003ca href=\"https://postgr.es/c/ae4569161\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-c98c0b36c2f7ee04","identity_text":"Allow transforming OR-clauses to arrays for faster index processing (Alexander Korotkov, Andrey Lepikhov)","part":"changes","patch_ids":["fb982918d31ae726b84a777e332b6884"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["ae4569161"],"source_entry_id":"18.0/changes/003","source_hash":"5fd9cfd78e09d29f7989ebf65e641d8464ca20ab208b3010f1927e2a5a38d21e","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"02c7be9bbfb909c1719246ac2948e31ec265c3b148e5d9b6ae59b607ffc7865e","text":"Allow transforming OR-clauses to arrays for faster index processing (Alexander Korotkov, Andrey Lepikhov) §","title":"Allow transforming OR-clauses to arrays for faster index processing","variants":[],"version":"18.0"},{"also_in":[],"category":"performance","category_label":"Performance","commit_aliases":["276279295","52c707483","8d96f57d5","908a96861"],"commit_groups":[["276279295"],["52c707483"],["8d96f57d5"],["908a96861"]],"commits":["276279295","52c707483","8d96f57d5","908a96861"],"cves":[],"db_id":"27889e11b1017fcd071cbebfd982e004","html":"\u003cp\u003eSpeed up the processing of \u003ca href=\"/docs/18/sql-select.html#SQL-INTERSECT\" title=\"INTERSECT Clause\"\u003e\u003ccode\u003eINTERSECT\u003c/code\u003e\u003c/a\u003e, \u003ca href=\"/docs/18/sql-select.html#SQL-EXCEPT\" title=\"EXCEPT Clause\"\u003e\u003ccode\u003eEXCEPT\u003c/code\u003e\u003c/a\u003e, \u003ca href=\"/docs/18/tutorial-window.html\" title=\"3.5. Window Functions\"\u003ewindow aggregates\u003c/a\u003e, and \u003ca href=\"/docs/18/sql-createview.html\" title=\"CREATE VIEW\"\u003eview column aliases\u003c/a\u003e (Tom Lane, David Rowley) \u003ca href=\"https://postgr.es/c/52c707483\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/276279295\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/8d96f57d5\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/908a96861\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-3e2b4de2db16b12f","identity_text":"Speed up the processing of INTERSECT, EXCEPT, window aggregates, and view column aliases (Tom Lane, David Rowley)","part":"changes","patch_ids":["88fc8de0d114dd8d37c995d33aa2e424","c34e95d351102295e83eda2c0898ef4f","d6f6d3fc510fd75b0cd2a6ccb16caf21","e02121b5ec912ea613d75476b5d8da31"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["276279295","52c707483","8d96f57d5","908a96861"],"source_entry_id":"18.0/changes/004","source_hash":"91354d1ac2e34f2ac56c584852bd500487ec143feea22c06d2d473ea4526c886","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"67a7f9ceb4d2956015c1be13e9166cb6044290d7faf0fb602f564494e744c06e","text":"Speed up the processing of INTERSECT, EXCEPT, window aggregates, and view column aliases (Tom Lane, David Rowley) § § § §","title":"Speed up the processing of INTERSECT, EXCEPT, window aggregates, and view column aliases","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["a8ccf4e93"],"commit_groups":[["a8ccf4e93"]],"commits":["a8ccf4e93"],"cves":[],"db_id":"e1633e7353cb2e283e589f245c02709b","html":"\u003cp\u003eAllow the keys of \u003ca href=\"/docs/18/sql-select.html#SQL-DISTINCT\" title=\"DISTINCT Clause\"\u003e\u003ccode\u003eSELECT DISTINCT\u003c/code\u003e\u003c/a\u003e to be internally reordered to avoid sorting (Richard Guo) \u003ca href=\"https://postgr.es/c/a8ccf4e93\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis optimization can be disabled using \u003ca href=\"/docs/18/runtime-config-query.html#GUC-ENABLE-DISTINCT-REORDERING\"\u003eenable_distinct_reordering\u003c/a\u003e.\u003c/p\u003e","id":"18.0-e1173d201acd35c6","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 .","part":"changes","patch_ids":["2a4dc17b68562e6259b7bb1052fff9ad"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["a8ccf4e93"],"source_entry_id":"18.0/changes/005","source_hash":"0b3d9b69f68103fec0e196e120de31d7d5ccbd1c26beea05060ff6a886ab9130","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"8e10ed699456a43e5c53f99fc9ddb0ec2951686ee8551c8e706fbd1d1b10766c","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["bd10ec529"],"commit_groups":[["bd10ec529"]],"commits":["bd10ec529"],"cves":[],"db_id":"69820747e9a30607a8a95df47dbabdd6","html":"\u003cp\u003eIgnore \u003ca href=\"/docs/18/sql-select.html#SQL-GROUPBY\" title=\"GROUP BY Clause\"\u003e\u003ccode\u003eGROUP BY\u003c/code\u003e\u003c/a\u003e columns that are functionally dependent on other columns (Zhang Mingli, Jian He, David Rowley) \u003ca href=\"https://postgr.es/c/bd10ec529\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf a \u003ccode\u003eGROUP BY\u003c/code\u003e 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.\u003c/p\u003e","id":"18.0-723dd69ea02477f1","identity_text":"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.","part":"changes","patch_ids":["34cad2fc9ab6206a92e572686514a8b6"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["bd10ec529"],"source_entry_id":"18.0/changes/006","source_hash":"590fd20dfbdf85d87e1c14e1c4ca54d910d8ce015f220e7798d40fa268c94536","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"f79bb17c14f5da30c295cc7cf55f487a682d1912a3cd315fb8c06f09d6f9fd62","text":"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.","title":"Ignore GROUP BY columns that are functionally dependent on other columns","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["247dea89f","67a54b9e8","cc5d98525","f5050f795"],"commit_groups":[["247dea89f"],["67a54b9e8"],["cc5d98525"],["f5050f795"]],"commits":["247dea89f","67a54b9e8","cc5d98525","f5050f795"],"cves":[],"db_id":"e536ba32048335bb638a016ded27116b","html":"\u003cp\u003eAllow some \u003ca href=\"/docs/18/sql-select.html#SQL-HAVING\" title=\"HAVING Clause\"\u003e\u003ccode\u003eHAVING\u003c/code\u003e\u003c/a\u003e clauses on \u003ca href=\"/docs/18/queries-table-expressions.html#QUERIES-GROUPING-SETS\" title=\"7.2.4. GROUPING SETS, CUBE, and ROLLUP\"\u003e\u003ccode\u003eGROUPING SETS\u003c/code\u003e\u003c/a\u003e to be pushed to \u003ca href=\"/docs/18/sql-select.html#SQL-WHERE\" title=\"WHERE Clause\"\u003e\u003ccode\u003eWHERE\u003c/code\u003e\u003c/a\u003e clauses (Richard Guo) \u003ca href=\"https://postgr.es/c/67a54b9e8\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/247dea89f\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/f5050f795\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/cc5d98525\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis allows earlier row filtering. This release also fixes some \u003ccode\u003eGROUPING SETS\u003c/code\u003e queries that used to return incorrect results.\u003c/p\u003e","id":"18.0-28dd1f0f20c4cc4b","identity_text":"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.","part":"changes","patch_ids":["1ae07ed70f6403998c8d004a95303270","302fc509a25f9b4b070cfc2ed497cc05","5ce25769fa8297252747bcadd5fb8096","bb70968006a3e0fdebcd1dd48f3e503a"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["247dea89f","67a54b9e8","cc5d98525","f5050f795"],"source_entry_id":"18.0/changes/007","source_hash":"7d93dee8cbb6c5b43abf85da682b3cd602844df0aad42cdf3bd1b210551f26fb","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"5de0004596ff255cc8fd70e95011362605c186180864bfadb9674a57e084c4d8","text":"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.","title":"Allow some HAVING clauses on GROUPING SETS to be pushed to WHERE clauses","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["036bdcec9","97173536e"],"commit_groups":[["036bdcec9"],["97173536e"]],"commits":["036bdcec9","97173536e"],"cves":[],"db_id":"d82aac51b035bfe8e15d4159c668f73a","html":"\u003cp\u003eImprove row estimates for \u003ca href=\"/docs/18/functions-srf.html#FUNCTIONS-SRF-SERIES\" title=\"Table 9.69. Series Generating Functions\"\u003e\u003ccode\u003egenerate_series()\u003c/code\u003e\u003c/a\u003e using \u003ca href=\"/docs/18/datatype-numeric.html\" title=\"8.1. Numeric Types\"\u003e\u003ccode\u003enumeric\u003c/code\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/datatype-datetime.html\" title=\"8.5. Date/Time Types\"\u003e\u003ccode\u003etimestamp\u003c/code\u003e\u003c/a\u003e values (David Rowley, Song Jinzhou) \u003ca href=\"https://postgr.es/c/036bdcec9\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/97173536e\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-75da163cbd9e48a6","identity_text":"Improve row estimates for generate_series() using numeric and timestamp values (David Rowley, Song Jinzhou)","part":"changes","patch_ids":["1dd699091397089a53c5d457b050033e","804e83795dfcb3c7cca716573e30de6a"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["036bdcec9","97173536e"],"source_entry_id":"18.0/changes/008","source_hash":"bfa62ab567808d130606b57322b3564d5ab00860079455bf2fba489acbfce75f","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"802febfa899f0c3d0039d8e72f923517c82398682ce553e3c5c63f2374a042d7","text":"Improve row estimates for generate_series() using numeric and timestamp values (David Rowley, Song Jinzhou) § §","title":"Improve row estimates for generate_series() using numeric and timestamp values","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["aa86129e1"],"commit_groups":[["aa86129e1"]],"commits":["aa86129e1"],"cves":[],"db_id":"f76a8468845b91ddcffeaa33fa3400a0","html":"\u003cp\u003eAllow the optimizer to use \u003ccode\u003eRight Semi Join\u003c/code\u003e plans (Richard Guo) \u003ca href=\"https://postgr.es/c/aa86129e1\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSemi-joins are used when needing to find if there is at least one match.\u003c/p\u003e","id":"18.0-70a56ade34590ddd","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.","part":"changes","patch_ids":["79e6e1842e88c7f535ade4eaba7be513"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["aa86129e1"],"source_entry_id":"18.0/changes/009","source_hash":"619b5f1bfc705891d795ac9ab763f6362d300120b9a2d649250a5fb0fe617a45","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"117c31abccc7e061fab7475bec0bdf75e420f53925d5e95de87e71dad3cea951","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["828e94c9d"],"commit_groups":[["828e94c9d"]],"commits":["828e94c9d"],"cves":[],"db_id":"7e8d7bcff75eca9f6d3794b3ed0388fb","html":"\u003cp\u003eAllow merge joins to use \u003ca href=\"/docs/18/runtime-config-query.html#GUC-ENABLE-INCREMENTAL-SORT\"\u003eincremental sorts\u003c/a\u003e (Richard Guo) \u003ca href=\"https://postgr.es/c/828e94c9d\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-0bf93b27e1b1c8e2","identity_text":"Allow merge joins to use incremental sorts (Richard Guo)","part":"changes","patch_ids":["22cb8f9f6594048e5c90b7c0a948ea39"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["828e94c9d"],"source_entry_id":"18.0/changes/010","source_hash":"232faeb186a197cb2d471ce89d7969bca2593ea44e545f90f86f5ec9974800b1","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"c730545e91cae06688ba34e2ac9097a5800e1f311eaa283af2f272f7a1ac2767","text":"Allow merge joins to use incremental sorts (Richard Guo) §","title":"Allow merge joins to use incremental sorts","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["88f55bc97","d69d45a5a"],"commit_groups":[["88f55bc97"],["d69d45a5a"]],"commits":["88f55bc97","d69d45a5a"],"cves":[],"db_id":"6365c622e7f4156b307f731e72d9a3de","html":"\u003cp\u003eImprove the efficiency of planning queries accessing many partitions (Ashutosh Bapat, Yuya Watari, David Rowley) \u003ca href=\"https://postgr.es/c/88f55bc97\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/d69d45a5a\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-200b52f9d63401ad","identity_text":"Improve the efficiency of planning queries accessing many partitions (Ashutosh Bapat, Yuya Watari, David Rowley)","part":"changes","patch_ids":["15b3816633681459d9dd93e64a48ce0d","ba8aa7045b27e8a9467ad9df65f2a614"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["88f55bc97","d69d45a5a"],"source_entry_id":"18.0/changes/011","source_hash":"7cec6b7a3c4b0b96689bd0d68404844c350a00677ea88e38b124b1582f228d77","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"abf3aa0c2277a1dc8d9ddb61b3ffe1d2c987f7e7d4295a9d96f9ad75fa3f8e2a","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["513f4472a","9b282a935"],"commit_groups":[["513f4472a"],["9b282a935"]],"commits":["513f4472a","9b282a935"],"cves":[],"db_id":"e1323b3c594bfa821577fa9462f03cdb","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/runtime-config-query.html#GUC-ENABLE-PARTITIONWISE-JOIN\"\u003epartitionwise joins\u003c/a\u003e in more cases, and reduce its memory usage (Richard Guo, Tom Lane, Ashutosh Bapat) \u003ca href=\"https://postgr.es/c/9b282a935\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/513f4472a\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-cd058ce20aafebed","identity_text":"Allow partitionwise joins in more cases, and reduce its memory usage (Richard Guo, Tom Lane, Ashutosh Bapat)","part":"changes","patch_ids":["2ff70c110f54ba540a2cece6e3a512cd","dd416b1d8a4d68e28e16f90c7055e0bb"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["513f4472a","9b282a935"],"source_entry_id":"18.0/changes/012","source_hash":"cccb81e8d167297ee2b086955ed9914693ecfdb1803b07df4ff007a993b1d1bd","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"40327e199cf2577490955fbcc74c05fe2901108bec3acfe4621734a986af7685","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["fae535da0"],"commit_groups":[["fae535da0"]],"commits":["fae535da0"],"cves":[],"db_id":"c65e9805a7d1ddaa6d1373559e4cc29f","html":"\u003cp\u003eImprove cost estimates of partition queries (Nikita Malakhov, Andrei Lepikhov) \u003ca href=\"https://postgr.es/c/fae535da0\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-0a96c3f22c743902","identity_text":"Improve cost estimates of partition queries (Nikita Malakhov, Andrei Lepikhov)","part":"changes","patch_ids":["61b7fea36f21c950e67f8bac538e8fce"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["fae535da0"],"source_entry_id":"18.0/changes/013","source_hash":"ad72fe467357e9b21f201ea22bac15faa0c66b16f28d43cb9b3f490b554ae9db","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"a36db3cf18d61186e69ff7181df62ed65dd845c1892191555ce2f6c4eecb52bd","text":"Improve cost estimates of partition queries (Nikita Malakhov, Andrei Lepikhov) §","title":"Improve cost estimates of partition queries","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["09b07c295","0dca5d68d"],"commit_groups":[["09b07c295"],["0dca5d68d"]],"commits":["09b07c295","0dca5d68d"],"cves":[],"db_id":"de187fd5833da9236d39e17a824451c0","html":"\u003cp\u003eImprove \u003ca href=\"/docs/18/xfunc-sql.html\" title=\"36.5. Query Language (SQL) Functions\"\u003e\u003cacronym\u003eSQL\u003c/acronym\u003e-language function\u003c/a\u003e plan caching (Alexander Pyhalov, Tom Lane) \u003ca href=\"https://postgr.es/c/0dca5d68d\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/09b07c295\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-0ed62a6dcc6eb60c","identity_text":"Improve SQL-language function plan caching (Alexander Pyhalov, Tom Lane)","part":"changes","patch_ids":["254214644dc444095fdc1eed63435eea","aca8b43ca22cd7e20074fc7a0a7722ba"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["09b07c295","0dca5d68d"],"source_entry_id":"18.0/changes/014","source_hash":"624d5ebd4fbd3484e763f4ffd477ed7308b2ba7c3b507bfe163d59e440d1c9f2","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"146626d1f5aff4758ae17dc01f8d5f905420813c8aeb98087d9ca08c5471eb23","text":"Improve SQL-language function plan caching (Alexander Pyhalov, Tom Lane) § §","title":"Improve SQL-language function plan caching","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["e22253467"],"commit_groups":[["e22253467"]],"commits":["e22253467"],"cves":[],"db_id":"6af674fe85c6718d1c2ae803cc5fa2d4","html":"\u003cp\u003eImprove handling of disabled optimizer features (Robert Haas) \u003ca href=\"https://postgr.es/c/e22253467\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-81f4be5c092dad16","identity_text":"Improve handling of disabled optimizer features (Robert Haas)","part":"changes","patch_ids":["78269645a1e3bdd21fcde369b7fb1c82"],"related_changes":[],"relations":[],"section":"Server / Optimizer","section_path":["Server","Optimizer"],"source_commits":["e22253467"],"source_entry_id":"18.0/changes/015","source_hash":"3ac7c9a012dfeb824499ec299452a4443f811573d8cdc48a32a87591feb62e84","source_url":"/docs/release/18.0/#RELEASE-18-OPTIMIZER","statement_hash":"0dcbf8861cd7ba230ddcdaf5746f5f46a4f85aa3e242a34f907c8eadbc61f43c","text":"Improve handling of disabled optimizer features (Robert Haas) §","title":"Improve handling of disabled optimizer features","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["8a510275d","92fe23d93"],"commit_groups":[["8a510275d"],["92fe23d93"]],"commits":["8a510275d","92fe23d93"],"cves":[],"db_id":"d6862625b987b44876b5f8813415e301","html":"\u003cp\u003eAllow skip scans of \u003ca href=\"/docs/18/xfunc-sql.html\" title=\"36.5. Query Language (SQL) Functions\"\u003ebtree\u003c/a\u003e indexes (Peter Geoghegan) \u003ca href=\"https://postgr.es/c/92fe23d93\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/8a510275d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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.\u003c/p\u003e","id":"18.0-5c8b8535c34dd690","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.","part":"changes","patch_ids":["635b38c19244d008c0a276c87c34aabf","e61ae831ab07aa91f44cf34554c51986"],"related_changes":[],"relations":[],"section":"Server / Indexes","section_path":["Server","Indexes"],"source_commits":["8a510275d","92fe23d93"],"source_entry_id":"18.0/changes/016","source_hash":"6fc7b9601b88e3906c876c63e64c4ed31901ffef59984e3a9f3c5467cf0e520e","source_url":"/docs/release/18.0/#RELEASE-18-INDEXES","statement_hash":"5f70bac2450552918acb0585c69d065150051c94ca3fd7c0e78accb784965d18","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["9d6db8bec","f278e1fe3"],"commit_groups":[["9d6db8bec"],["f278e1fe3"]],"commits":["9d6db8bec","f278e1fe3"],"cves":[],"db_id":"494315b065e8cf257c51cc573e8cd5ba","html":"\u003cp\u003eAllow non-btree unique indexes to be used as partition keys and in materialized views (Mark Dilger) \u003ca href=\"https://postgr.es/c/f278e1fe3\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/9d6db8bec\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe index type must still support equality.\u003c/p\u003e","id":"18.0-50b6cc437d755b78","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.","part":"changes","patch_ids":["5bf1633970b359c47772a29d428891b9","afc683b089394ea6ac807e8fc8c1d9ac"],"related_changes":[],"relations":[],"section":"Server / Indexes","section_path":["Server","Indexes"],"source_commits":["9d6db8bec","f278e1fe3"],"source_entry_id":"18.0/changes/017","source_hash":"48d1dc2e21671ed03ec096681269e55993854a87f636152113525b845910da6b","source_url":"/docs/release/18.0/#RELEASE-18-INDEXES","statement_hash":"8627db4022a3b996448b3199a1438d065510142c1a86887f48fb1af1aa338936","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["8492feb98"],"commit_groups":[["8492feb98"]],"commits":["8492feb98"],"cves":[],"db_id":"679afe20174701f36f8833868fba691a","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/gin.html\" title=\"65.4. GIN Indexes\"\u003e\u003ccode\u003eGIN\u003c/code\u003e\u003c/a\u003e indexes to be created in parallel (Tomas Vondra, Matthias van de Meent) \u003ca href=\"https://postgr.es/c/8492feb98\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-456432f04301fe8e","identity_text":"Allow GIN indexes to be created in parallel (Tomas Vondra, Matthias van de Meent)","part":"changes","patch_ids":["86bbb2d786cd9282ec7c0990ac84734b"],"related_changes":[],"relations":[],"section":"Server / Indexes","section_path":["Server","Indexes"],"source_commits":["8492feb98"],"source_entry_id":"18.0/changes/018","source_hash":"01c6d664aa699cd5856bca9e8beb983f220a3bbc4ba438ca287685b016c76882","source_url":"/docs/release/18.0/#RELEASE-18-INDEXES","statement_hash":"4dc151279990477d351d79cd8abfd0af480e2cc275a31cbd790f45a0e112db39","text":"Allow GIN indexes to be created in parallel (Tomas Vondra, Matthias van de Meent) §","title":"Allow GIN indexes to be created in parallel","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["e9e7b6604"],"commit_groups":[["e9e7b6604"]],"commits":["e9e7b6604"],"cves":[],"db_id":"bb89183dc8713a98a5f1732f23ebf357","html":"\u003cp\u003eAllow values to be sorted to speed range-type \u003ca href=\"/docs/18/gist.html\" title=\"65.2. GiST Indexes\"\u003eGiST\u003c/a\u003e and \u003ca href=\"/docs/18/btree.html\" title=\"65.1. B-Tree Indexes\"\u003ebtree\u003c/a\u003e index builds (Bernd Helmle) \u003ca href=\"https://postgr.es/c/e9e7b6604\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-36a61764cd73198e","identity_text":"Allow values to be sorted to speed range-type GiST and btree index builds (Bernd Helmle)","part":"changes","patch_ids":["21b0be863bb11025af07f036adc715cd"],"related_changes":[],"relations":[],"section":"Server / Indexes","section_path":["Server","Indexes"],"source_commits":["e9e7b6604"],"source_entry_id":"18.0/changes/019","source_hash":"ac18bed164464842781add926baf8a19f9b384695cfa6ffc14d622e837b24226","source_url":"/docs/release/18.0/#RELEASE-18-INDEXES","statement_hash":"1110884a4b4193d0fb56b65604f1f84d06c9b027816ac2b2f97f7eb335548e6f","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","variants":[],"version":"18.0"},{"also_in":[],"category":"performance","category_label":"Performance","commit_aliases":["02844012b","047cba7fa","06fb5612c","10f664684","12ce89fd0","247ce06b8","2a5e709e7","50cb7505b","55b454d0e","c325a7633","da7226993"],"commit_groups":[["02844012b"],["047cba7fa"],["06fb5612c"],["10f664684"],["12ce89fd0"],["247ce06b8"],["2a5e709e7"],["50cb7505b"],["55b454d0e"],["c325a7633"],["da7226993"]],"commits":["02844012b","047cba7fa","06fb5612c","10f664684","12ce89fd0","247ce06b8","2a5e709e7","50cb7505b","55b454d0e","c325a7633","da7226993"],"cves":[],"db_id":"37483c0834752f309aa567f79e0fff73","html":"\u003cp\u003eAdd an asynchronous I/O subsystem (Andres Freund, Thomas Munro, Nazir Bilal Yavuz, Melanie Plageman) \u003ca href=\"https://postgr.es/c/02844012b\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/da7226993\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/55b454d0e\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/247ce06b8\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/10f664684\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/06fb5612c\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/c325a7633\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/50cb7505b\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/047cba7fa\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/12ce89fd0\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/2a5e709e7\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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 \u003ca href=\"/docs/18/runtime-config-resource.html#GUC-IO-METHOD\"\u003eio_method\u003c/a\u003e, with server variables \u003ca href=\"/docs/18/runtime-config-resource.html#GUC-IO-COMBINE-LIMIT\"\u003eio_combine_limit\u003c/a\u003e and \u003ca href=\"/docs/18/runtime-config-resource.html#GUC-IO-MAX-COMBINE-LIMIT\"\u003eio_max_combine_limit\u003c/a\u003e added to control it. This also enables \u003ca href=\"/docs/18/runtime-config-resource.html#GUC-EFFECTIVE-IO-CONCURRENCY\"\u003eeffective_io_concurrency\u003c/a\u003e and \u003ca href=\"/docs/18/runtime-config-resource.html#GUC-MAINTENANCE-IO-CONCURRENCY\"\u003emaintenance_io_concurrency\u003c/a\u003e values greater than zero for systems without \u003ccode\u003efadvise()\u003c/code\u003e support. The new system view \u003ca href=\"/docs/18/view-pg-aios.html\" title=\"53.2. pg_aios\"\u003e\u003ccode\u003epg_aios\u003c/code\u003e\u003c/a\u003e shows the file handles being used for asynchronous I/O.\u003c/p\u003e","id":"18.0-fa23d49e1bbd33bf","identity_text":"Add an asynchronous I/O subsystem (Andres Freund, Thomas Munro, Nazir Bilal Yavuz, Melanie Plageman) This 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 guc-io-method , with server variables guc-io-combine-limit and guc-io-max-combine-limit added to control it. This also enables guc-effective-io-concurrency and guc-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.","part":"changes","patch_ids":["00a9c4d43ad5f440c73f46761173fb9b","0dbc83e3df4c59c2ca262ef445628a22","27d018309a2572d361015743ee98324a","4d8f6ef76cf84da9e8ef4cb69e686748","4f97e5094bf3ab32f794535fbb774657","69011e9c5887d0368badf9df4b6cdb59","6fe75ee49c9ddb6673fc72c6316a6cac","935377894ec40d13d8a0a722ff34d52e","9e38c5e8ef550e2076bcc2e8ab7b4e16","b7142d9ad8162a459c188b676c6a8396","b78c6771a059bc73ee21df19448cd72b"],"related_changes":[],"relations":[],"section":"Server / General Performance","section_path":["Server","General Performance"],"source_commits":["02844012b","047cba7fa","06fb5612c","10f664684","12ce89fd0","247ce06b8","2a5e709e7","50cb7505b","55b454d0e","c325a7633","da7226993"],"source_entry_id":"18.0/changes/020","source_hash":"fdd8656bbf1cf11f97d6fd57102a43e430a4b1b8d8c4d686a0a5ea63a4b0770c","source_url":"/docs/release/18.0/#RELEASE-18-PERFORMANCE","statement_hash":"b96b1508b7345c107e04bf5e3067b8f434fdad4aab6e74bb8cac2ed82dad1d3c","text":"Add an asynchronous I/O subsystem (Andres Freund, Thomas Munro, Nazir Bilal Yavuz, Melanie Plageman) § § § § § § § § § § § This 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.","title":"Add an asynchronous I/O subsystem","variants":[],"version":"18.0"},{"also_in":[],"category":"performance","category_label":"Performance","commit_aliases":["c4d5cb71d"],"commit_groups":[["c4d5cb71d"]],"commits":["c4d5cb71d"],"cves":[],"db_id":"aff48c3c83b235bf18a030e9ccc9c3b8","html":"\u003cp\u003eImprove the locking performance of queries that access many relations (Tomas Vondra) \u003ca href=\"https://postgr.es/c/c4d5cb71d\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-bdbe76807453073a","identity_text":"Improve the locking performance of queries that access many relations (Tomas Vondra)","part":"changes","patch_ids":["fc2837c0cff32783885ae70d5fbb55db"],"related_changes":[],"relations":[],"section":"Server / General Performance","section_path":["Server","General Performance"],"source_commits":["c4d5cb71d"],"source_entry_id":"18.0/changes/021","source_hash":"166ed61e81ac65ed621694d2130b525d95cd6eabf81198d9051b9df5a5471b51","source_url":"/docs/release/18.0/#RELEASE-18-PERFORMANCE","statement_hash":"bbf31aaa998b69605f19fb5f3337b504b4ae92cf39abf056f16dadd0b84efe2d","text":"Improve the locking performance of queries that access many relations (Tomas Vondra) §","title":"Improve the locking performance of queries that access many relations","variants":[],"version":"18.0"},{"also_in":[],"category":"performance","category_label":"Performance","commit_aliases":["0f5738202","4d143509c","626df47ad","a0942f441","adf97c156"],"commit_groups":[["0f5738202"],["4d143509c"],["626df47ad"],["a0942f441"],["adf97c156"]],"commits":["0f5738202","4d143509c","626df47ad","a0942f441","adf97c156"],"cves":[],"db_id":"8f6bb5232a0af20918ef87fc2bd9b72d","html":"\u003cp\u003eImprove the performance and reduce memory usage of hash joins and \u003ca href=\"/docs/18/sql-select.html#SQL-GROUPBY\" title=\"GROUP BY Clause\"\u003e\u003ccode\u003eGROUP BY\u003c/code\u003e\u003c/a\u003e (David Rowley, Jeff Davis) \u003ca href=\"https://postgr.es/c/adf97c156\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/0f5738202\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/4d143509c\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/a0942f441\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/626df47ad\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis also improves hash set operations used by \u003ca href=\"/docs/18/sql-select.html#SQL-EXCEPT\" title=\"EXCEPT Clause\"\u003e\u003ccode\u003eEXCEPT\u003c/code\u003e\u003c/a\u003e, and hash lookups of subplan values.\u003c/p\u003e","id":"18.0-b0a8003dc1022a25","identity_text":"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.","part":"changes","patch_ids":["1758487f83257304f9b99a49b55241a1","19978010109b328fc13a2f60b64a87b4","5aefbddf9e57264554b8994d3a88ae3a","66b388b0b82ff195761808bbad7daaa9","951eca554a095ba4544d50657927742d"],"related_changes":[],"relations":[],"section":"Server / General Performance","section_path":["Server","General Performance"],"source_commits":["0f5738202","4d143509c","626df47ad","a0942f441","adf97c156"],"source_entry_id":"18.0/changes/022","source_hash":"9f547ee246a07784a2bed2c258eb059c7b92ae34cf3cf037fa83d8419df57bcc","source_url":"/docs/release/18.0/#RELEASE-18-PERFORMANCE","statement_hash":"4661b20ed989107cc31aef5019cf8c04bc8793452b44fba95b5618841ad4db50","text":"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.","title":"Improve the performance and reduce memory usage of hash joins and GROUP BY","variants":[],"version":"18.0"},{"also_in":[],"category":"performance","category_label":"Performance","commit_aliases":["052026c9b","06eae9e62"],"commit_groups":[["052026c9b"],["06eae9e62"]],"commits":["052026c9b","06eae9e62"],"cves":[],"db_id":"b143946a18139ecebf85f4773c7419b5","html":"\u003cp\u003eAllow normal vacuums to freeze some pages, even though they are all-visible (Melanie Plageman) \u003ca href=\"https://postgr.es/c/052026c9b\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/06eae9e62\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis reduces the overhead of later full-relation freezing. The aggressiveness of this can be controlled by server variable and per-table setting \u003ca href=\"/docs/18/runtime-config-vacuum.html#GUC-VACUUM-MAX-EAGER-FREEZE-FAILURE-RATE\"\u003evacuum_max_eager_freeze_failure_rate\u003c/a\u003e. Previously vacuum never processed all-visible pages until freezing was required.\u003c/p\u003e","id":"18.0-9d04d053554c175a","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.","part":"changes","patch_ids":["67ea98ee74614c1e13cce028969b4f44","d3f807b22dffb17b1216f302711474dd"],"related_changes":[],"relations":[],"section":"Server / General Performance","section_path":["Server","General Performance"],"source_commits":["052026c9b","06eae9e62"],"source_entry_id":"18.0/changes/023","source_hash":"067908e36f6001abfd9b89898d6468091c7c408aba70fd6644ef0e6e78945b17","source_url":"/docs/release/18.0/#RELEASE-18-PERFORMANCE","statement_hash":"1d01a6afb8bdd666bc7b3013928540e3f748fdac185055067dcbcfcb19976f2d","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","variants":[],"version":"18.0"},{"also_in":[],"category":"performance","category_label":"Performance","commit_aliases":["0164a0f9e"],"commit_groups":[["0164a0f9e"]],"commits":["0164a0f9e"],"cves":[],"db_id":"d1bf74ed1cb4e3fbacc9001855d15f16","html":"\u003cp\u003eAdd server variable \u003ca href=\"/docs/18/runtime-config-vacuum.html#GUC-VACUUM-TRUNCATE\"\u003evacuum_truncate\u003c/a\u003e to control file truncation during \u003ca href=\"/docs/18/sql-vacuum.html\" title=\"VACUUM\"\u003e\u003cspan\u003eVACUUM\u003c/span\u003e\u003c/a\u003e (Nathan Bossart, Gurjeet Singh) \u003ca href=\"https://postgr.es/c/0164a0f9e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eA storage-level parameter with the same name and behavior already existed.\u003c/p\u003e","id":"18.0-f532d30d19208618","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.","part":"changes","patch_ids":["be7bc9e56cdce4915b9e4a702d43e637"],"related_changes":[],"relations":[],"section":"Server / General Performance","section_path":["Server","General Performance"],"source_commits":["0164a0f9e"],"source_entry_id":"18.0/changes/024","source_hash":"3bdf7d1f300811ca038842a0cc4e774e2520f4329d021c60a179b690525ba77f","source_url":"/docs/release/18.0/#RELEASE-18-PERFORMANCE","statement_hash":"944b8ce94c10828d6d6910957cf641b88dc95d22b1b8115647738cec01db9fbe","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","variants":[],"version":"18.0"},{"also_in":[],"category":"performance","category_label":"Performance","commit_aliases":["cc6be07eb","ff79b5b2a"],"commit_groups":[["cc6be07eb"],["ff79b5b2a"]],"commits":["cc6be07eb","ff79b5b2a"],"cves":[],"db_id":"426d3063330d1605a0f8dada895702c7","html":"\u003cp\u003eIncrease server variables \u003ca href=\"/docs/18/runtime-config-resource.html#GUC-EFFECTIVE-IO-CONCURRENCY\"\u003eeffective_io_concurrency\u003c/a\u003e's and \u003ca href=\"/docs/18/runtime-config-resource.html#GUC-MAINTENANCE-IO-CONCURRENCY\"\u003emaintenance_io_concurrency\u003c/a\u003e's default values to 16 (Melanie Plageman) \u003ca href=\"https://postgr.es/c/ff79b5b2a\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/cc6be07eb\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis more accurately reflects modern hardware.\u003c/p\u003e","id":"18.0-6a0f68c7a6c59848","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.","part":"changes","patch_ids":["5048dc209f8f981f9a097d9636573570","711b2163ed88e992fa8f7ebd50bcabfe"],"related_changes":[],"relations":[],"section":"Server / General Performance","section_path":["Server","General Performance"],"source_commits":["cc6be07eb","ff79b5b2a"],"source_entry_id":"18.0/changes/025","source_hash":"5ed1ab656f1d067bc897340478dcbb402d18bafb76ff5da9b9bec5940ff0e6da","source_url":"/docs/release/18.0/#RELEASE-18-PERFORMANCE","statement_hash":"2388b7de66243eaf67d83494c797d6d1e1d27a9f5ff72da1c364e2e04896d1a4","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["9219093ca"],"commit_groups":[["9219093ca"]],"commits":["9219093ca"],"cves":[],"db_id":"ff5e5f18a1f9dca408cdf9912c05dbc0","html":"\u003cp\u003eIncrease the logging granularity of server variable \u003ca href=\"/docs/18/runtime-config-logging.html#GUC-LOG-CONNECTIONS\"\u003elog_connections\u003c/a\u003e (Melanie Plageman) \u003ca href=\"https://postgr.es/c/9219093ca\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis server variable was previously only boolean, which is still supported.\u003c/p\u003e","id":"18.0-7eca16540c485be9","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.","part":"changes","patch_ids":["a7e481af208e8edfa0f5fb1487d6f5da"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["9219093ca"],"source_entry_id":"18.0/changes/026","source_hash":"42fa035457ddebe4280da1ffdf030abca58669ddee1f4de16c1998a7b9a4dfb2","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"bdb1f75b5ad766542e4be765b90646c65665a1de272e063859e8ddf2ad109820","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["18cd15e70"],"commit_groups":[["18cd15e70"]],"commits":["18cd15e70"],"cves":[],"db_id":"91c81466b98e0b8e4a0d92321b5a517e","html":"\u003cp\u003eAdd \u003ccode\u003elog_connections\u003c/code\u003e option to report the duration of connection stages (Melanie Plageman) \u003ca href=\"https://postgr.es/c/18cd15e70\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-5ced21ab8b3e15c8","identity_text":"Add log_connections option to report the duration of connection stages (Melanie Plageman)","part":"changes","patch_ids":["1b950cb014853bc85d486bf75efaca9d"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["18cd15e70"],"source_entry_id":"18.0/changes/027","source_hash":"41a344a0928e2afe9e641f311ef5ab55d86e85bce333e6a88a6a3c60f59cbdfb","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"16c0cad808e5939e479b2dd348ffdbb2ae9c55f3e23728d50e88003bece7df2c","text":"Add log_connections option to report the duration of connection stages (Melanie Plageman) §","title":"Add log_connections option to report the duration of connection stages","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["3516ea768"],"commit_groups":[["3516ea768"]],"commits":["3516ea768"],"cves":[],"db_id":"ec6128df26d217a2eecd0111f2e4d0a0","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/runtime-config-logging.html#GUC-LOG-LINE-PREFIX\"\u003elog_line_prefix\u003c/a\u003e escape \u003ccode\u003e%L\u003c/code\u003e to output the client \u003cacronym\u003eIP\u003c/acronym\u003e address (Greg Sabino Mullane) \u003ca href=\"https://postgr.es/c/3516ea768\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-929b539b3ad17261","identity_text":"Add guc-log-line-prefix escape %L to output the client IP address (Greg Sabino Mullane)","part":"changes","patch_ids":["245982fa5f97063e1932c06fd291a313"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["3516ea768"],"source_entry_id":"18.0/changes/028","source_hash":"1bdebb7b546333fd73fa5598efd7d15966692b03acaa8bf3b6823e7257095700","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"9dce6737c13142a305d26993679d19f61298311469a6a7edc10ef7bcb6bcbfd5","text":"Add log_line_prefix escape %L to output the client IP address (Greg Sabino Mullane) §","title":"Add log_line_prefix escape %L to output the client IP address","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["6d376c3b0","73bdcfab3"],"commit_groups":[["6d376c3b0"],["73bdcfab3"]],"commits":["6d376c3b0","73bdcfab3"],"cves":[],"db_id":"d8e2695d01232405d3118fd953a35550","html":"\u003cp\u003eAdd server variable \u003ca href=\"/docs/18/runtime-config-logging.html#GUC-LOG-LOCK-FAILURES\"\u003elog_lock_failures\u003c/a\u003e to log lock acquisition failures (Yuki Seino, Fujii Masao) \u003ca href=\"https://postgr.es/c/6d376c3b0\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/73bdcfab3\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eSpecifically it reports \u003ca href=\"/docs/18/sql-select.html#SQL-FOR-UPDATE-SHARE\" title=\"The Locking Clause\"\u003e\u003ccode\u003eSELECT ... NOWAIT\u003c/code\u003e\u003c/a\u003e lock failures.\u003c/p\u003e","id":"18.0-4edb641e0b8b7969","identity_text":"Add server variable guc-log-lock-failures to log lock acquisition failures (Yuki Seino, Fujii Masao) Specifically it reports SELECT ... NOWAIT lock failures.","part":"changes","patch_ids":["b077959c977125e9f3753f321bc477a3","e967c5c76962ab8a50984a559a44af22"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["6d376c3b0","73bdcfab3"],"source_entry_id":"18.0/changes/029","source_hash":"a88dff59604d880435132b5b633e2eb67a03d39010449f6c677e07aa3e5c5da7","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"86481d735160d1d7650fa217441fd2d70ed271d146fb44fd372e52c1bbfa1210","text":"Add server variable log_lock_failures to log lock acquisition failures (Yuki Seino, Fujii Masao) § § Specifically it reports SELECT ... NOWAIT lock failures.","title":"Add server variable log_lock_failures to log lock acquisition failures","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["30a6ed0ce"],"commit_groups":[["30a6ed0ce"]],"commits":["30a6ed0ce"],"cves":[],"db_id":"9671d2c26d28bca864a1d36f60376f71","html":"\u003cp\u003eModify \u003ca href=\"/docs/18/monitoring-stats.html#MONITORING-PG-STAT-ALL-TABLES-VIEW\" title=\"27.2.19. pg_stat_all_tables\"\u003e\u003ccode\u003epg_stat_all_tables\u003c/code\u003e\u003c/a\u003e and its variants to report the time spent in \u003ca href=\"/docs/18/sql-vacuum.html\" title=\"VACUUM\"\u003e\u003cspan\u003eVACUUM\u003c/span\u003e\u003c/a\u003e, \u003ca href=\"/docs/18/sql-analyze.html\" title=\"ANALYZE\"\u003e\u003cspan\u003eANALYZE\u003c/span\u003e\u003c/a\u003e, and their \u003ca href=\"/docs/18/routine-vacuuming.html#AUTOVACUUM\" title=\"24.1.6. The Autovacuum Daemon\"\u003eautomatic\u003c/a\u003e variants (Sami Imseih) \u003ca href=\"https://postgr.es/c/30a6ed0ce\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe new columns are \u003ccode\u003etotal_vacuum_time\u003c/code\u003e, \u003ccode\u003etotal_autovacuum_time\u003c/code\u003e, \u003ccode\u003etotal_analyze_time\u003c/code\u003e, and \u003ccode\u003etotal_autoanalyze_time\u003c/code\u003e.\u003c/p\u003e","id":"18.0-097f657303fd725e","identity_text":"Modify pg_stat_all_tables and its variants to report the time spent in sql-vacuum , sql-analyze , and their automatic variants (Sami Imseih) The new columns are total_vacuum_time, total_autovacuum_time, total_analyze_time, and total_autoanalyze_time.","part":"changes","patch_ids":["c2b3c6594a2d8e4e4efcb86b21ade10b"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["30a6ed0ce"],"source_entry_id":"18.0/changes/030","source_hash":"2092521e84d65496371a602695e86f1b45f3598fa64282cc8e1cb2df767cc998","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"904912b4331b059b0493e73dfb45564c4e6f06521c6face3aed12e28924a3bde","text":"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.","title":"Modify pg_stat_all_tables and its variants to report the time spent in VACUUM, ANALYZE, and their automatic variants","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["7720082ae","bb8dff999"],"commit_groups":[["7720082ae"],["bb8dff999"]],"commits":["7720082ae","bb8dff999"],"cves":[],"db_id":"bea9d94f702a252ba6381f744ff75946","html":"\u003cp\u003eAdd delay time reporting to \u003ca href=\"/docs/18/sql-vacuum.html\" title=\"VACUUM\"\u003e\u003cspan\u003eVACUUM\u003c/span\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/sql-analyze.html\" title=\"ANALYZE\"\u003e\u003cspan\u003eANALYZE\u003c/span\u003e\u003c/a\u003e (Bertrand Drouvot, Nathan Bossart) \u003ca href=\"https://postgr.es/c/bb8dff999\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/7720082ae\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis information appears in the server log, the system views \u003ca href=\"/docs/18/progress-reporting.html#VACUUM-PROGRESS-REPORTING\" title=\"27.4.5. VACUUM Progress Reporting\"\u003e\u003ccode\u003epg_stat_progress_vacuum\u003c/code\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/progress-reporting.html#PG-STAT-PROGRESS-ANALYZE-VIEW\" title=\"Table 27.38. pg_stat_progress_analyze View\"\u003e\u003ccode\u003epg_stat_progress_analyze\u003c/code\u003e\u003c/a\u003e, and the output of \u003ca href=\"/docs/18/sql-vacuum.html\" title=\"VACUUM\"\u003e\u003cspan\u003eVACUUM\u003c/span\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/sql-analyze.html\" title=\"ANALYZE\"\u003e\u003cspan\u003eANALYZE\u003c/span\u003e\u003c/a\u003e when in \u003ccode\u003eVERBOSE\u003c/code\u003e mode; tracking must be enabled with the server variable \u003ca href=\"/docs/18/runtime-config-statistics.html#GUC-TRACK-COST-DELAY-TIMING\"\u003etrack_cost_delay_timing\u003c/a\u003e.\u003c/p\u003e","id":"18.0-a8b19ee3c2ebd809","identity_text":"Add delay time reporting to sql-vacuum and sql-analyze (Bertrand Drouvot, Nathan Bossart) This information appears in the server log, the system views pg_stat_progress_vacuum and pg_stat_progress_analyze, and the output of sql-vacuum and sql-analyze when in VERBOSE mode; tracking must be enabled with the server variable guc-track-cost-delay-timing .","part":"changes","patch_ids":["37076735ba20e78cc49b9708ebdff26a","dcc774daa71cb4ef3040110ad61f951b"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["7720082ae","bb8dff999"],"source_entry_id":"18.0/changes/031","source_hash":"c3b6092e0b557183c88361a516e8cd0d9afc4df8b8705c21459ed505607217f1","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"fa996a38bca92758da7743b591fad3f548bcd94541d767a9356ea8efbc21a20c","text":"Add delay time reporting to VACUUM and ANALYZE (Bertrand Drouvot, Nathan Bossart) § § This 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.","title":"Add delay time reporting to VACUUM and ANALYZE","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4c1b4cdb8","bb7775234"],"commit_groups":[["4c1b4cdb8"],["bb7775234"]],"commits":["4c1b4cdb8","bb7775234"],"cves":[],"db_id":"89d1e2f5040630b5e6d5d285a3183e17","html":"\u003cp\u003eAdd \u003cacronym\u003eWAL\u003c/acronym\u003e, \u003cacronym\u003eCPU\u003c/acronym\u003e, and average read statistics output to \u003ccode\u003eANALYZE VERBOSE\u003c/code\u003e (Anthonin Bonnefoy) \u003ca href=\"https://postgr.es/c/4c1b4cdb8\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/bb7775234\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-3840c3b2fc9eee99","identity_text":"Add WAL, CPU, and average read statistics output to ANALYZE VERBOSE (Anthonin Bonnefoy)","part":"changes","patch_ids":["b3469919d266e3cb5e6a7fd510fd2e77","e8ed2cc2f82da83716586c11bc4c436b"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["4c1b4cdb8","bb7775234"],"source_entry_id":"18.0/changes/032","source_hash":"1a2dcb5dd39a88693da8ffce12adc58b376cbc99d61e7b665edc8b7a8057486c","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"0ba8f5189b2a89deba8c0398b4327b4ea28a27b30cfe526849d9f7dd081e54d5","text":"Add WAL, CPU, and average read statistics output to ANALYZE VERBOSE (Anthonin Bonnefoy) § §","title":"Add WAL, CPU, and average read statistics output to ANALYZE VERBOSE","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["6a8a7ce47"],"commit_groups":[["6a8a7ce47"]],"commits":["6a8a7ce47"],"cves":[],"db_id":"74713f8ae6d85f90e89e18ef3dc6a21d","html":"\u003cp\u003eAdd full \u003cacronym\u003eWAL\u003c/acronym\u003e buffer count to \u003ccode\u003eVACUUM\u003c/code\u003e/\u003ccode\u003eANALYZE (VERBOSE)\u003c/code\u003e and autovacuum log output (Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/6a8a7ce47\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-4b700ed68adb6f38","identity_text":"Add full WAL buffer count to VACUUM/ANALYZE (VERBOSE) and autovacuum log output (Bertrand Drouvot)","part":"changes","patch_ids":["72511d93ea1587fdaf73eba50b91d1d0"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["6a8a7ce47"],"source_entry_id":"18.0/changes/033","source_hash":"c9894dd7993ceae90219fd40d6eb2b8e99c64032b4b6c0c567537ce9d289b65d","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"0774d5388d6c2acf1684333e3113f73e85981e8a73cea3b0ab9ee148dc6b388f","text":"Add full WAL buffer count to VACUUM/ANALYZE (VERBOSE) and autovacuum log output (Bertrand Drouvot) §","title":"Add full WAL buffer count to VACUUM/ANALYZE (VERBOSE) and autovacuum log output","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["3f1db99bf","9aea73fc6"],"commit_groups":[["3f1db99bf"],["9aea73fc6"]],"commits":["3f1db99bf","9aea73fc6"],"cves":[],"db_id":"17e6c76925cfbd574a9ae5f72831fa69","html":"\u003cp\u003eAdd per-backend I/O statistics reporting (Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/9aea73fc6\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/3f1db99bf\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe statistics are accessed via \u003ca href=\"/docs/18/monitoring-stats.html#PG-STAT-GET-BACKEND-IO\"\u003e\u003ccode\u003epg_stat_get_backend_io()\u003c/code\u003e\u003c/a\u003e. Per-backend I/O statistics can be cleared via \u003ca href=\"/docs/18/monitoring-stats.html#MONITORING-STATS-FUNCS-TABLE\" title=\"Table 27.36. Additional Statistics Functions\"\u003e\u003ccode\u003epg_stat_reset_backend_stats()\u003c/code\u003e\u003c/a\u003e.\u003c/p\u003e","id":"18.0-e35712a71ba201d3","identity_text":"Add per-backend I/O statistics reporting (Bertrand Drouvot) The statistics are accessed via pg_stat_get_backend_io(). Per-backend I/O statistics can be cleared via pg_stat_reset_backend_stats().","part":"changes","patch_ids":["5322e6c9c9cd04d7bf3ea661542be001","a3ee8fafbb9811b8cda82e07e73283f9"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["3f1db99bf","9aea73fc6"],"source_entry_id":"18.0/changes/034","source_hash":"9e1631c53568af593ee7bced63f3b724a0ba10e31a2fd9ed1c4025ad9a38fae7","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"caae69fd5330c7bec4af68b84e21c7fc7e7a5d29f7fae594f65a92e7a22165c1","text":"Add per-backend I/O statistics reporting (Bertrand Drouvot) § § The statistics are accessed via pg_stat_get_backend_io(). Per-backend I/O statistics can be cleared via pg_stat_reset_backend_stats().","title":"Add per-backend I/O statistics reporting","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["f92c854cf"],"commit_groups":[["f92c854cf"]],"commits":["f92c854cf"],"cves":[],"db_id":"aa7e8fb55aec7ab4c8224a57cb360b58","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/monitoring-stats.html#MONITORING-PG-STAT-IO-VIEW\" title=\"27.2.13. pg_stat_io\"\u003e\u003ccode\u003epg_stat_io\u003c/code\u003e\u003c/a\u003e columns to report I/O activity in bytes (Nazir Bilal Yavuz) \u003ca href=\"https://postgr.es/c/f92c854cf\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe new columns are \u003ccode\u003eread_bytes\u003c/code\u003e, \u003ccode\u003ewrite_bytes\u003c/code\u003e, and \u003ccode\u003eextend_bytes\u003c/code\u003e. The \u003ccode\u003eop_bytes\u003c/code\u003e column, which always equaled \u003ca href=\"/docs/18/runtime-config-preset.html#GUC-BLOCK-SIZE\"\u003e\u003ccode\u003eBLCKSZ\u003c/code\u003e\u003c/a\u003e, has been removed.\u003c/p\u003e","id":"18.0-0e96d87fb9dc0733","identity_text":"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.","part":"changes","patch_ids":["a311e5aff8043d8480a656b9295d03b6"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["f92c854cf"],"source_entry_id":"18.0/changes/035","source_hash":"97f3dadc86ebdf37ec36e4e556f7f81273a6d2f21452bea7c88377d1a3c561ae","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"2e8238782eda3f1431802fe0e4f5c982fab48d2ee3dd4a701ea3842da4484eb0","text":"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.","title":"Add pg_stat_io columns to report I/O activity in bytes","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4538bd3f1","7f7f324eb","a051e71e2"],"commit_groups":[["4538bd3f1"],["7f7f324eb"],["a051e71e2"]],"commits":["4538bd3f1","7f7f324eb","a051e71e2"],"cves":[],"db_id":"4e8a04b21c8fb51fcf294e0a57d8462f","html":"\u003cp\u003eAdd \u003cacronym\u003eWAL\u003c/acronym\u003e I/O activity rows to \u003ccode\u003epg_stat_io\u003c/code\u003e (Nazir Bilal Yavuz, Bertrand Drouvot, Michael Paquier) \u003ca href=\"https://postgr.es/c/a051e71e2\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/4538bd3f1\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/7f7f324eb\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis includes \u003cacronym\u003eWAL\u003c/acronym\u003e receiver activity and a wait event for such writes.\u003c/p\u003e","id":"18.0-3b56014060aade39","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.","part":"changes","patch_ids":["0abab9a405c724624eabd4509d63171e","3d509df32980788958c9572c50adb4fd","bef53f830f1ba9f3cda0cc8ff4ed91e6"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["4538bd3f1","7f7f324eb","a051e71e2"],"source_entry_id":"18.0/changes/036","source_hash":"1073fae0e1addc89e2446fa37b2acba1f913d9723e1c4429053ee3268c3f10de","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"c5453439738584b897b3afc314105f41051f5aa95d24752734738916b65af097","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["6c349d83b"],"commit_groups":[["6c349d83b"]],"commits":["6c349d83b"],"cves":[],"db_id":"c17f05a65724a6039aa7e121e771aa10","html":"\u003cp\u003eChange server variable \u003ca href=\"/docs/18/runtime-config-statistics.html#GUC-TRACK-WAL-IO-TIMING\"\u003etrack_wal_io_timing\u003c/a\u003e to control tracking \u003cacronym\u003eWAL\u003c/acronym\u003e timing in \u003ccode\u003epg_stat_io\u003c/code\u003e instead of \u003ca href=\"/docs/18/monitoring-stats.html#PG-STAT-WAL-VIEW\" title=\"Table 27.26. pg_stat_wal View\"\u003e\u003ccode\u003epg_stat_wal\u003c/code\u003e\u003c/a\u003e (Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/6c349d83b\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-6c1a9bdb1bd7fe74","identity_text":"Change server variable guc-track-wal-io-timing to control tracking WAL timing in pg_stat_io instead of pg_stat_wal (Bertrand Drouvot)","part":"changes","patch_ids":["08fb6ea64d401512c5db7dbb4b9241af"],"related_changes":[{"db_id":"d0fcc1877409f4702f061ff62c4a5fe9","evidence":{"ambiguous_patch_ids":["08fb6ea64d401512c5db7dbb4b9241af"],"patch_ids":["08fb6ea64d401512c5db7dbb4b9241af"],"same_day":true},"kind":"related","label":"18.0","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","title":"Remove read/sync columns from pg_stat_wal","url":"/docs/compare/?release=18.0#18.0-202a628b223b3b6a","version":"18.0"}],"relations":[{"evidence":{"ambiguous_patch_ids":["08fb6ea64d401512c5db7dbb4b9241af"],"patch_ids":["08fb6ea64d401512c5db7dbb4b9241af"],"same_day":true},"rule":2,"target":"d0fcc1877409f4702f061ff62c4a5fe9","type":"related"}],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["6c349d83b"],"source_entry_id":"18.0/changes/037","source_hash":"d1231847afefe1d4d74417eeedaf338d2e73d369b33a3039d07def9f38206fd7","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"2f7ae7e2bcef0b17495e3f738ab823ef4fa3a7ff6d607334d8ca8141298e26c2","text":"Change server variable track_wal_io_timing to control tracking WAL timing in pg_stat_io instead of pg_stat_wal (Bertrand Drouvot) §","title":"Change server variable track_wal_io_timing to control tracking WAL timing in pg_stat_io instead of pg_stat_wal","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["2421e9a51","6c349d83b"],"commit_groups":[["2421e9a51"],["6c349d83b"]],"commits":["2421e9a51","6c349d83b"],"cves":[],"db_id":"d0fcc1877409f4702f061ff62c4a5fe9","html":"\u003cp\u003eRemove read/sync columns from \u003ccode\u003epg_stat_wal\u003c/code\u003e (Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/2421e9a51\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/6c349d83b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis removes columns \u003ccode\u003ewal_write\u003c/code\u003e, \u003ccode\u003ewal_sync\u003c/code\u003e, \u003ccode\u003ewal_write_time\u003c/code\u003e, and \u003ccode\u003ewal_sync_time\u003c/code\u003e.\u003c/p\u003e","id":"18.0-202a628b223b3b6a","identity_text":"Remove read/sync columns from pg_stat_wal (Bertrand Drouvot) This removes columns wal_write, wal_sync, wal_write_time, and wal_sync_time.","part":"changes","patch_ids":["08fb6ea64d401512c5db7dbb4b9241af","234c05d3f38c109ec2b38a93d6ac0806"],"related_changes":[{"db_id":"c17f05a65724a6039aa7e121e771aa10","evidence":{"ambiguous_patch_ids":["08fb6ea64d401512c5db7dbb4b9241af"],"patch_ids":["08fb6ea64d401512c5db7dbb4b9241af"],"same_day":true},"kind":"related","label":"18.0","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","title":"Change server variable track_wal_io_timing to control tracking WAL timing in pg_stat_io instead of pg_stat_wal","url":"/docs/compare/?release=18.0#18.0-6c1a9bdb1bd7fe74","version":"18.0"}],"relations":[{"evidence":{"ambiguous_patch_ids":["08fb6ea64d401512c5db7dbb4b9241af"],"patch_ids":["08fb6ea64d401512c5db7dbb4b9241af"],"same_day":true},"rule":2,"target":"c17f05a65724a6039aa7e121e771aa10","type":"related"}],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["2421e9a51","6c349d83b"],"source_entry_id":"18.0/changes/038","source_hash":"bdbb6b727ae2ec12ad3bc55377abbd441295c2aa83487fdcb3a37f0805a08762","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"7b33f152d6e61381fe6be52ffbdfe42a5da00b89105becd3eb6f9de24b2b319c","text":"Remove read/sync columns from pg_stat_wal (Bertrand Drouvot) § § This removes columns wal_write, wal_sync, wal_write_time, and wal_sync_time.","title":"Remove read/sync columns from pg_stat_wal","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["76def4cdd"],"commit_groups":[["76def4cdd"]],"commits":["76def4cdd"],"cves":[],"db_id":"062885cb962fb66b290bfca5b7d287a1","html":"\u003cp\u003eAdd function \u003ca href=\"/docs/18/monitoring-stats.html#PG-STAT-GET-BACKEND-WAL\"\u003e\u003ccode\u003epg_stat_get_backend_wal()\u003c/code\u003e\u003c/a\u003e to return per-backend \u003cacronym\u003eWAL\u003c/acronym\u003e statistics (Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/76def4cdd\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePer-backend \u003cacronym\u003eWAL\u003c/acronym\u003e statistics can be cleared via \u003ca href=\"/docs/18/monitoring-stats.html#MONITORING-STATS-FUNCS-TABLE\" title=\"Table 27.36. Additional Statistics Functions\"\u003e\u003ccode\u003epg_stat_reset_backend_stats()\u003c/code\u003e\u003c/a\u003e.\u003c/p\u003e","id":"18.0-634291e59601ff91","identity_text":"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().","part":"changes","patch_ids":["4e24f0fbea0bfb8adf57d60deed85cbe"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["76def4cdd"],"source_entry_id":"18.0/changes/039","source_hash":"242f296d8a20316ed2428d9cc9afa62a44163367fa7e0849e047ee688cfea11f","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"b74d0e38b049943fe62ccf7336ca21fd4a9fd9d020f9b94347272b09da3db5af","text":"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().","title":"Add function pg_stat_get_backend_wal() to return per-backend WAL statistics","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4e1fad378"],"commit_groups":[["4e1fad378"]],"commits":["4e1fad378"],"cves":[],"db_id":"b9a68e06cac60dffdbd6bf6eb05a794e","html":"\u003cp\u003eAdd function \u003ca href=\"/docs/18/functions-admin.html#FUNCTIONS-ADMIN-GENFILE-TABLE\" title=\"Table 9.108. Generic File Access Functions\"\u003e\u003ccode\u003epg_ls_summariesdir()\u003c/code\u003e\u003c/a\u003e to specifically list the contents of \u003ca href=\"/docs/18/storage-file-layout.html\" title=\"66.1. Database File Layout\"\u003e\u003ccode\u003ePGDATA\u003c/code\u003e\u003c/a\u003e/\u003ca href=\"/docs/18/runtime-config-wal.html#GUC-WAL-SUMMARY-KEEP-TIME\"\u003e\u003ccode\u003epg_wal/summaries\u003c/code\u003e\u003c/a\u003e (Yushi Ogiwara) \u003ca href=\"https://postgr.es/c/4e1fad378\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-b4a386c2e779722f","identity_text":"Add function pg_ls_summariesdir() to specifically list the contents of PGDATA/pg_wal/summaries (Yushi Ogiwara)","part":"changes","patch_ids":["9fe64e076fe5fc2c95c8fa5ba6f057ef"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["4e1fad378"],"source_entry_id":"18.0/changes/040","source_hash":"d6ccff9c03df46b05091a267c2cb8b7b5535dedef74c43578dfaf0e9d97bb59f","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"09d2ba0760f22482dda1728ad727396c99942f333bb0a66ba64ce98dfb4017c7","text":"Add function pg_ls_summariesdir() to specifically list the contents of PGDATA/pg_wal/summaries (Yushi Ogiwara) §","title":"Add function pg_ls_summariesdir() to specifically list the contents of PGDATA/pg_wal/summaries","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["559efce1d"],"commit_groups":[["559efce1d"]],"commits":["559efce1d"],"cves":[],"db_id":"066d4a943702f3b2e401f4e7aae7deab","html":"\u003cp\u003eAdd column \u003ca href=\"/docs/18/monitoring-stats.html#MONITORING-PG-STAT-CHECKPOINTER-VIEW\" title=\"27.2.15. pg_stat_checkpointer\"\u003e\u003ccode\u003epg_stat_checkpointer\u003c/code\u003e\u003c/a\u003e.\u003ccode\u003enum_done\u003c/code\u003e to report the number of completed checkpoints (Anton A. Melnikov) \u003ca href=\"https://postgr.es/c/559efce1d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eColumns \u003ccode\u003enum_timed\u003c/code\u003e and \u003ccode\u003enum_requested\u003c/code\u003e count both completed and skipped checkpoints.\u003c/p\u003e","id":"18.0-2ab3ba61126a6e6f","identity_text":"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.","part":"changes","patch_ids":["c949e573ffaba7a2a8d27d7162de1f0b"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["559efce1d"],"source_entry_id":"18.0/changes/041","source_hash":"b0f52803f5eace4dd8a6f300af475cd3f6d7567d9e52472b06a815ec78abd658","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"68a8924f2cff332cb007ffe69e69b6126cb2165fc11751dbddcea61dcddacc3a","text":"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.","title":"Add column pg_stat_checkpointer.num_done to report the number of completed checkpoints","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["17cc5f666"],"commit_groups":[["17cc5f666"]],"commits":["17cc5f666"],"cves":[],"db_id":"c727bac201403ee5787ce91519d78b8f","html":"\u003cp\u003eAdd column \u003ccode\u003epg_stat_checkpointer\u003c/code\u003e.\u003ccode\u003eslru_written\u003c/code\u003e to report \u003cacronym\u003eSLRU\u003c/acronym\u003e buffers written (Nitin Jadhav) \u003ca href=\"https://postgr.es/c/17cc5f666\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAlso, modify the checkpoint server log message to report separate shared buffer and \u003cacronym\u003eSLRU\u003c/acronym\u003e buffer values.\u003c/p\u003e","id":"18.0-61ce84aa748564e5","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.","part":"changes","patch_ids":["d6837b0ccfa7bed8d3ef332bff20c386"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["17cc5f666"],"source_entry_id":"18.0/changes/042","source_hash":"e3cd14d094f854569dcf0a7ec616f689d1baac8a113db529f691cfd28c517c08","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"d75f1cff8692d2b125311380a9eb939eed72a5eec22bed4041dad77e8aed16e7","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["e7a9496de"],"commit_groups":[["e7a9496de"]],"commits":["e7a9496de"],"cves":[],"db_id":"dfce089734ba453a8b429200599d48f4","html":"\u003cp\u003eAdd columns to \u003ca href=\"/docs/18/monitoring-stats.html#MONITORING-PG-STAT-DATABASE-VIEW\" title=\"27.2.17. pg_stat_database\"\u003e\u003ccode\u003epg_stat_database\u003c/code\u003e\u003c/a\u003e to report parallel worker activity (Benoit Lobréau) \u003ca href=\"https://postgr.es/c/e7a9496de\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe new columns are \u003ccode\u003eparallel_workers_to_launch\u003c/code\u003e and \u003ccode\u003eparallel_workers_launched\u003c/code\u003e.\u003c/p\u003e","id":"18.0-50beb09b38031570","identity_text":"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.","part":"changes","patch_ids":["537ec52eb436dc276f2922a0463b3fde"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["e7a9496de"],"source_entry_id":"18.0/changes/043","source_hash":"eb7a9a2fcda5d6b360e1516a8ecfca3e10034c0773a50d5480dd72cbbe41a363","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"2a16728a2a22066209d758116c71b02d570e00dc834d54006e01a8747ab449a3","text":"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.","title":"Add columns to pg_stat_database to report parallel worker activity","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["62d712ecf","9fbd53dea","c2da1a5d6"],"commit_groups":[["62d712ecf"],["9fbd53dea"],["c2da1a5d6"]],"commits":["62d712ecf","9fbd53dea","c2da1a5d6"],"cves":[],"db_id":"602391884e0f9956bc8189e3df9fa46c","html":"\u003cp\u003eHave \u003ca href=\"/docs/18/runtime-config-statistics.html#GUC-COMPUTE-QUERY-ID\"\u003equery id\u003c/a\u003e computation of constant lists consider only the first and last constants (Dmitry Dolgov, Sami Imseih) \u003ca href=\"https://postgr.es/c/62d712ecf\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/9fbd53dea\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/c2da1a5d6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eJumbling is used by \u003ca href=\"/docs/18/pgstatstatements.html\" title=\"F.32. pg_stat_statements — track statistics of SQL planning and execution\"\u003epg_stat_statements\u003c/a\u003e.\u003c/p\u003e","id":"18.0-e0b7fcc669e7cd20","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 .","part":"changes","patch_ids":["5788e402f9a32d0839d25eda04d2e777","892e3023e3eb75d6d37898823ef6e17d","b602290e314da4eb2c893c183d542ea2"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["62d712ecf","9fbd53dea","c2da1a5d6"],"source_entry_id":"18.0/changes/044","source_hash":"2cf9373f5b7eddab9fd5ff38dada6cd3257b8f28a837aed595560e11f200a37d","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"15594176dafd96eadc8774ee3c07b03bfac584e26aab1114deaf08975c0d6fa7","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["787514b30"],"commit_groups":[["787514b30"]],"commits":["787514b30"],"cves":[],"db_id":"b3b7d2a11d4d31f38f5974d4bc93b3e3","html":"\u003cp\u003eAdjust query id computations to group together queries using the same relation name (Michael Paquier, Sami Imseih) \u003ca href=\"https://postgr.es/c/787514b30\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is true even if the tables in different schemas have different column names.\u003c/p\u003e","id":"18.0-4bd7c5c5ceccdfa2","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.","part":"changes","patch_ids":["79273c32213aef68723d02e288664812"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["787514b30"],"source_entry_id":"18.0/changes/045","source_hash":"09abeab4f5099639b5d52aa31679edc914c3b3c20594c0d395bf45bf491d5e09","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"4cd23dc47a6dcb75efe88b4674803607d5b63bfc8d8855e3822b801ecc934093","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["12227a1d5"],"commit_groups":[["12227a1d5"]],"commits":["12227a1d5"],"cves":[],"db_id":"1fd42df52ed332c3d9d9f6ae19b16420","html":"\u003cp\u003eAdd column \u003ca href=\"/docs/18/view-pg-backend-memory-contexts.html\" title=\"53.5. pg_backend_memory_contexts\"\u003e\u003ccode\u003epg_backend_memory_contexts\u003c/code\u003e\u003c/a\u003e.\u003ccode\u003etype\u003c/code\u003e to report the type of memory context (David Rowley) \u003ca href=\"https://postgr.es/c/12227a1d5\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-3402d3ff0e2cd897","identity_text":"Add column pg_backend_memory_contexts.type to report the type of memory context (David Rowley)","part":"changes","patch_ids":["3977b1d7e6d02dc670220e1e3b219267"],"related_changes":[],"relations":[],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["12227a1d5"],"source_entry_id":"18.0/changes/046","source_hash":"15d29754ae427a052443f1a6626960cf94ba6bda77f6df23ffbece3059a2aaf5","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"24fbd68903b1f42423f271865f961e17ce5f1d8baa7a044061a3e8d64d131bfc","text":"Add column pg_backend_memory_contexts.type to report the type of memory context (David Rowley) §","title":"Add column pg_backend_memory_contexts.type to report the type of memory context","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["32d3ed816"],"commit_groups":[["32d3ed816"]],"commits":["32d3ed816"],"cves":[],"db_id":"7ed5d279df474d7ce518a2cd605d091d","html":"\u003cp\u003eAdd column \u003ccode\u003epg_backend_memory_contexts\u003c/code\u003e.\u003ccode\u003epath\u003c/code\u003e to show memory context parents (Melih Mutlu) \u003ca href=\"https://postgr.es/c/32d3ed816\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-f9c2e124d8a94a20","identity_text":"Add column pg_backend_memory_contexts.path to show memory context parents (Melih Mutlu)","part":"changes","patch_ids":["eaa8db2e49e44f9880c123bf159cab42"],"related_changes":[{"db_id":"b8c57d935d8b183f9ee20e7477f90abd","evidence":{"patch_ids":["eaa8db2e49e44f9880c123bf159cab42"],"same_day":true},"kind":"related","label":"18.0","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","title":"Change pg_backend_memory_contexts.level and pg_log_backend_memory_contexts() to be one-based","url":"/docs/compare/?release=18.0#18.0-3bddcb1c02f74659","version":"18.0"}],"relations":[{"evidence":{"patch_ids":["eaa8db2e49e44f9880c123bf159cab42"],"same_day":true},"rule":2,"target":"b8c57d935d8b183f9ee20e7477f90abd","type":"related"}],"section":"Server / Monitoring","section_path":["Server","Monitoring"],"source_commits":["32d3ed816"],"source_entry_id":"18.0/changes/047","source_hash":"fe70390be48a7656a5a036d23b8695f7dd1cb00476e46001e3b1ed259d1548af","source_url":"/docs/release/18.0/#RELEASE-18-MONITORING","statement_hash":"ffa15ce62078a744cf44121cfda2949c530bd7fb777e4900033a28988556de13","text":"Add column pg_backend_memory_contexts.path to show memory context parents (Melih Mutlu) §","title":"Add column pg_backend_memory_contexts.path to show memory context parents","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4564f1ceb","d898665bf"],"commit_groups":[["4564f1ceb"],["d898665bf"]],"commits":["4564f1ceb","d898665bf"],"cves":[],"db_id":"ad850851b5569f2cacc651752f08d04f","html":"\u003cp\u003eAdd function \u003ca href=\"/docs/18/functions-info.html#FUNCTIONS-INFO-OBJECT-TABLE\" title=\"Table 9.81. Object Information and Addressing Functions\"\u003e\u003ccode\u003epg_get_acl()\u003c/code\u003e\u003c/a\u003e to retrieve database access control details (Joel Jacobson) \u003ca href=\"https://postgr.es/c/4564f1ceb\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/d898665bf\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-33915810b55250be","identity_text":"Add function pg_get_acl() to retrieve database access control details (Joel Jacobson)","part":"changes","patch_ids":["4dc0424113c1959079f3a8cbcd6d075c","6f98238a578fbdf3c4f8b2f8442a9443"],"related_changes":[],"relations":[],"section":"Server / Privileges","section_path":["Server","Privileges"],"source_commits":["4564f1ceb","d898665bf"],"source_entry_id":"18.0/changes/048","source_hash":"39a0e54cf10496289f448e8b5cf7a83ad0f4a1dad5d8b88bc38a045012595af3","source_url":"/docs/release/18.0/#RELEASE-18-PRIVILEGES","statement_hash":"b5738fc376219c85ab240a4d03d8c61a19c7ef3218d218a2f99f961cfa02ae1d","text":"Add function pg_get_acl() to retrieve database access control details (Joel Jacobson) § §","title":"Add function pg_get_acl() to retrieve database access control details","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4eada203a"],"commit_groups":[["4eada203a"]],"commits":["4eada203a"],"cves":[],"db_id":"20e548031e0fa774a44ef2ccda8b5768","html":"\u003cp\u003eAdd function \u003ca href=\"/docs/18/functions-info.html#FUNCTIONS-INFO-ACCESS-TABLE\" title=\"Table 9.72. Access Privilege Inquiry Functions\"\u003e\u003ccode\u003ehas_largeobject_privilege()\u003c/code\u003e\u003c/a\u003e to check large object privileges (Yugo Nagata) \u003ca href=\"https://postgr.es/c/4eada203a\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-e083e86b0999f401","identity_text":"Add function has_largeobject_privilege() to check large object privileges (Yugo Nagata)","part":"changes","patch_ids":["692c244b77bff2a8f3509d0f3f788fb5"],"related_changes":[],"relations":[],"section":"Server / Privileges","section_path":["Server","Privileges"],"source_commits":["4eada203a"],"source_entry_id":"18.0/changes/049","source_hash":"bbfbf3c3ece75a40f49e6a874bdb5b72ba58a27f32a5ea35fd4d4c1eac892598","source_url":"/docs/release/18.0/#RELEASE-18-PRIVILEGES","statement_hash":"31f9f08133b37f73a56f5218942b92e031210ec05cba9a6cb6d49d942bfbac20","text":"Add function has_largeobject_privilege() to check large object privileges (Yugo Nagata) §","title":"Add function has_largeobject_privilege() to check large object privileges","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["0d6c47766"],"commit_groups":[["0d6c47766"]],"commits":["0d6c47766"],"cves":[],"db_id":"2115b59fe3ecb850d34420db9087d6ee","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/sql-alterdefaultprivileges.html\" title=\"ALTER DEFAULT PRIVILEGES\"\u003e\u003cspan\u003eALTER DEFAULT PRIVILEGES\u003c/span\u003e\u003c/a\u003e to define large object default privileges (Takatsuka Haruka, Yugo Nagata, Laurenz Albe) \u003ca href=\"https://postgr.es/c/0d6c47766\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-48cbad33bf051182","identity_text":"Allow sql-alterdefaultprivileges to define large object default privileges (Takatsuka Haruka, Yugo Nagata, Laurenz Albe)","part":"changes","patch_ids":["8bd885a988ec8e858d73081f630fd33d"],"related_changes":[],"relations":[],"section":"Server / Privileges","section_path":["Server","Privileges"],"source_commits":["0d6c47766"],"source_entry_id":"18.0/changes/050","source_hash":"4c91df429994b748ca8f11482114f697801f5b8c6c8b714ebf14f04619bf4653","source_url":"/docs/release/18.0/#RELEASE-18-PRIVILEGES","statement_hash":"91512a6ced76577a52c71c7f1692309e60bb18dc1ce44331c056f04fd50fb429","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["ccd38024b"],"commit_groups":[["ccd38024b"]],"commits":["ccd38024b"],"cves":[],"db_id":"20b3f6628c87707ad4d0eb8fd8768e0a","html":"\u003cp\u003eAdd predefined role \u003ca href=\"/docs/18/predefined-roles.html\" title=\"21.5. Predefined Roles\"\u003e\u003ccode\u003epg_signal_autovacuum_worker\u003c/code\u003e\u003c/a\u003e (Kirill Reshke) \u003ca href=\"https://postgr.es/c/ccd38024b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis allows sending signals to autovacuum workers.\u003c/p\u003e","id":"18.0-63bd5329a9fe779c","identity_text":"Add predefined role pg_signal_autovacuum_worker (Kirill Reshke) This allows sending signals to autovacuum workers.","part":"changes","patch_ids":["a254744dab5b2721c5babac8740a351d"],"related_changes":[],"relations":[],"section":"Server / Privileges","section_path":["Server","Privileges"],"source_commits":["ccd38024b"],"source_entry_id":"18.0/changes/051","source_hash":"bfdef5e379e1781509025a5997d7b24eee477202a1c63fdf10ed414f0ba7b3e4","source_url":"/docs/release/18.0/#RELEASE-18-PRIVILEGES","statement_hash":"c15408fea664f43b416b4b112fe35a5f8e4c76546718ab374fef03190e47327d","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["b3f0be788"],"commit_groups":[["b3f0be788"]],"commits":["b3f0be788"],"cves":[],"db_id":"746baa07cb5e517064dca7ea3454e3b0","html":"\u003cp\u003eAdd support for the \u003ca href=\"/docs/18/auth-oauth.html\" title=\"20.15. OAuth Authorization/Authentication\"\u003eOAuth authentication method\u003c/a\u003e (Jacob Champion, Daniel Gustafsson, Thomas Munro) \u003ca href=\"https://postgr.es/c/b3f0be788\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis adds an \u003ccode\u003eoauth\u003c/code\u003e authentication method to \u003ca href=\"/docs/18/auth-pg-hba-conf.html\" title=\"20.1. The pg_hba.conf File\"\u003e\u003ccode\u003epg_hba.conf\u003c/code\u003e\u003c/a\u003e, libpq OAuth options, a server variable \u003ca href=\"/docs/18/runtime-config-connection.html#GUC-OAUTH-VALIDATOR-LIBRARIES\"\u003eoauth_validator_libraries\u003c/a\u003e to load token validation libraries, and a configure flag \u003ca href=\"/docs/18/install-make.html#CONFIGURE-OPTION-WITH-LIBCURL\"\u003e\u003ccode\u003e--with-libcurl\u003c/code\u003e\u003c/a\u003e to add the required compile-time libraries.\u003c/p\u003e","id":"18.0-8937e04e6f598c9a","identity_text":"Add support for the OAuth authentication method (Jacob Champion, Daniel Gustafsson, Thomas Munro) This adds an oauth authentication method to pg_hba.conf, libpq OAuth options, a server variable guc-oauth-validator-libraries to load token validation libraries, and a configure flag --with-libcurl to add the required compile-time libraries.","part":"changes","patch_ids":["e84eb2fdc1830185f25750762e1cc528"],"related_changes":[],"relations":[],"section":"Server / Server Configuration","section_path":["Server","Server Configuration"],"source_commits":["b3f0be788"],"source_entry_id":"18.0/changes/052","source_hash":"1ac9338858fd8a7a47d62e75d679e10a0eb1bfabc9a52d1e7db8098aa7bd9e0d","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-CONFIG","statement_hash":"07ddc49607980c97519f77163181f14568e19bbe0b1e0dc01b218b1f6a71074d","text":"Add support for the OAuth authentication method (Jacob Champion, Daniel Gustafsson, Thomas Munro) § This 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.","title":"Add support for the OAuth authentication method","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["45188c2ea"],"commit_groups":[["45188c2ea"]],"commits":["45188c2ea"],"cves":[],"db_id":"13b081fb2e1030e7c402c99be84d674e","html":"\u003cp\u003eAdd server variable \u003ca href=\"/docs/18/runtime-config-connection.html#GUC-SSL-TLS13-CIPHERS\"\u003essl_tls13_ciphers\u003c/a\u003e to allow specification of multiple colon-separated TLSv1.3 cipher suites (Erica Zhang, Daniel Gustafsson) \u003ca href=\"https://postgr.es/c/45188c2ea\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-c129dc9baebd36d0","identity_text":"Add server variable guc-ssl-tls13-ciphers to allow specification of multiple colon-separated TLSv1.3 cipher suites (Erica Zhang, Daniel Gustafsson)","part":"changes","patch_ids":["b918cd02542986f670ea5e4ccce7bed8"],"related_changes":[],"relations":[],"section":"Server / Server Configuration","section_path":["Server","Server Configuration"],"source_commits":["45188c2ea"],"source_entry_id":"18.0/changes/053","source_hash":"5d256d99caaf5046100077cd472e922ae375d82b0f5b45bcfbac3a79833692b5","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-CONFIG","statement_hash":"ffe4b310bcfc2b812bd9ca43729c6e6988676e615fa96ac501930ef3cd998db9","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["daa02c6bd"],"commit_groups":[["daa02c6bd"]],"commits":["daa02c6bd"],"cves":[],"db_id":"0ff6b951577e789ccfcf50c5fdd16250","html":"\u003cp\u003eChange server variable \u003ca href=\"/docs/18/runtime-config-connection.html#GUC-SSL-GROUPS\"\u003essl_groups\u003c/a\u003e's default to include elliptic curve X25519 (Daniel Gustafsson, Jacob Champion) \u003ca href=\"https://postgr.es/c/daa02c6bd\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-7ae83796934b368a","identity_text":"Change server variable guc-ssl-groups 's default to include elliptic curve X25519 (Daniel Gustafsson, Jacob Champion)","part":"changes","patch_ids":["b6419e2ab5092340bdb51279a882c575"],"related_changes":[],"relations":[],"section":"Server / Server Configuration","section_path":["Server","Server Configuration"],"source_commits":["daa02c6bd"],"source_entry_id":"18.0/changes/054","source_hash":"769ef4c7a0e583d2f4cb847ab408143dd1d5d440e558c0b751debd0c43265451","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-CONFIG","statement_hash":"79f1b0ec5dbbc9c41cfae0c653c6b8af2978a2d458009ec866463efb3c895406","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["3d1ef3a15"],"commit_groups":[["3d1ef3a15"]],"commits":["3d1ef3a15"],"cves":[],"db_id":"96a81164afdac0bf4ed0486ab950b9cc","html":"\u003cp\u003eRename server variable \u003ccode\u003essl_ecdh_curve\u003c/code\u003e to \u003ca href=\"/docs/18/runtime-config-connection.html#GUC-SSL-GROUPS\"\u003essl_groups\u003c/a\u003e and allow multiple colon-separated \u003cacronym\u003eECDH\u003c/acronym\u003e curves to be specified (Erica Zhang, Daniel Gustafsson) \u003ca href=\"https://postgr.es/c/3d1ef3a15\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe previous name still works.\u003c/p\u003e","id":"18.0-ec11a3f47cab5302","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.","part":"changes","patch_ids":["c2561d4875ae281fdaea78d9e93eaee2"],"related_changes":[],"relations":[],"section":"Server / Server Configuration","section_path":["Server","Server Configuration"],"source_commits":["3d1ef3a15"],"source_entry_id":"18.0/changes/055","source_hash":"69fc229fb451ba3569f10661789b08fd931063d5102c111408c2c761550da092","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-CONFIG","statement_hash":"af282a32e71f1303e38dd9f838dce742a3ea5e5033c66e5a334acc730ab67445","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["9d9b9d46f","a460251f0"],"commit_groups":[["9d9b9d46f"],["a460251f0"]],"commits":["9d9b9d46f","a460251f0"],"cves":[],"db_id":"d4bdcc752134e88e3b6f69045f91e32f","html":"\u003cp\u003eMake \u003ca href=\"/docs/18/functions-admin.html#FUNCTIONS-ADMIN-SIGNAL-TABLE\" title=\"Table 9.96. Server Signaling Functions\"\u003ecancel request keys\u003c/a\u003e 256 bits (Heikki Linnakangas, Jelte Fennema-Nio) \u003ca href=\"https://postgr.es/c/a460251f0\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/9d9b9d46f\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is only possible when the server and client support wire protocol version 3.2, introduced in this release.\u003c/p\u003e","id":"18.0-fc222bd600eb20c7","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.","part":"changes","patch_ids":["3374f7d4348f979a16fb3f835b1434dd","78aeb882063c4d9c0113cb769f6f63c8"],"related_changes":[],"relations":[],"section":"Server / Server Configuration","section_path":["Server","Server Configuration"],"source_commits":["9d9b9d46f","a460251f0"],"source_entry_id":"18.0/changes/056","source_hash":"4da7c6464ec24190e054671959a89c1342b41fd9c2df30a579e2cb4c8e608823","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-CONFIG","statement_hash":"bf970fd6a3a870ec104cf3173699ac7821ccb4e686bb18b2d9050cfee203c953","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["c758119e5"],"commit_groups":[["c758119e5"]],"commits":["c758119e5"],"cves":[],"db_id":"14193c2c6216dac54ee9f03d74597315","html":"\u003cp\u003eAdd server variable \u003ca href=\"/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-WORKER-SLOTS\"\u003eautovacuum_worker_slots\u003c/a\u003e to specify the maximum number of background workers (Nathan Bossart) \u003ca href=\"https://postgr.es/c/c758119e5\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWith this variable set, \u003ca href=\"/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-MAX-WORKERS\"\u003eautovacuum_max_workers\u003c/a\u003e can be adjusted at runtime up to this maximum without a server restart.\u003c/p\u003e","id":"18.0-fad3071db20b5849","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.","part":"changes","patch_ids":["17efa2578b6fdfca54d1895a47b5d85c"],"related_changes":[],"relations":[],"section":"Server / Server Configuration","section_path":["Server","Server Configuration"],"source_commits":["c758119e5"],"source_entry_id":"18.0/changes/057","source_hash":"cccf9f941c4560c33011e635dcab0b9c28ae26749ffd1608f7169c4ecf499acc","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-CONFIG","statement_hash":"2340cf9dd0c8914c3ae78fcca1d6cb8a3eec267275fe98352062b37d256a1302","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","variants":[],"version":"18.0"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["306dc520b"],"commit_groups":[["306dc520b"]],"commits":["306dc520b"],"cves":[],"db_id":"c6c8d0da14fc739954f67e4c3e8e297c","html":"\u003cp\u003eAllow specification of the fixed number of dead tuples that will trigger an \u003ca href=\"/docs/18/routine-vacuuming.html#AUTOVACUUM\" title=\"24.1.6. The Autovacuum Daemon\"\u003eautovacuum\u003c/a\u003e (Nathan Bossart, Frédéric Yhuel) \u003ca href=\"https://postgr.es/c/306dc520b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe server variable is \u003ca href=\"/docs/18/runtime-config-vacuum.html#GUC-AUTOVACUUM-VACUUM-MAX-THRESHOLD\"\u003eautovacuum_vacuum_max_threshold\u003c/a\u003e. Percentages are still used for triggering.\u003c/p\u003e","id":"18.0-cc3cc0af71ac8fcd","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.","part":"changes","patch_ids":["fede0a2ed06d94a30aac6de8675efbce"],"related_changes":[],"relations":[],"section":"Server / Server Configuration","section_path":["Server","Server Configuration"],"source_commits":["306dc520b"],"source_entry_id":"18.0/changes/058","source_hash":"fd553683edfb9d3b450f0a00d5e58d81232bb84ff144ad688ad048e97b11922e","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-CONFIG","statement_hash":"f26aed72e786336ffb0181c576796c1b0d66b6c0c79fa7ab8337a9deb9a04a70","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["adb5f85fa"],"commit_groups":[["adb5f85fa"]],"commits":["adb5f85fa"],"cves":[],"db_id":"7d0f8a8401a0235fee5c42443323fd9f","html":"\u003cp\u003eChange server variable \u003ca href=\"/docs/18/runtime-config-resource.html#GUC-MAX-FILES-PER-PROCESS\"\u003emax_files_per_process\u003c/a\u003e to limit only files opened by a backend (Andres Freund) \u003ca href=\"https://postgr.es/c/adb5f85fa\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously files opened by the postmaster were also counted toward this limit.\u003c/p\u003e","id":"18.0-88c8af4f4659a505","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.","part":"changes","patch_ids":["1253eb7b68a386abd794c882137adc02"],"related_changes":[],"relations":[],"section":"Server / Server Configuration","section_path":["Server","Server Configuration"],"source_commits":["adb5f85fa"],"source_entry_id":"18.0/changes/059","source_hash":"2618bfe12d00c39268c401694e59d9fad97443ba987c22b6d62e307da9068d9a","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-CONFIG","statement_hash":"04e1a6687e91598505d1cd8239184c483171e03aa143374ed943a3e8b71c817c","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["0dcaea569"],"commit_groups":[["0dcaea569"]],"commits":["0dcaea569"],"cves":[],"db_id":"baa925cc966c3797d6c1baeb8600b3af","html":"\u003cp\u003eAdd server variable \u003ca href=\"/docs/18/runtime-config-preset.html#GUC-NUM-OS-SEMAPHORES\"\u003enum_os_semaphores\u003c/a\u003e to report the required number of semaphores (Nathan Bossart) \u003ca href=\"https://postgr.es/c/0dcaea569\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is useful for operating system configuration.\u003c/p\u003e","id":"18.0-a70925addf13174f","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.","part":"changes","patch_ids":["7cab2bba487b8dfdc88b894d86ebcb31"],"related_changes":[],"relations":[],"section":"Server / Server Configuration","section_path":["Server","Server Configuration"],"source_commits":["0dcaea569"],"source_entry_id":"18.0/changes/060","source_hash":"9ab5511113bd82e70e3a03fc12538f6345af41f77c718778b40bf3d3a03203b6","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-CONFIG","statement_hash":"db627bdf62b6a351d882ccec445c9221ec8e4d930aed5bf5e6b0b5b611bd8094","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4f7f7b037","81eaaa2c4"],"commit_groups":[["4f7f7b037"],["81eaaa2c4"]],"commits":["4f7f7b037","81eaaa2c4"],"cves":[],"db_id":"9a0ac630df36e673c00b61131cd0c2ff","html":"\u003cp\u003eAdd server variable \u003ca href=\"/docs/18/runtime-config-client.html#GUC-EXTENSION-CONTROL-PATH\"\u003eextension_control_path\u003c/a\u003e to specify the location of extension control files (Peter Eisentraut, Matheus Alcantara) \u003ca href=\"https://postgr.es/c/4f7f7b037\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/81eaaa2c4\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-fcaec73419edafbc","identity_text":"Add server variable guc-extension-control-path to specify the location of extension control files (Peter Eisentraut, Matheus Alcantara)","part":"changes","patch_ids":["2c992ea1a18c7e56b1999e13915ad2f8","95178da37b740ae32403368a9d5de091"],"related_changes":[],"relations":[],"section":"Server / Server Configuration","section_path":["Server","Server Configuration"],"source_commits":["4f7f7b037","81eaaa2c4"],"source_entry_id":"18.0/changes/061","source_hash":"9d62b8c0663f70e4f69542ec94abb0e3f367bb880d1661fa4b5ee26a52495548","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-CONFIG","statement_hash":"b2d063e72b9d991ddf32656536cdf6aa960609b5293a9f7685124d9018ed0d46","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["ac0e33136"],"commit_groups":[["ac0e33136"]],"commits":["ac0e33136"],"cves":[],"db_id":"7e52ed73d316bf78778f528fedb05f84","html":"\u003cp\u003eAllow inactive replication slots to be automatically invalidated using server variable \u003ca href=\"/docs/18/runtime-config-replication.html#GUC-IDLE-REPLICATION-SLOT-TIMEOUT\"\u003eidle_replication_slot_timeout\u003c/a\u003e (Nisha Moond, Bharath Rupireddy) \u003ca href=\"https://postgr.es/c/ac0e33136\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-d6cdb50cb80abdda","identity_text":"Allow inactive replication slots to be automatically invalidated using server variable guc-idle-replication-slot-timeout (Nisha Moond, Bharath Rupireddy)","part":"changes","patch_ids":["df8d31e4efb6cb139d5c669e2215050c"],"related_changes":[],"relations":[],"section":"Server / Streaming Replication and Recovery","section_path":["Server","Streaming Replication and Recovery"],"source_commits":["ac0e33136"],"source_entry_id":"18.0/changes/062","source_hash":"8c442254dde2045ae1b1e87460c9e70a650a5b8afddfac774dc1463a967d81ba","source_url":"/docs/release/18.0/#RELEASE-18-REPLICATION","statement_hash":"eb9a1e5c89e5b4fa71a37fedc208ddb8c2f0f95fbc1eec06821cbc772f3bd8fc","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["04ff636cb"],"commit_groups":[["04ff636cb"]],"commits":["04ff636cb"],"cves":[],"db_id":"1428b3f7f6cc1a4506850622a40c3ffb","html":"\u003cp\u003eAdd server variable \u003ca href=\"/docs/18/runtime-config-replication.html#GUC-MAX-ACTIVE-REPLICATION-ORIGINS\"\u003emax_active_replication_origins\u003c/a\u003e to control the maximum active replication origins (Euler Taveira) \u003ca href=\"https://postgr.es/c/04ff636cb\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis was previously controlled by \u003ca href=\"/docs/18/runtime-config-replication.html#GUC-MAX-REPLICATION-SLOTS\"\u003emax_replication_slots\u003c/a\u003e, but this new setting allows a higher origin count in cases where fewer slots are required.\u003c/p\u003e","id":"18.0-03713c460c2a7d56","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.","part":"changes","patch_ids":["a8c08a420a79bd1a161ea23d9bef6d71"],"related_changes":[],"relations":[],"section":"Server / Streaming Replication and Recovery","section_path":["Server","Streaming Replication and Recovery"],"source_commits":["04ff636cb"],"source_entry_id":"18.0/changes/063","source_hash":"33b1bea544f15476df511f7f493e700d5039ed734c0053ce03bf246913999aca","source_url":"/docs/release/18.0/#RELEASE-18-REPLICATION","statement_hash":"9e85b8d9968595a466cfb230295bcf24c446ed069e908115b73bf70ddbaf2392","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["6252b1eaf","7054186c4","745217a05","87ce27de6"],"commit_groups":[["6252b1eaf"],["7054186c4"],["745217a05"],["87ce27de6"]],"commits":["6252b1eaf","7054186c4","745217a05","87ce27de6"],"cves":[],"db_id":"5202261d9ce471fa7ab14e9e38ae61ef","html":"\u003cp\u003eAllow the values of \u003ca href=\"/docs/18/sql-createtable.html#SQL-CREATETABLE-PARMS-GENERATED-STORED\"\u003egenerated columns\u003c/a\u003e to be logically replicated (Shubham Khanna, Vignesh C, Zhijie Hou, Shlok Kyal, Peter Smith) \u003ca href=\"https://postgr.es/c/745217a05\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/7054186c4\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/87ce27de6\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/6252b1eaf\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eIf the publication specifies a column list, all specified columns, generated and non-generated, are published. Without a specified column list, publication option \u003ccode\u003epublish_generated_columns\u003c/code\u003e 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-\u003cspan\u003ePostgreSQL\u003c/span\u003e subscribers which lack such a capability.\u003c/p\u003e","id":"18.0-b3be55f006e9da56","identity_text":"Allow the values of generated columns to be logically replicated (Shubham Khanna, Vignesh C, Zhijie Hou, Shlok Kyal, Peter Smith) If 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.","part":"changes","patch_ids":["1665b39bcf49aa722b1893f0f6a01425","3341f4a55afcad51ffb341807df994d9","369fa64a83003bb9b411f50bb7db1dc9","4288fdb022ae4713ce4aa5fa5fa0f5cc"],"related_changes":[],"relations":[],"section":"Server / Logical Replication","section_path":["Server","Logical Replication"],"source_commits":["6252b1eaf","7054186c4","745217a05","87ce27de6"],"source_entry_id":"18.0/changes/064","source_hash":"8ce5cf78247c4224e21a3859bb19dbd3ae248d206b36330a42cd21f09eb98501","source_url":"/docs/release/18.0/#RELEASE-18-LOGICAL","statement_hash":"083520dac02028f1cb8e9374c5f6fee5c51e6f31ad5594e2b5d7f6386a3b9577","text":"Allow the values of generated columns to be logically replicated (Shubham Khanna, Vignesh C, Zhijie Hou, Shlok Kyal, Peter Smith) § § § § If 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.","title":"Allow the values of generated columns to be logically replicated","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["1bf1140be"],"commit_groups":[["1bf1140be"]],"commits":["1bf1140be"],"cves":[],"db_id":"64ac8d883b9496b763afc3ba0c0bac52","html":"\u003cp\u003eChange the default \u003ca href=\"/docs/18/sql-createsubscription.html\" title=\"CREATE SUBSCRIPTION\"\u003e\u003cspan\u003eCREATE SUBSCRIPTION\u003c/span\u003e\u003c/a\u003e streaming option from \u003ccode\u003eoff\u003c/code\u003e to \u003ccode\u003eparallel\u003c/code\u003e (Vignesh C) \u003ca href=\"https://postgr.es/c/1bf1140be\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-2d4096e3c7abe9a2","identity_text":"Change the default sql-createsubscription streaming option from off to parallel (Vignesh C)","part":"changes","patch_ids":["6ef9a9f39489f250a02f1462b636b45f"],"related_changes":[],"relations":[],"section":"Server / Logical Replication","section_path":["Server","Logical Replication"],"source_commits":["1bf1140be"],"source_entry_id":"18.0/changes/065","source_hash":"dce9ffa74056678f5973ff428b9f15c4f65d9403797d8b7feb364f5e78f6b6b7","source_url":"/docs/release/18.0/#RELEASE-18-LOGICAL","statement_hash":"ccdb8be0260f594a383cc3edfe4b5c3fb3df37d5354d857e476778efb79b3ff4","text":"Change the default CREATE SUBSCRIPTION streaming option from off to parallel (Vignesh C) §","title":"Change the default CREATE SUBSCRIPTION streaming option from off to parallel","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["1462aad2e","4868c96bc"],"commit_groups":[["1462aad2e"],["4868c96bc"]],"commits":["1462aad2e","4868c96bc"],"cves":[],"db_id":"41cd5554ab5a99df850ddc649a630bf5","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/sql-altersubscription.html\" title=\"ALTER SUBSCRIPTION\"\u003e\u003cspan\u003eALTER SUBSCRIPTION\u003c/span\u003e\u003c/a\u003e to change the replication slot's two-phase commit behavior (Hayato Kuroda, Ajin Cherian, Amit Kapila, Zhijie Hou) \u003ca href=\"https://postgr.es/c/1462aad2e\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/4868c96bc\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-a97cc604ed380ce6","identity_text":"Allow sql-altersubscription to change the replication slot's two-phase commit behavior (Hayato Kuroda, Ajin Cherian, Amit Kapila, Zhijie Hou)","part":"changes","patch_ids":["15c1439cde9cf963e340507c56e6bd57","fd8060f9266b72de63d063d80a6bb2f9"],"related_changes":[],"relations":[],"section":"Server / Logical Replication","section_path":["Server","Logical Replication"],"source_commits":["1462aad2e","4868c96bc"],"source_entry_id":"18.0/changes/066","source_hash":"b96743f044a02e2201e5e678b547c8fdb56efd310343f8b3e4919fa6c862dfc7","source_url":"/docs/release/18.0/#RELEASE-18-LOGICAL","statement_hash":"4c14605560e017cf4d89bb8a33a0ab993f4a9ff353648fde85d7e88cde571530","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["640178c92","6c2b5edec","73eba5004","9758174e2","edcb71258"],"commit_groups":[["640178c92"],["6c2b5edec"],["73eba5004"],["9758174e2"],["edcb71258"]],"commits":["640178c92","6c2b5edec","73eba5004","9758174e2","edcb71258"],"cves":[],"db_id":"d501fbaa05f2f82279ea37f34a051e90","html":"\u003cp\u003eLog \u003ca href=\"/docs/18/hot-standby.html#HOT-STANDBY-CONFLICT\" title=\"26.4.2. Handling Query Conflicts\"\u003econflicts\u003c/a\u003e while applying logical replication changes (Zhijie Hou, Nisha Moond) \u003ca href=\"https://postgr.es/c/9758174e2\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/edcb71258\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/640178c92\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/6c2b5edec\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/73eba5004\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAlso report in new columns of \u003ca href=\"/docs/18/monitoring-stats.html#MONITORING-PG-STAT-SUBSCRIPTION-STATS\" title=\"27.2.9. pg_stat_subscription_stats\"\u003e\u003ccode\u003epg_stat_subscription_stats\u003c/code\u003e\u003c/a\u003e.\u003c/p\u003e","id":"18.0-a8d78b040297e9b0","identity_text":"Log conflicts while applying logical replication changes (Zhijie Hou, Nisha Moond) Also report in new columns of pg_stat_subscription_stats.","part":"changes","patch_ids":["51def9eea7743271af2095d95b545a4f","8b6edece41c91a3f70d5596159ddbe32","ae3bbcf20f2ea20c2688908c03c2959a","ae68c8345354c13eb606659698b10d59","f0ec97314be2a61418e5a1c0f3506967"],"related_changes":[],"relations":[],"section":"Server / Logical Replication","section_path":["Server","Logical Replication"],"source_commits":["640178c92","6c2b5edec","73eba5004","9758174e2","edcb71258"],"source_entry_id":"18.0/changes/067","source_hash":"05b6c5eed4fe0a503528ebf6e93550346f53902f7896fdfd02fa0f490a545a5d","source_url":"/docs/release/18.0/#RELEASE-18-LOGICAL","statement_hash":"a122cf64cd9a507a10cc7e4d8d75e98e4d0911707c1e708541f68fcd20a195cf","text":"Log conflicts while applying logical replication changes (Zhijie Hou, Nisha Moond) § § § § § Also report in new columns of pg_stat_subscription_stats.","title":"Log conflicts while applying logical replication changes","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["1e4351af3","83ea6c540","cdc168ad4"],"commit_groups":[["1e4351af3"],["83ea6c540"],["cdc168ad4"]],"commits":["1e4351af3","83ea6c540","cdc168ad4"],"cves":[],"db_id":"e55bde9210ccbba653a3ff687ce8c8d5","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/sql-createtable.html#SQL-CREATETABLE-PARMS-GENERATED-STORED\"\u003egenerated columns\u003c/a\u003e to be virtual, and make them the default (Peter Eisentraut, Jian He, Richard Guo, Dean Rasheed) \u003ca href=\"https://postgr.es/c/83ea6c540\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/cdc168ad4\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/1e4351af3\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eVirtual generated columns generate their values when the columns are read, not written. The write behavior can still be specified via the \u003ccode\u003eSTORED\u003c/code\u003e option.\u003c/p\u003e","id":"18.0-d75b3348cb3c29c1","identity_text":"Allow generated columns to be virtual, and make them the default (Peter Eisentraut, Jian He, Richard Guo, Dean Rasheed) Virtual generated columns generate their values when the columns are read, not written. The write behavior can still be specified via the STORED option.","part":"changes","patch_ids":["3e371ba8f3c63409d6e3c656c1bdb71c","447c816d3adc612f5ef8fd3d4f63cc04","dc34ef60f4a74f75244fff70b71d30ca"],"related_changes":[],"relations":[],"section":"Utility Commands","section_path":["Utility Commands"],"source_commits":["1e4351af3","83ea6c540","cdc168ad4"],"source_entry_id":"18.0/changes/068","source_hash":"8b9bb147252ad7e35c8f655d35d8c3a7e914db7df27c4bd4a357130d618b67b2","source_url":"/docs/release/18.0/#RELEASE-18-UTILITY","statement_hash":"5dc1a0db02d845a39dfa141f18f21f435065540c7745af4f23009c79c78be2b5","text":"Allow generated columns to be virtual, and make them the default (Peter Eisentraut, Jian He, Richard Guo, Dean Rasheed) § § § Virtual generated columns generate their values when the columns are read, not written. The write behavior can still be specified via the STORED option.","title":"Allow generated columns to be virtual, and make them the default","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["80feb727c"],"commit_groups":[["80feb727c"]],"commits":["80feb727c"],"cves":[],"db_id":"a6ab1b647947ca727232553f3a8dc197","html":"\u003cp\u003eAdd \u003ccode\u003eOLD\u003c/code\u003e/\u003ccode\u003eNEW\u003c/code\u003e support to \u003ca href=\"/docs/18/dml-returning.html\" title=\"6.4. Returning Data from Modified Rows\"\u003e\u003ccode\u003eRETURNING\u003c/code\u003e\u003c/a\u003e in \u003cacronym\u003eDML\u003c/acronym\u003e queries (Dean Rasheed) \u003ca href=\"https://postgr.es/c/80feb727c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously \u003ccode\u003eRETURNING\u003c/code\u003e only returned new values for \u003ca href=\"/docs/18/sql-insert.html\" title=\"INSERT\"\u003e\u003cspan\u003eINSERT\u003c/span\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/sql-update.html\" title=\"UPDATE\"\u003e\u003cspan\u003eUPDATE\u003c/span\u003e\u003c/a\u003e, and old values for \u003ca href=\"/docs/18/sql-delete.html\" title=\"DELETE\"\u003e\u003cspan\u003eDELETE\u003c/span\u003e\u003c/a\u003e; \u003ca href=\"/docs/18/sql-merge.html\" title=\"MERGE\"\u003e\u003cspan\u003eMERGE\u003c/span\u003e\u003c/a\u003e would return the appropriate value for the internal query executed. This new syntax allows the \u003ccode\u003eRETURNING\u003c/code\u003e list of \u003ccode\u003eINSERT\u003c/code\u003e/\u003ccode\u003eUPDATE\u003c/code\u003e/\u003ccode\u003eDELETE\u003c/code\u003e/\u003ccode\u003eMERGE\u003c/code\u003e to explicitly return old and new values by using the special aliases \u003ccode\u003eold\u003c/code\u003e and \u003ccode\u003enew\u003c/code\u003e. These aliases can be renamed to avoid identifier conflicts.\u003c/p\u003e","id":"18.0-1b582314268a1627","identity_text":"Add OLD/NEW support to RETURNING in DML queries (Dean Rasheed) Previously RETURNING only returned new values for sql-insert and sql-update , and old values for sql-delete ; sql-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.","part":"changes","patch_ids":["4fca2a9efd37d56cb0881b858a6b90f0"],"related_changes":[],"relations":[],"section":"Utility Commands","section_path":["Utility Commands"],"source_commits":["80feb727c"],"source_entry_id":"18.0/changes/069","source_hash":"a8fc808c426e5a39fe1dc4198d1fc55913f32e15adb8f6ffac2992288794c5d6","source_url":"/docs/release/18.0/#RELEASE-18-UTILITY","statement_hash":"2d5bdf5703ba0215fc209242d19c9debd27beb536915449517e314371beaea1e","text":"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.","title":"Add OLD/NEW support to RETURNING in DML queries","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["302cf1575"],"commit_groups":[["302cf1575"]],"commits":["302cf1575"],"cves":[],"db_id":"3c08bf99d8f77ab94596e695234e7097","html":"\u003cp\u003eAllow foreign tables to be created like existing local tables (Zhang Mingli) \u003ca href=\"https://postgr.es/c/302cf1575\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe syntax is \u003ca href=\"/docs/18/sql-createforeigntable.html\" title=\"CREATE FOREIGN TABLE\"\u003e\u003ccode\u003eCREATE FOREIGN TABLE ... LIKE\u003c/code\u003e\u003c/a\u003e.\u003c/p\u003e","id":"18.0-5507537d48f3fa62","identity_text":"Allow foreign tables to be created like existing local tables (Zhang Mingli) The syntax is CREATE FOREIGN TABLE ... LIKE.","part":"changes","patch_ids":["411e9a2745f01f897f4e54030814cdda"],"related_changes":[],"relations":[],"section":"Utility Commands","section_path":["Utility Commands"],"source_commits":["302cf1575"],"source_entry_id":"18.0/changes/070","source_hash":"62be8c19fa522f585e5dde472a79dd0aca848387218592415e6459267cb044c1","source_url":"/docs/release/18.0/#RELEASE-18-UTILITY","statement_hash":"650c85d540879cb0964e2e35ff37c707d3011899d487df426f0eca681a4e7ed5","text":"Allow foreign tables to be created like existing local tables (Zhang Mingli) § The syntax is CREATE FOREIGN TABLE ... LIKE.","title":"Allow foreign tables to be created like existing local tables","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["85b7efa1c"],"commit_groups":[["85b7efa1c"]],"commits":["85b7efa1c"],"cves":[],"db_id":"f3cb3e9cf2993fd77e182438fd54d155","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/functions-matching.html#FUNCTIONS-LIKE\" title=\"9.7.1. LIKE\"\u003e\u003ccode\u003eLIKE\u003c/code\u003e\u003c/a\u003e with \u003ca href=\"/docs/18/collation.html#COLLATION-NONDETERMINISTIC\" title=\"23.2.2.4. Nondeterministic Collations\"\u003enondeterministic collations\u003c/a\u003e (Peter Eisentraut) \u003ca href=\"https://postgr.es/c/85b7efa1c\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-fe1a855e89d5c6c8","identity_text":"Allow LIKE with nondeterministic collations (Peter Eisentraut)","part":"changes","patch_ids":["a5fc7223c5e3de4e0b0adde360f9a8ab"],"related_changes":[],"relations":[],"section":"Utility Commands","section_path":["Utility Commands"],"source_commits":["85b7efa1c"],"source_entry_id":"18.0/changes/071","source_hash":"f18c3846540e26051772bf9f2ce2e36b80aaee96301004d7a41dfd9d5e174e11","source_url":"/docs/release/18.0/#RELEASE-18-UTILITY","statement_hash":"df1ccd059c05458d62412178f18b09f9ac5b61de20fa13903026b25d6b0a281d","text":"Allow LIKE with nondeterministic collations (Peter Eisentraut) §","title":"Allow LIKE with nondeterministic collations","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["329304c90"],"commit_groups":[["329304c90"]],"commits":["329304c90"],"cves":[],"db_id":"1633612e398b9d62fc3745ae04ffbdcb","html":"\u003cp\u003eAllow text position search functions with nondeterministic collations (Peter Eisentraut) \u003ca href=\"https://postgr.es/c/329304c90\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese used to generate an error.\u003c/p\u003e","id":"18.0-547a5b7139bf17c9","identity_text":"Allow text position search functions with nondeterministic collations (Peter Eisentraut) These used to generate an error.","part":"changes","patch_ids":["43d52072e1fb7ccdaab204775ce5218b"],"related_changes":[],"relations":[],"section":"Utility Commands","section_path":["Utility Commands"],"source_commits":["329304c90"],"source_entry_id":"18.0/changes/072","source_hash":"44de95f0bc4bf8dedce0af6fad80799804648813e2b8d379595f9119068daf23","source_url":"/docs/release/18.0/#RELEASE-18-UTILITY","statement_hash":"819c561a7502a24a171a66abb4e6b6d3543683ac066ea66ccff53a0fce4befea","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["d3d098316"],"commit_groups":[["d3d098316"]],"commits":["d3d098316"],"cves":[],"db_id":"30595e5c571a05cc7aee9889ba3a082f","html":"\u003cp\u003eAdd builtin collation provider \u003ca href=\"/docs/18/locale.html#LOCALE-PROVIDERS\" title=\"23.1.4. Locale Providers\"\u003e\u003ccode\u003ePG_UNICODE_FAST\u003c/code\u003e\u003c/a\u003e (Jeff Davis) \u003ca href=\"https://postgr.es/c/d3d098316\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis locale supports case mapping, but sorts in code point order, not natural language order.\u003c/p\u003e","id":"18.0-353986c77138379c","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.","part":"changes","patch_ids":["04e3a10e98b76c4d3552450e42090216"],"related_changes":[],"relations":[],"section":"Utility Commands","section_path":["Utility Commands"],"source_commits":["d3d098316"],"source_entry_id":"18.0/changes/073","source_hash":"c67e8fc3c341be4b77ad03dc233abe7dcf8538d89e6aa0f6ccdf7ecd5fced9ee","source_url":"/docs/release/18.0/#RELEASE-18-UTILITY","statement_hash":"a2fd33890c8b434927b30005c495e84f2917c37b0d70177e7af7e169446cb0cc","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["62ddf7ee9"],"commit_groups":[["62ddf7ee9"]],"commits":["62ddf7ee9"],"cves":[],"db_id":"94f45240a0275d0638838beebe665ece","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/sql-vacuum.html\" title=\"VACUUM\"\u003e\u003cspan\u003eVACUUM\u003c/span\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/sql-analyze.html\" title=\"ANALYZE\"\u003e\u003cspan\u003eANALYZE\u003c/span\u003e\u003c/a\u003e to process partitioned tables without processing their children (Michael Harris) \u003ca href=\"https://postgr.es/c/62ddf7ee9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is enabled with the new \u003ccode\u003eONLY\u003c/code\u003e option. This is useful since autovacuum does not process partitioned tables, just its children.\u003c/p\u003e","id":"18.0-f2283e0ad8b607f4","identity_text":"Allow sql-vacuum and sql-analyze to process partitioned tables without processing their children (Michael Harris) This is enabled with the new ONLY option. This is useful since autovacuum does not process partitioned tables, just its children.","part":"changes","patch_ids":["29279fd7549098871f985b99df60e141"],"related_changes":[{"db_id":"c27156e947f09ff22df4dce5613e8f4c","evidence":{"patch_ids":["29279fd7549098871f985b99df60e141"],"same_day":true},"kind":"related","label":"18.0","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","title":"Change VACUUM and ANALYZE to process the inheritance children of a parent","url":"/docs/compare/?release=18.0#18.0-c84ca88e6e5518a9","version":"18.0"}],"relations":[{"evidence":{"patch_ids":["29279fd7549098871f985b99df60e141"],"same_day":true},"rule":2,"target":"c27156e947f09ff22df4dce5613e8f4c","type":"related"}],"section":"Utility Commands","section_path":["Utility Commands"],"source_commits":["62ddf7ee9"],"source_entry_id":"18.0/changes/074","source_hash":"05c7937bacc706d236a69b8c4fc589b591495e0020f6ccc2a065ca5215497451","source_url":"/docs/release/18.0/#RELEASE-18-UTILITY","statement_hash":"186081ff4a06c8a75bdfc573ce88d92f94310682d9ee69294323a9c8326c9e6f","text":"Allow VACUUM and ANALYZE to process partitioned tables without processing their children (Michael Harris) § This is enabled with the new ONLY option. This is useful since autovacuum does not process partitioned tables, just its children.","title":"Allow VACUUM and ANALYZE to process partitioned tables without processing their children","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["650ab8aaf","d32d14639","e839c8ecc"],"commit_groups":[["650ab8aaf"],["d32d14639"],["e839c8ecc"]],"commits":["650ab8aaf","d32d14639","e839c8ecc"],"cves":[],"db_id":"6e9858b57c68ea99d8150fd4b9910b9f","html":"\u003cp\u003eAdd functions to modify per-relation and per-column optimizer statistics (Corey Huinker) \u003ca href=\"https://postgr.es/c/e839c8ecc\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/d32d14639\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/650ab8aaf\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe functions are \u003ca href=\"/docs/18/functions-admin.html#FUNCTIONS-ADMIN-STATSMOD\" title=\"Table 9.105. Database Object Statistics Manipulation Functions\"\u003e\u003ccode\u003epg_restore_relation_stats()\u003c/code\u003e\u003c/a\u003e, \u003ccode\u003epg_restore_attribute_stats()\u003c/code\u003e, \u003ccode\u003epg_clear_relation_stats()\u003c/code\u003e, and \u003ccode\u003epg_clear_attribute_stats()\u003c/code\u003e.\u003c/p\u003e","id":"18.0-00fa56f14a769e0c","identity_text":"Add functions to modify per-relation and per-column optimizer statistics (Corey Huinker) The functions are pg_restore_relation_stats(), pg_restore_attribute_stats(), pg_clear_relation_stats(), and pg_clear_attribute_stats().","part":"changes","patch_ids":["4b5624c10aaa5b112428b0a7a7f438af","aec78a3156d287b4d2d70cdd28529fcb","eaa21c78bd0fb6108287d3368130333b"],"related_changes":[],"relations":[],"section":"Utility Commands","section_path":["Utility Commands"],"source_commits":["650ab8aaf","d32d14639","e839c8ecc"],"source_entry_id":"18.0/changes/075","source_hash":"674b01db84fb9420f02aad464846ffa2cb53e14b1d1fbbb110ec279daa7ad21d","source_url":"/docs/release/18.0/#RELEASE-18-UTILITY","statement_hash":"7eaa13e8bdea924978103d7640a4fbfb4bfa5d38f0861eb50b3ae7fb57e908a3","text":"Add functions to modify per-relation and per-column optimizer statistics (Corey Huinker) § § § The functions are pg_restore_relation_stats(), pg_restore_attribute_stats(), pg_clear_relation_stats(), and pg_clear_attribute_stats().","title":"Add functions to modify per-relation and per-column optimizer statistics","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["f78ca6f3e"],"commit_groups":[["f78ca6f3e"]],"commits":["f78ca6f3e"],"cves":[],"db_id":"b992193589e7617ce4982491eb56e0e8","html":"\u003cp\u003eAdd server variable \u003ca href=\"/docs/18/runtime-config-resource.html#GUC-FILE-COPY-METHOD\"\u003efile_copy_method\u003c/a\u003e to control the file copying method (Nazir Bilal Yavuz) \u003ca href=\"https://postgr.es/c/f78ca6f3e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis controls whether \u003ca href=\"/docs/18/sql-createdatabase.html\" title=\"CREATE DATABASE\"\u003e\u003ccode\u003eCREATE DATABASE ... STRATEGY=FILE_COPY\u003c/code\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/sql-alterdatabase.html\" title=\"ALTER DATABASE\"\u003e\u003ccode\u003eALTER DATABASE ... SET TABLESPACE\u003c/code\u003e\u003c/a\u003e uses file copy or clone.\u003c/p\u003e","id":"18.0-615abfe2518a2e1a","identity_text":"Add server variable guc-file-copy-method to control the file copying method (Nazir Bilal Yavuz) This controls whether CREATE DATABASE ... STRATEGY=FILE_COPY and ALTER DATABASE ... SET TABLESPACE uses file copy or clone.","part":"changes","patch_ids":["439a7381d3a81157f6048dcf27ba49c2"],"related_changes":[],"relations":[],"section":"Utility Commands","section_path":["Utility Commands"],"source_commits":["f78ca6f3e"],"source_entry_id":"18.0/changes/076","source_hash":"55ffac7e2445fc4100affe783d64394b74d1f2e231c9ff84dec30c9a304d45d3","source_url":"/docs/release/18.0/#RELEASE-18-UTILITY","statement_hash":"d2befdc7cea14270674f2666fadea7539a2a737ce15620835aa47ff9bd481014","text":"Add server variable file_copy_method to control the file copying method (Nazir Bilal Yavuz) § This controls whether CREATE DATABASE ... STRATEGY=FILE_COPY and ALTER DATABASE ... SET TABLESPACE uses file copy or clone.","title":"Add server variable file_copy_method to control the file copying method","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["89f908a6d","fc0438b4e"],"commit_groups":[["89f908a6d"],["fc0438b4e"]],"commits":["89f908a6d","fc0438b4e"],"cves":[],"db_id":"656f1a2aaf525351eb1b8eece841fb72","html":"\u003cp\u003eAllow the specification of non-overlapping \u003ca href=\"/docs/18/sql-createtable.html#SQL-CREATETABLE-PARMS-PRIMARY-KEY\"\u003e\u003ccode\u003ePRIMARY KEY\u003c/code\u003e\u003c/a\u003e, \u003ca href=\"/docs/18/sql-createtable.html#SQL-CREATETABLE-PARMS-UNIQUE\"\u003e\u003ccode\u003eUNIQUE\u003c/code\u003e\u003c/a\u003e, and \u003ca href=\"/docs/18/sql-createtable.html#SQL-CREATETABLE-PARMS-REFERENCES\"\u003eforeign key\u003c/a\u003e constraints (Paul A. Jungwirth) \u003ca href=\"https://postgr.es/c/fc0438b4e\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/89f908a6d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is specified by \u003ccode\u003eWITHOUT OVERLAPS\u003c/code\u003e for \u003ccode\u003ePRIMARY KEY\u003c/code\u003e and \u003ccode\u003eUNIQUE\u003c/code\u003e, and by \u003ccode\u003ePERIOD\u003c/code\u003e for foreign keys, all applied to the last specified column.\u003c/p\u003e","id":"18.0-db27a9639261e139","identity_text":"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.","part":"changes","patch_ids":["9d21a99c31ba9ddbc8896e95bc3a20c8","ed4443224512a7d7c9e0593dd5194bd1"],"related_changes":[],"relations":[],"section":"Utility Commands / Constraints","section_path":["Utility Commands","Constraints"],"source_commits":["89f908a6d","fc0438b4e"],"source_entry_id":"18.0/changes/077","source_hash":"cec7b6e045c9545e4f10003ed952bf9225e93776662baf6f97aab61666ffbe22","source_url":"/docs/release/18.0/#RELEASE-18-CONSTRAINTS","statement_hash":"f26c4016e11249e5cafa6f494580e249b2ffd42b0e460e4b6da81439d8a183c1","text":"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.","title":"Allow the specification of non-overlapping PRIMARY KEY, UNIQUE, and foreign key constraints","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["ca87c415e","eec0040c4"],"commit_groups":[["ca87c415e"],["eec0040c4"]],"commits":["ca87c415e","eec0040c4"],"cves":[],"db_id":"156ef162ef6c54bcf8685caaa1f35f9c","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/sql-createtable.html#SQL-CREATETABLE-PARMS-CHECK\"\u003e\u003ccode\u003eCHECK\u003c/code\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/sql-createtable.html#SQL-CREATETABLE-PARMS-REFERENCES\"\u003eforeign key\u003c/a\u003e constraints to be specified as \u003ccode\u003eNOT ENFORCED\u003c/code\u003e (Amul Sul) \u003ca href=\"https://postgr.es/c/ca87c415e\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/eec0040c4\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis also adds column \u003ca href=\"/docs/18/catalog-pg-constraint.html\" title=\"52.13. pg_constraint\"\u003e\u003ccode\u003epg_constraint\u003c/code\u003e\u003c/a\u003e.\u003ccode\u003econenforced\u003c/code\u003e.\u003c/p\u003e","id":"18.0-0b43fb4e9ec35c53","identity_text":"Allow CHECK and foreign key constraints to be specified as NOT ENFORCED (Amul Sul) This also adds column pg_constraint.conenforced.","part":"changes","patch_ids":["28c11a4e5c4747a11fea5d43ea2536bb","897c774e88b353e9aaeb6731a2e16f1e"],"related_changes":[],"relations":[],"section":"Utility Commands / Constraints","section_path":["Utility Commands","Constraints"],"source_commits":["ca87c415e","eec0040c4"],"source_entry_id":"18.0/changes/078","source_hash":"47a74d174f45c84fadfefcd99f91a1c5b2a162611ee164e7a53164d9a4c34e1b","source_url":"/docs/release/18.0/#RELEASE-18-CONSTRAINTS","statement_hash":"9d9913a6743e4062207224366278ff21a4ddbc3afbab5cd896fbb02070710e2f","text":"Allow CHECK and foreign key constraints to be specified as NOT ENFORCED (Amul Sul) § § This also adds column pg_constraint.conenforced.","title":"Allow CHECK and foreign key constraints to be specified as NOT ENFORCED","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["9321d2fdf"],"commit_groups":[["9321d2fdf"]],"commits":["9321d2fdf"],"cves":[],"db_id":"68a1f7d62d756e8a62c81960b94b7516","html":"\u003cp\u003eRequire \u003ca href=\"/docs/18/sql-createtable.html#SQL-CREATETABLE-PARMS-REFERENCES\"\u003eprimary/foreign key\u003c/a\u003e relationships to use either deterministic collations or the the same nondeterministic collations (Peter Eisentraut) \u003ca href=\"https://postgr.es/c/9321d2fdf\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe restore of a \u003ca href=\"/docs/18/app-pgdump.html\" title=\"pg_dump\"\u003e\u003cspan\u003e\u003cspan\u003epg_dump\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e, also used by \u003ca href=\"/docs/18/pgupgrade.html\" title=\"pg_upgrade\"\u003e\u003cspan\u003e\u003cspan\u003epg_upgrade\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e, will fail if these requirements are not met; schema changes must be made for these upgrade methods to succeed.\u003c/p\u003e","id":"18.0-8f6d0fef92cbe901","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.","part":"changes","patch_ids":["0ce5a6d8a11a1381cec57c4513b145b6"],"related_changes":[],"relations":[],"section":"Utility Commands / Constraints","section_path":["Utility Commands","Constraints"],"source_commits":["9321d2fdf"],"source_entry_id":"18.0/changes/079","source_hash":"2b17eb3b34045fd66a066a2076d863f0fa350f40aa79c07d72d3a50fcdeff6f3","source_url":"/docs/release/18.0/#RELEASE-18-CONSTRAINTS","statement_hash":"2618c39bc6d6dedcb5838152a2f2578f929d0e51755b824342e7609b6456ce31","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["14e87ffa5","81ce602d4"],"commit_groups":[["14e87ffa5"],["81ce602d4"]],"commits":["14e87ffa5","81ce602d4"],"cves":[],"db_id":"8a4e6850401232dbd894c7a1988f9765","html":"\u003cp\u003eStore column \u003ca href=\"/docs/18/sql-createtable.html#SQL-CREATETABLE-PARMS-NOT-NULL\"\u003e\u003ccode\u003eNOT NULL\u003c/code\u003e\u003c/a\u003e specifications in \u003ca href=\"/docs/18/catalog-pg-constraint.html\" title=\"52.13. pg_constraint\"\u003e\u003ccode\u003epg_constraint\u003c/code\u003e\u003c/a\u003e (Álvaro Herrera, Bernd Helmle) \u003ca href=\"https://postgr.es/c/14e87ffa5\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/81ce602d4\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis allows names to be specified for \u003ccode\u003eNOT NULL\u003c/code\u003e constraint. This also adds \u003ccode\u003eNOT NULL\u003c/code\u003e constraints to foreign tables and \u003ccode\u003eNOT NULL\u003c/code\u003e inheritance control to local tables.\u003c/p\u003e","id":"18.0-0039523c093ff51f","identity_text":"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.","part":"changes","patch_ids":["505109f4ed771badde73056b108e1d2e","cbc655e13a914f142d5328fd2f764c89"],"related_changes":[],"relations":[],"section":"Utility Commands / Constraints","section_path":["Utility Commands","Constraints"],"source_commits":["14e87ffa5","81ce602d4"],"source_entry_id":"18.0/changes/080","source_hash":"8d664870fe4f56fdb40b1e71956c91806ece38272c325ee7364c831d08a4078a","source_url":"/docs/release/18.0/#RELEASE-18-CONSTRAINTS","statement_hash":"1c879bc0432ab853565526cf4359ab6808a77d0d5c13a35df594c1bd9ee148eb","text":"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.","title":"Store column NOT NULL specifications in pg_constraint","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["a379061a2"],"commit_groups":[["a379061a2"]],"commits":["a379061a2"],"cves":[],"db_id":"f12f345f0589967cff7f213f4c4bca92","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/sql-altertable.html\" title=\"ALTER TABLE\"\u003e\u003cspan\u003eALTER TABLE\u003c/span\u003e\u003c/a\u003e to set the \u003ccode\u003eNOT VALID\u003c/code\u003e attribute of \u003ccode\u003eNOT NULL\u003c/code\u003e constraints (Rushabh Lathia, Jian He) \u003ca href=\"https://postgr.es/c/a379061a2\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-71a718667ea9d30a","identity_text":"Allow sql-altertable to set the NOT VALID attribute of NOT NULL constraints (Rushabh Lathia, Jian He)","part":"changes","patch_ids":["a2748ca9c6b723c431540e39acdedc40"],"related_changes":[],"relations":[],"section":"Utility Commands / Constraints","section_path":["Utility Commands","Constraints"],"source_commits":["a379061a2"],"source_entry_id":"18.0/changes/081","source_hash":"7a63541c0cbbb94bf4c1f24b20eb8d40802864525d0a1f1d7c799ec1ef11ded5","source_url":"/docs/release/18.0/#RELEASE-18-CONSTRAINTS","statement_hash":"a8527c487edbe6f9a27b333d0cb36ae75e63f09eb9da9be99855bf147481647a","text":"Allow ALTER TABLE to set the NOT VALID attribute of NOT NULL constraints (Rushabh Lathia, Jian He) §","title":"Allow ALTER TABLE to set the NOT VALID attribute of NOT NULL constraints","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4a02af8b1","f4e53e10b"],"commit_groups":[["4a02af8b1"],["f4e53e10b"]],"commits":["4a02af8b1","f4e53e10b"],"cves":[],"db_id":"adedc047dd49b7985ea964547e1bb243","html":"\u003cp\u003eAllow modification of the inheritability of \u003ccode\u003eNOT NULL\u003c/code\u003e constraints (Suraj Kharage, Álvaro Herrera) \u003ca href=\"https://postgr.es/c/f4e53e10b\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/4a02af8b1\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe syntax is \u003ca href=\"/docs/18/sql-altertable.html\" title=\"ALTER TABLE\"\u003e\u003ccode\u003eALTER TABLE ... ALTER CONSTRAINT ... [NO] INHERIT\u003c/code\u003e\u003c/a\u003e.\u003c/p\u003e","id":"18.0-fef76810fd909153","identity_text":"Allow modification of the inheritability of NOT NULL constraints (Suraj Kharage, Álvaro Herrera) The syntax is ALTER TABLE ... ALTER CONSTRAINT ... [NO] INHERIT.","part":"changes","patch_ids":["56786cb45efb3212c89bdb6ba9fb1df5","909cea2bfeaec8651ebceab1164a3e8c"],"related_changes":[],"relations":[],"section":"Utility Commands / Constraints","section_path":["Utility Commands","Constraints"],"source_commits":["4a02af8b1","f4e53e10b"],"source_entry_id":"18.0/changes/082","source_hash":"1c4f8756f1658494559bcf0a5e867d67b99c36db57dc1d6d871e2860cb1d23c9","source_url":"/docs/release/18.0/#RELEASE-18-CONSTRAINTS","statement_hash":"2389a86ed4c13eb10fce8148371ee5a6a016890e39b2a991d29d19326a10d62e","text":"Allow modification of the inheritability of NOT NULL constraints (Suraj Kharage, Álvaro Herrera) § § The syntax is ALTER TABLE ... ALTER CONSTRAINT ... [NO] INHERIT.","title":"Allow modification of the inheritability of NOT NULL constraints","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["b663b9436"],"commit_groups":[["b663b9436"]],"commits":["b663b9436"],"cves":[],"db_id":"00f0a79bb9b96d16af5a0d9ed236739d","html":"\u003cp\u003eAllow \u003ccode\u003eNOT VALID\u003c/code\u003e foreign key constraints on partitioned tables (Amul Sul) \u003ca href=\"https://postgr.es/c/b663b9436\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-1858e6bfd78676a8","identity_text":"Allow NOT VALID foreign key constraints on partitioned tables (Amul Sul)","part":"changes","patch_ids":["c2923b14543c6619fb5c4ab76a00fd21"],"related_changes":[],"relations":[],"section":"Utility Commands / Constraints","section_path":["Utility Commands","Constraints"],"source_commits":["b663b9436"],"source_entry_id":"18.0/changes/083","source_hash":"062a57914f39af06b5e61c9892baed456e5c24e484a6259c145f99dfd61fda32","source_url":"/docs/release/18.0/#RELEASE-18-CONSTRAINTS","statement_hash":"15cb6c826ef8120a3dec63ed2b6c3cd1e5eebed7e6a87ec7d752833735252b0d","text":"Allow NOT VALID foreign key constraints on partitioned tables (Amul Sul) §","title":"Allow NOT VALID foreign key constraints on partitioned tables","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4dea33ce7"],"commit_groups":[["4dea33ce7"]],"commits":["4dea33ce7"],"cves":[],"db_id":"18344143b41582623ed016d08d3724f0","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/sql-altertable.html#SQL-ALTERTABLE-DESC-DROP-CONSTRAINT\"\u003edropping\u003c/a\u003e of constraints \u003ccode\u003eONLY\u003c/code\u003e on partitioned tables (Álvaro Herrera) \u003ca href=\"https://postgr.es/c/4dea33ce7\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis was previously erroneously prohibited.\u003c/p\u003e","id":"18.0-f1d806ac686f4f4b","identity_text":"Allow dropping of constraints ONLY on partitioned tables (Álvaro Herrera) This was previously erroneously prohibited.","part":"changes","patch_ids":["e01f71769bcebafa65ea9e9facbc8f0e"],"related_changes":[],"relations":[],"section":"Utility Commands / Constraints","section_path":["Utility Commands","Constraints"],"source_commits":["4dea33ce7"],"source_entry_id":"18.0/changes/084","source_hash":"8c1219c56b3716c6e0669450727af7aed75763ee754fd98663afe83cdbb70624","source_url":"/docs/release/18.0/#RELEASE-18-CONSTRAINTS","statement_hash":"2f709f0920ff299f36d06fa6d2c5e29a93df41901d6a0aa8e7f22d2226fd478d","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4ac2a9bec"],"commit_groups":[["4ac2a9bec"]],"commits":["4ac2a9bec"],"cves":[],"db_id":"674d24a9f1cfc352eb2363f11a5c7539","html":"\u003cp\u003eAdd \u003ccode\u003eREJECT_LIMIT\u003c/code\u003e to control the number of invalid rows \u003ccode\u003eCOPY FROM\u003c/code\u003e can ignore (Atsushi Torikoshi) \u003ca href=\"https://postgr.es/c/4ac2a9bec\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is available when \u003ccode\u003eON_ERROR = 'ignore'\u003c/code\u003e.\u003c/p\u003e","id":"18.0-b15309054d630829","identity_text":"Add REJECT_LIMIT to control the number of invalid rows COPY FROM can ignore (Atsushi Torikoshi) This is available when ON_ERROR = 'ignore'.","part":"changes","patch_ids":["7f4f9e66d9ca5682846e93efd1b5fc7d"],"related_changes":[],"relations":[],"section":"Utility Commands / COPY","section_path":["Utility Commands","COPY"],"source_commits":["4ac2a9bec"],"source_entry_id":"18.0/changes/085","source_hash":"f3981715f3b71b16f4c72e77aa2ec03da5d40cb477dd6d80bc4cf5c4d4f90e5c","source_url":"/docs/release/18.0/#RELEASE-18-COPY","statement_hash":"698a53fb14412adff83d040ae615676e6a127786304207e285e2519d605a92e2","text":"Add REJECT_LIMIT to control the number of invalid rows COPY FROM can ignore (Atsushi Torikoshi) § This is available when ON_ERROR = 'ignore'.","title":"Add REJECT_LIMIT to control the number of invalid rows COPY FROM can ignore","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["534874fac"],"commit_groups":[["534874fac"]],"commits":["534874fac"],"cves":[],"db_id":"23a5576dc9182181550cee0d3d6263bc","html":"\u003cp\u003eAllow \u003ccode\u003eCOPY TO\u003c/code\u003e to copy rows from populated materialized views (Jian He) \u003ca href=\"https://postgr.es/c/534874fac\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-5cd8e6c78484f775","identity_text":"Allow COPY TO to copy rows from populated materialized views (Jian He)","part":"changes","patch_ids":["9ad7b973037ff1a0a179ec607ca95b25"],"related_changes":[],"relations":[],"section":"Utility Commands / COPY","section_path":["Utility Commands","COPY"],"source_commits":["534874fac"],"source_entry_id":"18.0/changes/086","source_hash":"e37c4454ecdf402763cdc909e3004d4bd7ae457a278af9953c8d49c850da3008","source_url":"/docs/release/18.0/#RELEASE-18-COPY","statement_hash":"580d88384b12572bdc1dba7d048eec5819aaebb667e38fe313dc4e980a4939c0","text":"Allow COPY TO to copy rows from populated materialized views (Jian He) §","title":"Allow COPY TO to copy rows from populated materialized views","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["e7834a1a2"],"commit_groups":[["e7834a1a2"]],"commits":["e7834a1a2"],"cves":[],"db_id":"30be8963700022701b7661b754782b3b","html":"\u003cp\u003eAdd \u003ccode\u003eCOPY\u003c/code\u003e \u003ccode\u003eLOG_VERBOSITY\u003c/code\u003e level \u003ccode\u003esilent\u003c/code\u003e to suppress log output of ignored rows (Atsushi Torikoshi) \u003ca href=\"https://postgr.es/c/e7834a1a2\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis new level suppresses output for discarded input rows when \u003ccode\u003eon_error = 'ignore'\u003c/code\u003e.\u003c/p\u003e","id":"18.0-6731adec896c7c19","identity_text":"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'.","part":"changes","patch_ids":["f569a49fa09919d4034e2b06b4c342ce"],"related_changes":[],"relations":[],"section":"Utility Commands / COPY","section_path":["Utility Commands","COPY"],"source_commits":["e7834a1a2"],"source_entry_id":"18.0/changes/087","source_hash":"e30568a05a51cc956d53c72dd6423d9460b332d5296181fd3e08afd8bd29367c","source_url":"/docs/release/18.0/#RELEASE-18-COPY","statement_hash":"6d5f23b832ecbeab177e4573126032823a2586d9ba213cd63d0d47a0f54a12a6","text":"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'.","title":"Add COPY LOG_VERBOSITY level silent to suppress log output of ignored rows","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["401a6956f"],"commit_groups":[["401a6956f"]],"commits":["401a6956f"],"cves":[],"db_id":"75550bfda376779970fec97260fe8639","html":"\u003cp\u003eDisallow \u003ccode\u003eCOPY FREEZE\u003c/code\u003e on foreign tables (Nathan Bossart) \u003ca href=\"https://postgr.es/c/401a6956f\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously, the \u003ccode\u003eCOPY\u003c/code\u003e worked but the \u003ccode\u003eFREEZE\u003c/code\u003e was ignored, so disallow this command.\u003c/p\u003e","id":"18.0-1a1baaed5585a779","identity_text":"Disallow COPY FREEZE on foreign tables (Nathan Bossart) Previously, the COPY worked but the FREEZE was ignored, so disallow this command.","part":"changes","patch_ids":["eee714494241fff433db4787d9092a87"],"related_changes":[],"relations":[],"section":"Utility Commands / COPY","section_path":["Utility Commands","COPY"],"source_commits":["401a6956f"],"source_entry_id":"18.0/changes/088","source_hash":"2bfc9a6e767e8725680471126a503535a61702174b5a16a1bf2bd6118f06eb97","source_url":"/docs/release/18.0/#RELEASE-18-COPY","statement_hash":"032b9ea2d143e561478378fffea7290a140c3417066719b65f9a85e0be0fc8cc","text":"Disallow COPY FREEZE on foreign tables (Nathan Bossart) § Previously, the COPY worked but the FREEZE was ignored, so disallow this command.","title":"Disallow COPY FREEZE on foreign tables","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["c2a4078eb"],"commit_groups":[["c2a4078eb"]],"commits":["c2a4078eb"],"cves":[],"db_id":"7d0150a8d96ebdd5210b00551808f87c","html":"\u003cp\u003eAutomatically include \u003ccode\u003eBUFFERS\u003c/code\u003e output in \u003ccode\u003eEXPLAIN ANALYZE\u003c/code\u003e (Guillaume Lelarge, David Rowley) \u003ca href=\"https://postgr.es/c/c2a4078eb\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-4732efcce00b7547","identity_text":"Automatically include BUFFERS output in EXPLAIN ANALYZE (Guillaume Lelarge, David Rowley)","part":"changes","patch_ids":["fe41e5c5aa3992b5c1d39d93a7d6ea31"],"related_changes":[],"relations":[],"section":"Utility Commands / EXPLAIN","section_path":["Utility Commands","EXPLAIN"],"source_commits":["c2a4078eb"],"source_entry_id":"18.0/changes/089","source_hash":"4f1cc832b26669ebc18ab566168b38ef39fca619a6c92e252369b01f5a0bc9b1","source_url":"/docs/release/18.0/#RELEASE-18-EXPLAIN","statement_hash":"4d3ebf18daea69902eaf0d735f16086aa29e7bb1546e40ac2dd310ec32bfb65a","text":"Automatically include BUFFERS output in EXPLAIN ANALYZE (Guillaume Lelarge, David Rowley) §","title":"Automatically include BUFFERS output in EXPLAIN ANALYZE","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["320545bfc"],"commit_groups":[["320545bfc"]],"commits":["320545bfc"],"cves":[],"db_id":"b1402b6353f73f398c174abfd4cb75f4","html":"\u003cp\u003eAdd full \u003cacronym\u003eWAL\u003c/acronym\u003e buffer count to \u003ccode\u003eEXPLAIN (WAL)\u003c/code\u003e output (Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/320545bfc\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-f88980978c25aa7b","identity_text":"Add full WAL buffer count to EXPLAIN (WAL) output (Bertrand Drouvot)","part":"changes","patch_ids":["585091e9e2e1078246b0ecd89829b72f"],"related_changes":[],"relations":[],"section":"Utility Commands / EXPLAIN","section_path":["Utility Commands","EXPLAIN"],"source_commits":["320545bfc"],"source_entry_id":"18.0/changes/090","source_hash":"e70f8707fdfc9a5e11eecfc7be79f12ac25687ff9f9a598bab2bbed10e7952a3","source_url":"/docs/release/18.0/#RELEASE-18-EXPLAIN","statement_hash":"2bef83ac1581f3e0e2e23bb3dffbd7e2bca8cd32e26f6b3b7649706bc5985e3b","text":"Add full WAL buffer count to EXPLAIN (WAL) output (Bertrand Drouvot) §","title":"Add full WAL buffer count to EXPLAIN (WAL) output","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["0fbceae84"],"commit_groups":[["0fbceae84"]],"commits":["0fbceae84"],"cves":[],"db_id":"bab8dbda4117422a88669df5576a5023","html":"\u003cp\u003eIn \u003ccode\u003eEXPLAIN ANALYZE\u003c/code\u003e, report the number of index lookups used per index scan node (Peter Geoghegan) \u003ca href=\"https://postgr.es/c/0fbceae84\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-0ec1e9f670b7bf87","identity_text":"In EXPLAIN ANALYZE, report the number of index lookups used per index scan node (Peter Geoghegan)","part":"changes","patch_ids":["47bcd366fc2b2d8e747acc4acdbe8c4a"],"related_changes":[],"relations":[],"section":"Utility Commands / EXPLAIN","section_path":["Utility Commands","EXPLAIN"],"source_commits":["0fbceae84"],"source_entry_id":"18.0/changes/091","source_hash":"b06d2547a2689ffeff48c0ee4af3b40f10b120d0b14fd78b648019997ca231f1","source_url":"/docs/release/18.0/#RELEASE-18-EXPLAIN","statement_hash":"58f0bb81e5341548a9a6e1f357ff1230ec2d0249b162ecc2c4516fa91c0cda6d","text":"In EXPLAIN ANALYZE, report the number of index lookups used per index scan node (Peter Geoghegan) §","title":"In EXPLAIN ANALYZE, report the number of index lookups used per index scan node","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["95dbd827f","ddb17e387"],"commit_groups":[["95dbd827f"],["ddb17e387"]],"commits":["95dbd827f","ddb17e387"],"cves":[],"db_id":"2cbb7e039caf18034654ec1ad2162ce6","html":"\u003cp\u003eModify \u003ccode\u003eEXPLAIN\u003c/code\u003e to output fractional row counts (Ibrar Ahmed, Ilia Evdokimov, Robert Haas) \u003ca href=\"https://postgr.es/c/ddb17e387\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/95dbd827f\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-8f617caa6756d686","identity_text":"Modify EXPLAIN to output fractional row counts (Ibrar Ahmed, Ilia Evdokimov, Robert Haas)","part":"changes","patch_ids":["277dfa6cd96707a4511579fea69bdf42","a7a2bc7d28fb59615d3820a1aef1ada5"],"related_changes":[],"relations":[],"section":"Utility Commands / EXPLAIN","section_path":["Utility Commands","EXPLAIN"],"source_commits":["95dbd827f","ddb17e387"],"source_entry_id":"18.0/changes/092","source_hash":"8b372df1de3e847251475feecff87511212ef4a7308f2ab3f9d3991a4f7f1271","source_url":"/docs/release/18.0/#RELEASE-18-EXPLAIN","statement_hash":"f3ad444cd57c43a8eb9aef5c6daf8d22789e8e21aecd35286d59347003a31e47","text":"Modify EXPLAIN to output fractional row counts (Ibrar Ahmed, Ilia Evdokimov, Robert Haas) § §","title":"Modify EXPLAIN to output fractional row counts","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["1eff8279d","40708acd6","53abb1e0e","95d6e9af0"],"commit_groups":[["1eff8279d"],["40708acd6"],["53abb1e0e"],["95d6e9af0"]],"commits":["1eff8279d","40708acd6","53abb1e0e","95d6e9af0"],"cves":[],"db_id":"f7637a7e9a3f81b57fe9146041535ad8","html":"\u003cp\u003eAdd memory and disk usage details to \u003ccode\u003eMaterial\u003c/code\u003e, \u003ccode\u003eWindow Aggregate\u003c/code\u003e, and common table expression nodes to \u003ccode\u003eEXPLAIN\u003c/code\u003e output (David Rowley, Tatsuo Ishii) \u003ca href=\"https://postgr.es/c/1eff8279d\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/53abb1e0e\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/95d6e9af0\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/40708acd6\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-601ba6789b6723ef","identity_text":"Add memory and disk usage details to Material, Window Aggregate, and common table expression nodes to EXPLAIN output (David Rowley, Tatsuo Ishii)","part":"changes","patch_ids":["1df52fbee5d573687d789986df7b35c2","c360be90ce7d5bd791ad4622b5bfbe57","ee6f3673f5e42eb9d5bf8e348328fafe","f8173d6a2780f722fa00fec00898b957"],"related_changes":[],"relations":[],"section":"Utility Commands / EXPLAIN","section_path":["Utility Commands","EXPLAIN"],"source_commits":["1eff8279d","40708acd6","53abb1e0e","95d6e9af0"],"source_entry_id":"18.0/changes/093","source_hash":"f128c3ab11e36d502813b59e5ae2fff45e8771de891b8f3d9df293688b89b071","source_url":"/docs/release/18.0/#RELEASE-18-EXPLAIN","statement_hash":"82672a2762009bce7205451b2953885a722ed7d77e229835b6189709c86f9901","text":"Add memory and disk usage details to Material, Window Aggregate, and common table expression nodes to EXPLAIN output (David Rowley, Tatsuo Ishii) § § § §","title":"Add memory and disk usage details to Material, Window Aggregate, and common table expression nodes to EXPLAIN output","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["8b1b34254"],"commit_groups":[["8b1b34254"]],"commits":["8b1b34254"],"cves":[],"db_id":"e18d645dd62690d4179d6a67439f312c","html":"\u003cp\u003eAdd details about window function arguments to \u003ccode\u003eEXPLAIN\u003c/code\u003e output (Tom Lane) \u003ca href=\"https://postgr.es/c/8b1b34254\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-88dd6a58e55cfdde","identity_text":"Add details about window function arguments to EXPLAIN output (Tom Lane)","part":"changes","patch_ids":["ec84a482b22364ca0904164bf7b650a1"],"related_changes":[],"relations":[],"section":"Utility Commands / EXPLAIN","section_path":["Utility Commands","EXPLAIN"],"source_commits":["8b1b34254"],"source_entry_id":"18.0/changes/094","source_hash":"a9c598e09704fea78f54ec79c93b4f2ed12edb7ffa65c7f4ff645e8207780e58","source_url":"/docs/release/18.0/#RELEASE-18-EXPLAIN","statement_hash":"b368768879451808ef2f7dd803b2c8af870c11d3c483e0d30a7664d513201eec","text":"Add details about window function arguments to EXPLAIN output (Tom Lane) §","title":"Add details about window function arguments to EXPLAIN output","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["5a1e6df3b"],"commit_groups":[["5a1e6df3b"]],"commits":["5a1e6df3b"],"cves":[],"db_id":"778e042a7bca864fc20e787657eae283","html":"\u003cp\u003eAdd \u003ccode\u003eParallel Bitmap Heap Scan\u003c/code\u003e worker cache statistics to \u003ccode\u003eEXPLAIN ANALYZE\u003c/code\u003e (David Geier, Heikki Linnakangas, Donghang Lin, Alena Rybakina, David Rowley) \u003ca href=\"https://postgr.es/c/5a1e6df3b\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-c57e3b87c33cec9d","identity_text":"Add Parallel Bitmap Heap Scan worker cache statistics to EXPLAIN ANALYZE (David Geier, Heikki Linnakangas, Donghang Lin, Alena Rybakina, David Rowley)","part":"changes","patch_ids":["e13545dcffc8e4f5983b60b2c8dc26ba"],"related_changes":[],"relations":[],"section":"Utility Commands / EXPLAIN","section_path":["Utility Commands","EXPLAIN"],"source_commits":["5a1e6df3b"],"source_entry_id":"18.0/changes/095","source_hash":"382a101c5350e51e68527939a7c17f3fbe53b219e5fe816c8ac8707b587e49d8","source_url":"/docs/release/18.0/#RELEASE-18-EXPLAIN","statement_hash":"d40345a739f93231913a4643f6a21e7b83e12c707c288b83ad808ec462ebfab5","text":"Add Parallel Bitmap Heap Scan worker cache statistics to EXPLAIN ANALYZE (David Geier, Heikki Linnakangas, Donghang Lin, Alena Rybakina, David Rowley) §","title":"Add Parallel Bitmap Heap Scan worker cache statistics to EXPLAIN ANALYZE","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["161320b4b","84b8fccbe","c01743aa4"],"commit_groups":[["161320b4b"],["84b8fccbe"],["c01743aa4"]],"commits":["161320b4b","84b8fccbe","c01743aa4"],"cves":[],"db_id":"23300e43061f5fe045f54955a393e875","html":"\u003cp\u003eIndicate disabled nodes in \u003ccode\u003eEXPLAIN ANALYZE\u003c/code\u003e output (Robert Haas, David Rowley, Laurenz Albe) \u003ca href=\"https://postgr.es/c/c01743aa4\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/161320b4b\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/84b8fccbe\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-b4f1bde46728e1ad","identity_text":"Indicate disabled nodes in EXPLAIN ANALYZE output (Robert Haas, David Rowley, Laurenz Albe)","part":"changes","patch_ids":["a368e7a7240f0fb39e7661639c1ec43f","b0f9881746d36f6f632c01f913c024af","b3db3ec60dd1a995198a4a30f82beeb4"],"related_changes":[],"relations":[],"section":"Utility Commands / EXPLAIN","section_path":["Utility Commands","EXPLAIN"],"source_commits":["161320b4b","84b8fccbe","c01743aa4"],"source_entry_id":"18.0/changes/096","source_hash":"fe9c0805a96c737b939c7d7c8fdc3329f7bda6e4ff8933f5a1f2595bb3219c99","source_url":"/docs/release/18.0/#RELEASE-18-EXPLAIN","statement_hash":"d7e90390fe778b0bea90d6844d9f6909dcab1b9e76b1990046da386d75f0f3bd","text":"Indicate disabled nodes in EXPLAIN ANALYZE output (Robert Haas, David Rowley, Laurenz Albe) § § §","title":"Indicate disabled nodes in EXPLAIN ANALYZE output","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["286a365b9","4e7f62bc3"],"commit_groups":[["286a365b9"],["4e7f62bc3"]],"commits":["286a365b9","4e7f62bc3"],"cves":[],"db_id":"1b2ed6a4886122496b4235e9bc502410","html":"\u003cp\u003eImprove \u003ca href=\"/docs/18/collation.html#COLLATION-MANAGING-STANDARD\" title=\"23.2.2.1. Standard Collations\"\u003eUnicode\u003c/a\u003e full case mapping and conversion (Jeff Davis) \u003ca href=\"https://postgr.es/c/4e7f62bc3\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/286a365b9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis adds the ability to do conditional and title case mapping, and case map single characters to multiple characters.\u003c/p\u003e","id":"18.0-2af3118e9cf895c6","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.","part":"changes","patch_ids":["0bc695a859154bdbe2aa4141a8c131d7","c4d90a2c6dc576697ae6803230585a80"],"related_changes":[],"relations":[],"section":"Data Types","section_path":["Data Types"],"source_commits":["286a365b9","4e7f62bc3"],"source_entry_id":"18.0/changes/097","source_hash":"44c26c92986f06630e401c20db860295e1e24fcd5259ea9ea934f4bf062fdd8e","source_url":"/docs/release/18.0/#RELEASE-18-DATATYPES","statement_hash":"02776b8149a82584d272cc2094e4a669aca778c5844f65839a5f72cf0687f143","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["a5579a90a"],"commit_groups":[["a5579a90a"]],"commits":["a5579a90a"],"cves":[],"db_id":"707a9526e8d1e6416419dcc4e0f8c1fb","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/datatype-json.html\" title=\"8.14. JSON Types\"\u003e\u003ccode\u003ejsonb\u003c/code\u003e\u003c/a\u003e \u003ccode\u003enull\u003c/code\u003e values to be cast to scalar types as \u003ccode\u003eNULL\u003c/code\u003e (Tom Lane) \u003ca href=\"https://postgr.es/c/a5579a90a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003ePreviously such casts generated an error.\u003c/p\u003e","id":"18.0-e8ea7869a8082253","identity_text":"Allow jsonb null values to be cast to scalar types as NULL (Tom Lane) Previously such casts generated an error.","part":"changes","patch_ids":["f6184b101cbccd529291b34b9ea43559"],"related_changes":[],"relations":[],"section":"Data Types","section_path":["Data Types"],"source_commits":["a5579a90a"],"source_entry_id":"18.0/changes/098","source_hash":"1e15ce0182df8ba9bb4f5d3c70a693a1c71b87744e48c4280afcb76462804520","source_url":"/docs/release/18.0/#RELEASE-18-DATATYPES","statement_hash":"e835773742df55f58b57f5dbf777b47ddc9916b939e5f10a60426d8f63610fdd","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4603903d2"],"commit_groups":[["4603903d2"]],"commits":["4603903d2"],"cves":[],"db_id":"ed4ae5d934182b8abe85d461b1aec905","html":"\u003cp\u003eAdd optional parameter to \u003ca href=\"/docs/18/functions-json.html#FUNCTIONS-JSON-PROCESSING-TABLE\" title=\"Table 9.51. JSON Processing Functions\"\u003e\u003ccode\u003ejson{b}_strip_nulls\u003c/code\u003e\u003c/a\u003e to allow removal of null array elements (Florents Tselai) \u003ca href=\"https://postgr.es/c/4603903d2\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-69d404540f719906","identity_text":"Add optional parameter to json{b}_strip_nulls to allow removal of null array elements (Florents Tselai)","part":"changes","patch_ids":["53957a139405a1a63e2a80ae5c7633c5"],"related_changes":[],"relations":[],"section":"Data Types","section_path":["Data Types"],"source_commits":["4603903d2"],"source_entry_id":"18.0/changes/099","source_hash":"4c2e22cc8bbb8a2d5f13e86d2e97e51a1bc8f88c107067a603ace9ebb1958a85","source_url":"/docs/release/18.0/#RELEASE-18-DATATYPES","statement_hash":"2353d6854c138551fa6c128dc9828ac36b241d8c813afe7719a90cbfd0e910d5","text":"Add optional parameter to json{b}_strip_nulls to allow removal of null array elements (Florents Tselai) §","title":"Add optional parameter to json{b}_strip_nulls to allow removal of null array elements","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["6c12ae09f"],"commit_groups":[["6c12ae09f"]],"commits":["6c12ae09f"],"cves":[],"db_id":"4de325fa4535491c0694238b7c98f7e6","html":"\u003cp\u003eAdd function \u003ca href=\"/docs/18/functions-array.html#ARRAY-FUNCTIONS-TABLE\" title=\"Table 9.57. Array Functions\"\u003e\u003ccode\u003earray_sort()\u003c/code\u003e\u003c/a\u003e which sorts an array's first dimension (Junwang Zhao, Jian He) \u003ca href=\"https://postgr.es/c/6c12ae09f\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-cea24b509f4bf358","identity_text":"Add function array_sort() which sorts an array's first dimension (Junwang Zhao, Jian He)","part":"changes","patch_ids":["c7bff0b37a68e7db3427774c38619ac7"],"related_changes":[],"relations":[],"section":"Data Types","section_path":["Data Types"],"source_commits":["6c12ae09f"],"source_entry_id":"18.0/changes/100","source_hash":"d7b1e0835defdcd73c1e32e6c1505e43bd755d4dea033a81de1a49ce898debb2","source_url":"/docs/release/18.0/#RELEASE-18-DATATYPES","statement_hash":"1b8e208dd9da84b68630db6e70eaa1b1e97cbd8295baf3141f5837933861cba9","text":"Add function array_sort() which sorts an array's first dimension (Junwang Zhao, Jian He) §","title":"Add function array_sort() which sorts an array's first dimension","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["49d6c7d8d"],"commit_groups":[["49d6c7d8d"]],"commits":["49d6c7d8d"],"cves":[],"db_id":"04303e115e57612dca79ef5a9ab63041","html":"\u003cp\u003eAdd function \u003ca href=\"/docs/18/functions-array.html#ARRAY-FUNCTIONS-TABLE\" title=\"Table 9.57. Array Functions\"\u003e\u003ccode\u003earray_reverse()\u003c/code\u003e\u003c/a\u003e which reverses an array's first dimension (Aleksander Alekseev) \u003ca href=\"https://postgr.es/c/49d6c7d8d\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-19b55afd582ddf02","identity_text":"Add function array_reverse() which reverses an array's first dimension (Aleksander Alekseev)","part":"changes","patch_ids":["03ae5b8911f272ccafb9c3876c7f3387"],"related_changes":[],"relations":[],"section":"Data Types","section_path":["Data Types"],"source_commits":["49d6c7d8d"],"source_entry_id":"18.0/changes/101","source_hash":"0631b9c5fc256653b132c39b3f93cb09c7938372c029c53b13f58d93b434e1d7","source_url":"/docs/release/18.0/#RELEASE-18-DATATYPES","statement_hash":"8008e051e0fc517cdec2a45e989e6e7cf3ead188464cab7ad031a5aa5adf21bc","text":"Add function array_reverse() which reverses an array's first dimension (Aleksander Alekseev) §","title":"Add function array_reverse() which reverses an array's first dimension","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["0697b2390"],"commit_groups":[["0697b2390"]],"commits":["0697b2390"],"cves":[],"db_id":"f44735403faab808dbc8e70e494d5367","html":"\u003cp\u003eAdd function \u003ca href=\"/docs/18/functions-string.html#FUNCTIONS-STRING-OTHER\" title=\"Table 9.10. Other String Functions and Operators\"\u003e\u003ccode\u003ereverse()\u003c/code\u003e\u003c/a\u003e to reverse bytea bytes (Aleksander Alekseev) \u003ca href=\"https://postgr.es/c/0697b2390\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-a256c0a1a1f5c17b","identity_text":"Add function reverse() to reverse bytea bytes (Aleksander Alekseev)","part":"changes","patch_ids":["5cd9af568be42f1acea780c7bf2bdae5"],"related_changes":[],"relations":[],"section":"Data Types","section_path":["Data Types"],"source_commits":["0697b2390"],"source_entry_id":"18.0/changes/102","source_hash":"1391c72bc875fa563fe97e4f3f326d89ade66c1b138208d1e0a1347035f3eef4","source_url":"/docs/release/18.0/#RELEASE-18-DATATYPES","statement_hash":"db66fdeed8508fd104685446965f51db4ef1eff1fd2180c36767e29306ad806b","text":"Add function reverse() to reverse bytea bytes (Aleksander Alekseev) §","title":"Add function reverse() to reverse bytea bytes","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["6da469bad"],"commit_groups":[["6da469bad"]],"commits":["6da469bad"],"cves":[],"db_id":"5551ec9759852e876b78cdf60b7e5861","html":"\u003cp\u003eAllow casting between integer types and \u003ca href=\"/docs/18/datatype-binary.html\" title=\"8.4. Binary Data Types\"\u003e\u003ccode\u003ebytea\u003c/code\u003e\u003c/a\u003e (Aleksander Alekseev) \u003ca href=\"https://postgr.es/c/6da469bad\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe integer values are stored as \u003ccode\u003ebytea\u003c/code\u003e two's complement values.\u003c/p\u003e","id":"18.0-91ec2a175f6e81fe","identity_text":"Allow casting between integer types and bytea (Aleksander Alekseev) The integer values are stored as bytea two's complement values.","part":"changes","patch_ids":["129367dc9e7217c5b7de91653664e367"],"related_changes":[],"relations":[],"section":"Data Types","section_path":["Data Types"],"source_commits":["6da469bad"],"source_entry_id":"18.0/changes/103","source_hash":"ac3d81087880686f7b48568deaab6ff750ea049c29d4a529345affdd9137af3a","source_url":"/docs/release/18.0/#RELEASE-18-DATATYPES","statement_hash":"6e79726a30c9f23d82d38671f942cd48ed1a9b83b8184d44b3cd08ccdc47ba18","text":"Allow casting between integer types and bytea (Aleksander Alekseev) § The integer values are stored as bytea two's complement values.","title":"Allow casting between integer types and bytea","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["82a46cca9"],"commit_groups":[["82a46cca9"]],"commits":["82a46cca9"],"cves":[],"db_id":"b3a13160940dac3f7a1a1af7f4cf764d","html":"\u003cp\u003eUpdate Unicode data to \u003ca href=\"/docs/18/collation.html#COLLATION-MANAGING-STANDARD\" title=\"23.2.2.1. Standard Collations\"\u003eUnicode\u003c/a\u003e 16.0.0 (Peter Eisentraut) \u003ca href=\"https://postgr.es/c/82a46cca9\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-b7f5c835bb8cb99a","identity_text":"Update Unicode data to Unicode 16.0.0 (Peter Eisentraut)","part":"changes","patch_ids":["37e8f514959e205b0155b61312d52d56"],"related_changes":[],"relations":[],"section":"Data Types","section_path":["Data Types"],"source_commits":["82a46cca9"],"source_entry_id":"18.0/changes/104","source_hash":"7b363edbf7fc1652e00ae639f016a531400b78a1501225262fbf76a7fc2c0dd8","source_url":"/docs/release/18.0/#RELEASE-18-DATATYPES","statement_hash":"dc448dd80b25033f629182d9bb00f6e6eb258933e0fc988309cd3ddbaf4be408","text":"Update Unicode data to Unicode 16.0.0 (Peter Eisentraut) §","title":"Update Unicode data to Unicode 16.0.0","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["197427fb3","7edd2cbc5","8388cae55","9c46d902b","b464e51ab","c0c364fa1"],"commit_groups":[["197427fb3","7edd2cbc5","8388cae55","9c46d902b","b464e51ab","c0c364fa1"]],"commits":["b464e51ab"],"cves":[],"db_id":"d02c90e2590d4a47f73a5782496b4966","html":"\u003cp\u003eAdd full text search \u003ca href=\"/docs/18/textsearch-dictionaries.html#TEXTSEARCH-SNOWBALL-DICTIONARY\" title=\"12.6.6. Snowball Dictionary\"\u003estemming\u003c/a\u003e for Estonian (Tom Lane) \u003ca href=\"https://postgr.es/c/b464e51ab\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-5f1391509757dd6d","identity_text":"Add full text search stemming for Estonian (Tom Lane)","part":"changes","patch_ids":["d20fbffc83ee90d1348f1d03836b8f18"],"related_changes":[{"db_id":"fe6fa87c7f7a2f01e5226fc8b75d4395","evidence":{"patch_ids":["d20fbffc83ee90d1348f1d03836b8f18"],"same_day":false},"kind":"related","label":"17.5","source_url":"/docs/release/17.5/#RELEASE-17-5-CHANGES","title":"Avoid crash when a Snowball stemmer encounters an out-of-memory condition","url":"/docs/compare/?release=17.5#17.5-88fad50b7b3b2e15","version":"17.5"},{"db_id":"c2850458f2850974df366bef8a85488e","evidence":{"patch_ids":["d20fbffc83ee90d1348f1d03836b8f18"],"same_day":false},"kind":"related","label":"16.9","source_url":"/docs/release/16.9/#RELEASE-16-9-CHANGES","title":"Avoid crash when a Snowball stemmer encounters an out-of-memory condition","url":"/docs/compare/?release=16.9#16.9-71f38ed0f1b64f88","version":"16.9"},{"db_id":"00feddbb8384a7a8cefe4217cd497215","evidence":{"patch_ids":["d20fbffc83ee90d1348f1d03836b8f18"],"same_day":false},"kind":"related","label":"15.13","source_url":"/docs/release/15.13/#id-1.11.6.12.5","title":"Avoid crash when a Snowball stemmer encounters an out-of-memory condition","url":"/docs/compare/?release=15.13#15.13-6fa1c30b53ef4a7a","version":"15.13"},{"db_id":"d6bf0f560b8ac8cad3c1d6a070b45594","evidence":{"patch_ids":["d20fbffc83ee90d1348f1d03836b8f18"],"same_day":false},"kind":"related","label":"14.18","source_url":"/docs/release/14.18/#id-1.11.6.12.5","title":"Avoid crash when a Snowball stemmer encounters an out-of-memory condition","url":"/docs/compare/?release=14.18#14.18-813abffbc8584526","version":"14.18"},{"db_id":"43dbc69a435522e8a12bbf37193bcbca","evidence":{"patch_ids":["d20fbffc83ee90d1348f1d03836b8f18"],"same_day":false},"kind":"related","label":"13.21","source_url":"/docs/release/13.21/#id-1.11.6.8.6","title":"Avoid crash when a Snowball stemmer encounters an out-of-memory condition","url":"/docs/compare/?release=13.21#13.21-7de382d5402e6e82","version":"13.21"}],"relations":[{"evidence":{"patch_ids":["d20fbffc83ee90d1348f1d03836b8f18"],"same_day":false},"rule":2,"target":"00feddbb8384a7a8cefe4217cd497215","type":"related"},{"evidence":{"patch_ids":["d20fbffc83ee90d1348f1d03836b8f18"],"same_day":false},"rule":2,"target":"43dbc69a435522e8a12bbf37193bcbca","type":"related"},{"evidence":{"patch_ids":["d20fbffc83ee90d1348f1d03836b8f18"],"same_day":false},"rule":2,"target":"c2850458f2850974df366bef8a85488e","type":"related"},{"evidence":{"patch_ids":["d20fbffc83ee90d1348f1d03836b8f18"],"same_day":false},"rule":2,"target":"d6bf0f560b8ac8cad3c1d6a070b45594","type":"related"},{"evidence":{"patch_ids":["d20fbffc83ee90d1348f1d03836b8f18"],"same_day":false},"rule":2,"target":"fe6fa87c7f7a2f01e5226fc8b75d4395","type":"related"}],"section":"Data Types","section_path":["Data Types"],"source_commits":["b464e51ab"],"source_entry_id":"18.0/changes/105","source_hash":"dd6878414ee23406689c7eefc1a641935c96e6bd890e0e1431ff6fd28bfca759","source_url":"/docs/release/18.0/#RELEASE-18-DATATYPES","statement_hash":"765cc1defacc087129eb32bf5f736de4c5be16883a95fba7b8adca47a87ce874","text":"Add full text search stemming for Estonian (Tom Lane) §","title":"Add full text search stemming for Estonian","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["cd838e200"],"commit_groups":[["cd838e200"]],"commits":["cd838e200"],"cves":[],"db_id":"29cf32d71ceaf941577232a9a6de849b","html":"\u003cp\u003eImprove the \u003ca href=\"/docs/18/datatype-xml.html\" title=\"8.13. XML Type\"\u003e\u003ccode\u003eXML\u003c/code\u003e\u003c/a\u003e error codes to more closely match the \u003cacronym\u003eSQL\u003c/acronym\u003e standard (Tom Lane) \u003ca href=\"https://postgr.es/c/cd838e200\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese errors are reported via \u003ca href=\"/docs/18/errcodes-appendix.html\" title=\"Appendix A. PostgreSQL Error Codes\"\u003e\u003ccode\u003eSQLSTATE\u003c/code\u003e\u003c/a\u003e.\u003c/p\u003e","id":"18.0-484da2e971e2ea9a","identity_text":"Improve the XML error codes to more closely match the SQL standard (Tom Lane) These errors are reported via SQLSTATE.","part":"changes","patch_ids":["d0cddeae6cd2c47e599df50be2682b02"],"related_changes":[],"relations":[],"section":"Data Types","section_path":["Data Types"],"source_commits":["cd838e200"],"source_entry_id":"18.0/changes/106","source_hash":"b003b4d98dbd5677c14bef49c97e4a7845d1314b654ffa4843f446d7091d0cc6","source_url":"/docs/release/18.0/#RELEASE-18-DATATYPES","statement_hash":"7e7aa4253ca1fd37a6b6fde5f48c3cfc8d4b57bc08b4970e5dc0f9548fa01120","text":"Improve the XML error codes to more closely match the SQL standard (Tom Lane) § These errors are reported via SQLSTATE.","title":"Improve the XML error codes to more closely match the SQL standard","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["bfc599206"],"commit_groups":[["bfc599206"]],"commits":["bfc599206"],"cves":[],"db_id":"b6349fdce5ba2ae112d0be3d05e38198","html":"\u003cp\u003eAdd function \u003ca href=\"/docs/18/functions-string.html#FUNCTIONS-STRING-OTHER\" title=\"Table 9.10. Other String Functions and Operators\"\u003e\u003ccode\u003ecasefold()\u003c/code\u003e\u003c/a\u003e to allow for more sophisticated case-insensitive matching (Jeff Davis) \u003ca href=\"https://postgr.es/c/bfc599206\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis 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.\u003c/p\u003e","id":"18.0-eec605cfdc403633","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.","part":"changes","patch_ids":["0684a21f7afe3e30c9299aaa67789314"],"related_changes":[],"relations":[],"section":"Functions","section_path":["Functions"],"source_commits":["bfc599206"],"source_entry_id":"18.0/changes/107","source_hash":"45cb069e223659d8f877c9a2110d431b847abaa3d2bf90c2d51977f38f2e6cb4","source_url":"/docs/release/18.0/#RELEASE-18-FUNCTIONS","statement_hash":"c9d001f8f460c1f05dad5d20c8956c701fd640f0996cec7198b5decd3f545c09","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["2d24fd942","a0f1fce80"],"commit_groups":[["2d24fd942"],["a0f1fce80"]],"commits":["2d24fd942","a0f1fce80"],"cves":[],"db_id":"ff1f62132a8b10a5b46e5398263f6f25","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/functions-aggregate.html#FUNCTIONS-AGGREGATE-TABLE\" title=\"Table 9.62. General-Purpose Aggregate Functions\"\u003e\u003ccode\u003eMIN()\u003c/code\u003e\u003c/a\u003e/\u003ca href=\"/docs/18/functions-aggregate.html#FUNCTIONS-AGGREGATE-TABLE\" title=\"Table 9.62. General-Purpose Aggregate Functions\"\u003e\u003ccode\u003eMAX()\u003c/code\u003e\u003c/a\u003e aggregates on arrays and composite types (Aleksander Alekseev, Marat Buharov) \u003ca href=\"https://postgr.es/c/a0f1fce80\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/2d24fd942\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-6997f70f04ef9a9f","identity_text":"Allow MIN()/MAX() aggregates on arrays and composite types (Aleksander Alekseev, Marat Buharov)","part":"changes","patch_ids":["3edf790a09115a97da7454a772b4af24","918dcba37bfa104714d105730a4fe810"],"related_changes":[],"relations":[],"section":"Functions","section_path":["Functions"],"source_commits":["2d24fd942","a0f1fce80"],"source_entry_id":"18.0/changes/108","source_hash":"5cadbbf5599ab2314a87ecb4f26020de91d5430e9148ef87b799d1518fcb25db","source_url":"/docs/release/18.0/#RELEASE-18-FUNCTIONS","statement_hash":"34aeb4e9e3d29179eef8e884691002728bd47baa789e80ea81c923f3f1058f93","text":"Allow MIN()/MAX() aggregates on arrays and composite types (Aleksander Alekseev, Marat Buharov) § §","title":"Allow MIN()/MAX() aggregates on arrays and composite types","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["6be39d77a"],"commit_groups":[["6be39d77a"]],"commits":["6be39d77a"],"cves":[],"db_id":"b3cffadee5353df8dd7872750d4fb682","html":"\u003cp\u003eAdd a \u003ccode\u003eWEEK\u003c/code\u003e option to \u003ca href=\"/docs/18/functions-datetime.html#FUNCTIONS-DATETIME-EXTRACT\" title=\"9.9.1. EXTRACT, date_part\"\u003e\u003ccode\u003eEXTRACT()\u003c/code\u003e\u003c/a\u003e (Tom Lane) \u003ca href=\"https://postgr.es/c/6be39d77a\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-f22633dee861de77-1","identity_text":"Add a WEEK option to EXTRACT() (Tom Lane)","part":"changes","patch_ids":["c19cf27dbaa7653c29b3098b611b1638"],"related_changes":[{"db_id":"ade04ae5639b5e3efcd757143411e3ce","evidence":{"ambiguous_patch_ids":["c19cf27dbaa7653c29b3098b611b1638"],"patch_ids":["c19cf27dbaa7653c29b3098b611b1638"],"same_day":true},"kind":"related","label":"18.0","source_url":"/docs/release/18.0/#RELEASE-18-FUNCTIONS","title":"Improve the output EXTRACT(QUARTER ...) for negative values","url":"/docs/compare/?release=18.0#18.0-f22633dee861de77-2","version":"18.0"}],"relations":[{"evidence":{"ambiguous_patch_ids":["c19cf27dbaa7653c29b3098b611b1638"],"patch_ids":["c19cf27dbaa7653c29b3098b611b1638"],"same_day":true},"rule":2,"target":"ade04ae5639b5e3efcd757143411e3ce","type":"related"}],"section":"Functions","section_path":["Functions"],"source_commits":["6be39d77a"],"source_entry_id":"18.0/changes/109","source_hash":"c369144b029e6d7b953c4f7ee1baf0f025f8ff93f1ab0ece012d7d3c272b17b1","source_url":"/docs/release/18.0/#RELEASE-18-FUNCTIONS","statement_hash":"d8e836149292c973d2a0f09ad1d451f9e0d694896adc926732c9f533896bd490","text":"Add a WEEK option to EXTRACT() (Tom Lane) §","title":"Add a WEEK option to EXTRACT()","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["6be39d77a"],"commit_groups":[["6be39d77a"]],"commits":["6be39d77a"],"cves":[],"db_id":"ade04ae5639b5e3efcd757143411e3ce","html":"\u003cp\u003eImprove the output \u003ccode\u003eEXTRACT(QUARTER ...)\u003c/code\u003e for negative values (Tom Lane) \u003ca href=\"https://postgr.es/c/6be39d77a\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-f22633dee861de77-2","identity_text":"Improve the output EXTRACT(QUARTER ...) for negative values (Tom Lane)","part":"changes","patch_ids":["c19cf27dbaa7653c29b3098b611b1638"],"related_changes":[{"db_id":"b3cffadee5353df8dd7872750d4fb682","evidence":{"ambiguous_patch_ids":["c19cf27dbaa7653c29b3098b611b1638"],"patch_ids":["c19cf27dbaa7653c29b3098b611b1638"],"same_day":true},"kind":"related","label":"18.0","source_url":"/docs/release/18.0/#RELEASE-18-FUNCTIONS","title":"Add a WEEK option to EXTRACT()","url":"/docs/compare/?release=18.0#18.0-f22633dee861de77-1","version":"18.0"}],"relations":[{"evidence":{"ambiguous_patch_ids":["c19cf27dbaa7653c29b3098b611b1638"],"patch_ids":["c19cf27dbaa7653c29b3098b611b1638"],"same_day":true},"rule":2,"target":"b3cffadee5353df8dd7872750d4fb682","type":"related"}],"section":"Functions","section_path":["Functions"],"source_commits":["6be39d77a"],"source_entry_id":"18.0/changes/110","source_hash":"72c85521604e9cca15c3f296bcf42cbfa34ae96e6cbafa6537be6b0d02e10620","source_url":"/docs/release/18.0/#RELEASE-18-FUNCTIONS","statement_hash":"a214ee4643d1d9bf98ef496b4419597961fc04d5f9e0d55db52838d472d932f1","text":"Improve the output EXTRACT(QUARTER ...) for negative values (Tom Lane) §","title":"Improve the output EXTRACT(QUARTER ...) for negative values","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["172e6b3ad"],"commit_groups":[["172e6b3ad"]],"commits":["172e6b3ad"],"cves":[],"db_id":"e0cbd160d06a691a81d92c71d409a5ef","html":"\u003cp\u003eAdd roman numeral support to \u003ca href=\"/docs/18/functions-formatting.html#FUNCTIONS-FORMATTING-TABLE\" title=\"Table 9.26. Formatting Functions\"\u003e\u003ccode\u003eto_number()\u003c/code\u003e\u003c/a\u003e (Hunaid Sohail) \u003ca href=\"https://postgr.es/c/172e6b3ad\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is accessed via the \u003ccode\u003eRN\u003c/code\u003e pattern.\u003c/p\u003e","id":"18.0-db03fc0c4d7c7e77","identity_text":"Add roman numeral support to to_number() (Hunaid Sohail) This is accessed via the RN pattern.","part":"changes","patch_ids":["133b66dc3fa7a00aecec6623a2a0104a"],"related_changes":[],"relations":[],"section":"Functions","section_path":["Functions"],"source_commits":["172e6b3ad"],"source_entry_id":"18.0/changes/111","source_hash":"32bda5c343b0e274152cea92bbc66b00d80c0ad61b63250b896faf088627ead4","source_url":"/docs/release/18.0/#RELEASE-18-FUNCTIONS","statement_hash":"3ad41892efe6fea4d12c377eae3bb3908d356da0f989fc2b51e3072b9dcd7439","text":"Add roman numeral support to to_number() (Hunaid Sohail) § This is accessed via the RN pattern.","title":"Add roman numeral support to to_number()","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["78c5e141e"],"commit_groups":[["78c5e141e"]],"commits":["78c5e141e"],"cves":[],"db_id":"cece32c4a51bdf23bee2a0f29962d93d","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/datatype-uuid.html\" title=\"8.12. UUID Type\"\u003e\u003ccode\u003eUUID\u003c/code\u003e\u003c/a\u003e version 7 generation function \u003ca href=\"/docs/18/functions-uuid.html#FUNC_UUID_GEN_TABLE\" title=\"Table 9.45. UUID Generation Functions\"\u003e\u003ccode\u003euuidv7()\u003c/code\u003e\u003c/a\u003e (Andrey Borodin) \u003ca href=\"https://postgr.es/c/78c5e141e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis \u003ccode\u003eUUID\u003c/code\u003e value is temporally sortable. Function alias \u003ca href=\"/docs/18/functions-uuid.html#FUNC_UUID_GEN_TABLE\" title=\"Table 9.45. UUID Generation Functions\"\u003e\u003ccode\u003euuidv4()\u003c/code\u003e\u003c/a\u003e has been added to explicitly generate version 4 UUIDs.\u003c/p\u003e","id":"18.0-542d8a8a70b3db3c","identity_text":"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.","part":"changes","patch_ids":["56fa70c05aee3519b8c7f629a11367fa"],"related_changes":[],"relations":[],"section":"Functions","section_path":["Functions"],"source_commits":["78c5e141e"],"source_entry_id":"18.0/changes/112","source_hash":"7877416c8bc1ed72cd83517c7cfa2be9454b995e7c9ecbc06655eb24026b18dd","source_url":"/docs/release/18.0/#RELEASE-18-FUNCTIONS","statement_hash":"e0da520f09f4f2ac133bc0bff5d10a98c32f202b283cfa8927ddc7514e82334d","text":"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.","title":"Add UUID version 7 generation function uuidv7()","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["760162fed"],"commit_groups":[["760162fed"]],"commits":["760162fed"],"cves":[],"db_id":"4adbc4a880c6d186b573a23b72e25743","html":"\u003cp\u003eAdd functions \u003ca href=\"/docs/18/functions-binarystring.html#FUNCTIONS-BINARYSTRING-OTHER\" title=\"Table 9.12. Other Binary String Functions\"\u003e\u003ccode\u003ecrc32()\u003c/code\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/functions-binarystring.html#FUNCTIONS-BINARYSTRING-OTHER\" title=\"Table 9.12. Other Binary String Functions\"\u003e\u003ccode\u003ecrc32c()\u003c/code\u003e\u003c/a\u003e to compute \u003cacronym\u003eCRC\u003c/acronym\u003e values (Aleksander Alekseev) \u003ca href=\"https://postgr.es/c/760162fed\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-0793591dedbc959b","identity_text":"Add functions crc32() and crc32c() to compute CRC values (Aleksander Alekseev)","part":"changes","patch_ids":["f072ba34fd057475f25240221b644589"],"related_changes":[],"relations":[],"section":"Functions","section_path":["Functions"],"source_commits":["760162fed"],"source_entry_id":"18.0/changes/113","source_hash":"186d4a85f05026c3f1e1b5cedc85be001793dd4387c3846bd784693e34d9df3e","source_url":"/docs/release/18.0/#RELEASE-18-FUNCTIONS","statement_hash":"b7c1fff56676d7a5ea8f068fd55d5c9250a4f76ec60d2244c2e801cfe67c7e03","text":"Add functions crc32() and crc32c() to compute CRC values (Aleksander Alekseev) §","title":"Add functions crc32() and crc32c() to compute CRC values","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["a3b6dfd41"],"commit_groups":[["a3b6dfd41"]],"commits":["a3b6dfd41"],"cves":[],"db_id":"986dd3e980b067ffd2e6eecdfc4befd1","html":"\u003cp\u003eAdd math functions \u003ca href=\"/docs/18/functions-math.html#FUNCTIONS-MATH-FUNC-TABLE\" title=\"Table 9.5. Mathematical Functions\"\u003e\u003ccode\u003egamma()\u003c/code\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/functions-math.html#FUNCTIONS-MATH-FUNC-TABLE\" title=\"Table 9.5. Mathematical Functions\"\u003e\u003ccode\u003elgamma()\u003c/code\u003e\u003c/a\u003e (Dean Rasheed) \u003ca href=\"https://postgr.es/c/a3b6dfd41\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-88be5f9be0b211b5","identity_text":"Add math functions gamma() and lgamma() (Dean Rasheed)","part":"changes","patch_ids":["e0b46f5f41bfa3e2a42c6d003da6b3d5"],"related_changes":[],"relations":[],"section":"Functions","section_path":["Functions"],"source_commits":["a3b6dfd41"],"source_entry_id":"18.0/changes/114","source_hash":"0e6224fe43da67b085f65cee813ae8aad126061d045f1ff177ccd09630b490bd","source_url":"/docs/release/18.0/#RELEASE-18-FUNCTIONS","statement_hash":"6e74c2ea38c261b8bb55b6b1bcd723c5977a27e47fe892c9b2fbb23d25a61bef","text":"Add math functions gamma() and lgamma() (Dean Rasheed) §","title":"Add math functions gamma() and lgamma()","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["246dedc5d"],"commit_groups":[["246dedc5d"]],"commits":["246dedc5d"],"cves":[],"db_id":"a4ea7ded150aaebd8e3d529313e4ff98","html":"\u003cp\u003eAllow \u003ccode\u003e=\u0026gt;\u003c/code\u003e syntax for named cursor arguments in \u003ca href=\"/docs/18/plpgsql.html\" title=\"Chapter 41. PL/pgSQL — SQL Procedural Language\"\u003ePL/pgSQL\u003c/a\u003e (Pavel Stehule) \u003ca href=\"https://postgr.es/c/246dedc5d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eWe previously only accepted \u003ccode\u003e:=\u003c/code\u003e.\u003c/p\u003e","id":"18.0-d96ba464f44620eb","identity_text":"Allow =\u003e syntax for named cursor arguments in PL/pgSQL (Pavel Stehule) We previously only accepted :=.","part":"changes","patch_ids":["93da3674645c806399e4a7258ccd3d35"],"related_changes":[],"relations":[],"section":"Functions","section_path":["Functions"],"source_commits":["246dedc5d"],"source_entry_id":"18.0/changes/115","source_hash":"0d96d209799c5f086a10c64775cb42339b3d437dcb75d4c0b0d7ca78d9aa678e","source_url":"/docs/release/18.0/#RELEASE-18-FUNCTIONS","statement_hash":"add7c95473de1dd4a0566aaf8254da83d00c65a5719b19d40aa9c92d4001cd1c","text":"Allow =\u003e syntax for named cursor arguments in PL/pgSQL (Pavel Stehule) § We previously only accepted :=.","title":"Allow =\u003e syntax for named cursor arguments in PL/pgSQL","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["580f8727c"],"commit_groups":[["580f8727c"]],"commits":["580f8727c"],"cves":[],"db_id":"325c0a35a7406d298611bb6828289ff0","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/functions-matching.html#FUNCTIONS-POSIX-REGEXP\" title=\"9.7.3. POSIX Regular Expressions\"\u003e\u003ccode\u003eregexp_match[es]()\u003c/code\u003e\u003c/a\u003e/\u003ca href=\"/docs/18/functions-matching.html#FUNCTIONS-POSIX-REGEXP\" title=\"9.7.3. POSIX Regular Expressions\"\u003e\u003ccode\u003eregexp_like()\u003c/code\u003e\u003c/a\u003e/\u003ca href=\"/docs/18/functions-matching.html#FUNCTIONS-POSIX-REGEXP\" title=\"9.7.3. POSIX Regular Expressions\"\u003e\u003ccode\u003eregexp_replace()\u003c/code\u003e\u003c/a\u003e/\u003ca href=\"/docs/18/functions-matching.html#FUNCTIONS-POSIX-REGEXP\" title=\"9.7.3. POSIX Regular Expressions\"\u003e\u003ccode\u003eregexp_count()\u003c/code\u003e\u003c/a\u003e/\u003ca href=\"/docs/18/functions-matching.html#FUNCTIONS-POSIX-REGEXP\" title=\"9.7.3. POSIX Regular Expressions\"\u003e\u003ccode\u003eregexp_instr()\u003c/code\u003e\u003c/a\u003e/\u003ca href=\"/docs/18/functions-matching.html#FUNCTIONS-POSIX-REGEXP\" title=\"9.7.3. POSIX Regular Expressions\"\u003e\u003ccode\u003eregexp_substr()\u003c/code\u003e\u003c/a\u003e/\u003ca href=\"/docs/18/functions-matching.html#FUNCTIONS-POSIX-REGEXP\" title=\"9.7.3. POSIX Regular Expressions\"\u003e\u003ccode\u003eregexp_split_to_table()\u003c/code\u003e\u003c/a\u003e/\u003ca href=\"/docs/18/functions-matching.html#FUNCTIONS-POSIX-REGEXP\" title=\"9.7.3. POSIX Regular Expressions\"\u003e\u003ccode\u003eregexp_split_to_array()\u003c/code\u003e\u003c/a\u003e to use named arguments (Jian He) \u003ca href=\"https://postgr.es/c/580f8727c\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-0d9be41bbb427c11","identity_text":"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)","part":"changes","patch_ids":["4e22fed07663f7a3f1934e689acb6eaa"],"related_changes":[],"relations":[],"section":"Functions","section_path":["Functions"],"source_commits":["580f8727c"],"source_entry_id":"18.0/changes/116","source_hash":"537f565df3ddb721db2bfe04fb5165619d5ed54a98e5025bf7ebe2594e7ea5fe","source_url":"/docs/release/18.0/#RELEASE-18-FUNCTIONS","statement_hash":"3d7072f71a631c3271d07df2f0b0325b7ae5f4d8f46ea986b04a57acad9a86a3","text":"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) §","title":"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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["cdb6b0fdb"],"commit_groups":[["cdb6b0fdb"]],"commits":["cdb6b0fdb"],"cves":[],"db_id":"4b86d214e32c355a269673a5aa3b2558","html":"\u003cp\u003eAdd function \u003ca href=\"/docs/18/libpq-status.html#LIBPQ-PQFULLPROTOCOLVERSION\"\u003e\u003ccode\u003ePQfullProtocolVersion()\u003c/code\u003e\u003c/a\u003e to report the full, including minor, protocol version number (Jacob Champion, Jelte Fennema-Nio) \u003ca href=\"https://postgr.es/c/cdb6b0fdb\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-0c1a57f2ceb09589","identity_text":"Add function PQfullProtocolVersion() to report the full, including minor, protocol version number (Jacob Champion, Jelte Fennema-Nio)","part":"changes","patch_ids":["52abaad7880c01090a771e4447bc86e2"],"related_changes":[],"relations":[],"section":"Libpq","section_path":["Libpq"],"source_commits":["cdb6b0fdb"],"source_entry_id":"18.0/changes/117","source_hash":"4d15532b628660643127aa6505deec0b8d3a38c80917c9354108c3340c1fd166","source_url":"/docs/release/18.0/#RELEASE-18-LIBPQ","statement_hash":"f9bd22e1e8f83bd582c6d52c403e9b0ef03dbbb8144aeb9364fb4e3225d47d07","text":"Add function PQfullProtocolVersion() to report the full, including minor, protocol version number (Jacob Champion, Jelte Fennema-Nio) §","title":"Add function PQfullProtocolVersion() to report the full, including minor, protocol version number","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["285613c60","507034910"],"commit_groups":[["285613c60"],["507034910"]],"commits":["285613c60","507034910"],"cves":[],"db_id":"324ad8ffd0dc73072b6cae1163bbd895","html":"\u003cp\u003eAdd libpq connection \u003ca href=\"/docs/18/libpq-connect.html#LIBPQ-CONNECT-SSL-MAX-PROTOCOL-VERSION\"\u003eparameters\u003c/a\u003e and \u003ca href=\"/docs/18/libpq-envars.html\" title=\"32.15. Environment Variables\"\u003eenvironment variables\u003c/a\u003e to specify the minimum and maximum acceptable protocol version for connections (Jelte Fennema-Nio) \u003ca href=\"https://postgr.es/c/285613c60\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/507034910\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-93af92d9546daff9","identity_text":"Add libpq connection parameters and environment variables to specify the minimum and maximum acceptable protocol version for connections (Jelte Fennema-Nio)","part":"changes","patch_ids":["534b2c53e2e1a92c27d124b03e588165","75729722b6f7aba5cfb305b2f8099d9d"],"related_changes":[],"relations":[],"section":"Libpq","section_path":["Libpq"],"source_commits":["285613c60","507034910"],"source_entry_id":"18.0/changes/118","source_hash":"dd8e24e0798022c5e49d33b8f037eae94f69ab39a4a885b8b176f5e16dbcf97e","source_url":"/docs/release/18.0/#RELEASE-18-LIBPQ","statement_hash":"5bc66e57f7b5710b779499207adb20134778a80ccd962165684afde348719556","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["0d06a7eac","28a1121fd"],"commit_groups":[["0d06a7eac"],["28a1121fd"]],"commits":["0d06a7eac","28a1121fd"],"cves":[],"db_id":"218352fe6746ce16b55b280a597a34c3","html":"\u003cp\u003eReport \u003ca href=\"/docs/18/runtime-config-client.html#GUC-SEARCH-PATH\"\u003esearch_path\u003c/a\u003e changes to the client (Alexander Kukushkin, Jelte Fennema-Nio, Tomas Vondra) \u003ca href=\"https://postgr.es/c/28a1121fd\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/0d06a7eac\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-207d234a979be0ba","identity_text":"Report guc-search-path changes to the client (Alexander Kukushkin, Jelte Fennema-Nio, Tomas Vondra)","part":"changes","patch_ids":["5ff7e1b21d24cbfadde9ec259d6a73c7","6773d35e5f3a311c7ff50c9c2faf3885"],"related_changes":[],"relations":[],"section":"Libpq","section_path":["Libpq"],"source_commits":["0d06a7eac","28a1121fd"],"source_entry_id":"18.0/changes/119","source_hash":"1b3b66fd3e804bfd9a8f8eb4900833f7becb2d7ae3e27f57d8450450272b7e24","source_url":"/docs/release/18.0/#RELEASE-18-LIBPQ","statement_hash":"50991c451a4bfb5e106b4ba60fe467da4d2e687a547ce099c82004fbe44fd3e9","text":"Report search_path changes to the client (Alexander Kukushkin, Jelte Fennema-Nio, Tomas Vondra) § §","title":"Report search_path changes to the client","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["7adec2d5f","a5c6b8f22","b8b3f861f","e87c14b19","ea92f3a0a"],"commit_groups":[["7adec2d5f"],["a5c6b8f22"],["b8b3f861f"],["e87c14b19"],["ea92f3a0a"]],"commits":["7adec2d5f","a5c6b8f22","b8b3f861f","e87c14b19","ea92f3a0a"],"cves":[],"db_id":"189544d0fbeb310833d8101ad81be81d","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/libpq-control.html#LIBPQ-PQTRACE\"\u003e\u003ccode\u003ePQtrace()\u003c/code\u003e\u003c/a\u003e output for all message types, including authentication (Jelte Fennema-Nio) \u003ca href=\"https://postgr.es/c/ea92f3a0a\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/a5c6b8f22\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/b8b3f861f\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/e87c14b19\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/7adec2d5f\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-beeeaad682b3e543","identity_text":"Add PQtrace() output for all message types, including authentication (Jelte Fennema-Nio)","part":"changes","patch_ids":["7830574fda35c2cd540f06ea5cd22fe7","acc865fe8e046c03d36dbaf9deafa10e","dccfa75590b5f88a141ec68c6abef022","ef0fcd62d83e5a9752310ce62aa470d2","f1361c9f5c56a8086363704e63d70cd9"],"related_changes":[],"relations":[],"section":"Libpq","section_path":["Libpq"],"source_commits":["7adec2d5f","a5c6b8f22","b8b3f861f","e87c14b19","ea92f3a0a"],"source_entry_id":"18.0/changes/120","source_hash":"229bf64e1d8e766cd4a7b64992dd7057c31c49ee08a766d973f0fed3a3136264","source_url":"/docs/release/18.0/#RELEASE-18-LIBPQ","statement_hash":"c5e10674404ba12ef5a21f94c4df6e89c062cf8daae10222475b36a39dda6485","text":"Add PQtrace() output for all message types, including authentication (Jelte Fennema-Nio) § § § § §","title":"Add PQtrace() output for all message types, including authentication","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["2da74d8d6"],"commit_groups":[["2da74d8d6"]],"commits":["2da74d8d6"],"cves":[],"db_id":"dec95e8329f62b657fc15ccfb7d006fb","html":"\u003cp\u003eAdd libpq connection parameter \u003ca href=\"/docs/18/libpq-connect.html#LIBPQ-CONNECT-SSLKEYLOGFILE\"\u003e\u003ccode\u003esslkeylogfile\u003c/code\u003e\u003c/a\u003e which dumps out \u003cacronym\u003eSSL\u003c/acronym\u003e key material (Abhishek Chanda, Daniel Gustafsson) \u003ca href=\"https://postgr.es/c/2da74d8d6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is useful for debugging.\u003c/p\u003e","id":"18.0-ef7c9ed7c8f229dc","identity_text":"Add libpq connection parameter sslkeylogfile which dumps out SSL key material (Abhishek Chanda, Daniel Gustafsson) This is useful for debugging.","part":"changes","patch_ids":["5c9abb135b2e6fb82671370102be25d3"],"related_changes":[],"relations":[],"section":"Libpq","section_path":["Libpq"],"source_commits":["2da74d8d6"],"source_entry_id":"18.0/changes/121","source_hash":"8a53c283c907184c5c28dc8b1a80814c955c04574c96f11e2d4b6d6ad07852f9","source_url":"/docs/release/18.0/#RELEASE-18-LIBPQ","statement_hash":"0cbbb246f331bdcf188172740da0fa02fe152d60204197e426ec23a6c89278c5","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["3c86223c9"],"commit_groups":[["3c86223c9"]],"commits":["3c86223c9"],"cves":[],"db_id":"caaca0ad82471ba571571208f6771f02","html":"\u003cp\u003eModify some libpq function signatures to use \u003ccode\u003eint64_t\u003c/code\u003e (Thomas Munro) \u003ca href=\"https://postgr.es/c/3c86223c9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese previously used \u003ccode\u003epg_int64\u003c/code\u003e, which is now deprecated.\u003c/p\u003e","id":"18.0-f56e310a693fee70","identity_text":"Modify some libpq function signatures to use int64_t (Thomas Munro) These previously used pg_int64, which is now deprecated.","part":"changes","patch_ids":["a9a13dc006668f08f5abd06bcf09cb8e"],"related_changes":[],"relations":[],"section":"Libpq","section_path":["Libpq"],"source_commits":["3c86223c9"],"source_entry_id":"18.0/changes/122","source_hash":"10b871bad097417a99cafa49cc3d5d1c211c6de4e2bf8386fbbde08d3facb504","source_url":"/docs/release/18.0/#RELEASE-18-LIBPQ","statement_hash":"325b9ac281e658a1f6acd0aaae59a7c20882f4f76754cbd9cd6c886266e8b478","text":"Modify some libpq function signatures to use int64_t (Thomas Munro) § These previously used pg_int64, which is now deprecated.","title":"Modify some libpq function signatures to use int64_t","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["d55322b0d","fc39b286a"],"commit_groups":[["d55322b0d"],["fc39b286a"]],"commits":["d55322b0d","fc39b286a"],"cves":[],"db_id":"f1f07070c0f9905a1dadadaf792aeb8f","html":"\u003cp\u003eAllow \u003cspan\u003epsql\u003c/span\u003e to parse, bind, and close named prepared statements (Anthonin Bonnefoy, Michael Paquier) \u003ca href=\"https://postgr.es/c/d55322b0d\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/fc39b286a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is accomplished with new commands \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-META-COMMAND-PARSE\"\u003e\u003ccode\u003e\\parse\u003c/code\u003e\u003c/a\u003e, \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-META-COMMAND-BIND-NAMED\"\u003e\u003ccode\u003e\\bind_named\u003c/code\u003e\u003c/a\u003e, and \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-META-COMMAND-CLOSE-PREPARED\"\u003e\u003ccode\u003e\\close_prepared\u003c/code\u003e\u003c/a\u003e.\u003c/p\u003e","id":"18.0-2fb6e0f0c8f9dca8","identity_text":"Allow psql to parse, bind, and close named prepared statements (Anthonin Bonnefoy, Michael Paquier) This is accomplished with new commands \\parse, \\bind_named, and \\close_prepared.","part":"changes","patch_ids":["c1a58c5c685a3ecbf2a745226578758a","df70e0fc8c75d8b781d59c4c9c988dc2"],"related_changes":[],"relations":[],"section":"psql","section_path":["psql"],"source_commits":["d55322b0d","fc39b286a"],"source_entry_id":"18.0/changes/123","source_hash":"77c05c6a0c7eefaa3828f25811f82a7b7e8197f14e6b0b3ca40906780cc67c8a","source_url":"/docs/release/18.0/#RELEASE-18-PSQL","statement_hash":"d69eda95d2e3f3d9d78e8def9469297aa5914f6c8b5405798b94e5847ef4218e","text":"Allow psql to parse, bind, and close named prepared statements (Anthonin Bonnefoy, Michael Paquier) § § This is accomplished with new commands \\parse, \\bind_named, and \\close_prepared.","title":"Allow psql to parse, bind, and close named prepared statements","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["17caf6644","2cce0fe44","41625ab8e"],"commit_groups":[["17caf6644"],["2cce0fe44"],["41625ab8e"]],"commits":["17caf6644","2cce0fe44","41625ab8e"],"cves":[],"db_id":"4d5f486511455c18c068b6488465fe4d","html":"\u003cp\u003eAdd \u003cspan\u003epsql\u003c/span\u003e backslash commands to allowing issuance of pipeline queries (Anthonin Bonnefoy) \u003ca href=\"https://postgr.es/c/41625ab8e\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/17caf6644\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/2cce0fe44\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe new commands are \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-META-COMMAND-PIPELINE\"\u003e\u003ccode\u003e\\startpipeline\u003c/code\u003e\u003c/a\u003e, \u003ccode\u003e\\syncpipeline\u003c/code\u003e, \u003ccode\u003e\\sendpipeline\u003c/code\u003e, \u003ccode\u003e\\endpipeline\u003c/code\u003e, \u003ccode\u003e\\flushrequest\u003c/code\u003e, \u003ccode\u003e\\flush\u003c/code\u003e, and \u003ccode\u003e\\getresults\u003c/code\u003e.\u003c/p\u003e","id":"18.0-6aeeef1ea176f829","identity_text":"Add psql backslash commands to allowing issuance of pipeline queries (Anthonin Bonnefoy) The new commands are \\startpipeline, \\syncpipeline, \\sendpipeline, \\endpipeline, \\flushrequest, \\flush, and \\getresults.","part":"changes","patch_ids":["35ac484ccee3ad9012651c9ebb417256","70e78ced9a8ba8366255b2db649c9893","df86acd976c7a1bed1bc2ab4cb1192c0"],"related_changes":[],"relations":[],"section":"psql","section_path":["psql"],"source_commits":["17caf6644","2cce0fe44","41625ab8e"],"source_entry_id":"18.0/changes/124","source_hash":"065c75020e0a2e7dcbb2190d382fe267753aec2fed22e926ae12b843cc277e62","source_url":"/docs/release/18.0/#RELEASE-18-PSQL","statement_hash":"7a3ae596d3038107a6c2878a16eef9d8d6e31e6830e8ad4070210e11705433d7","text":"Add psql backslash commands to allowing issuance of pipeline queries (Anthonin Bonnefoy) § § § The new commands are \\startpipeline, \\syncpipeline, \\sendpipeline, \\endpipeline, \\flushrequest, \\flush, and \\getresults.","title":"Add psql backslash commands to allowing issuance of pipeline queries","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["3ce357584"],"commit_groups":[["3ce357584"]],"commits":["3ce357584"],"cves":[],"db_id":"95d64c85bbb64cccbeaed6eff0e1a423","html":"\u003cp\u003eAllow adding pipeline status to the \u003cspan\u003epsql\u003c/span\u003e prompt and add related state variables (Anthonin Bonnefoy) \u003ca href=\"https://postgr.es/c/3ce357584\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe new prompt character is \u003ccode\u003e%P\u003c/code\u003e and the new \u003cspan\u003epsql\u003c/span\u003e variables are \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-VARIABLES-PIPELINE-SYNC-COUNT\"\u003e\u003ccode\u003ePIPELINE_SYNC_COUNT\u003c/code\u003e\u003c/a\u003e, \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-VARIABLES-PIPELINE-COMMAND-COUNT\"\u003e\u003ccode\u003ePIPELINE_COMMAND_COUNT\u003c/code\u003e\u003c/a\u003e, and \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-VARIABLES-PIPELINE-RESULT-COUNT\"\u003e\u003ccode\u003ePIPELINE_RESULT_COUNT\u003c/code\u003e\u003c/a\u003e.\u003c/p\u003e","id":"18.0-02580f08fbaf6131","identity_text":"Allow adding pipeline status to the psql prompt and add related state variables (Anthonin Bonnefoy) The new prompt character is %P and the new psql variables are PIPELINE_SYNC_COUNT, PIPELINE_COMMAND_COUNT, and PIPELINE_RESULT_COUNT.","part":"changes","patch_ids":["062ee32471ba9950e13d9460b1c630ed"],"related_changes":[],"relations":[],"section":"psql","section_path":["psql"],"source_commits":["3ce357584"],"source_entry_id":"18.0/changes/125","source_hash":"ca4d56dd83a7e4b6224510acf54f1d3175534f96e58fb840e6f282c967477b87","source_url":"/docs/release/18.0/#RELEASE-18-PSQL","statement_hash":"342de8131124813468934a1a6a5b420c312c79e1aba97898e6a94db6850a206c","text":"Allow adding pipeline status to the psql prompt and add related state variables (Anthonin Bonnefoy) § The new prompt character is %P and the new psql variables are PIPELINE_SYNC_COUNT, PIPELINE_COMMAND_COUNT, and PIPELINE_RESULT_COUNT.","title":"Allow adding pipeline status to the psql prompt and add related state variables","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["477728b5d"],"commit_groups":[["477728b5d"]],"commits":["477728b5d"],"cves":[],"db_id":"b448890a42701668cc28db2c98fe65af","html":"\u003cp\u003eAllow adding the connection service name to the \u003cspan\u003epsql\u003c/span\u003e prompt or access it via \u003cspan\u003epsql\u003c/span\u003e variable (Michael Banck) \u003ca href=\"https://postgr.es/c/477728b5d\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-997c75493a7de85c","identity_text":"Allow adding the connection service name to the psql prompt or access it via psql variable (Michael Banck)","part":"changes","patch_ids":["8bc6eb53f480b1773dba3d9ca6fa27ef"],"related_changes":[],"relations":[],"section":"psql","section_path":["psql"],"source_commits":["477728b5d"],"source_entry_id":"18.0/changes/126","source_hash":"d708d70528e3a3f746395fa23b8324b7dfe19e3fa2560f0d3fb61d86a8f4af8b","source_url":"/docs/release/18.0/#RELEASE-18-PSQL","statement_hash":"b7b84052ccad3b3cdd4e58fd81d7e92d01dcd30e03a638017f02df36fe51481c","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["00f4c2959"],"commit_groups":[["00f4c2959"]],"commits":["00f4c2959"],"cves":[],"db_id":"5dd3f4378c9385065373f9512386183d","html":"\u003cp\u003eAdd \u003cspan\u003epsql\u003c/span\u003e option to use expanded mode on all list commands (Dean Rasheed) \u003ca href=\"https://postgr.es/c/00f4c2959\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAdding backslash suffix \u003ccode\u003ex\u003c/code\u003e enables this.\u003c/p\u003e","id":"18.0-b431886faffda5ff","identity_text":"Add psql option to use expanded mode on all list commands (Dean Rasheed) Adding backslash suffix x enables this.","part":"changes","patch_ids":["2a6f4ded65d281267015b5b6cc939f54"],"related_changes":[],"relations":[],"section":"psql","section_path":["psql"],"source_commits":["00f4c2959"],"source_entry_id":"18.0/changes/127","source_hash":"c295ed9ac299dc91d03e266119cfa5c422c1056a964c2bf9bb936427b8c2d1a3","source_url":"/docs/release/18.0/#RELEASE-18-PSQL","statement_hash":"67f72ef9ab6c8e1c087e265379fba0355acb6aaf4ebf846ec3f223d08f73af6e","text":"Add psql option to use expanded mode on all list commands (Dean Rasheed) § Adding backslash suffix x enables this.","title":"Add psql option to use expanded mode on all list commands","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["bba2fbc62"],"commit_groups":[["bba2fbc62"]],"commits":["bba2fbc62"],"cves":[],"db_id":"b7756586e365c7157c475c0430299268","html":"\u003cp\u003eChange \u003cspan\u003epsql\u003c/span\u003e's \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-META-COMMAND-CONNINFO\"\u003e\u003ccode\u003e\\conninfo\u003c/code\u003e\u003c/a\u003e to use tabular format and include more information (Álvaro Herrera, Maiquel Grassi, Hunaid Sohail) \u003ca href=\"https://postgr.es/c/bba2fbc62\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-8984d4a06e8e1c29","identity_text":"Change psql's app-psql-meta-command-conninfo to use tabular format and include more information (Álvaro Herrera, Maiquel Grassi, Hunaid Sohail)","part":"changes","patch_ids":["8d29126a5a016ba3aa3ac63ed17eed9e"],"related_changes":[],"relations":[],"section":"psql","section_path":["psql"],"source_commits":["bba2fbc62"],"source_entry_id":"18.0/changes/128","source_hash":"f50ab465a0ba201803a8cb40aac06c8f854c661fbc6959a15809b50060959f8c","source_url":"/docs/release/18.0/#RELEASE-18-PSQL","statement_hash":"587565e7970af826aba72167bdd2c90fa3ad561d7bdffc95a3fdf5db3e7a9af2","text":"Change psql's \\conninfo to use tabular format and include more information (Álvaro Herrera, Maiquel Grassi, Hunaid Sohail) §","title":"Change psql's \\conninfo to use tabular format and include more information","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["2355e5111"],"commit_groups":[["2355e5111"]],"commits":["2355e5111"],"cves":[],"db_id":"9d578cae753a7068d3a2429369a138e4","html":"\u003cp\u003eAdd function's leakproof indicator to \u003cspan\u003epsql\u003c/span\u003e's \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-META-COMMAND-DF-LC\"\u003e\u003ccode\u003e\\df+\u003c/code\u003e\u003c/a\u003e, \u003ccode\u003e\\do+\u003c/code\u003e, \u003ccode\u003e\\dAo+\u003c/code\u003e, and \u003ccode\u003e\\dC+\u003c/code\u003e outputs (Yugo Nagata) \u003ca href=\"https://postgr.es/c/2355e5111\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-624508557749474f","identity_text":"Add function's leakproof indicator to psql's \\df+, \\do+, \\dAo+, and \\dC+ outputs (Yugo Nagata)","part":"changes","patch_ids":["4ee947bb08aead676fe72b63526cdd39"],"related_changes":[],"relations":[],"section":"psql","section_path":["psql"],"source_commits":["2355e5111"],"source_entry_id":"18.0/changes/129","source_hash":"b8a6c1bf50c01dfea7e893090f16b02f8a9b074d135f06979cf7e11861937d9b","source_url":"/docs/release/18.0/#RELEASE-18-PSQL","statement_hash":"b7ecafc8df9220ee7d63778ed0ac8ad0e28546694bb5fdbba0ac97017dfbb54d","text":"Add function's leakproof indicator to psql's \\df+, \\do+, \\dAo+, and \\dC+ outputs (Yugo Nagata) §","title":"Add function's leakproof indicator to psql's \\df+, \\do+, \\dAo+, and \\dC+ outputs","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["978f38c77"],"commit_groups":[["978f38c77"]],"commits":["978f38c77"],"cves":[],"db_id":"818c7f68713a76e08678870d759f6291","html":"\u003cp\u003eAdd access method details for partitioned relations in \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-META-COMMAND-DP-UC\"\u003e\u003ccode\u003e\\dP+\u003c/code\u003e\u003c/a\u003e (Justin Pryzby) \u003ca href=\"https://postgr.es/c/978f38c77\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-1dea4d8870fe7263","identity_text":"Add access method details for partitioned relations in \\dP+ (Justin Pryzby)","part":"changes","patch_ids":["7cca4f5d69bc8dc6d2b6ccbaa33d8e79"],"related_changes":[],"relations":[],"section":"psql","section_path":["psql"],"source_commits":["978f38c77"],"source_entry_id":"18.0/changes/130","source_hash":"513f2fab8dea574eba77472892d2f8de48560874d9a7182acc43f2b25404614a","source_url":"/docs/release/18.0/#RELEASE-18-PSQL","statement_hash":"3ab40daca3f13039aba595247e60f46d4f6453febeb29ab79a875c6f98986293","text":"Add access method details for partitioned relations in \\dP+ (Justin Pryzby) §","title":"Add access method details for partitioned relations in \\dP+","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["d696406a9"],"commit_groups":[["d696406a9"]],"commits":["d696406a9"],"cves":[],"db_id":"8b0be23bf885cc5302c60d810f5e5d17","html":"\u003cp\u003eAdd \u003ccode\u003edefault_version\u003c/code\u003e to the \u003cspan\u003epsql\u003c/span\u003e \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-META-COMMAND-DX-LC\"\u003e\u003ccode\u003e\\dx\u003c/code\u003e\u003c/a\u003e extension output (Magnus Hagander) \u003ca href=\"https://postgr.es/c/d696406a9\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-545b1beb3150fb2a","identity_text":"Add default_version to the psql \\dx extension output (Magnus Hagander)","part":"changes","patch_ids":["a177f1929edb0edaa402f9aa8c4dc5b1"],"related_changes":[],"relations":[],"section":"psql","section_path":["psql"],"source_commits":["d696406a9"],"source_entry_id":"18.0/changes/131","source_hash":"f45ef00d2add84d90c55cbbc7e9938ca51f52bbcc6c24082fda3375e868a6ff4","source_url":"/docs/release/18.0/#RELEASE-18-PSQL","statement_hash":"97eb7c8a5e03d2311600a2472cb9936526e73dfb492e20a800a6b6068c604820","text":"Add default_version to the psql \\dx extension output (Magnus Hagander) §","title":"Add default_version to the psql \\dx extension output","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["1a759c832"],"commit_groups":[["1a759c832"]],"commits":["1a759c832"],"cves":[],"db_id":"fb9188646ca6019ee7d68115e98063b7","html":"\u003cp\u003eAdd \u003cspan\u003epsql\u003c/span\u003e variable \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-VARIABLES-WATCH-INTERVAL\"\u003e\u003ccode\u003eWATCH_INTERVAL\u003c/code\u003e\u003c/a\u003e to set the default \u003ca href=\"/docs/18/app-psql.html#APP-PSQL-META-COMMAND-WATCH\"\u003e\u003ccode\u003e\\watch\u003c/code\u003e\u003c/a\u003e wait time (Daniel Gustafsson) \u003ca href=\"https://postgr.es/c/1a759c832\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-dc2d98bde772ded1","identity_text":"Add psql variable app-psql-variables-watch-interval to set the default \\watch wait time (Daniel Gustafsson)","part":"changes","patch_ids":["f4150999ddde237444a665e7664bb364"],"related_changes":[],"relations":[],"section":"psql","section_path":["psql"],"source_commits":["1a759c832"],"source_entry_id":"18.0/changes/132","source_hash":"32dbe7ae008210a57ddbd29b951551fca0c360487d239b82a521420aff9d9aca","source_url":"/docs/release/18.0/#RELEASE-18-PSQL","statement_hash":"e31ae7e017e542c379f3fad9f44583ecacf3b7e2e1c7156a171e1ba5b89e91cd","text":"Add psql variable WATCH_INTERVAL to set the default \\watch wait time (Daniel Gustafsson) §","title":"Add psql variable WATCH_INTERVAL to set the default \\watch wait time","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["04bec894a","983a588e0"],"commit_groups":[["04bec894a"],["983a588e0"]],"commits":["04bec894a","983a588e0"],"cves":[],"db_id":"db70c584fb64d9f59231adb14744b4a2","html":"\u003cp\u003eChange \u003ca href=\"/docs/18/app-initdb.html\" title=\"initdb\"\u003e\u003cspan\u003e\u003cspan\u003einitdb\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e to default to enabling checksums (Greg Sabino Mullane) \u003ca href=\"https://postgr.es/c/983a588e0\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/04bec894a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe new \u003cspan\u003einitdb\u003c/span\u003e option \u003ccode\u003e--no-data-checksums\u003c/code\u003e disables checksums.\u003c/p\u003e","id":"18.0-d9b49042b8f09224","identity_text":"Change app-initdb to default to enabling checksums (Greg Sabino Mullane) The new initdb option --no-data-checksums disables checksums.","part":"changes","patch_ids":["2f0b053af829369c3e773971e514dfc9","f78286ddb1f2e6833c76c4a8351542bf"],"related_changes":[{"db_id":"f3c7465886914cc33d3dae8014f0ac38","evidence":{"patch_ids":["f78286ddb1f2e6833c76c4a8351542bf"],"same_day":true},"kind":"related","label":"18.0","source_url":"/docs/release/18.0/#RELEASE-18-MIGRATION","title":"Change initdb default to enable data checksums","url":"/docs/compare/?release=18.0#18.0-a8fa82432892119f","version":"18.0"}],"relations":[{"evidence":{"patch_ids":["f78286ddb1f2e6833c76c4a8351542bf"],"same_day":true},"rule":2,"target":"f3c7465886914cc33d3dae8014f0ac38","type":"related"}],"section":"Server Applications","section_path":["Server Applications"],"source_commits":["04bec894a","983a588e0"],"source_entry_id":"18.0/changes/133","source_hash":"f8f34e3e2ad1f1316678e49b712c445e3ddd519b898c474e581fdfa668983b8c","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-APPS","statement_hash":"a04cf4bcb0a1f1804333415522f466bd804eca240f36149cdbd72bcb10c51e82","text":"Change initdb to default to enabling checksums (Greg Sabino Mullane) § § The new initdb option --no-data-checksums disables checksums.","title":"Change initdb to default to enabling checksums","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["cf131fa94"],"commit_groups":[["cf131fa94"]],"commits":["cf131fa94"],"cves":[],"db_id":"9952d39dc06228d3a10d17bc3b5169fe","html":"\u003cp\u003eAdd \u003cspan\u003einitdb\u003c/span\u003e option \u003ccode\u003e--no-sync-data-files\u003c/code\u003e to avoid syncing heap/index files (Nathan Bossart) \u003ca href=\"https://postgr.es/c/cf131fa94\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003einitdb\u003c/span\u003e option \u003ccode\u003e--no-sync\u003c/code\u003e is still available to avoid syncing any files.\u003c/p\u003e","id":"18.0-3aa4f5ae30376479","identity_text":"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.","part":"changes","patch_ids":["4e1d69b6c246228bc290d1f93422d624"],"related_changes":[],"relations":[],"section":"Server Applications","section_path":["Server Applications"],"source_commits":["cf131fa94"],"source_entry_id":"18.0/changes/134","source_hash":"75c8f0bdfad04f0d23cb26c70c1ac8035b373f8861476b487902137fb7226355","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-APPS","statement_hash":"7713e4c4118e732a811941c3e11d09cec1b024f960b3b7998b6b19a60f3f83ca","text":"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.","title":"Add initdb option --no-sync-data-files to avoid syncing heap/index files","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["987910502","edba754f0"],"commit_groups":[["987910502"],["edba754f0"]],"commits":["987910502","edba754f0"],"cves":[],"db_id":"853076317df1e045ebd45b56522f230a","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/app-vacuumdb.html\" title=\"vacuumdb\"\u003e\u003cspan\u003e\u003cspan\u003evacuumdb\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e option \u003ccode\u003e--missing-stats-only\u003c/code\u003e to compute only missing optimizer statistics (Corey Huinker, Nathan Bossart) \u003ca href=\"https://postgr.es/c/edba754f0\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/987910502\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis option can only be run by superusers and can only be used with options \u003ccode\u003e--analyze-only\u003c/code\u003e and \u003ccode\u003e--analyze-in-stages\u003c/code\u003e.\u003c/p\u003e","id":"18.0-7e9d4c0fc2dfb35a","identity_text":"Add app-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.","part":"changes","patch_ids":["067aff8cba670576fe0c3fd89d649257","b94a1cae6980cfb5f7ef4424d00fcb6a"],"related_changes":[],"relations":[],"section":"Server Applications","section_path":["Server Applications"],"source_commits":["987910502","edba754f0"],"source_entry_id":"18.0/changes/135","source_hash":"1199d1c1b8dd6304d46f2f0be670b1746b4d32ede3679f66ba9258fcc89c8330","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-APPS","statement_hash":"5385ca51a2d01858906e995b4406bf1ef97d31883665cc58aae33e348c5b9490","text":"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.","title":"Add vacuumdb option --missing-stats-only to compute only missing optimizer statistics","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["99aeb8470"],"commit_groups":[["99aeb8470"]],"commits":["99aeb8470"],"cves":[],"db_id":"cbac9921cfb2186e54629d635e3729f3","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/app-pgcombinebackup.html\" title=\"pg_combinebackup\"\u003e\u003cspan\u003e\u003cspan\u003epg_combinebackup\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e option \u003ccode\u003e-k\u003c/code\u003e/\u003ccode\u003e--link\u003c/code\u003e to enable hard linking (Israel Barth Rubio, Robert Haas) \u003ca href=\"https://postgr.es/c/99aeb8470\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eOnly some files can be hard linked. This should not be used if the backups will be used independently.\u003c/p\u003e","id":"18.0-d07e626cfc87cc2d","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.","part":"changes","patch_ids":["b2774e6278fb43524469fa415bf7c504"],"related_changes":[],"relations":[],"section":"Server Applications","section_path":["Server Applications"],"source_commits":["99aeb8470"],"source_entry_id":"18.0/changes/136","source_hash":"eefef01cb696f44d91b49f7817d447e5f2b2aeac8ca97a0513d80a36ce3eab22","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-APPS","statement_hash":"5736af1019c3d5e2bd2ae443e4a9261637afca5e0e0ff655d599e24adaf4ea01","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["8dfd31290"],"commit_groups":[["8dfd31290"]],"commits":["8dfd31290"],"cves":[],"db_id":"4a31265bb9d301899f61cbb72dc938fe","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/app-pgverifybackup.html\" title=\"pg_verifybackup\"\u003e\u003cspan\u003e\u003cspan\u003epg_verifybackup\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e to verify tar-format backups (Amul Sul) \u003ca href=\"https://postgr.es/c/8dfd31290\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-75fede038d668a8d","identity_text":"Allow app-pgverifybackup to verify tar-format backups (Amul Sul)","part":"changes","patch_ids":["f61db0ff36a5aaba1fefc4551593c41a"],"related_changes":[],"relations":[],"section":"Server Applications","section_path":["Server Applications"],"source_commits":["8dfd31290"],"source_entry_id":"18.0/changes/137","source_hash":"e2b0d86a1a6fe34a3eaef7656a3093c8fef2bcf4bb4045b3b394c42b6e595297","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-APPS","statement_hash":"033fcbd8882efc5f140f40a57fd1009957f6354e0fff3b3c07f05be1d2c1ce01","text":"Allow pg_verifybackup to verify tar-format backups (Amul Sul) §","title":"Allow pg_verifybackup to verify tar-format backups","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4ecdd4110"],"commit_groups":[["4ecdd4110"]],"commits":["4ecdd4110"],"cves":[],"db_id":"31e83eaf955dc5094a8982493afd63f3","html":"\u003cp\u003eIf \u003ca href=\"/docs/18/app-pgrewind.html\" title=\"pg_rewind\"\u003e\u003cspan\u003e\u003cspan\u003epg_rewind\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e's \u003ccode\u003e--source-server\u003c/code\u003e specifies a database name, use it in \u003ccode\u003e--write-recovery-conf\u003c/code\u003e output (Masahiko Sawada) \u003ca href=\"https://postgr.es/c/4ecdd4110\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-f775ed91253ae2a7","identity_text":"If app-pgrewind 's --source-server specifies a database name, use it in --write-recovery-conf output (Masahiko Sawada)","part":"changes","patch_ids":["422026f71813c5ab788723a75cfa5fd6"],"related_changes":[],"relations":[],"section":"Server Applications","section_path":["Server Applications"],"source_commits":["4ecdd4110"],"source_entry_id":"18.0/changes/138","source_hash":"b8e56e6ae6588f2cb4df8056eac8508fcaa1a7d5c2bed9b03e0c9c7c3fa92317","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-APPS","statement_hash":"85b876a7486c3a65c5a92598f9e9b5dad71b32bdd0c7932389bfbfb0fdef6adc","text":"If pg_rewind's --source-server specifies a database name, use it in --write-recovery-conf output (Masahiko Sawada) §","title":"If pg_rewind's --source-server specifies a database name, use it in --write-recovery-conf output","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["30666d185"],"commit_groups":[["30666d185"]],"commits":["30666d185"],"cves":[],"db_id":"de60efb8b41468fb0459eaacd7e58849","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/app-pgresetwal.html\" title=\"pg_resetwal\"\u003e\u003cspan\u003e\u003cspan\u003epg_resetwal\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e option \u003ccode\u003e--char-signedness\u003c/code\u003e to change the default \u003ccode\u003echar\u003c/code\u003e signedness (Masahiko Sawada) \u003ca href=\"https://postgr.es/c/30666d185\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-915172048ef89595","identity_text":"Add app-pgresetwal option --char-signedness to change the default char signedness (Masahiko Sawada)","part":"changes","patch_ids":["5f6d5be1745e81fcdc6e9b19df0c805d"],"related_changes":[],"relations":[],"section":"Server Applications","section_path":["Server Applications"],"source_commits":["30666d185"],"source_entry_id":"18.0/changes/139","source_hash":"1109968f9e43b45953a526f184648d85db28b47d688f491e1bf329b1223e6a82","source_url":"/docs/release/18.0/#RELEASE-18-SERVER-APPS","statement_hash":"2e2828b91010abfb7434c834860be467a228d211bd371f7f730efd531fd3e713","text":"Add pg_resetwal option --char-signedness to change the default char signedness (Masahiko Sawada) §","title":"Add pg_resetwal option --char-signedness to change the default char signedness","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["a3e8dc143","bde2fb797"],"commit_groups":[["a3e8dc143"],["bde2fb797"]],"commits":["a3e8dc143","bde2fb797"],"cves":[],"db_id":"45377d9a7cbb5f6d8a91743818fe9f95","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/app-pgdump.html\" title=\"pg_dump\"\u003e\u003cspan\u003e\u003cspan\u003epg_dump\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e option \u003ccode\u003e--statistics\u003c/code\u003e (Jeff Davis) \u003ca href=\"https://postgr.es/c/bde2fb797\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/a3e8dc143\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-9b8052d9682b1054","identity_text":"Add app-pgdump option --statistics (Jeff Davis)","part":"changes","patch_ids":["0b036a7b9a6fe69f0ae3fc14f07f890e","3403ebf99c25408505f5bbc915ea6a92"],"related_changes":[],"relations":[],"section":"Server Applications / pg_dump/pg_dumpall/pg_restore","section_path":["Server Applications","pg_dump/pg_dumpall/pg_restore"],"source_commits":["a3e8dc143","bde2fb797"],"source_entry_id":"18.0/changes/140","source_hash":"2d3d93b82ef664b1f0244b7e43fe05588854ab0ca7c11011f7a607d3ee6c90d6","source_url":"/docs/release/18.0/#RELEASE-18-PGDUMP","statement_hash":"d940022b9100e359cdd29574a6c0b6d758a89af40770a693ddc3a5b2232c1974","text":"Add pg_dump option --statistics (Jeff Davis) § §","title":"Add pg_dump option --statistics","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["9c49f0e8c","acea3fc49"],"commit_groups":[["9c49f0e8c"],["acea3fc49"]],"commits":["9c49f0e8c","acea3fc49"],"cves":[],"db_id":"57dfabc21cb09eee80237e7dbdeb4cfd","html":"\u003cp\u003eAdd \u003cspan\u003epg_dump\u003c/span\u003e and \u003ca href=\"/docs/18/app-pg-dumpall.html\" title=\"pg_dumpall\"\u003e\u003cspan\u003e\u003cspan\u003epg_dumpall\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e option \u003ccode\u003e--sequence-data\u003c/code\u003e to dump sequence data that would normally be excluded (Nathan Bossart) \u003ca href=\"https://postgr.es/c/9c49f0e8c\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/acea3fc49\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-2543385556630458","identity_text":"Add pg_dump and app-pg-dumpall option --sequence-data to dump sequence data that would normally be excluded (Nathan Bossart)","part":"changes","patch_ids":["ce7a77b9bb38b32190aa243f00af6062","d4543602d88dfc88e50236d446d2d446"],"related_changes":[],"relations":[],"section":"Server Applications / pg_dump/pg_dumpall/pg_restore","section_path":["Server Applications","pg_dump/pg_dumpall/pg_restore"],"source_commits":["9c49f0e8c","acea3fc49"],"source_entry_id":"18.0/changes/141","source_hash":"4424f6df2367d695a36039440ad3354cad22e464adf6623f4a6ab6f11550ed11","source_url":"/docs/release/18.0/#RELEASE-18-PGDUMP","statement_hash":"f73184a2cfa206e9f7b47760836ce121d8a19c8db2af75e1831a8c988cc8e7fe","text":"Add pg_dump and pg_dumpall option --sequence-data to dump sequence data that would normally be excluded (Nathan Bossart) § §","title":"Add pg_dump and pg_dumpall option --sequence-data to dump sequence data that would normally be excluded","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["1fd1bd871"],"commit_groups":[["1fd1bd871"]],"commits":["1fd1bd871"],"cves":[],"db_id":"8d5b8469bade89e9c1af7e30be1f4707","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/app-pgdump.html\" title=\"pg_dump\"\u003e\u003cspan\u003e\u003cspan\u003epg_dump\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e, \u003ca href=\"/docs/18/app-pg-dumpall.html\" title=\"pg_dumpall\"\u003e\u003cspan\u003e\u003cspan\u003epg_dumpall\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e, and \u003ca href=\"/docs/18/app-pgrestore.html\" title=\"pg_restore\"\u003e\u003cspan\u003e\u003cspan\u003epg_restore\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e options \u003ccode\u003e--statistics-only\u003c/code\u003e, \u003ccode\u003e--no-statistics\u003c/code\u003e, \u003ccode\u003e--no-data\u003c/code\u003e, and \u003ccode\u003e--no-schema\u003c/code\u003e (Corey Huinker, Jeff Davis) \u003ca href=\"https://postgr.es/c/1fd1bd871\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-1c7cab16e2b0faec","identity_text":"Add app-pgdump , app-pg-dumpall , and app-pgrestore options --statistics-only, --no-statistics, --no-data, and --no-schema (Corey Huinker, Jeff Davis)","part":"changes","patch_ids":["5d0cb3cccce1158170d1cd02ebb43757"],"related_changes":[{"db_id":"afbfe0f474eef5c2d8090e1f45feeeba","evidence":{"ambiguous_patch_ids":["5d0cb3cccce1158170d1cd02ebb43757"],"patch_ids":["5d0cb3cccce1158170d1cd02ebb43757"],"same_day":true},"kind":"related","label":"18.0","source_url":"/docs/release/18.0/#RELEASE-18-PGUPGRADE","title":"Allow pg_upgrade to preserve optimizer statistics","url":"/docs/compare/?release=18.0#18.0-4b580bc4439297d2","version":"18.0"}],"relations":[{"evidence":{"ambiguous_patch_ids":["5d0cb3cccce1158170d1cd02ebb43757"],"patch_ids":["5d0cb3cccce1158170d1cd02ebb43757"],"same_day":true},"rule":2,"target":"afbfe0f474eef5c2d8090e1f45feeeba","type":"related"}],"section":"Server Applications / pg_dump/pg_dumpall/pg_restore","section_path":["Server Applications","pg_dump/pg_dumpall/pg_restore"],"source_commits":["1fd1bd871"],"source_entry_id":"18.0/changes/142","source_hash":"48e0a689c9b0d5e55ef3d9ae16fc5c4a905c41197e8434f2f4f569b5a3250d84","source_url":"/docs/release/18.0/#RELEASE-18-PGDUMP","statement_hash":"19059f6013aef8345c941793ebe68ab82f27b44f9d1247c34243111b8ea7a09d","text":"Add pg_dump, pg_dumpall, and pg_restore options --statistics-only, --no-statistics, --no-data, and --no-schema (Corey Huinker, Jeff Davis) §","title":"Add pg_dump, pg_dumpall, and pg_restore options --statistics-only, --no-statistics, --no-data, and --no-schema","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["cd3c45125"],"commit_groups":[["cd3c45125"]],"commits":["cd3c45125"],"cves":[],"db_id":"f65a09f6ed8414315ea3ab15d44b063d","html":"\u003cp\u003eAdd option \u003ccode\u003e--no-policies\u003c/code\u003e to disable row level security policy processing in \u003ca href=\"/docs/18/app-pgdump.html\" title=\"pg_dump\"\u003e\u003cspan\u003e\u003cspan\u003epg_dump\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e, \u003ca href=\"/docs/18/app-pg-dumpall.html\" title=\"pg_dumpall\"\u003e\u003cspan\u003e\u003cspan\u003epg_dumpall\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e, \u003ca href=\"/docs/18/app-pgrestore.html\" title=\"pg_restore\"\u003e\u003cspan\u003e\u003cspan\u003epg_restore\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e (Nikolay Samokhvalov) \u003ca href=\"https://postgr.es/c/cd3c45125\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is useful for migrating to systems with different policies.\u003c/p\u003e","id":"18.0-448108837474663a","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.","part":"changes","patch_ids":["e8632c1f2c717fcff1a04211ab59a0c3"],"related_changes":[],"relations":[],"section":"Server Applications / pg_dump/pg_dumpall/pg_restore","section_path":["Server Applications","pg_dump/pg_dumpall/pg_restore"],"source_commits":["cd3c45125"],"source_entry_id":"18.0/changes/143","source_hash":"9231fdf3af2971c21ef9738044c6bf6fc9a4e82d61c155057f623aeacf8d1381","source_url":"/docs/release/18.0/#RELEASE-18-PGDUMP","statement_hash":"c2544d757037ea2d9f0d54209afb5dfcd831c83b0fb375579be57d3ffb98b730","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["1fd1bd871","c9d502eb6","d5f1b6a75"],"commit_groups":[["1fd1bd871"],["c9d502eb6"],["d5f1b6a75"]],"commits":["1fd1bd871","c9d502eb6","d5f1b6a75"],"cves":[],"db_id":"afbfe0f474eef5c2d8090e1f45feeeba","html":"\u003cp\u003eAllow \u003cspan\u003epg_upgrade\u003c/span\u003e to preserve optimizer statistics (Corey Huinker, Jeff Davis, Nathan Bossart) \u003ca href=\"https://postgr.es/c/1fd1bd871\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/c9d502eb6\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/d5f1b6a75\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/1fd1bd871\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eExtended statistics are not preserved. Also add \u003cspan\u003epg_upgrade\u003c/span\u003e option \u003ccode\u003e--no-statistics\u003c/code\u003e to disable statistics preservation.\u003c/p\u003e","id":"18.0-4b580bc4439297d2","identity_text":"Allow pg_upgrade to preserve optimizer statistics (Corey Huinker, Jeff Davis, Nathan Bossart) Extended statistics are not preserved. Also add pg_upgrade option --no-statistics to disable statistics preservation.","part":"changes","patch_ids":["394936eb907d9de5748a0a010a502753","5d0cb3cccce1158170d1cd02ebb43757","9d11899adf9cf21258dc987420e25832"],"related_changes":[{"db_id":"8d5b8469bade89e9c1af7e30be1f4707","evidence":{"ambiguous_patch_ids":["5d0cb3cccce1158170d1cd02ebb43757"],"patch_ids":["5d0cb3cccce1158170d1cd02ebb43757"],"same_day":true},"kind":"related","label":"18.0","source_url":"/docs/release/18.0/#RELEASE-18-PGDUMP","title":"Add pg_dump, pg_dumpall, and pg_restore options --statistics-only, --no-statistics, --no-data, and --no-schema","url":"/docs/compare/?release=18.0#18.0-1c7cab16e2b0faec","version":"18.0"}],"relations":[{"evidence":{"ambiguous_patch_ids":["5d0cb3cccce1158170d1cd02ebb43757"],"patch_ids":["5d0cb3cccce1158170d1cd02ebb43757"],"same_day":true},"rule":2,"target":"8d5b8469bade89e9c1af7e30be1f4707","type":"related"}],"section":"Server Applications / pg_upgrade","section_path":["Server Applications","pg_upgrade"],"source_commits":["1fd1bd871","c9d502eb6","d5f1b6a75"],"source_entry_id":"18.0/changes/144","source_hash":"ecf645ad4de74295862351e977c8da59f7c2af26f64a7500473f40f768a10c16","source_url":"/docs/release/18.0/#RELEASE-18-PGUPGRADE","statement_hash":"e18f67b21353450f4c5d6f714edfc631a34936d49aeb7064d84514378024acac","text":"Allow pg_upgrade to preserve optimizer statistics (Corey Huinker, Jeff Davis, Nathan Bossart) § § § § Extended statistics are not preserved. Also add pg_upgrade option --no-statistics to disable statistics preservation.","title":"Allow pg_upgrade to preserve optimizer statistics","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["40e2e5e92","46cad8b31","6ab8f27bc","6d3d2e8e5","7baa36de5","9db3018cf","bbf83cab9","c34eabfbb","c880cf258","cf2f82a37","f93f5f7b9"],"commit_groups":[["40e2e5e92"],["46cad8b31"],["6ab8f27bc"],["6d3d2e8e5"],["7baa36de5"],["9db3018cf"],["bbf83cab9"],["c34eabfbb"],["c880cf258"],["cf2f82a37"],["f93f5f7b9"]],"commits":["40e2e5e92","46cad8b31","6ab8f27bc","6d3d2e8e5","7baa36de5","9db3018cf","bbf83cab9","c34eabfbb","c880cf258","cf2f82a37","f93f5f7b9"],"cves":[],"db_id":"f9d4e72dc027a71ce2a37a4129d73c6d","html":"\u003cp\u003eAllow \u003cspan\u003epg_upgrade\u003c/span\u003e to process database checks in parallel (Nathan Bossart) \u003ca href=\"https://postgr.es/c/40e2e5e92\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/6d3d2e8e5\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/7baa36de5\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/46cad8b31\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/6ab8f27bc\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/bbf83cab9\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/9db3018cf\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/c34eabfbb\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/cf2f82a37\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/f93f5f7b9\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/c880cf258\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is controlled by the existing \u003ccode\u003e--jobs\u003c/code\u003e option.\u003c/p\u003e","id":"18.0-d8756d9cbd2b27ec","identity_text":"Allow pg_upgrade to process database checks in parallel (Nathan Bossart) This is controlled by the existing --jobs option.","part":"changes","patch_ids":["39d7bd98f5854223c3d58a547a4902aa","5ae351aee2ec1eb7531ddb523ae48e85","5d92df319c237bb627175e5564de1c46","6bedf241e4d5b07a2ac61d723ea4e964","77821ad60c100a1e9888a07a9b2869f7","b086dcc033e4eec4f10e04fbbd07818f","b5650ea4d83bdf9e634285ce798e2430","c6ef2c23b919aa135fcc566958ceb6a9","d47694834da9942ed2c592d8eacf8993","de1419043d49359a7ca596aee355ff07","df6634fce6c9cedeed8afd588b041845"],"related_changes":[],"relations":[],"section":"Server Applications / pg_upgrade","section_path":["Server Applications","pg_upgrade"],"source_commits":["40e2e5e92","46cad8b31","6ab8f27bc","6d3d2e8e5","7baa36de5","9db3018cf","bbf83cab9","c34eabfbb","c880cf258","cf2f82a37","f93f5f7b9"],"source_entry_id":"18.0/changes/145","source_hash":"0b5c0c1256bdf56fd1a023d5ff1ab1516afcdc337e7ee3b0f9b85acfb343155d","source_url":"/docs/release/18.0/#RELEASE-18-PGUPGRADE","statement_hash":"c05e7f4baaf6c58f0446522b852d7004694d10b5221f78902728516deb65d021","text":"Allow pg_upgrade to process database checks in parallel (Nathan Bossart) § § § § § § § § § § § This is controlled by the existing --jobs option.","title":"Allow pg_upgrade to process database checks in parallel","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["626d7236b"],"commit_groups":[["626d7236b"]],"commits":["626d7236b"],"cves":[],"db_id":"f554eecffc9529fc8a7bf5df05f1ee48","html":"\u003cp\u003eAdd \u003cspan\u003epg_upgrade\u003c/span\u003e option \u003ccode\u003e--swap\u003c/code\u003e to swap directories rather than copy, clone, or link files (Nathan Bossart) \u003ca href=\"https://postgr.es/c/626d7236b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis mode is potentially the fastest.\u003c/p\u003e","id":"18.0-67f639ce48c62e2e","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.","part":"changes","patch_ids":["925b13034396ed82973d22527b295ac1"],"related_changes":[],"relations":[],"section":"Server Applications / pg_upgrade","section_path":["Server Applications","pg_upgrade"],"source_commits":["626d7236b"],"source_entry_id":"18.0/changes/146","source_hash":"5105f96fe345879f059f5dec740fcdf62c3fb86f637efc061ea65ff41062563f","source_url":"/docs/release/18.0/#RELEASE-18-PGUPGRADE","statement_hash":"446dc8dd0a3efeea98cbe5eef953503f703ba461702c2ad5d7041434781f351e","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["1aab68059","a8238f87f"],"commit_groups":[["1aab68059"],["a8238f87f"]],"commits":["1aab68059","a8238f87f"],"cves":[],"db_id":"512ccd3d1bb4f010fe11b0eb637be55c","html":"\u003cp\u003eAdd \u003cspan\u003epg_upgrade\u003c/span\u003e option \u003ccode\u003e--set-char-signedness\u003c/code\u003e to set the default \u003ccode\u003echar\u003c/code\u003e signedness of new cluster (Masahiko Sawada) \u003ca href=\"https://postgr.es/c/a8238f87f\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/1aab68059\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is to handle cases where a pre-\u003cspan\u003ePostgreSQL\u003c/span\u003e 18 cluster's default \u003cacronym\u003eCPU\u003c/acronym\u003e signedness does not match the new cluster.\u003c/p\u003e","id":"18.0-f19ad14633daaefd","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.","part":"changes","patch_ids":["85f2c26487e180e9e34c5a419dbbbf35","b55f3df554d6f4f601f40f9bd71932dc"],"related_changes":[],"relations":[],"section":"Server Applications / pg_upgrade","section_path":["Server Applications","pg_upgrade"],"source_commits":["1aab68059","a8238f87f"],"source_entry_id":"18.0/changes/147","source_hash":"81fc7dfeaecc0c2acbed8c77a91318171c093256de3f1c6509e4ddb9b3506a2b","source_url":"/docs/release/18.0/#RELEASE-18-PGUPGRADE","statement_hash":"5d736231626605165fd5a2523999bf34662259ec86505d0abb98425210873d2d","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["fb2ea12f4"],"commit_groups":[["fb2ea12f4"]],"commits":["fb2ea12f4"],"cves":[],"db_id":"954788171dcb6930008281d2189eef2b","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/app-pgcreatesubscriber.html\" title=\"pg_createsubscriber\"\u003e\u003cspan\u003e\u003cspan\u003epg_createsubscriber\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e option \u003ccode\u003e--all\u003c/code\u003e to create logical replicas for all databases (Shubham Khanna) \u003ca href=\"https://postgr.es/c/fb2ea12f4\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-326132e0413a2af5","identity_text":"Add app-pgcreatesubscriber option --all to create logical replicas for all databases (Shubham Khanna)","part":"changes","patch_ids":["245e6d7207164c875aec56850b5dd55c"],"related_changes":[],"relations":[],"section":"Server Applications / Logical Replication Applications","section_path":["Server Applications","Logical Replication Applications"],"source_commits":["fb2ea12f4"],"source_entry_id":"18.0/changes/148","source_hash":"faf0501784185f0274b91341f0cea4d1ee6e811868673a3a6ee1ed33847c5743","source_url":"/docs/release/18.0/#RELEASE-18-LOGICALREP-APP","statement_hash":"c4a2693c70db1fc909c0ec71efb48bf2afef9841773d730329b484b5e39c01bb","text":"Add pg_createsubscriber option --all to create logical replicas for all databases (Shubham Khanna) §","title":"Add pg_createsubscriber option --all to create logical replicas for all databases","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["60dda7bbc","e5aeed4b8"],"commit_groups":[["60dda7bbc"],["e5aeed4b8"]],"commits":["60dda7bbc","e5aeed4b8"],"cves":[],"db_id":"a3ee32edc1ed5ed8fc4beb24a728e94c","html":"\u003cp\u003eAdd \u003cspan\u003epg_createsubscriber\u003c/span\u003e option \u003ccode\u003e--clean\u003c/code\u003e to remove publications (Shubham Khanna) \u003ca href=\"https://postgr.es/c/e5aeed4b8\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/60dda7bbc\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-43d66b2640370b92","identity_text":"Add pg_createsubscriber option --clean to remove publications (Shubham Khanna)","part":"changes","patch_ids":["8dcabb64a74beea420e0402e41aa4d21","c203fff53a96a19f82a444e6ce2b5966"],"related_changes":[],"relations":[],"section":"Server Applications / Logical Replication Applications","section_path":["Server Applications","Logical Replication Applications"],"source_commits":["60dda7bbc","e5aeed4b8"],"source_entry_id":"18.0/changes/149","source_hash":"2da64372e5883b9f3bdb349da006a3aa23028a390fab7edff19003a7d49a0316","source_url":"/docs/release/18.0/#RELEASE-18-LOGICALREP-APP","statement_hash":"1b7cc63371adabb9b0a36adb1a8829f98a748e42e2ed5ff2a972812322515b23","text":"Add pg_createsubscriber option --clean to remove publications (Shubham Khanna) § §","title":"Add pg_createsubscriber option --clean to remove publications","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["e117cfb2f"],"commit_groups":[["e117cfb2f"]],"commits":["e117cfb2f"],"cves":[],"db_id":"ddd2eec200c963d80868d55e604e2e3a","html":"\u003cp\u003eAdd \u003cspan\u003epg_createsubscriber\u003c/span\u003e option \u003ccode\u003e--enable-two-phase\u003c/code\u003e to enable prepared transactions (Shubham Khanna) \u003ca href=\"https://postgr.es/c/e117cfb2f\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-716d7b5f8a521be7","identity_text":"Add pg_createsubscriber option --enable-two-phase to enable prepared transactions (Shubham Khanna)","part":"changes","patch_ids":["9f0265494d5def7f02e8f05819a94c23"],"related_changes":[],"relations":[],"section":"Server Applications / Logical Replication Applications","section_path":["Server Applications","Logical Replication Applications"],"source_commits":["e117cfb2f"],"source_entry_id":"18.0/changes/150","source_hash":"343f583b66e94905a85d02018a62265c74dc248149a2d26e069195c9ef400ead","source_url":"/docs/release/18.0/#RELEASE-18-LOGICALREP-APP","statement_hash":"faec4e2c79436622d74ba1b7f84f70be155252fc23e1b39dcdad38cd5ffc05c6","text":"Add pg_createsubscriber option --enable-two-phase to enable prepared transactions (Shubham Khanna) §","title":"Add pg_createsubscriber option --enable-two-phase to enable prepared transactions","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["cf2655a90"],"commit_groups":[["cf2655a90"]],"commits":["cf2655a90"],"cves":[],"db_id":"99a65ba8cccf85a1b00949d9784e824d","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/app-pgrecvlogical.html\" title=\"pg_recvlogical\"\u003e\u003cspan\u003e\u003cspan\u003epg_recvlogical\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e option \u003ccode\u003e--enable-failover\u003c/code\u003e to specify failover slots (Hayato Kuroda) \u003ca href=\"https://postgr.es/c/cf2655a90\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eAlso add option \u003ccode\u003e--enable-two-phase\u003c/code\u003e as a synonym for \u003ccode\u003e--two-phase\u003c/code\u003e, and deprecate the latter.\u003c/p\u003e","id":"18.0-9451ebe7b4fbdfba","identity_text":"Add app-pgrecvlogical 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.","part":"changes","patch_ids":["f79f6257cc134079c46d90ba5379ee73"],"related_changes":[],"relations":[],"section":"Server Applications / Logical Replication Applications","section_path":["Server Applications","Logical Replication Applications"],"source_commits":["cf2655a90"],"source_entry_id":"18.0/changes/151","source_hash":"88d9dfa30e5ff57caeb5e8300717a8f74efeb33f2f5d2a0704986b8b80e9f686","source_url":"/docs/release/18.0/#RELEASE-18-LOGICALREP-APP","statement_hash":"ec97ab729002ad98ab6300ea9df86f7113426cb2f32822d741404b144a051152","text":"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.","title":"Add pg_recvlogical option --enable-failover to specify failover slots","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["c68100aa4"],"commit_groups":[["c68100aa4"]],"commits":["c68100aa4"],"cves":[],"db_id":"8f364820e55644a3a9e26c58d361267b","html":"\u003cp\u003eAllow \u003cspan\u003epg_recvlogical\u003c/span\u003e \u003ccode\u003e--drop-slot\u003c/code\u003e to work without \u003ccode\u003e--dbname\u003c/code\u003e (Hayato Kuroda) \u003ca href=\"https://postgr.es/c/c68100aa4\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-469a5c74393039c4","identity_text":"Allow pg_recvlogical --drop-slot to work without --dbname (Hayato Kuroda)","part":"changes","patch_ids":["33d58051231422c994deb2adafe09815"],"related_changes":[],"relations":[],"section":"Server Applications / Logical Replication Applications","section_path":["Server Applications","Logical Replication Applications"],"source_commits":["c68100aa4"],"source_entry_id":"18.0/changes/152","source_hash":"4c6b0f837901f50c25bc9205453bb7b4ef00415891e3eed73509249ca294591d","source_url":"/docs/release/18.0/#RELEASE-18-LOGICALREP-APP","statement_hash":"7a8e8735b056aa3b8f0fd15ad90f0690b2e9a69bc625d7c8a66b4465cab96d14","text":"Allow pg_recvlogical --drop-slot to work without --dbname (Hayato Kuroda) §","title":"Allow pg_recvlogical --drop-slot to work without --dbname","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4b211003e","a0a5869a8"],"commit_groups":[["4b211003e"],["a0a5869a8"]],"commits":["4b211003e","a0a5869a8"],"cves":[],"db_id":"59fdac27249ed47565b6f75c16e0cd37","html":"\u003cp\u003eSeparate the loading and running of \u003ca href=\"/docs/18/xfunc-c.html#XFUNC-ADDIN-INJECTION-POINTS\" title=\"36.10.14. Injection Points\"\u003einjection points\u003c/a\u003e (Michael Paquier, Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/4b211003e\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/a0a5869a8\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eInjection points can now be created, but not run, via \u003ca href=\"/docs/18/xfunc-c.html#XFUNC-ADDIN-INJECTION-POINTS\" title=\"36.10.14. Injection Points\"\u003e\u003ccode\u003eINJECTION_POINT_LOAD()\u003c/code\u003e\u003c/a\u003e, and such injection points can be run via \u003ca href=\"/docs/18/xfunc-c.html#XFUNC-ADDIN-INJECTION-POINTS\" title=\"36.10.14. Injection Points\"\u003e\u003ccode\u003eINJECTION_POINT_CACHED()\u003c/code\u003e\u003c/a\u003e.\u003c/p\u003e","id":"18.0-09b969a654ab4db4","identity_text":"Separate the loading and running of injection points (Michael Paquier, Heikki Linnakangas) Injection points can now be created, but not run, via INJECTION_POINT_LOAD(), and such injection points can be run via INJECTION_POINT_CACHED().","part":"changes","patch_ids":["613d98e15d1b3445fb5c464537496995","7b03a2eaca0889ac9bd69ab74602affc"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["4b211003e","a0a5869a8"],"source_entry_id":"18.0/changes/153","source_hash":"893df888cecfaa14b955913efb9204b93a7b2018ba3f7a9e397a29af6bcb71b3","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"88d18cc833292ed5dc6609366922320f4b754c28efda5a19a0778d9ce7001fbd","text":"Separate the loading and running of injection points (Michael Paquier, Heikki Linnakangas) § § Injection points can now be created, but not run, via INJECTION_POINT_LOAD(), and such injection points can be run via INJECTION_POINT_CACHED().","title":"Separate the loading and running of injection points","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["371f2db8b"],"commit_groups":[["371f2db8b"]],"commits":["371f2db8b"],"cves":[],"db_id":"18e4ff23a56d78d29d6ae66814cb5956","html":"\u003cp\u003eSupport runtime arguments in injection points (Michael Paquier) \u003ca href=\"https://postgr.es/c/371f2db8b\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-2a684741a2d184a7","identity_text":"Support runtime arguments in injection points (Michael Paquier)","part":"changes","patch_ids":["904e25b09a2067d4faafaee411020747"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["371f2db8b"],"source_entry_id":"18.0/changes/154","source_hash":"05301770ccd349689d8b69904a931228a96e0662899a3ade25f228442b6353fc","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"5628295a828190147d169e94449983354f8ae8ff5a86e747e2323a9fafe55684","text":"Support runtime arguments in injection points (Michael Paquier) §","title":"Support runtime arguments in injection points","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["20e0e7da9"],"commit_groups":[["20e0e7da9"]],"commits":["20e0e7da9"],"cves":[],"db_id":"69ea97ff28af6ada25aca341f8a735b0","html":"\u003cp\u003eAllow inline injection point test code with \u003ca href=\"/docs/18/xfunc-c.html#XFUNC-ADDIN-INJECTION-POINTS\" title=\"36.10.14. Injection Points\"\u003e\u003ccode\u003eIS_INJECTION_POINT_ATTACHED()\u003c/code\u003e\u003c/a\u003e (Heikki Linnakangas) \u003ca href=\"https://postgr.es/c/20e0e7da9\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-b8063b04940470a1","identity_text":"Allow inline injection point test code with IS_INJECTION_POINT_ATTACHED() (Heikki Linnakangas)","part":"changes","patch_ids":["2674b27a1325c15a5774f87f3db64257"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["20e0e7da9"],"source_entry_id":"18.0/changes/155","source_hash":"79e4cea60860d8836e161e88fdabc5f64d65b8ed64a9f03e86904ead26b4d830","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"205a386562b145149d35fbbbf10a8d236a72a87070e3f78c0fc594e2c19dfb63","text":"Allow inline injection point test code with IS_INJECTION_POINT_ATTACHED() (Heikki Linnakangas) §","title":"Allow inline injection point test code with IS_INJECTION_POINT_ATTACHED()","variants":[],"version":"18.0"},{"also_in":[],"category":"performance","category_label":"Performance","commit_aliases":["ca6fde922"],"commit_groups":[["ca6fde922"]],"commits":["ca6fde922"],"cves":[],"db_id":"bf59b3a6451a01581991094dc922205b","html":"\u003cp\u003eImprove the performance of processing long \u003ca href=\"/docs/18/datatype-json.html\" title=\"8.14. JSON Types\"\u003e\u003ccode\u003eJSON\u003c/code\u003e\u003c/a\u003e strings using \u003cacronym\u003eSIMD\u003c/acronym\u003e (Single Instruction Multiple Data) (David Rowley) \u003ca href=\"https://postgr.es/c/ca6fde922\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-90ebf5445d5aa78e","identity_text":"Improve the performance of processing long JSON strings using SIMD (Single Instruction Multiple Data) (David Rowley)","part":"changes","patch_ids":["6cd1200fc56103b10efacfbc076570b2"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["ca6fde922"],"source_entry_id":"18.0/changes/156","source_hash":"2b68724e9ee7f08af34fb5dc99e67d9a8ab04ede02afe191439e3458dd0f05e6","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"b5d92db4da4785f9e55e37acc9bac0dd40e7bb88a4bb126cc0e859e91cbee94c","text":"Improve the performance of processing long JSON strings using SIMD (Single Instruction Multiple Data) (David Rowley) §","title":"Improve the performance of processing long JSON strings using SIMD (Single Instruction Multiple Data)","variants":[],"version":"18.0"},{"also_in":[],"category":"performance","category_label":"Performance","commit_aliases":["3c6e8c123"],"commit_groups":[["3c6e8c123"]],"commits":["3c6e8c123"],"cves":[],"db_id":"ecafb4a5cc6e92dddebe2ea023f597fc","html":"\u003cp\u003eSpeed up CRC32C calculations using x86 \u003cacronym\u003eAVX\u003c/acronym\u003e-512 instructions (Raghuveer Devulapalli, Paul Amonson) \u003ca href=\"https://postgr.es/c/3c6e8c123\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-b11e30db33f1640b","identity_text":"Speed up CRC32C calculations using x86 AVX-512 instructions (Raghuveer Devulapalli, Paul Amonson)","part":"changes","patch_ids":["019ee0d01e78e91881714ff3219df19d"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["3c6e8c123"],"source_entry_id":"18.0/changes/157","source_hash":"5c411d4b51c4b6be50ef868a21271a59e4a75118bd9ef67ecd94fe284fa402d6","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"9ebfb29bd90710429d9371df23815bf2b5a56103e50f8fd93d29218148000bd5","text":"Speed up CRC32C calculations using x86 AVX-512 instructions (Raghuveer Devulapalli, Paul Amonson) §","title":"Speed up CRC32C calculations using x86 AVX-512 instructions","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["519338ace","6be53c276"],"commit_groups":[["519338ace"],["6be53c276"]],"commits":["519338ace","6be53c276"],"cves":[],"db_id":"e50b80ab8e5fdb402e0beb48a5db4bc9","html":"\u003cp\u003eAdd \u003cacronym\u003eARM\u003c/acronym\u003e Neon and \u003cacronym\u003eSVE CPU\u003c/acronym\u003e intrinsics for popcount (integer bit counting) (Chiranmoy Bhattacharya, Devanga Susmitha, Rama Malladi) \u003ca href=\"https://postgr.es/c/6be53c276\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/519338ace\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-db83e36c1db3de67","identity_text":"Add ARM Neon and SVE CPU intrinsics for popcount (integer bit counting) (Chiranmoy Bhattacharya, Devanga Susmitha, Rama Malladi)","part":"changes","patch_ids":["205916923c7dd75d0231c55476cd4c48","fd2f2d7fbcf88e0449c66f9f417165fc"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["519338ace","6be53c276"],"source_entry_id":"18.0/changes/158","source_hash":"09d6f13a948bcd90f3f3ac8e4018d0c533c115226c68a7db35a0bca2856dc813","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"ee09c22e85fe2068ac5f7492e13742c8aea22c6679a441f8015237ca7bdeeca7","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)","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["8dc28d7eb","9428c001f","c4e44224c","ca481d3c9"],"commit_groups":[["8dc28d7eb"],["9428c001f"],["c4e44224c"],["ca481d3c9"]],"commits":["8dc28d7eb","9428c001f","c4e44224c","ca481d3c9"],"cves":[],"db_id":"a7dfad9e7ea9413b1f4feb4de2d8c632","html":"\u003cp\u003eImprove the speed of numeric multiplication and division (Joel Jacobson, Dean Rasheed) \u003ca href=\"https://postgr.es/c/ca481d3c9\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/c4e44224c\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/8dc28d7eb\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/9428c001f\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-ecae7587264d9281","identity_text":"Improve the speed of numeric multiplication and division (Joel Jacobson, Dean Rasheed)","part":"changes","patch_ids":["2f55166563d7d9ec64de99e0bf6e591a","674fb4fd8062e095c5e8fbfa7beab186","8d573b00acf40046627605c19414157d","eb6faba6db5698c6310910540adef0d3"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["8dc28d7eb","9428c001f","c4e44224c","ca481d3c9"],"source_entry_id":"18.0/changes/159","source_hash":"6edd099ca744adedc636a8415e8be30ad6220455ffa27ad1859cf8db0e9e45b0","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"8921ae4e40b001cd77fce579693d0a2e93ba934d8c04d74b261b43866655c114","text":"Improve the speed of numeric multiplication and division (Joel Jacobson, Dean Rasheed) § § § §","title":"Improve the speed of numeric multiplication and division","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["65c298f61","8cc139bec","ba2a3c230"],"commit_groups":[["65c298f61"],["8cc139bec"],["ba2a3c230"]],"commits":["65c298f61","8cc139bec","ba2a3c230"],"cves":[],"db_id":"c46ccca9f1946dfd4459a691e07af2db","html":"\u003cp\u003eAdd configure option \u003ca href=\"/docs/18/install-make.html#CONFIGURE-OPTION-WITH-LIBNUMA\"\u003e\u003ccode\u003e--with-libnuma\u003c/code\u003e\u003c/a\u003e to enable \u003cacronym\u003eNUMA\u003c/acronym\u003e awareness (Jakub Wartak, Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/65c298f61\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/8cc139bec\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/ba2a3c230\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe function \u003ca href=\"/docs/18/functions-info.html#FUNCTIONS-INFO-SESSION-TABLE\" title=\"Table 9.71. Session Information Functions\"\u003e\u003ccode\u003epg_numa_available()\u003c/code\u003e\u003c/a\u003e reports on \u003cacronym\u003eNUMA\u003c/acronym\u003e awareness, and system views \u003ca href=\"/docs/18/view-pg-shmem-allocations-numa.html\" title=\"53.28. pg_shmem_allocations_numa\"\u003e\u003ccode\u003epg_shmem_allocations_numa\u003c/code\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/pgbuffercache.html#PGBUFFERCACHE-PG-BUFFERCACHE-NUMA\" title=\"F.25.2. The pg_buffercache_numa View\"\u003e\u003ccode\u003epg_buffercache_numa\u003c/code\u003e\u003c/a\u003e which report on shared memory distribution across \u003cacronym\u003eNUMA\u003c/acronym\u003e nodes.\u003c/p\u003e","id":"18.0-fd7d506191195bf5","identity_text":"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.","part":"changes","patch_ids":["0bda3a2939f0c8e553f2cd364b861d66","a0086763a22eaef1a94129dc2cb83f26","ff9b0977e0d9bc988b2742729958c76a"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["65c298f61","8cc139bec","ba2a3c230"],"source_entry_id":"18.0/changes/160","source_hash":"0b0694513101ef09876066d6557fa4d54f9a726b8c32a495d2e11cb5dbb87a56","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"db9faab559f61ef090bb1474d8e37a8edb03dfee891204a25cf413b42cb27eae","text":"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.","title":"Add configure option --with-libnuma to enable NUMA awareness","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["b52c4fc3c"],"commit_groups":[["b52c4fc3c"]],"commits":["b52c4fc3c"],"cves":[],"db_id":"a183c4433783924b1f543b04dffbe63e","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/storage-toast.html\" title=\"66.2. TOAST\"\u003e\u003cacronym\u003eTOAST\u003c/acronym\u003e\u003c/a\u003e table to \u003ca href=\"/docs/18/catalog-pg-index.html\" title=\"52.26. pg_index\"\u003e\u003ccode\u003epg_index\u003c/code\u003e\u003c/a\u003e to allow for very large expression indexes (Nathan Bossart) \u003ca href=\"https://postgr.es/c/b52c4fc3c\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-9d0c448b436ae645","identity_text":"Add TOAST table to pg_index to allow for very large expression indexes (Nathan Bossart)","part":"changes","patch_ids":["825a8af7998ad11c985cc0c19920c0aa"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["b52c4fc3c"],"source_entry_id":"18.0/changes/161","source_hash":"e38df8c4adac3c916dd37e49534a831db4c663c75afb9f1572aa9d9a19e1310b","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"585ce1fc6b90250a5d9f417054d52adc8449c84cb9126c4a7c8e18ded4b9bc89","text":"Add TOAST table to pg_index to allow for very large expression indexes (Nathan Bossart) §","title":"Add TOAST table to pg_index to allow for very large expression indexes","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["02a8d0c45"],"commit_groups":[["02a8d0c45"]],"commits":["02a8d0c45"],"cves":[],"db_id":"de9715e00924e543a93173bd557f8a87","html":"\u003cp\u003eRemove column \u003ca href=\"/docs/18/catalog-pg-attribute.html\" title=\"52.7. pg_attribute\"\u003e\u003ccode\u003epg_attribute\u003c/code\u003e\u003c/a\u003e.\u003ccode\u003eattcacheoff\u003c/code\u003e (David Rowley) \u003ca href=\"https://postgr.es/c/02a8d0c45\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-7c4c1a0fa6a16941","identity_text":"Remove column pg_attribute.attcacheoff (David Rowley)","part":"changes","patch_ids":["2a64af08b922f4b5dfec5863eeacc734"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["02a8d0c45"],"source_entry_id":"18.0/changes/162","source_hash":"645f698b676a9ba73d5e041adbcaff61122cc02dafe32585a497ee892ea42a60","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"f1b5f09c6883050623ac1812e798880f8ba176d23813a4ced4f4bd063d39ad1d","text":"Remove column pg_attribute.attcacheoff (David Rowley) §","title":"Remove column pg_attribute.attcacheoff","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["99f8f3fbb"],"commit_groups":[["99f8f3fbb"]],"commits":["99f8f3fbb"],"cves":[],"db_id":"2e16a121d2fdae3f34873b26af68f724","html":"\u003cp\u003eAdd column \u003ca href=\"/docs/18/catalog-pg-class.html\" title=\"52.11. pg_class\"\u003e\u003ccode\u003epg_class\u003c/code\u003e\u003c/a\u003e.\u003ccode\u003erelallfrozen\u003c/code\u003e (Melanie Plageman) \u003ca href=\"https://postgr.es/c/99f8f3fbb\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-78805849d91844f9","identity_text":"Add column pg_class.relallfrozen (Melanie Plageman)","part":"changes","patch_ids":["e34a60db7964acc6555e873dfb10725a"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["99f8f3fbb"],"source_entry_id":"18.0/changes/163","source_hash":"02febe83c5ceca231086a3ac50eeaa199052ee8b196e5ca9c648c59dde6831ca","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"96beb2905e3a248595ecdda5e965d732eec214f703f8add76ce30ed4598a9414","text":"Add column pg_class.relallfrozen (Melanie Plageman) §","title":"Add column pg_class.relallfrozen","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["56fead44d","af4002b38"],"commit_groups":[["56fead44d"],["af4002b38"]],"commits":["56fead44d","af4002b38"],"cves":[],"db_id":"c0896ad6ccc9b4c2522da43d546da5f5","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/indexam.html\" title=\"Chapter 63. Index Access Method Interface Definition\"\u003e\u003ccode\u003eamgettreeheight\u003c/code\u003e\u003c/a\u003e, \u003ccode\u003eamconsistentequality\u003c/code\u003e, and \u003ccode\u003eamconsistentordering\u003c/code\u003e to the index access method \u003cacronym\u003eAPI\u003c/acronym\u003e (Mark Dilger) \u003ca href=\"https://postgr.es/c/56fead44d\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/af4002b38\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-c782cff0c813679a","identity_text":"Add amgettreeheight, amconsistentequality, and amconsistentordering to the index access method API (Mark Dilger)","part":"changes","patch_ids":["d54243aea7af44672498af96b843565f","fb0944545fe3714256167ec92793a5fc"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["56fead44d","af4002b38"],"source_entry_id":"18.0/changes/164","source_hash":"d9121373abf7531fa3051db8fd45e11e34a371bb1779aa72dbd4573002763cc6","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"6ef133d3b85ce6783272fac722c9d4e931a1f2092c9da0e51cb9b27246ad7051","text":"Add amgettreeheight, amconsistentequality, and amconsistentordering to the index access method API (Mark Dilger) § §","title":"Add amgettreeheight, amconsistentequality, and amconsistentordering to the index access method API","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["7406ab623"],"commit_groups":[["7406ab623"]],"commits":["7406ab623"],"cves":[],"db_id":"547b4d266eb95df0ca214e88f83f2ac3","html":"\u003cp\u003eAdd GiST support function \u003ca href=\"/docs/18/gist.html#GIST-EXTENSIBILITY\" title=\"65.2.3. Extensibility\"\u003e\u003ccode\u003estratnum()\u003c/code\u003e\u003c/a\u003e (Paul A. Jungwirth) \u003ca href=\"https://postgr.es/c/7406ab623\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-460501ce376100d3","identity_text":"Add GiST support function stratnum() (Paul A. Jungwirth)","part":"changes","patch_ids":["c0f4d3964e16c6eacecdf93706337b0f"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["7406ab623"],"source_entry_id":"18.0/changes/165","source_hash":"cd860c634e5c11ef7814413f8dfc7d4e50a604bc8ae0127b42546e3f70578790","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"ab651fe748b337f580f4b0931d16866d0f092f26619271305ee30d4e09247dd2","text":"Add GiST support function stratnum() (Paul A. Jungwirth) §","title":"Add GiST support function stratnum()","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["44fe30fda"],"commit_groups":[["44fe30fda"]],"commits":["44fe30fda"],"cves":[],"db_id":"1527e2bcee85b6c81195ac3b56adf9ec","html":"\u003cp\u003eRecord the default \u003cacronym\u003eCPU\u003c/acronym\u003e signedness of \u003ccode\u003echar\u003c/code\u003e in \u003ca href=\"/docs/18/app-pgcontroldata.html\" title=\"pg_controldata\"\u003e\u003cspan\u003e\u003cspan\u003epg_controldata\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e (Masahiko Sawada) \u003ca href=\"https://postgr.es/c/44fe30fda\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-4ab938fcc679b324","identity_text":"Record the default CPU signedness of char in app-pgcontroldata (Masahiko Sawada)","part":"changes","patch_ids":["a1e6c83e979843b0eaf5ffe14783e0e3"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["44fe30fda"],"source_entry_id":"18.0/changes/166","source_hash":"363da2533daefb50791d8811bea21405b4ee732ce6c4f3f355442806e1dd31fa","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"47a0f9c4a0f67658919456be40ebfed6e7fa4cc578e1cbb804123622a3dc417b","text":"Record the default CPU signedness of char in pg_controldata (Masahiko Sawada) §","title":"Record the default CPU signedness of char in pg_controldata","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["0793ab810","72a3d0462"],"commit_groups":[["0793ab810"],["72a3d0462"]],"commits":["0793ab810","72a3d0462"],"cves":[],"db_id":"d9d289d7c17d30019901f5104438a9b5","html":"\u003cp\u003eAdd support for Python \"Limited \u003cacronym\u003eAPI\u003c/acronym\u003e\" in \u003ca href=\"/docs/18/plpython.html\" title=\"Chapter 44. PL/Python — Python Procedural Language\"\u003ePL/Python\u003c/a\u003e (Peter Eisentraut) \u003ca href=\"https://postgr.es/c/72a3d0462\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/0793ab810\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis helps prevent problems caused by \u003cspan\u003ePython\u003c/span\u003e 3.x version mismatches.\u003c/p\u003e","id":"18.0-4255e556057b15b2","identity_text":"Add support for Python \"Limited API\" in PL/Python (Peter Eisentraut) This helps prevent problems caused by Python 3.x version mismatches.","part":"changes","patch_ids":["cbf73ec20c058f368547efbe37a75ed9","d615c6575bcf9dabc148901891890deb"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["0793ab810","72a3d0462"],"source_entry_id":"18.0/changes/167","source_hash":"f49def5963789b61e9e11e6b78ad16b391ce6657675eb5e12857c3d90c25063f","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"bf3af05933e7d77673abcb674c13915120867f48aac15d60053f750a42d0d7d0","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["45363fca6"],"commit_groups":[["45363fca6"]],"commits":["45363fca6"],"cves":[],"db_id":"3803d2204af4aafb31861db9c07294df","html":"\u003cp\u003eChange the minimum supported \u003cspan\u003ePython\u003c/span\u003e version to 3.6.8 (Jacob Champion) \u003ca href=\"https://postgr.es/c/45363fca6\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-923b07e7289358ea","identity_text":"Change the minimum supported Python version to 3.6.8 (Jacob Champion)","part":"changes","patch_ids":["d238a5c385201266bab1298ddc3d6937"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["45363fca6"],"source_entry_id":"18.0/changes/168","source_hash":"edfc0a822c1e6decb577eb651c059faf6285be5446a2ae201393b823c93a7b4a","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"8e0582a6e94665c56a736b1daf82f2826837a955bf1ad3c8fed3ee41c1854b9b","text":"Change the minimum supported Python version to 3.6.8 (Jacob Champion) §","title":"Change the minimum supported Python version to 3.6.8","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["6c66b7443","a70e01d43"],"commit_groups":[["6c66b7443"],["a70e01d43"]],"commits":["6c66b7443","a70e01d43"],"cves":[],"db_id":"48cbbe1a33f004fe33768f2881d5d92f","html":"\u003cp\u003eRemove support for \u003cspan\u003eOpenSSL\u003c/span\u003e versions older than 1.1.1 (Daniel Gustafsson) \u003ca href=\"https://postgr.es/c/a70e01d43\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/6c66b7443\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-c729ed080047e9a6","identity_text":"Remove support for OpenSSL versions older than 1.1.1 (Daniel Gustafsson)","part":"changes","patch_ids":["abb2eed446c79007a20dabd90ec11e07","e230f75c4521f002154fbc695ab93e0a"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["6c66b7443","a70e01d43"],"source_entry_id":"18.0/changes/169","source_hash":"fef36e34b98c4cf8afc0e87fda7cd8014955b79b409cd798e1776f2cbb3cc19d","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"c8e7dae9a85d85423b23da56e2d21b96b7f26438f93b7ac8c175a38b66b24100","text":"Remove support for OpenSSL versions older than 1.1.1 (Daniel Gustafsson) § §","title":"Remove support for OpenSSL versions older than 1.1.1","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["972c2cd28"],"commit_groups":[["972c2cd28"]],"commits":["972c2cd28"],"cves":[],"db_id":"50c7a44be3192eea399751ed1200e8e8","html":"\u003cp\u003eIf \u003cspan\u003eLLVM\u003c/span\u003e is enabled, require version 14 or later (Thomas Munro) \u003ca href=\"https://postgr.es/c/972c2cd28\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-48539960f4e6144e","identity_text":"If LLVM is enabled, require version 14 or later (Thomas Munro)","part":"changes","patch_ids":["8a4ef85fef8148a0752a6381c6a739bb"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["972c2cd28"],"source_entry_id":"18.0/changes/170","source_hash":"312a91a833836d352538d85b42e2e70e2f3593c02b219f7e95f80da5e10bfaf4","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"36fc6c5974c10ca846263ab84a10c91abb0ab4d1f95effb5f1513c71c37a4bbe","text":"If LLVM is enabled, require version 14 or later (Thomas Munro) §","title":"If LLVM is enabled, require version 14 or later","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["9324c8c58"],"commit_groups":[["9324c8c58"]],"commits":["9324c8c58"],"cves":[],"db_id":"22bad4a55bc766af423a30b6bf1b99b9","html":"\u003cp\u003eAdd macro \u003ca href=\"/docs/18/functions-info.html\" title=\"9.27. System Information Functions and Operators\"\u003e\u003ccode\u003ePG_MODULE_MAGIC_EXT\u003c/code\u003e\u003c/a\u003e to allow extensions to report their name and version (Andrei Lepikhov) \u003ca href=\"https://postgr.es/c/9324c8c58\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis information can be access via the new function \u003ca href=\"/docs/18/functions-info.html#FUNCTIONS-INFO-SESSION-TABLE\" title=\"Table 9.71. Session Information Functions\"\u003e\u003ccode\u003epg_get_loaded_modules()\u003c/code\u003e\u003c/a\u003e.\u003c/p\u003e","id":"18.0-cc466a564036d579","identity_text":"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().","part":"changes","patch_ids":["ed1ff647f1c305bd35f657351b9a7adf"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["9324c8c58"],"source_entry_id":"18.0/changes/171","source_hash":"473925ca43927bf0fecf0ebb8b99b79703e70fb6920ef16d9a6197b242837012","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"b4515add36ae14827b8bf37983849f8407d2e2de81d57662cf8c2e42fb2dc367","text":"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().","title":"Add macro PG_MODULE_MAGIC_EXT to allow extensions to report their name and version","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["218527d01"],"commit_groups":[["218527d01"]],"commits":["218527d01"],"cves":[],"db_id":"6c9d752ad2524932db7f67c114ea208c","html":"\u003cp\u003eDocument that \u003ca href=\"/docs/18/spi-spi-connect.html\" title=\"SPI_connect\"\u003e\u003ccode\u003eSPI_connect()\u003c/code\u003e\u003c/a\u003e/\u003ca href=\"/docs/18/spi-spi-connect.html\" title=\"SPI_connect\"\u003e\u003ccode\u003eSPI_connect_ext()\u003c/code\u003e\u003c/a\u003e always returns success (\u003ccode\u003eSPI_OK_CONNECT\u003c/code\u003e) (Stepan Neretin) \u003ca href=\"https://postgr.es/c/218527d01\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eErrors are always reported via \u003ccode\u003eereport()\u003c/code\u003e.\u003c/p\u003e","id":"18.0-1f7ee7beb9720d96","identity_text":"Document that SPI_connect()/SPI_connect_ext() always returns success (SPI_OK_CONNECT) (Stepan Neretin) Errors are always reported via ereport().","part":"changes","patch_ids":["8db80b5d2f22fef141642ab40ac0c845"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["218527d01"],"source_entry_id":"18.0/changes/172","source_hash":"aa52b5fa421b28ab0bc7e593947371732a940dc52c961ec9185e124ddf4d35ff","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"67c11936fe67155db84d081f3909f3742a03731f80e2342d6e16669433687aba","text":"Document that SPI_connect()/SPI_connect_ext() always returns success (SPI_OK_CONNECT) (Stepan Neretin) § Errors are always reported via ereport().","title":"Document that SPI_connect()/SPI_connect_ext() always returns success (SPI_OK_CONNECT)","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["e54a42ac9"],"commit_groups":[["e54a42ac9"]],"commits":["e54a42ac9"],"cves":[],"db_id":"bce92895bdc4d2128762d0826b82afe5","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/xfunc-c.html#XFUNC-API-ABI-STABILITY-GUIDANCE\" title=\"36.10.6. Server API and ABI Stability Guidance\"\u003edocumentation section\u003c/a\u003e about \u003cacronym\u003eAPI\u003c/acronym\u003e and \u003cacronym\u003eABI\u003c/acronym\u003e compatibility (David Wheeler, Peter Eisentraut) \u003ca href=\"https://postgr.es/c/e54a42ac9\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-dbb8c166c369ad8f","identity_text":"Add documentation section about API and ABI compatibility (David Wheeler, Peter Eisentraut)","part":"changes","patch_ids":["ed9bc344aa72386c8e767c718632ec82"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["e54a42ac9"],"source_entry_id":"18.0/changes/173","source_hash":"90c971529d419760d77397cb587a82b521c16886289aebdd0a9950e6910000f9","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"0295a4b203df0b9501cc58312ecd1041db9220faa5a8a3ae88d0fb981ee922f4","text":"Add documentation section about API and ABI compatibility (David Wheeler, Peter Eisentraut) §","title":"Add documentation section about API and ABI compatibility","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["5afaba629"],"commit_groups":[["5afaba629"]],"commits":["5afaba629"],"cves":[],"db_id":"65f45b8de45e88579fb3a07c1fc5ca82","html":"\u003cp\u003eRemove the experimental designation of \u003cspan\u003eMeson\u003c/span\u003e builds on \u003cspan\u003eWindows\u003c/span\u003e (Aleksander Alekseev) \u003ca href=\"https://postgr.es/c/5afaba629\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-c62188fa02597863","identity_text":"Remove the experimental designation of Meson builds on Windows (Aleksander Alekseev)","part":"changes","patch_ids":["7f3733853ec88ef6dcc506c3f311ca02"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["5afaba629"],"source_entry_id":"18.0/changes/174","source_hash":"6fa8dda0e2cd9ac5555c784bf5c0ef8242c1206143e83bc3f734bc4ebaecdc2a","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"4b791d0ce6d561df0dc9266dbc1c032420c8b1a17d776165cd28778ec4824762","text":"Remove the experimental designation of Meson builds on Windows (Aleksander Alekseev) §","title":"Remove the experimental designation of Meson builds on Windows","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["813852613","e25626677"],"commit_groups":[["813852613"],["e25626677"]],"commits":["813852613","e25626677"],"cves":[],"db_id":"cb76202d341bfde3157c7f5662fdca08","html":"\u003cp\u003eRemove configure options \u003ccode\u003e--disable-spinlocks\u003c/code\u003e and \u003ccode\u003e--disable-atomics\u003c/code\u003e (Thomas Munro) \u003ca href=\"https://postgr.es/c/e25626677\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/813852613\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThirty-two-bit atomic operations are now required.\u003c/p\u003e","id":"18.0-b529394c7414f821","identity_text":"Remove configure options --disable-spinlocks and --disable-atomics (Thomas Munro) Thirty-two-bit atomic operations are now required.","part":"changes","patch_ids":["1adba83a13269f9fe1796e4c938f5668","c5a68b790cc12df3a522cd1c85e50f75"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["813852613","e25626677"],"source_entry_id":"18.0/changes/175","source_hash":"dea8d45db1e65b97fa1c42d83d77ae1a21b44ff4bf947e134c0ae0c51fec84eb","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"f075e693a989fc62b94be60cc6414f54094d772e3fc9f2cc5a1a1beefdca9437","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["edadeb071"],"commit_groups":[["edadeb071"]],"commits":["edadeb071"],"cves":[],"db_id":"a167452f08dbddf1b2de4b6f87175253","html":"\u003cp\u003eRemove support for the \u003cacronym\u003eHPPA\u003c/acronym\u003e/\u003cacronym\u003ePA-RISC\u003c/acronym\u003e architecture (Tom Lane) \u003ca href=\"https://postgr.es/c/edadeb071\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-e16d84f131471052","identity_text":"Remove support for the HPPA/PA-RISC architecture (Tom Lane)","part":"changes","patch_ids":["4c7fcd694e4cfcfdf4d2b66e07bcc93b"],"related_changes":[],"relations":[],"section":"Source Code","section_path":["Source Code"],"source_commits":["edadeb071"],"source_entry_id":"18.0/changes/176","source_hash":"8f4d3cb0f0e25fcd326fb98621d0aefc3e51c019fd35d16cfdf8c01567fe96be","source_url":"/docs/release/18.0/#RELEASE-18-SOURCE-CODE","statement_hash":"34e0e62ec64cf13e242497f80e1704894b16ff8d2f43db397bcdbb5fd4d87a42","text":"Remove support for the HPPA/PA-RISC architecture (Tom Lane) §","title":"Remove support for the HPPA/PA-RISC architecture","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["7cdfeee32"],"commit_groups":[["7cdfeee32"]],"commits":["7cdfeee32"],"cves":[],"db_id":"67c4f0ce87d750c9d1fc47621ad4ca18","html":"\u003cp\u003eAdd extension \u003ca href=\"/docs/18/pglogicalinspect.html\" title=\"F.28. pg_logicalinspect — logical decoding components inspection\"\u003epg_logicalinspect\u003c/a\u003e to inspect logical snapshots (Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/7cdfeee32\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-7290fc125f61d724","identity_text":"Add extension pglogicalinspect to inspect logical snapshots (Bertrand Drouvot)","part":"changes","patch_ids":["a7b197beccb692abf2aeb8c35a0a48a1"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["7cdfeee32"],"source_entry_id":"18.0/changes/177","source_hash":"2687560225facdefa50011e45e121f7d2ba43f8c8dbd44cf574154afa1445beb","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"aacda762c76e2c1fbfdaa69e9c927a9740a1692b0b61c349e5016a3c3b699a0a","text":"Add extension pg_logicalinspect to inspect logical snapshots (Bertrand Drouvot) §","title":"Add extension pg_logicalinspect to inspect logical snapshots","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["8d5ceb113"],"commit_groups":[["8d5ceb113"]],"commits":["8d5ceb113"],"cves":[],"db_id":"87a2dbbbebd8175b5bf005cb3cfc67ca","html":"\u003cp\u003eAdd extension \u003ca href=\"/docs/18/pgoverexplain.html\" title=\"F.29. pg_overexplain — allow EXPLAIN to dump even more details\"\u003epg_overexplain\u003c/a\u003e which adds debug details to \u003ca href=\"/docs/18/sql-explain.html\" title=\"EXPLAIN\"\u003e\u003ccode\u003eEXPLAIN\u003c/code\u003e\u003c/a\u003e output (Robert Haas) \u003ca href=\"https://postgr.es/c/8d5ceb113\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-b013c231e39d5be8","identity_text":"Add extension pgoverexplain which adds debug details to EXPLAIN output (Robert Haas)","part":"changes","patch_ids":["2ed4181cb477cdca663a38f91a5f217c"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["8d5ceb113"],"source_entry_id":"18.0/changes/178","source_hash":"7515ce17b867bfaab97a731353d79de47d4cad8cb11c156dc88cd77a008a3e6a","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"d9fca54d692a23040461084ec35270936c31625992377c566a8c37899f1f0787","text":"Add extension pg_overexplain which adds debug details to EXPLAIN output (Robert Haas) §","title":"Add extension pg_overexplain which adds debug details to EXPLAIN output","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4f08ab554","857df3cef","c297a47c5","fe186bda7"],"commit_groups":[["4f08ab554"],["857df3cef"],["c297a47c5"],["fe186bda7"]],"commits":["4f08ab554","857df3cef","c297a47c5","fe186bda7"],"cves":[],"db_id":"57766a54c36633792199e697fc70e7df","html":"\u003cp\u003eAdd output columns to \u003ca href=\"/docs/18/postgres-fdw.html#POSTGRES-FDW-FUNCTIONS\" title=\"F.38.2. Functions\"\u003e\u003ccode\u003epostgres_fdw_get_connections()\u003c/code\u003e\u003c/a\u003e (Hayato Kuroda, Sagar Dilip Shedge) \u003ca href=\"https://postgr.es/c/c297a47c5\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/857df3cef\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/4f08ab554\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/fe186bda7\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eNew output column \u003ccode\u003eused_in_xact\u003c/code\u003e indicates if the foreign data wrapper is being used by a current transaction, \u003ccode\u003eclosed\u003c/code\u003e indicates if it is closed, \u003ccode\u003euser_name\u003c/code\u003e indicates the user name, and \u003ccode\u003eremote_backend_pid\u003c/code\u003e indicates the remote backend process identifier.\u003c/p\u003e","id":"18.0-4831466123b6482b","identity_text":"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.","part":"changes","patch_ids":["69b3dae14669bd99116e5c32e7ce74b0","6a1a0a8505001d8b25302d12068877e7","c0a12ec1a2d53150c1b560fb21c4539c","d67e56f99dc5bb1eb71cebb589bee3a5"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["4f08ab554","857df3cef","c297a47c5","fe186bda7"],"source_entry_id":"18.0/changes/179","source_hash":"2757fb81880ea4eb26d1e4463218e9a19e266a0e629f94c057cb3aec12bcea56","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"3720900a35e82886147a69fd3730383d5206cad9f0e7aafdf9a19742425cfc42","text":"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.","title":"Add output columns to postgres_fdw_get_connections()","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["761c79508"],"commit_groups":[["761c79508"]],"commits":["761c79508"],"cves":[],"db_id":"e470a9bf401deab26d02f6095d0d4417","html":"\u003cp\u003eAllow \u003ca href=\"/docs/18/auth-password.html\" title=\"20.5. Password Authentication\"\u003e\u003cacronym\u003eSCRAM\u003c/acronym\u003e\u003c/a\u003e authentication from the client to be passed to \u003ca href=\"/docs/18/postgres-fdw.html\" title=\"F.38. postgres_fdw — access data stored in external PostgreSQL servers\"\u003epostgres_fdw\u003c/a\u003e servers (Matheus Alcantara, Peter Eisentraut) \u003ca href=\"https://postgr.es/c/761c79508\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis avoids storing \u003cspan\u003epostgres_fdw\u003c/span\u003e authentication information in the database, and is enabled with the \u003cspan\u003epostgres_fdw\u003c/span\u003e \u003ca href=\"/docs/18/postgres-fdw.html#POSTGRES-FDW-OPTION-USE-SCRAM-PASSTHROUGH\"\u003e\u003ccode\u003euse_scram_passthrough\u003c/code\u003e\u003c/a\u003e connection option. libpq uses new connection parameters \u003ca href=\"/docs/18/libpq-connect.html#LIBPQ-CONNECT-SCRAM-CLIENT-KEY\"\u003escram_client_key\u003c/a\u003e and \u003ca href=\"/docs/18/libpq-connect.html#LIBPQ-CONNECT-SCRAM-SERVER-KEY\"\u003escram_server_key\u003c/a\u003e.\u003c/p\u003e","id":"18.0-5519d2468e9d5ea2","identity_text":"Allow SCRAM authentication from the client to be passed to postgres-fdw servers (Matheus Alcantara, Peter Eisentraut) This 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 libpq-connect-scram-client-key and libpq-connect-scram-server-key .","part":"changes","patch_ids":["af2270afccff9e2eee136add3ddf9516"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["761c79508"],"source_entry_id":"18.0/changes/180","source_hash":"5acf9481abc4c3c8dc1300ade55bcee491bededaef10ba7b4c9d16ee213d4b3f","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"7752ceee84e239333dabe3abd26dcd183aad92846d5412c6919e21ed04e49920","text":"Allow SCRAM authentication from the client to be passed to postgres_fdw servers (Matheus Alcantara, Peter Eisentraut) § This 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.","title":"Allow SCRAM authentication from the client to be passed to postgres_fdw servers","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["3642df265"],"commit_groups":[["3642df265"]],"commits":["3642df265"],"cves":[],"db_id":"db82382f896f8242594f26f0e98cd318","html":"\u003cp\u003eAllow \u003cacronym\u003eSCRAM\u003c/acronym\u003e authentication from the client to be passed to \u003ca href=\"/docs/18/dblink.html\" title=\"F.11. dblink — connect to other PostgreSQL databases\"\u003edblink\u003c/a\u003e servers (Matheus Alcantara) \u003ca href=\"https://postgr.es/c/3642df265\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-40e7df9bbd01fbdd","identity_text":"Allow SCRAM authentication from the client to be passed to dblink servers (Matheus Alcantara)","part":"changes","patch_ids":["071743b3a560980bed101b42da01a888"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["3642df265"],"source_entry_id":"18.0/changes/181","source_hash":"d5d459964678c5f8377c3bd875649fc44172ce4cb2a1b6401f0950b80fc6ba4a","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"606c662a7292efbe14169ab67273e036f3695f6e116ffb4735ab23da0a7f3415","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["a1c4c8a9e"],"commit_groups":[["a1c4c8a9e"]],"commits":["a1c4c8a9e"],"cves":[],"db_id":"6982b0c41f58b8ad05599dd36f57aaa9","html":"\u003cp\u003eAdd \u003ccode\u003eon_error\u003c/code\u003e and \u003ccode\u003elog_verbosity\u003c/code\u003e options to \u003ca href=\"/docs/18/file-fdw.html\" title=\"F.15. file_fdw — access data files in the server's file system\"\u003efile_fdw\u003c/a\u003e (Atsushi Torikoshi) \u003ca href=\"https://postgr.es/c/a1c4c8a9e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThese control how \u003cspan\u003efile_fdw\u003c/span\u003e handles and reports invalid file rows.\u003c/p\u003e","id":"18.0-be0a5c377c8ad1d6","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.","part":"changes","patch_ids":["21992e0340c7459eca57bac98530eee3"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["a1c4c8a9e"],"source_entry_id":"18.0/changes/182","source_hash":"115a0c8a418b7106acd2734d853b844db562b082c4bda8f83428f4e298314284","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"c5180a0af1dd4fdd3162754e1b488f348273f6c2f9209b82ebf3d374fabffd98","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["6c8f67032"],"commit_groups":[["6c8f67032"]],"commits":["6c8f67032"],"cves":[],"db_id":"48a8faf8ec485497fca4db2bacbaeab7","html":"\u003cp\u003eAdd \u003ccode\u003ereject_limit\u003c/code\u003e to control the number of invalid rows \u003cspan\u003efile_fdw\u003c/span\u003e can ignore (Atsushi Torikoshi) \u003ca href=\"https://postgr.es/c/6c8f67032\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is active when \u003ccode\u003eON_ERROR = 'ignore'\u003c/code\u003e.\u003c/p\u003e","id":"18.0-d073f00449dd1fe3","identity_text":"Add reject_limit to control the number of invalid rows file_fdw can ignore (Atsushi Torikoshi) This is active when ON_ERROR = 'ignore'.","part":"changes","patch_ids":["5b6c0783ca982f9138e4795b3e829d8a"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["6c8f67032"],"source_entry_id":"18.0/changes/183","source_hash":"914ef144cb149e5828a4af2d2b3498fdd849dab913c363a52d16e74e3911885f","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"731012e4db71426106868c5367cd50ce2ef63f3770862fd07904f6a9a0245032","text":"Add reject_limit to control the number of invalid rows file_fdw can ignore (Atsushi Torikoshi) § This is active when ON_ERROR = 'ignore'.","title":"Add reject_limit to control the number of invalid rows file_fdw can ignore","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["f7e1b3828"],"commit_groups":[["f7e1b3828"]],"commits":["f7e1b3828"],"cves":[],"db_id":"c2f3e4981e48c781d80d8d683bfeafdc","html":"\u003cp\u003eAdd configurable variable \u003ccode\u003emin_password_length\u003c/code\u003e to \u003ca href=\"/docs/18/passwordcheck.html\" title=\"F.24. passwordcheck — verify password strength\"\u003epasswordcheck\u003c/a\u003e (Emanuele Musella, Maurizio Boriani) \u003ca href=\"https://postgr.es/c/f7e1b3828\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis controls the minimum password length.\u003c/p\u003e","id":"18.0-633e2729df5f6460","identity_text":"Add configurable variable min_password_length to passwordcheck (Emanuele Musella, Maurizio Boriani) This controls the minimum password length.","part":"changes","patch_ids":["8adca4662ef9e316e20e61eac39f5953"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["f7e1b3828"],"source_entry_id":"18.0/changes/184","source_hash":"1b94e879146707658c8624a2cc1d0d5d51823ca6cec56d81901b4e94cb11b78c","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"3c96a08392c835400e1601043498429b0df9c4a3c6205b65fa827329a880c71d","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["cae0f3c40"],"commit_groups":[["cae0f3c40"]],"commits":["cae0f3c40"],"cves":[],"db_id":"7d68f2a4e71d87ab7e6b4494d5b3c176","html":"\u003cp\u003eHave \u003ca href=\"/docs/18/pgbench.html\" title=\"pgbench\"\u003e\u003cspan\u003e\u003cspan\u003epgbench\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e report the number of failed, retried, or skipped transactions in per-script reports (Yugo Nagata) \u003ca href=\"https://postgr.es/c/cae0f3c40\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-ccb942ad8d145ac9","identity_text":"Have pgbench report the number of failed, retried, or skipped transactions in per-script reports (Yugo Nagata)","part":"changes","patch_ids":["7ae9139da216927d66da497ea952bf95"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["cae0f3c40"],"source_entry_id":"18.0/changes/185","source_hash":"b6ab8471bd55acbc24e7b6d8e4dbc4490126311ba216112a2325d59926d09340","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"18f1805b3f36c44aa22e9a7c871bfc854cae06d2d1ba7d54f1c9ef8c03dabac0","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["448904423"],"commit_groups":[["448904423"]],"commits":["448904423"],"cves":[],"db_id":"5f8aee170ab63cf20094d429feccf7c0","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/isn.html\" title=\"F.20. isn — data types for international standard numbers (ISBN, EAN, UPC, etc.)\"\u003eisn\u003c/a\u003e server variable \u003ccode\u003eweak\u003c/code\u003e to control invalid check digit acceptance (Viktor Holmberg) \u003ca href=\"https://postgr.es/c/448904423\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis was previously only controlled by function \u003ca href=\"/docs/18/isn.html#ISN-FUNCTIONS\" title=\"Table F.11. isn Functions\"\u003e\u003ccode\u003eisn_weak()\u003c/code\u003e\u003c/a\u003e.\u003c/p\u003e","id":"18.0-6929095b04fe5b40","identity_text":"Add isn server variable weak to control invalid check digit acceptance (Viktor Holmberg) This was previously only controlled by function isn_weak().","part":"changes","patch_ids":["18f9d78d0b131468273798f1c5d15c6f"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["448904423"],"source_entry_id":"18.0/changes/186","source_hash":"02b17a33ef29c5ffa267140e9614fd175f35fb008501832e4e8b2738b89ccc04","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"5acf45b1736bba51038a52d3be296633c8f71d63e863e5b4fa2a8bd6b564504e","text":"Add isn server variable weak to control invalid check digit acceptance (Viktor Holmberg) § This was previously only controlled by function isn_weak().","title":"Add isn server variable weak to control invalid check digit acceptance","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["e4309f73f"],"commit_groups":[["e4309f73f"]],"commits":["e4309f73f"],"cves":[],"db_id":"7e911d1361965be0a82fa600d4ebef9d","html":"\u003cp\u003eAllow values to be sorted to speed \u003ca href=\"/docs/18/btree-gist.html\" title=\"F.8. btree_gist — GiST operator classes with B-tree behavior\"\u003ebtree_gist\u003c/a\u003e index builds (Bernd Helmle, Andrey Borodin) \u003ca href=\"https://postgr.es/c/e4309f73f\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-f65afd9fd3a24d96","identity_text":"Allow values to be sorted to speed btree-gist index builds (Bernd Helmle, Andrey Borodin)","part":"changes","patch_ids":["cffdd969af417cd314b82e92cb6a914f"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["e4309f73f"],"source_entry_id":"18.0/changes/187","source_hash":"212669f707e1fce095f4a15af5bba9c3db22d8a44760a389af1d2d2f668d8dde","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"cebec6909a36bdf2166bf54e64bff4c820d6b198d1e688f1c4007e765cf72614","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["14ffaece0"],"commit_groups":[["14ffaece0"]],"commits":["14ffaece0"],"cves":[],"db_id":"901639a50d26960109ceeaf20c9a6525","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/amcheck.html\" title=\"F.1. amcheck — tools to verify table and index consistency\"\u003eamcheck\u003c/a\u003e check function \u003ca href=\"/docs/18/amcheck.html#AMCHECK-FUNCTIONS\" title=\"F.1.1. Functions\"\u003e\u003ccode\u003egin_index_check()\u003c/code\u003e\u003c/a\u003e to verify \u003ccode\u003eGIN\u003c/code\u003e indexes (Grigory Kryachko, Heikki Linnakangas, Andrey Borodin) \u003ca href=\"https://postgr.es/c/14ffaece0\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-d35d4aa1899363aa","identity_text":"Add amcheck check function gin_index_check() to verify GIN indexes (Grigory Kryachko, Heikki Linnakangas, Andrey Borodin)","part":"changes","patch_ids":["3da01d3c7aa186dc71d957e208a485dc"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["14ffaece0"],"source_entry_id":"18.0/changes/188","source_hash":"e92d948d2ddc6876642e73f177289d6b41bb2fe21922122f6e1e7eeaf83fff3c","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"da2898009fd05a775abd078506b5f09c6e8b1e8fec26d605efd008c0d231dab0","text":"Add amcheck check function gin_index_check() to verify GIN indexes (Grigory Kryachko, Heikki Linnakangas, Andrey Borodin) §","title":"Add amcheck check function gin_index_check() to verify GIN indexes","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["dcf7e1697"],"commit_groups":[["dcf7e1697"]],"commits":["dcf7e1697"],"cves":[],"db_id":"53a630578a75630174d2c269609886e6","html":"\u003cp\u003eAdd functions \u003ca href=\"/docs/18/pgbuffercache.html#PGBUFFERCACHE-PG-BUFFERCACHE-EVICT-RELATION\" title=\"F.25.6. The pg_buffercache_evict_relation() Function\"\u003e\u003ccode\u003epg_buffercache_evict_relation()\u003c/code\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/pgbuffercache.html#PGBUFFERCACHE-PG-BUFFERCACHE-EVICT-ALL\" title=\"F.25.7. The pg_buffercache_evict_all() Function\"\u003e\u003ccode\u003epg_buffercache_evict_all()\u003c/code\u003e\u003c/a\u003e to evict unpinned shared buffers (Nazir Bilal Yavuz) \u003ca href=\"https://postgr.es/c/dcf7e1697\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe existing function \u003ca href=\"/docs/18/pgbuffercache.html#PGBUFFERCACHE-PG-BUFFERCACHE-EVICT\" title=\"F.25.5. The pg_buffercache_evict() Function\"\u003e\u003ccode\u003epg_buffercache_evict()\u003c/code\u003e\u003c/a\u003e now returns the buffer flush status.\u003c/p\u003e","id":"18.0-a511612dd1dbda61","identity_text":"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.","part":"changes","patch_ids":["18bc743ec0e02f2bfdd5e711a373a351"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["dcf7e1697"],"source_entry_id":"18.0/changes/189","source_hash":"ff8384fcca3171ad9ba328245edab24a7394c982bd1ee80a16272f59622034c3","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"741214ec5c0080df2f48fe0ecb949fe4d8cc9dcffc25225e8d4f433bd4032752","text":"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.","title":"Add functions pg_buffercache_evict_relation() and pg_buffercache_evict_all() to evict unpinned shared buffers","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["4fd02bf7c","50ba65e73","c65bc2e1d"],"commit_groups":[["4fd02bf7c"],["50ba65e73"],["c65bc2e1d"]],"commits":["4fd02bf7c","50ba65e73","c65bc2e1d"],"cves":[],"db_id":"17128679b68e62fcef0d48d266afb493","html":"\u003cp\u003eAllow extensions to install custom \u003ca href=\"/docs/18/sql-explain.html\" title=\"EXPLAIN\"\u003e\u003cspan\u003eEXPLAIN\u003c/span\u003e\u003c/a\u003e options (Robert Haas, Sami Imseih) \u003ca href=\"https://postgr.es/c/c65bc2e1d\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/4fd02bf7c\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/50ba65e73\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-d112bddfd7837836","identity_text":"Allow extensions to install custom sql-explain options (Robert Haas, Sami Imseih)","part":"changes","patch_ids":["4a90cb7809dd3268e814052cb9d568f6","a7446b42cbf558abedd81726ef25be11","b1d23fea200234c95397b7e93fd14848"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["4fd02bf7c","50ba65e73","c65bc2e1d"],"source_entry_id":"18.0/changes/190","source_hash":"126c1e252fd401d5cbcf8667b52299d2f5510b10142a7ea6310dcbba82c8bd12","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"e8646573cbbb7286af9b4ad50cc583bc6310d49c513b0e947a6bca0270e16301","text":"Allow extensions to install custom EXPLAIN options (Robert Haas, Sami Imseih) § § §","title":"Allow extensions to install custom EXPLAIN options","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["2eff9e678","7949d9594"],"commit_groups":[["2eff9e678"],["7949d9594"]],"commits":["2eff9e678","7949d9594"],"cves":[],"db_id":"51ed37dd51200e7f7a59592baf05f997","html":"\u003cp\u003eAllow extensions to use the server's cumulative statistics \u003cacronym\u003eAPI\u003c/acronym\u003e (Michael Paquier) \u003ca href=\"https://postgr.es/c/7949d9594\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/2eff9e678\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-72dccadf752b71eb","identity_text":"Allow extensions to use the server's cumulative statistics API (Michael Paquier)","part":"changes","patch_ids":["3eb79f54769a802749d52f97f9f8c4cd","4af802e5801cb1008a49bbd7ffb1b4c6"],"related_changes":[],"relations":[],"section":"Additional Modules","section_path":["Additional Modules"],"source_commits":["2eff9e678","7949d9594"],"source_entry_id":"18.0/changes/191","source_hash":"7611ce1609aa627ae59449ba16bf0a6a11d238cb4b3f48d277fa6399e2615ef5","source_url":"/docs/release/18.0/#RELEASE-18-MODULES","statement_hash":"a6e76441b49e4dfc8c5b6323c846f1efe63f20730e0cc0450e6f197b1eb9b2a0","text":"Allow extensions to use the server's cumulative statistics API (Michael Paquier) § §","title":"Allow extensions to use the server's cumulative statistics API","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["6b652e6ce"],"commit_groups":[["6b652e6ce"]],"commits":["6b652e6ce"],"cves":[],"db_id":"222e3bfb3e07da2a4bb138e9b89a9ea9","html":"\u003cp\u003eAllow the queries of \u003ca href=\"/docs/18/sql-createtableas.html\" title=\"CREATE TABLE AS\"\u003e\u003cspan\u003eCREATE TABLE AS\u003c/span\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/sql-declare.html\" title=\"DECLARE\"\u003e\u003cspan\u003eDECLARE\u003c/span\u003e\u003c/a\u003e to be tracked by \u003cspan\u003epg_stat_statements\u003c/span\u003e (Anthonin Bonnefoy) \u003ca href=\"https://postgr.es/c/6b652e6ce\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThey are also now assigned query ids.\u003c/p\u003e","id":"18.0-f9d180ce3867ba06","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.","part":"changes","patch_ids":["6f27bba477d5d34ec287e6d1f0cb4c01"],"related_changes":[],"relations":[],"section":"Additional Modules / pg_stat_statements","section_path":["Additional Modules","pg_stat_statements"],"source_commits":["6b652e6ce"],"source_entry_id":"18.0/changes/192","source_hash":"a71330cbf6ff1fcbcb3577f9497064f4234185cd87242388194c557aabf1ba1b","source_url":"/docs/release/18.0/#RELEASE-18-PGSTATSTATEMENTS","statement_hash":"529743a734ea4d3d2e0ab03ec1c2bc3a516f21292fd3896db229b7e1ee80bdfd","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","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["dc6851596"],"commit_groups":[["dc6851596"]],"commits":["dc6851596"],"cves":[],"db_id":"d87ff3c638d05d56d3504f36a1d0eb9e","html":"\u003cp\u003eAllow the parameterization of \u003ca href=\"/docs/18/sql-set.html\" title=\"SET\"\u003e\u003cspan\u003eSET\u003c/span\u003e\u003c/a\u003e values in \u003cspan\u003epg_stat_statements\u003c/span\u003e (Greg Sabino Mullane, Michael Paquier) \u003ca href=\"https://postgr.es/c/dc6851596\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis reduces the bloat caused by \u003ccode\u003eSET\u003c/code\u003e statements with differing constants.\u003c/p\u003e","id":"18.0-9feb714b6e408a34","identity_text":"Allow the parameterization of sql-set values in pg_stat_statements (Greg Sabino Mullane, Michael Paquier) This reduces the bloat caused by SET statements with differing constants.","part":"changes","patch_ids":["3d32975392dfbf77a358e6067a48fe4d"],"related_changes":[],"relations":[],"section":"Additional Modules / pg_stat_statements","section_path":["Additional Modules","pg_stat_statements"],"source_commits":["dc6851596"],"source_entry_id":"18.0/changes/193","source_hash":"1f417978794e493fec83127f28bd0ea95e8b299c427563b1296dbcb2150ca0ca","source_url":"/docs/release/18.0/#RELEASE-18-PGSTATSTATEMENTS","statement_hash":"45589530b5dde17afb7b34a69cafc678f86039fa9b52d8c08a42e0052b5b7086","text":"Allow the parameterization of SET values in pg_stat_statements (Greg Sabino Mullane, Michael Paquier) § This reduces the bloat caused by SET statements with differing constants.","title":"Allow the parameterization of SET values in pg_stat_statements","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["cf54a2c00"],"commit_groups":[["cf54a2c00"]],"commits":["cf54a2c00"],"cves":[],"db_id":"823f8d0879e0c04f27c34b7a3b667631","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/pgstatstatements.html#PGSTATSTATEMENTS-PG-STAT-STATEMENTS\" title=\"F.32.1. The pg_stat_statements View\"\u003e\u003ccode\u003epg_stat_statements\u003c/code\u003e\u003c/a\u003e columns to report parallel activity (Guillaume Lelarge) \u003ca href=\"https://postgr.es/c/cf54a2c00\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThe new columns are \u003ccode\u003eparallel_workers_to_launch\u003c/code\u003e and \u003ccode\u003eparallel_workers_launched\u003c/code\u003e.\u003c/p\u003e","id":"18.0-58fe8ed3eb4ac00f","identity_text":"Add pg_stat_statements columns to report parallel activity (Guillaume Lelarge) The new columns are parallel_workers_to_launch and parallel_workers_launched.","part":"changes","patch_ids":["6831774269bf4d573b364772321f1d98"],"related_changes":[],"relations":[],"section":"Additional Modules / pg_stat_statements","section_path":["Additional Modules","pg_stat_statements"],"source_commits":["cf54a2c00"],"source_entry_id":"18.0/changes/194","source_hash":"4bea78cbf69168bd47d9d84472e256b83685ff82c01f4d938e37329c48e8034d","source_url":"/docs/release/18.0/#RELEASE-18-PGSTATSTATEMENTS","statement_hash":"9c17fad8b061e59f13e9c70ddcdc3c5fcd20b2bbfe2878b5ceac9531b5be3eca","text":"Add pg_stat_statements columns to report parallel activity (Guillaume Lelarge) § The new columns are parallel_workers_to_launch and parallel_workers_launched.","title":"Add pg_stat_statements columns to report parallel activity","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["ce5bcc4a9"],"commit_groups":[["ce5bcc4a9"]],"commits":["ce5bcc4a9"],"cves":[],"db_id":"04bb9752bb54f8a586216fc387f41183","html":"\u003cp\u003eAdd \u003ccode\u003epg_stat_statements\u003c/code\u003e.\u003ccode\u003ewal_buffers_full\u003c/code\u003e to report full \u003cacronym\u003eWAL\u003c/acronym\u003e buffers (Bertrand Drouvot) \u003ca href=\"https://postgr.es/c/ce5bcc4a9\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-319957903c0be0f5","identity_text":"Add pg_stat_statements.wal_buffers_full to report full WAL buffers (Bertrand Drouvot)","part":"changes","patch_ids":["b596d0e68f37807e59aa316714895446"],"related_changes":[],"relations":[],"section":"Additional Modules / pg_stat_statements","section_path":["Additional Modules","pg_stat_statements"],"source_commits":["ce5bcc4a9"],"source_entry_id":"18.0/changes/195","source_hash":"00483f0bb6bed3dc52e750abffeaaee664740c6aa8ceda1af850420bab8fdbfa","source_url":"/docs/release/18.0/#RELEASE-18-PGSTATSTATEMENTS","statement_hash":"70c55196e78f23063400ef5243fea51808dbb9887de6fb64c904a32c7882458f","text":"Add pg_stat_statements.wal_buffers_full to report full WAL buffers (Bertrand Drouvot) §","title":"Add pg_stat_statements.wal_buffers_full to report full WAL buffers","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["749a9e20c"],"commit_groups":[["749a9e20c"]],"commits":["749a9e20c"],"cves":[],"db_id":"6d930bd35ba876206f5a9813beccedcf","html":"\u003cp\u003eAdd \u003cspan\u003epgcrypto\u003c/span\u003e algorithms \u003ca href=\"/docs/18/pgcrypto.html#PGCRYPTO-CRYPT-ALGORITHMS\" title=\"Table F.18. Supported Algorithms for crypt()\"\u003e\u003ccode\u003esha256crypt\u003c/code\u003e\u003c/a\u003e and \u003ca href=\"/docs/18/pgcrypto.html#PGCRYPTO-CRYPT-ALGORITHMS\" title=\"Table F.18. Supported Algorithms for crypt()\"\u003e\u003ccode\u003esha512crypt\u003c/code\u003e\u003c/a\u003e (Bernd Helmle) \u003ca href=\"https://postgr.es/c/749a9e20c\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-454d1f7907667b27","identity_text":"Add pgcrypto algorithms sha256crypt and sha512crypt (Bernd Helmle)","part":"changes","patch_ids":["f5cd375f1c18937c407ef70ec720a716"],"related_changes":[],"relations":[],"section":"Additional Modules / pgcrypto","section_path":["Additional Modules","pgcrypto"],"source_commits":["749a9e20c"],"source_entry_id":"18.0/changes/196","source_hash":"80d5466488cbf40745c79ffbf3905ec0e844acdae70f987d6512d4b8d3b4f9ab","source_url":"/docs/release/18.0/#RELEASE-18-PGCRYPTO","statement_hash":"bff6b8e55820215a69430966b55770e950076a2a38845002186f696873fa2bd1","text":"Add pgcrypto algorithms sha256crypt and sha512crypt (Bernd Helmle) §","title":"Add pgcrypto algorithms sha256crypt and sha512crypt","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["9ad1b3d01"],"commit_groups":[["9ad1b3d01"]],"commits":["9ad1b3d01"],"cves":[],"db_id":"ec341ecdfcaabcd1827eb401ea40905d","html":"\u003cp\u003eAdd \u003ca href=\"/docs/18/pgcrypto.html#PGCRYPTO-RAW-ENC-FUNCS\" title=\"F.26.4. Raw Encryption Functions\"\u003e\u003cacronym\u003eCFB\u003c/acronym\u003e\u003c/a\u003e mode to \u003cspan\u003epgcrypto\u003c/span\u003e encryption and decryption (Umar Hayat) \u003ca href=\"https://postgr.es/c/9ad1b3d01\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-9cb3dbf5db925f06","identity_text":"Add CFB mode to pgcrypto encryption and decryption (Umar Hayat)","part":"changes","patch_ids":["b040d33a3888055fc5edf9f0c6e56795"],"related_changes":[],"relations":[],"section":"Additional Modules / pgcrypto","section_path":["Additional Modules","pgcrypto"],"source_commits":["9ad1b3d01"],"source_entry_id":"18.0/changes/197","source_hash":"7f5b08debbba5d1cc71560caa889a862bb5b8108f756e758ad8bc02d4921180a","source_url":"/docs/release/18.0/#RELEASE-18-PGCRYPTO","statement_hash":"7c89f9937951f96c3f497c06864857f8e8c21ba76f5ef791d1eed77d00a71e81","text":"Add CFB mode to pgcrypto encryption and decryption (Umar Hayat) §","title":"Add CFB mode to pgcrypto encryption and decryption","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["924d89a35"],"commit_groups":[["924d89a35"]],"commits":["924d89a35"],"cves":[],"db_id":"861402831b46a55debf94f9e181d24e4","html":"\u003cp\u003eAdd function \u003ca href=\"/docs/18/pgcrypto.html#PGCRYPTO-OPENSSL-SUPPORT-FUNCS\" title=\"F.26.6. OpenSSL Support Functions\"\u003e\u003ccode\u003efips_mode()\u003c/code\u003e\u003c/a\u003e to report the server's \u003cacronym\u003eFIPS\u003c/acronym\u003e mode (Daniel Gustafsson) \u003ca href=\"https://postgr.es/c/924d89a35\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"18.0-e6ffde3f90c7ca5a","identity_text":"Add function fips_mode() to report the server's FIPS mode (Daniel Gustafsson)","part":"changes","patch_ids":["f3552518869c0bbfacbd3fcc442038d8"],"related_changes":[],"relations":[],"section":"Additional Modules / pgcrypto","section_path":["Additional Modules","pgcrypto"],"source_commits":["924d89a35"],"source_entry_id":"18.0/changes/198","source_hash":"6887df5888073525195bf750e494c1f0258185ce6b39a3b9c366aaf87bc467ea","source_url":"/docs/release/18.0/#RELEASE-18-PGCRYPTO","statement_hash":"54d83b9015ab399dec746f14f85c5f46ae4ed4dd02972e94a5ce579ee4817f1d","text":"Add function fips_mode() to report the server's FIPS mode (Daniel Gustafsson) §","title":"Add function fips_mode() to report the server's FIPS mode","variants":[],"version":"18.0"},{"also_in":[],"category":"feature","category_label":"Features","commit_aliases":["035f99cbe"],"commit_groups":[["035f99cbe"]],"commits":["035f99cbe"],"cves":[],"db_id":"85292659fb670a2d9202838e30370170","html":"\u003cp\u003eAdd \u003cspan\u003epgcrypto\u003c/span\u003e server variable \u003ca href=\"/docs/18/pgcrypto.html#PGCRYPTO-CONFIGURATION-PARAMETERS-BUILTIN_CRYPTO_ENABLED\"\u003e\u003ccode\u003ebuiltin_crypto_enabled\u003c/code\u003e\u003c/a\u003e to allow disabling builtin non-\u003cacronym\u003eFIPS\u003c/acronym\u003e mode cryptographic functions (Daniel Gustafsson, Joe Conway) \u003ca href=\"https://postgr.es/c/035f99cbe\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eThis is useful for guaranteeing \u003cacronym\u003eFIPS\u003c/acronym\u003e mode behavior.\u003c/p\u003e","id":"18.0-1c1c15834b2fb0f5","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.","part":"changes","patch_ids":["c996d7a6dfbb6918d1e1c1bdc8763d5d"],"related_changes":[],"relations":[],"section":"Additional Modules / pgcrypto","section_path":["Additional Modules","pgcrypto"],"source_commits":["035f99cbe"],"source_entry_id":"18.0/changes/199","source_hash":"7ec37d9ad093c24c937b540278b9a28ded5495aa79ee7e13b25b399ad32123f6","source_url":"/docs/release/18.0/#RELEASE-18-PGCRYPTO","statement_hash":"9c517ea3b0ae09d9ac23588dcc459bf5530faea31bee9ef47a11255f44c8ee81","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","variants":[],"version":"18.0"}],"entry_count":210,"eol":"2030-11-14","eol_date":"2030-11-14","label":"18.0","major":"18","manual":"18","manual_build":"18.6","manual_url":"/docs/18/release-18.html","migration_html":"\u003cp\u003eA dump/restore using \u003ca href=\"/docs/18/app-pg-dumpall.html\" title=\"pg_dumpall\"\u003e\u003cspan\u003e\u003cspan\u003epg_dumpall\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e or use of \u003ca href=\"/docs/18/pgupgrade.html\" title=\"pg_upgrade\"\u003e\u003cspan\u003e\u003cspan\u003epg_upgrade\u003c/span\u003e\u003c/span\u003e\u003c/a\u003e or logical replication is required for those wishing to migrate data from any previous release. See \u003ca href=\"/docs/18/upgrading.html\" title=\"18.6. Upgrading a PostgreSQL Cluster\"\u003eSection 18.6\u003c/a\u003e for general information on migrating to new major releases.\u003c/p\u003e\n\u003cp\u003eVersion 18 contains a number of changes that may affect compatibility with previous releases. Observe the following incompatibilities:\u003c/p\u003e\n\u003cdiv\u003e\n\u003c/div\u003e","minor":0,"placeholder":false,"source_as_of":"","source_url":"/docs/release/18.0/","status":"stable","status_label":"Supported","support_days":1463,"supported":true,"version":"18.0"}],"history":{"candidates":["18.0","18.1","18.2","18.3","18.4","18.6"],"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"]},"release_count":6,"remaining_cves":[],"security_as_of":"2026-09-26","security_regressions":[],"source_as_of":"2026-09-26","stats":[{"count":297,"key":"all","label":"All changes"},{"count":188,"key":"feature","label":"Features"},{"count":49,"key":"bugfix","label":"Bug fixes"},{"count":3,"key":"security","label":"Security"},{"count":10,"key":"performance","label":"Performance"},{"count":11,"key":"compatibility","label":"Compatibility"},{"count":36,"key":"improvement","label":"Improvements"}],"to_release":{"age_days":91,"build":"18.6","changes_count":140,"compatibility_count":0,"content_hash":"575a5072ec6e2481991ad0b4cdb89c632870708db9b883a92a47d5e531533bab","date":"2026-08-13","date_text":"2026-08-13","doc_git":"","doc_loaded_at":"2026-09-25T02:22:44.760693","entry_count":140,"eol":"2030-11-14","eol_date":"2030-11-14","label":"18.6","major":"18","manual":"18","manual_build":"18.6","manual_url":"/docs/18/release-18-6.html","migration_html":"\u003cp\u003eA dump/restore is not required for those running 18.X.\u003c/p\u003e\n\u003cp\u003eHowever, the first three security entries below describe configuration adjustments and data cleanups that you may need to make after updating.\u003c/p\u003e\n\u003cp\u003eAlso, if you have any GIN indexes, see the changelog entry below about possibly-corrupt \u003ccode\u003ereltuples\u003c/code\u003e values for their tables.\u003c/p\u003e\n\u003cp\u003eAlso, if you use \u003ccode\u003econtrib/btree_gist\u003c/code\u003e or \u003ccode\u003econtrib/ltree\u003c/code\u003e, you may need to reindex indexes made with those extensions; see the relevant entries below.\u003c/p\u003e\n\u003cp\u003eAlso, if you are upgrading from a version earlier than 18.2, see \u003ca href=\"/docs/18/release-18-2.html\" title=\"E.4. Release 18.2\"\u003eSection E.4\u003c/a\u003e.\u003c/p\u003e","minor":6,"placeholder":false,"source_as_of":"","source_url":"/docs/release/18.6/","status":"stable","status_label":"Supported","support_days":1463,"supported":true,"version":"18.6"},"total":297,"warnings":[]}