{"already_in_source_count":0,"candidate_count":59,"cross_major":false,"cve_available":true,"cve_count":3,"cves":[{"affected":{"11":"11","12":"12","13":"13","14":"14","15":"15","16":"16"},"component":"core server","cvss_version":"3.0","description_en":"While modifying certain SQL array values, missing overflow checks let authenticated database users write arbitrary bytes to a memory area that facilitates arbitrary code execution. Missing overflow checks also let authenticated database users read a wide area of server memory. The CVE-2021-32027 fix covered some attacks of this description, but it missed others.\n\nThe PostgreSQL project thanks Pedro Gallegos for reporting this problem.","first_published":"2023-11-09","fixed":{"11":"11.22","12":"12.17","13":"13.13","14":"14.10","15":"15.5","16":"16.1"},"fixed_version":"16.1","id":"CVE-2023-5869","introduced":{},"published":{"11":"2023-11-09","12":"2023-11-09","13":"2023-11-09","14":"2023-11-09","15":"2023-11-09","16":"2023-11-09"},"score":8.8,"title":"检测计算新数组维度时的整数溢出","url":"https://www.postgresql.org/support/security/CVE-2023-5869/","vector":"AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"},{"affected":{"11":"11","12":"12","13":"13","14":"14","15":"15","16":"16"},"component":"core server","cvss_version":"3.0","description_en":"Certain aggregate function calls receiving \"unknown\"-type arguments could disclose bytes of server memory from the end of the \"unknown\"-type value to the next zero byte. One typically gets an \"unknown\"-type value via a string literal having no type designation. We have not confirmed or ruled out viability of attacks that arrange for presence of notable, confidential information in disclosed bytes.\n\nThe PostgreSQL project thanks Jingzhou Fu for reporting this problem.","first_published":"2023-11-09","fixed":{"11":"11.22","12":"12.17","13":"13.13","14":"14.10","15":"15.5","16":"16.1"},"fixed_version":"16.1","id":"CVE-2023-5868","introduced":{},"published":{"11":"2023-11-09","12":"2023-11-09","13":"2023-11-09","14":"2023-11-09","15":"2023-11-09","16":"2023-11-09"},"score":4.3,"title":"修复 DISTINCT \"any\" 聚合函数中对未知类型参数的处理","url":"https://www.postgresql.org/support/security/CVE-2023-5868/","vector":"AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N"},{"affected":{"11":"11","12":"12","13":"13","14":"14","15":"15","16":"16"},"component":"core server","cvss_version":"3.0","description_en":"Documentation says the pg_signal_backend role cannot signal \"a backend owned by a superuser\". On the contrary, it can signal background workers, including the logical replication launcher. It can signal autovacuum workers and the autovacuum launcher. Signaling autovacuum workers and those two launchers provides no meaningful exploit, so exploiting this vulnerability requires a non-core extension with a less-resilient background worker. For example, a non-core background worker that does not auto-restart would experience a denial of service with respect to that particular background worker.\n\nThe PostgreSQL project thanks Hemanth Sandrana and Mahendrakar Srinivasarao for reporting this problem.","first_published":"2023-11-09","fixed":{"11":"11.22","12":"12.17","13":"13.13","14":"14.10","15":"15.5","16":"16.1"},"fixed_version":"16.1","id":"CVE-2023-5870","introduced":{},"published":{"11":"2023-11-09","12":"2023-11-09","13":"2023-11-09","14":"2023-11-09","15":"2023-11-09","16":"2023-11-09"},"score":2.2,"title":"防止 pg_signal_backend 角色向后台工作进程和自动清理进程发送信号","url":"https://www.postgresql.org/support/security/CVE-2023-5870/","vector":"AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:N/A:L"}],"duplicate_count":0,"excluded_count":0,"exclusions":[],"from_release":null,"groups":[{"age_days":1067,"build":"16.1","changes_count":59,"compatibility_count":0,"content_hash":"62c73002569d60f9b018256836ce4baa47367fb23cff88dbe0286ed92bbe8494","date":"2023-11-09","date_text":"2023-11-09","doc_git":"","doc_loaded_at":"2026-09-26T02:56:37.084400","entries":[{"also_in":[],"category":"security","category_label":"Security","commit_aliases":["3b0776fde","4f4a422fb","8c6633f4d","9146d0d65","d3d1e2509","d3de70fdb","e911afd09"],"commit_groups":[["3b0776fde","4f4a422fb","8c6633f4d","9146d0d65","d3d1e2509","d3de70fdb","e911afd09"]],"commits":["d3d1e2509"],"cves":["CVE-2023-5868"],"db_id":"99b0ad14eb1a1212a1b58eba457cddaf","html":"\u003cp\u003e修复 \u003ccode\u003eDISTINCT\u003c/code\u003e \u003ccode\u003e\"any\"\u003c/code\u003e 聚合函数中对未知类型参数的处理（Tom Lane）\u003ca href=\"https://postgr.es/c/d3d1e2509\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e此错误导致 \u003ccode\u003etext\u003c/code\u003e 类型的值在运行时被解释为 \u003ccode\u003eunknown\u003c/code\u003e 类型的值（即以零终止的字符串）。这可能导致泄露 \u003ccode\u003etext\u003c/code\u003e 值之后的服务器内存。\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003ePostgreSQL\u003c/span\u003e 项目感谢 Jingzhou Fu 报告此问题。（CVE-2023-5868）\u003c/p\u003e","id":"16.1-f4a32f59543aa7d4","identity_text":"Fix handling of unknown-type arguments in DISTINCT \"any\" aggregate functions (Tom Lane) This error led to a text-type value being interpreted as an unknown-type value (that is, a zero-terminated string) at runtime. This could result in disclosure of server memory following the text value. The PostgreSQL Project thanks Jingzhou Fu for reporting this problem. (CVE-2023-5868)","part":"changes","patch_ids":["377783eb6ed06698ffae0a66dac5d5af"],"related_changes":[{"db_id":"5f9df7523a98b9b77b643a8e78b33c9f","evidence":{"patch_ids":["377783eb6ed06698ffae0a66dac5d5af"],"same_day":true,"statement_hash":"bf7258f7eeb548923cd5038b3937b14fb41e52398a82fc2f455c997e83cdb422"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复 DISTINCT \"any\" 聚合函数中对未知类型参数的处理","url":"/docs/compare/?release=15.5#15.5-007533800ff37dbc","version":"15.5"},{"db_id":"f5153bd2bddb2965fe2e2dcf7419bf67","evidence":{"patch_ids":["377783eb6ed06698ffae0a66dac5d5af"],"same_day":true,"statement_hash":"bf7258f7eeb548923cd5038b3937b14fb41e52398a82fc2f455c997e83cdb422"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复 DISTINCT \"any\" 聚合函数中对未知类型参数的处理","url":"/docs/compare/?release=14.10#14.10-02faee33a889dd5e","version":"14.10"},{"db_id":"411ed3e5d2a9be5f075e65357cb57db3","evidence":{"patch_ids":["377783eb6ed06698ffae0a66dac5d5af"],"same_day":true,"statement_hash":"bf7258f7eeb548923cd5038b3937b14fb41e52398a82fc2f455c997e83cdb422"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复 DISTINCT \"any\" 聚合函数中对未知类型参数的处理","url":"/docs/compare/?release=13.13#13.13-cb74a975d65eb2b7","version":"13.13"},{"db_id":"c698278fc761a66399286e0735278ad7","evidence":{"patch_ids":["377783eb6ed06698ffae0a66dac5d5af"],"same_day":true,"statement_hash":"bf7258f7eeb548923cd5038b3937b14fb41e52398a82fc2f455c997e83cdb422"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"修复 DISTINCT \"any\" 聚合函数中对未知类型参数的处理","url":"/docs/compare/?release=12.17#12.17-98e305aa20a51a8c","version":"12.17"},{"db_id":"b0e41cd3662df33978f634d732140974","evidence":{"patch_ids":["377783eb6ed06698ffae0a66dac5d5af"],"same_day":true,"statement_hash":"bf7258f7eeb548923cd5038b3937b14fb41e52398a82fc2f455c997e83cdb422"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"修复 DISTINCT \"any\" 聚合函数中对未知类型参数的处理","url":"/docs/compare/?release=11.22#11.22-88a15e360ecf1c36","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["377783eb6ed06698ffae0a66dac5d5af"],"same_day":true,"statement_hash":"bf7258f7eeb548923cd5038b3937b14fb41e52398a82fc2f455c997e83cdb422"},"rule":2,"target":"411ed3e5d2a9be5f075e65357cb57db3","type":"equivalent"},{"evidence":{"patch_ids":["377783eb6ed06698ffae0a66dac5d5af"],"same_day":true,"statement_hash":"bf7258f7eeb548923cd5038b3937b14fb41e52398a82fc2f455c997e83cdb422"},"rule":2,"target":"5f9df7523a98b9b77b643a8e78b33c9f","type":"equivalent"},{"evidence":{"patch_ids":["377783eb6ed06698ffae0a66dac5d5af"],"same_day":true,"statement_hash":"bf7258f7eeb548923cd5038b3937b14fb41e52398a82fc2f455c997e83cdb422"},"rule":2,"target":"b0e41cd3662df33978f634d732140974","type":"equivalent"},{"evidence":{"patch_ids":["377783eb6ed06698ffae0a66dac5d5af"],"same_day":true,"statement_hash":"bf7258f7eeb548923cd5038b3937b14fb41e52398a82fc2f455c997e83cdb422"},"rule":2,"target":"c698278fc761a66399286e0735278ad7","type":"equivalent"},{"evidence":{"patch_ids":["377783eb6ed06698ffae0a66dac5d5af"],"same_day":true,"statement_hash":"bf7258f7eeb548923cd5038b3937b14fb41e52398a82fc2f455c997e83cdb422"},"rule":2,"target":"f5153bd2bddb2965fe2e2dcf7419bf67","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["d3d1e2509"],"source_entry_id":"16.1/changes/001","source_hash":"c8f5501a2e1f21977339326f8f14952a76b3661eba1c3588d381373a1c39916b","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"bf7258f7eeb548923cd5038b3937b14fb41e52398a82fc2f455c997e83cdb422","text":"修复 DISTINCT \"any\" 聚合函数中对未知类型参数的处理（Tom Lane）§ 此错误导致 text 类型的值在运行时被解释为 unknown 类型的值（即以零终止的字符串）。这可能导致泄露 text 值之后的服务器内存。 PostgreSQL 项目感谢 Jingzhou Fu 报告此问题。（CVE-2023-5868）","title":"修复 DISTINCT \"any\" 聚合函数中对未知类型参数的处理","variants":[],"version":"16.1"},{"also_in":[],"category":"security","category_label":"Security","commit_aliases":["18b585155","26c599beb","3bc6bc3ee","c48008f59","d267cea24","e24daa94b","edc0a8d82"],"commit_groups":[["18b585155","26c599beb","3bc6bc3ee","c48008f59","d267cea24","e24daa94b","edc0a8d82"]],"commits":["e24daa94b"],"cves":["CVE-2023-5869"],"db_id":"bf9a8d1e1a2f36fc165ec2db760161d6","html":"\u003cp\u003e检测计算新数组维度时的整数溢出（Tom Lane）\u003ca href=\"https://postgr.es/c/e24daa94b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e当向超出当前数组边界的数组下标赋予新元素时，在极端情况下可能发生未检测到的整数溢出。可能利用内存越界写入来执行任意代码，也可能泄露服务器内存。\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003ePostgreSQL\u003c/span\u003e 项目感谢 Pedro Gallegos 报告此问题。（CVE-2023-5869）\u003c/p\u003e","id":"16.1-4c16ed3bd29aa177","identity_text":"Detect integer overflow while computing new array dimensions (Tom Lane) When assigning new elements to array subscripts that are outside the current array bounds, an undetected integer overflow could occur in edge cases. Memory stomps that are potentially exploitable for arbitrary code execution are possible, and so is disclosure of server memory. The PostgreSQL Project thanks Pedro Gallegos for reporting this problem. (CVE-2023-5869)","part":"changes","patch_ids":["00147d3eddf145838149e503b27471ba"],"related_changes":[{"db_id":"cb3a97594563bb28577f0b455189e032","evidence":{"patch_ids":["00147d3eddf145838149e503b27471ba"],"same_day":true,"statement_hash":"635846be981662e45373dc6783ce309a45134b56196850d31be1570d67652f4a"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"检测计算新数组维度时的整数溢出","url":"/docs/compare/?release=15.5#15.5-e6fff3ddb818bbdf","version":"15.5"},{"db_id":"53a48386c7c2b0738e20233af123cb83","evidence":{"patch_ids":["00147d3eddf145838149e503b27471ba"],"same_day":true,"statement_hash":"635846be981662e45373dc6783ce309a45134b56196850d31be1570d67652f4a"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"检测计算新数组维度时的整数溢出","url":"/docs/compare/?release=14.10#14.10-581b45cad797a532","version":"14.10"},{"db_id":"d439c86ebeb0e6972d7e13755cb2cea9","evidence":{"patch_ids":["00147d3eddf145838149e503b27471ba"],"same_day":true,"statement_hash":"635846be981662e45373dc6783ce309a45134b56196850d31be1570d67652f4a"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"检测计算新数组维度时的整数溢出","url":"/docs/compare/?release=13.13#13.13-b3cd77d12b62df2b","version":"13.13"},{"db_id":"2c78902a72483c44567dbd0e43cf8db1","evidence":{"patch_ids":["00147d3eddf145838149e503b27471ba"],"same_day":true,"statement_hash":"635846be981662e45373dc6783ce309a45134b56196850d31be1570d67652f4a"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"检测计算新数组维度时的整数溢出","url":"/docs/compare/?release=12.17#12.17-77a934e216e7596b","version":"12.17"},{"db_id":"3ea179ce96b78d0ac28bb92db24d7bb5","evidence":{"patch_ids":["00147d3eddf145838149e503b27471ba"],"same_day":true,"statement_hash":"635846be981662e45373dc6783ce309a45134b56196850d31be1570d67652f4a"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"检测计算新数组维度时的整数溢出","url":"/docs/compare/?release=11.22#11.22-54f46ed4e9376414","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["00147d3eddf145838149e503b27471ba"],"same_day":true,"statement_hash":"635846be981662e45373dc6783ce309a45134b56196850d31be1570d67652f4a"},"rule":2,"target":"2c78902a72483c44567dbd0e43cf8db1","type":"equivalent"},{"evidence":{"patch_ids":["00147d3eddf145838149e503b27471ba"],"same_day":true,"statement_hash":"635846be981662e45373dc6783ce309a45134b56196850d31be1570d67652f4a"},"rule":2,"target":"3ea179ce96b78d0ac28bb92db24d7bb5","type":"equivalent"},{"evidence":{"patch_ids":["00147d3eddf145838149e503b27471ba"],"same_day":true,"statement_hash":"635846be981662e45373dc6783ce309a45134b56196850d31be1570d67652f4a"},"rule":2,"target":"53a48386c7c2b0738e20233af123cb83","type":"equivalent"},{"evidence":{"patch_ids":["00147d3eddf145838149e503b27471ba"],"same_day":true,"statement_hash":"635846be981662e45373dc6783ce309a45134b56196850d31be1570d67652f4a"},"rule":2,"target":"cb3a97594563bb28577f0b455189e032","type":"equivalent"},{"evidence":{"patch_ids":["00147d3eddf145838149e503b27471ba"],"same_day":true,"statement_hash":"635846be981662e45373dc6783ce309a45134b56196850d31be1570d67652f4a"},"rule":2,"target":"d439c86ebeb0e6972d7e13755cb2cea9","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["e24daa94b"],"source_entry_id":"16.1/changes/002","source_hash":"704321ea50e58bee8a9c0d8424bafbbe061e6a38ed1ad17ed97da20073d82e47","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"635846be981662e45373dc6783ce309a45134b56196850d31be1570d67652f4a","text":"检测计算新数组维度时的整数溢出（Tom Lane）§ 当向超出当前数组边界的数组下标赋予新元素时，在极端情况下可能发生未检测到的整数溢出。可能利用内存越界写入来执行任意代码，也可能泄露服务器内存。 PostgreSQL 项目感谢 Pedro Gallegos 报告此问题。（CVE-2023-5869）","title":"检测计算新数组维度时的整数溢出","variants":[],"version":"16.1"},{"also_in":[],"category":"security","category_label":"Security","commit_aliases":["2893f2f40","28b609550","2c3c5ec49","2c7a2a00a","3a9b18b30","508acb901","595c988c9","785412731","7bbf4d037","a27be40c1","b72de09a1","e082734c8","ecd5d240c","fbc371909"],"commit_groups":[["2893f2f40","28b609550","3a9b18b30","508acb901","595c988c9","785412731","e082734c8"],["2c3c5ec49","2c7a2a00a","7bbf4d037","a27be40c1","b72de09a1","ecd5d240c","fbc371909"]],"commits":["2c3c5ec49","785412731"],"cves":["CVE-2023-5870"],"db_id":"4b0992ca977f635c7758a17608f5e59f","html":"\u003cp\u003e防止 \u003ccode\u003epg_signal_backend\u003c/code\u003e 角色向后台工作进程和自动清理进程发送信号（Noah Misch，Jelte Fennema-Nio）\u003ca href=\"https://postgr.es/c/785412731\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/2c3c5ec49\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e文档说明 \u003ccode\u003epg_signal_backend\u003c/code\u003e 不能向超级用户拥有的进程发送信号。但它能够向这些后台进程发送信号，因为它们公布的角色 OID 为零。现在将此视为表示超级用户所有权。取消这些进程类型之一的安全影响就核心代码而言相当小（我们只会启动另一个），但扩展可能添加更容易受影响的后台工作进程。\u003c/p\u003e\n\u003cp\u003e同时确保在这些进程中正确设置 \u003ccode\u003eis_superuser\u003c/code\u003e 参数。对于该疏忽，目前没有已知的具体安全后果，但对于某些扩展来说可能是重要的。\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003ePostgreSQL\u003c/span\u003e 项目感谢 Hemanth Sandrana 和 Mahendrakar Srinivasarao 报告此问题。（CVE-2023-5870）\u003c/p\u003e","id":"16.1-bee2c1eaae999c16","identity_text":"Prevent the pg_signal_backend role from signalling background workers and autovacuum processes (Noah Misch, Jelte Fennema-Nio) The documentation says that pg_signal_backend cannot issue signals to superuser-owned processes. It was able to signal these background processes, though, because they advertise a role OID of zero. Treat that as indicating superuser ownership. The security implications of cancelling one of these process types are fairly small so far as the core code goes (we'll just start another one), but extensions might add background workers that are more vulnerable. Also ensure that the is_superuser parameter is set correctly in such processes. No specific security consequences are known for that oversight, but it might be significant for some extensions. The PostgreSQL Project thanks Hemanth Sandrana and Mahendrakar Srinivasarao for reporting this problem. (CVE-2023-5870)","part":"changes","patch_ids":["8ead78d15b6001e9b1dadb64d2686862","fe5f7d00b5b89117d583e472e94ac48a"],"related_changes":[{"db_id":"f4ba501cfe72d1a5acc9ceb661c83667","evidence":{"patch_ids":["8ead78d15b6001e9b1dadb64d2686862","fe5f7d00b5b89117d583e472e94ac48a"],"same_day":true,"statement_hash":"23bc362c6c5807721e41d714ce6276b5d91f3b15af887efbc0d681a91541b844"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"防止 pg_signal_backend 角色向后台工作进程和自动清理进程发送信号","url":"/docs/compare/?release=15.5#15.5-edd37c3a2a604e66","version":"15.5"},{"db_id":"ba304364dca158290e41073934a3134c","evidence":{"patch_ids":["8ead78d15b6001e9b1dadb64d2686862","fe5f7d00b5b89117d583e472e94ac48a"],"same_day":true,"statement_hash":"23bc362c6c5807721e41d714ce6276b5d91f3b15af887efbc0d681a91541b844"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"防止 pg_signal_backend 角色向后台工作进程和自动清理进程发送信号","url":"/docs/compare/?release=14.10#14.10-ea5079e94edabc74","version":"14.10"},{"db_id":"aad7a037e7eea1cda3add2629e6504ff","evidence":{"patch_ids":["8ead78d15b6001e9b1dadb64d2686862","fe5f7d00b5b89117d583e472e94ac48a"],"same_day":true,"statement_hash":"23bc362c6c5807721e41d714ce6276b5d91f3b15af887efbc0d681a91541b844"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"防止 pg_signal_backend 角色向后台工作进程和自动清理进程发送信号","url":"/docs/compare/?release=13.13#13.13-2024116eff31fd4f","version":"13.13"},{"db_id":"67b664496af6540010383348f9d71ad4","evidence":{"patch_ids":["8ead78d15b6001e9b1dadb64d2686862","fe5f7d00b5b89117d583e472e94ac48a"],"same_day":true,"statement_hash":"23bc362c6c5807721e41d714ce6276b5d91f3b15af887efbc0d681a91541b844"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"防止 pg_signal_backend 角色向后台工作进程和自动清理进程发送信号","url":"/docs/compare/?release=12.17#12.17-5de0c13ef0792005","version":"12.17"},{"db_id":"6f6be896c75edd111e2b6617f47d957b","evidence":{"patch_ids":["8ead78d15b6001e9b1dadb64d2686862","fe5f7d00b5b89117d583e472e94ac48a"],"same_day":true,"statement_hash":"23bc362c6c5807721e41d714ce6276b5d91f3b15af887efbc0d681a91541b844"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"防止 pg_signal_backend 角色向后台工作进程和自动清理进程发送信号","url":"/docs/compare/?release=11.22#11.22-682c6fc45a019a5c","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["8ead78d15b6001e9b1dadb64d2686862","fe5f7d00b5b89117d583e472e94ac48a"],"same_day":true,"statement_hash":"23bc362c6c5807721e41d714ce6276b5d91f3b15af887efbc0d681a91541b844"},"rule":2,"target":"67b664496af6540010383348f9d71ad4","type":"equivalent"},{"evidence":{"patch_ids":["8ead78d15b6001e9b1dadb64d2686862","fe5f7d00b5b89117d583e472e94ac48a"],"same_day":true,"statement_hash":"23bc362c6c5807721e41d714ce6276b5d91f3b15af887efbc0d681a91541b844"},"rule":2,"target":"6f6be896c75edd111e2b6617f47d957b","type":"equivalent"},{"evidence":{"patch_ids":["8ead78d15b6001e9b1dadb64d2686862","fe5f7d00b5b89117d583e472e94ac48a"],"same_day":true,"statement_hash":"23bc362c6c5807721e41d714ce6276b5d91f3b15af887efbc0d681a91541b844"},"rule":2,"target":"aad7a037e7eea1cda3add2629e6504ff","type":"equivalent"},{"evidence":{"patch_ids":["8ead78d15b6001e9b1dadb64d2686862","fe5f7d00b5b89117d583e472e94ac48a"],"same_day":true,"statement_hash":"23bc362c6c5807721e41d714ce6276b5d91f3b15af887efbc0d681a91541b844"},"rule":2,"target":"ba304364dca158290e41073934a3134c","type":"equivalent"},{"evidence":{"patch_ids":["8ead78d15b6001e9b1dadb64d2686862","fe5f7d00b5b89117d583e472e94ac48a"],"same_day":true,"statement_hash":"23bc362c6c5807721e41d714ce6276b5d91f3b15af887efbc0d681a91541b844"},"rule":2,"target":"f4ba501cfe72d1a5acc9ceb661c83667","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["2c3c5ec49","785412731"],"source_entry_id":"16.1/changes/003","source_hash":"ec8c4f7d7ca30c6ecec37ff11be13c8ee78d47e3100a52f4aa49b59ddbcb6a70","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"23bc362c6c5807721e41d714ce6276b5d91f3b15af887efbc0d681a91541b844","text":"防止 pg_signal_backend 角色向后台工作进程和自动清理进程发送信号（Noah Misch，Jelte Fennema-Nio）§ § 文档说明 pg_signal_backend 不能向超级用户拥有的进程发送信号。但它能够向这些后台进程发送信号，因为它们公布的角色 OID 为零。现在将此视为表示超级用户所有权。取消这些进程类型之一的安全影响就核心代码而言相当小（我们只会启动另一个），但扩展可能添加更容易受影响的后台工作进程。 同时确保在这些进程中正确设置 is_superuser 参数。对于该疏忽，目前没有已知的具体安全后果，但对于某些扩展来说可能是重要的。 PostgreSQL 项目感谢 Hemanth Sandrana 和 Mahendrakar Srinivasarao 报告此问题。（CVE-2023-5870）","title":"防止 pg_signal_backend 角色向后台工作进程和自动清理进程发送信号","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["26917ebea","28d3c2ddc","747cef5a5","c3c284b37","d7f521325","db7394d4d"],"commit_groups":[["26917ebea","28d3c2ddc","747cef5a5","c3c284b37","d7f521325","db7394d4d"]],"commits":["d7f521325"],"cves":[],"db_id":"bfff1d6c07bb200f3982d273d15be0c5","html":"\u003cp\u003e修复 GiST 索引构建中递归页面分裂时的错误行为（Heikki Linnakangas）\u003ca href=\"https://postgr.es/c/d7f521325\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e修复了一个页面下行链接位置被错误跟踪的情况，并引入了一些逻辑来允许从此类情况中恢复，而不是静默地执行错误操作。此错误可能导致后续索引搜索返回不正确的结果。建议在安装此更新后重建所有 GiST 索引。\u003c/p\u003e","id":"16.1-9637104c834c3a09","identity_text":"Fix misbehavior during recursive page split in GiST index build (Heikki Linnakangas) Fix a case where the location of a page downlink was incorrectly tracked, and introduce some logic to allow recovering from such situations rather than silently doing the wrong thing. This error could result in incorrect answers from subsequent index searches. It may be advisable to reindex all GiST indexes after installing this update.","part":"changes","patch_ids":["dda8015b2cb7febbee0d8ec81b15e1f1"],"related_changes":[{"db_id":"c1e0614a5596d77272d473d776a05d82","evidence":{"patch_ids":["dda8015b2cb7febbee0d8ec81b15e1f1"],"same_day":true,"statement_hash":"5c3738c63cdf2d59adc87135bcac7d2486c5d29a6b3a04ce34d8ddb67192edfa"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复 GiST 索引构建中递归页面分裂时的错误行为","url":"/docs/compare/?release=15.5#15.5-ca9856742c0d9b93","version":"15.5"},{"db_id":"f8d168b50c33bdb06dbbba6b3a70b4c2","evidence":{"patch_ids":["dda8015b2cb7febbee0d8ec81b15e1f1"],"same_day":true,"statement_hash":"5c3738c63cdf2d59adc87135bcac7d2486c5d29a6b3a04ce34d8ddb67192edfa"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复 GiST 索引构建中递归页面分裂时的错误行为","url":"/docs/compare/?release=14.10#14.10-d1b2459041361b0a","version":"14.10"},{"db_id":"41d33305cccfb4f8758f8e889cc1bad2","evidence":{"patch_ids":["dda8015b2cb7febbee0d8ec81b15e1f1"],"same_day":true,"statement_hash":"5c3738c63cdf2d59adc87135bcac7d2486c5d29a6b3a04ce34d8ddb67192edfa"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复 GiST 索引构建中递归页面分裂时的错误行为","url":"/docs/compare/?release=13.13#13.13-39edf4f51df72bcd","version":"13.13"},{"db_id":"2a7ddeba40f11da483b6c48eeaebb284","evidence":{"patch_ids":["dda8015b2cb7febbee0d8ec81b15e1f1"],"same_day":true,"statement_hash":"5c3738c63cdf2d59adc87135bcac7d2486c5d29a6b3a04ce34d8ddb67192edfa"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"修复 GiST 索引构建中递归页面分裂时的错误行为","url":"/docs/compare/?release=12.17#12.17-83be794e35c5e14a","version":"12.17"}],"relations":[{"evidence":{"patch_ids":["dda8015b2cb7febbee0d8ec81b15e1f1"],"same_day":true,"statement_hash":"5c3738c63cdf2d59adc87135bcac7d2486c5d29a6b3a04ce34d8ddb67192edfa"},"rule":2,"target":"2a7ddeba40f11da483b6c48eeaebb284","type":"equivalent"},{"evidence":{"patch_ids":["dda8015b2cb7febbee0d8ec81b15e1f1"],"same_day":true,"statement_hash":"5c3738c63cdf2d59adc87135bcac7d2486c5d29a6b3a04ce34d8ddb67192edfa"},"rule":2,"target":"41d33305cccfb4f8758f8e889cc1bad2","type":"equivalent"},{"evidence":{"patch_ids":["dda8015b2cb7febbee0d8ec81b15e1f1"],"same_day":true,"statement_hash":"5c3738c63cdf2d59adc87135bcac7d2486c5d29a6b3a04ce34d8ddb67192edfa"},"rule":2,"target":"c1e0614a5596d77272d473d776a05d82","type":"equivalent"},{"evidence":{"patch_ids":["dda8015b2cb7febbee0d8ec81b15e1f1"],"same_day":true,"statement_hash":"5c3738c63cdf2d59adc87135bcac7d2486c5d29a6b3a04ce34d8ddb67192edfa"},"rule":2,"target":"f8d168b50c33bdb06dbbba6b3a70b4c2","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["d7f521325"],"source_entry_id":"16.1/changes/004","source_hash":"1d46c4cffb49566e4344c3061cec2c7428dfb8ebaa041db274f3d692c87a6ff7","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"5c3738c63cdf2d59adc87135bcac7d2486c5d29a6b3a04ce34d8ddb67192edfa","text":"修复 GiST 索引构建中递归页面分裂时的错误行为（Heikki Linnakangas）§ 修复了一个页面下行链接位置被错误跟踪的情况，并引入了一些逻辑来允许从此类情况中恢复，而不是静默地执行错误操作。此错误可能导致后续索引搜索返回不正确的结果。建议在安装此更新后重建所有 GiST 索引。","title":"修复 GiST 索引构建中递归页面分裂时的错误行为","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["0834df909","5f27b5f84","6fd1dbdb2","782be0f71","bf1c21c4f"],"commit_groups":[["0834df909","5f27b5f84","6fd1dbdb2","782be0f71","bf1c21c4f"]],"commits":["bf1c21c4f"],"cves":[],"db_id":"bdd9a651ad30d749e407ffce635a70f6","html":"\u003cp\u003e防止对 \u003ccode\u003einterval\u003c/code\u003e 列的 B-树索引条目进行去重（Noah Misch）\u003ca href=\"https://postgr.es/c/bf1c21c4f\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e存在可区分但比较相等的 \u003ccode\u003einterval\u003c/code\u003e 值，例如 \u003ccode\u003e24:00:00\u003c/code\u003e 和 \u003ccode\u003e1 day\u003c/code\u003e。这违反了 B-树去重所做的假设，因此 \u003ccode\u003einterval\u003c/code\u003e 列需要从去重中排除。此疏忽可能导致仅索引扫描返回不正确的结果。此外，更新后 \u003cspan\u003eamcheck\u003c/span\u003e 将对几乎所有此类索引报告错误。用户应当重建 \u003ccode\u003einterval\u003c/code\u003e 列上的所有 B-树索引。\u003c/p\u003e","id":"16.1-56f53f7a899d03d9","identity_text":"Prevent de-duplication of btree index entries for interval columns (Noah Misch) There are interval values that are distinguishable but compare equal, for example 24:00:00 and 1 day. This breaks assumptions made by btree de-duplication, so interval columns need to be excluded from de-duplication. This oversight can cause incorrect results from index-only scans. Moreover, after updating amcheck will report an error for almost all such indexes. Users should reindex any btree indexes on interval columns.","part":"changes","patch_ids":["770ce32b7813901103fe23fb21b4ffeb"],"related_changes":[{"db_id":"e6d2faeabba2de947636ad76709dbec2","evidence":{"patch_ids":["770ce32b7813901103fe23fb21b4ffeb"],"same_day":true,"statement_hash":"a6745f00f7053fdc5d93931e78e339cd0275c54067e4154f5fdaece98dd7cc26"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"防止对 interval 列的 B-树索引条目进行去重","url":"/docs/compare/?release=15.5#15.5-04f10e64c06fbe6f","version":"15.5"},{"db_id":"f94c80d3702648f88e51766968050275","evidence":{"patch_ids":["770ce32b7813901103fe23fb21b4ffeb"],"same_day":true,"statement_hash":"a6745f00f7053fdc5d93931e78e339cd0275c54067e4154f5fdaece98dd7cc26"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"防止对 interval 列的 B-树索引条目进行去重","url":"/docs/compare/?release=14.10#14.10-1f652351dd5ca6f8","version":"14.10"},{"db_id":"2ceb2742b948456e32736fbefc247941","evidence":{"patch_ids":["770ce32b7813901103fe23fb21b4ffeb"],"same_day":true,"statement_hash":"a6745f00f7053fdc5d93931e78e339cd0275c54067e4154f5fdaece98dd7cc26"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"防止对 interval 列的 B-树索引条目进行去重","url":"/docs/compare/?release=13.13#13.13-ad75943739d781e6","version":"13.13"}],"relations":[{"evidence":{"patch_ids":["770ce32b7813901103fe23fb21b4ffeb"],"same_day":true,"statement_hash":"a6745f00f7053fdc5d93931e78e339cd0275c54067e4154f5fdaece98dd7cc26"},"rule":2,"target":"2ceb2742b948456e32736fbefc247941","type":"equivalent"},{"evidence":{"patch_ids":["770ce32b7813901103fe23fb21b4ffeb"],"same_day":true,"statement_hash":"a6745f00f7053fdc5d93931e78e339cd0275c54067e4154f5fdaece98dd7cc26"},"rule":2,"target":"e6d2faeabba2de947636ad76709dbec2","type":"equivalent"},{"evidence":{"patch_ids":["770ce32b7813901103fe23fb21b4ffeb"],"same_day":true,"statement_hash":"a6745f00f7053fdc5d93931e78e339cd0275c54067e4154f5fdaece98dd7cc26"},"rule":2,"target":"f94c80d3702648f88e51766968050275","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["bf1c21c4f"],"source_entry_id":"16.1/changes/005","source_hash":"7775ea43598386dce7997c0bbe1a2e97892d91d569f35f359a7ea4d7b0001693","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"a6745f00f7053fdc5d93931e78e339cd0275c54067e4154f5fdaece98dd7cc26","text":"防止对 interval 列的 B-树索引条目进行去重（Noah Misch）§ 存在可区分但比较相等的 interval 值，例如 24:00:00 和 1 day。这违反了 B-树去重所做的假设，因此 interval 列需要从去重中排除。此疏忽可能导致仅索引扫描返回不正确的结果。此外，更新后 amcheck 将对几乎所有此类索引报告错误。用户应当重建 interval 列上的所有 B-树索引。","title":"防止对 interval 列的 B-树索引条目进行去重","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["088233f8d","394d51731","d1740e169","e7965226d"],"commit_groups":[["088233f8d","394d51731","d1740e169","e7965226d"]],"commits":["e7965226d"],"cves":[],"db_id":"54993f9ecfae1876b620371fc919195a","html":"\u003cp\u003e在 BRIN \u003ccode\u003edatetime_minmax_multi_ops\u003c/code\u003e 索引中更合理地处理 \u003ccode\u003edate\u003c/code\u003e 值（Tomas Vondra）\u003ca href=\"https://postgr.es/c/e7965226d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e日期的距离计算是反向的，导致了关于合并哪些条目的错误决策。索引仍然产生正确的结果，但效率远低于应有的水平。建议重建 \u003ccode\u003edate\u003c/code\u003e 列上的 BRIN \u003ccode\u003eminmax_multi\u003c/code\u003e 索引。\u003c/p\u003e","id":"16.1-4d2a92470d7a3596","identity_text":"Process date values more sanely in BRIN datetime_minmax_multi_ops indexes (Tomas Vondra) The distance calculation for dates was backward, causing poor decisions about which entries to merge. The index still produces correct results, but is much less efficient than it should be. Reindexing BRIN minmax_multi indexes on date columns is advisable.","part":"changes","patch_ids":["d9df1955ea7fa75deac8fbf85f007394"],"related_changes":[{"db_id":"f3871f66f8d8cbc99517cfb12af4aaec","evidence":{"patch_ids":["d9df1955ea7fa75deac8fbf85f007394"],"same_day":true,"statement_hash":"d7b4facb8d97061980cd3f77e42b4fc59384eb85b4d6d65e34e1afa0f91d6dd1"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"在 BRIN datetime_minmax_multi_ops 索引中更合理地处理 date 值","url":"/docs/compare/?release=15.5#15.5-bd6d32e496541e2d","version":"15.5"},{"db_id":"7f1ad2b3d8bd336e9ca34a9e3eaf3e79","evidence":{"patch_ids":["d9df1955ea7fa75deac8fbf85f007394"],"same_day":true,"statement_hash":"d7b4facb8d97061980cd3f77e42b4fc59384eb85b4d6d65e34e1afa0f91d6dd1"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"在 BRIN datetime_minmax_multi_ops 索引中更合理地处理 date 值","url":"/docs/compare/?release=14.10#14.10-e3bada6d50e267ab","version":"14.10"}],"relations":[{"evidence":{"patch_ids":["d9df1955ea7fa75deac8fbf85f007394"],"same_day":true,"statement_hash":"d7b4facb8d97061980cd3f77e42b4fc59384eb85b4d6d65e34e1afa0f91d6dd1"},"rule":2,"target":"7f1ad2b3d8bd336e9ca34a9e3eaf3e79","type":"equivalent"},{"evidence":{"patch_ids":["d9df1955ea7fa75deac8fbf85f007394"],"same_day":true,"statement_hash":"d7b4facb8d97061980cd3f77e42b4fc59384eb85b4d6d65e34e1afa0f91d6dd1"},"rule":2,"target":"f3871f66f8d8cbc99517cfb12af4aaec","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["e7965226d"],"source_entry_id":"16.1/changes/006","source_hash":"6c43dbd24a77c956d610554fa3c86722bdc1b57493f598af22d6c3c965bbfee9","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"d7b4facb8d97061980cd3f77e42b4fc59384eb85b4d6d65e34e1afa0f91d6dd1","text":"在 BRIN datetime_minmax_multi_ops 索引中更合理地处理 date 值（Tomas Vondra）§ 日期的距离计算是反向的，导致了关于合并哪些条目的错误决策。索引仍然产生正确的结果，但效率远低于应有的水平。建议重建 date 列上的 BRIN minmax_multi 索引。","title":"在 BRIN datetime_minmax_multi_ops 索引中更合理地处理 date 值","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["0635fe02b","497fc9208","52c934cc1","8da86d62a","90c4da6d4","b5489b75c","d04a9283b","daa7b0d7c"],"commit_groups":[["0635fe02b","90c4da6d4","b5489b75c","daa7b0d7c"],["497fc9208","52c934cc1","8da86d62a","d04a9283b"]],"commits":["0635fe02b","497fc9208"],"cves":[],"db_id":"c5156f42619392828bb32c558d27c1d5","html":"\u003cp\u003e在 BRIN \u003ccode\u003edatetime_minmax_multi_ops\u003c/code\u003e 索引中更合理地处理较大的 \u003ccode\u003etimestamp\u003c/code\u003e 和 \u003ccode\u003etimestamptz\u003c/code\u003e 值（Tomas Vondra）\u003ca href=\"https://postgr.es/c/497fc9208\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/0635fe02b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e无穷值被错误地视为与其他值距离为零而非较大距离，导致了关于合并哪些条目的错误决策。此外，有限但非常大的值（接近可表示时间戳范围的端点）可能导致内部溢出，同样导致错误决策。索引仍然产生正确的结果，但效率远低于应有的水平。如果列包含或曾经包含无穷值或非常大的有限值，建议重建 \u003ccode\u003etimestamp\u003c/code\u003e 和 \u003ccode\u003etimestamptz\u003c/code\u003e 列上的 BRIN \u003ccode\u003eminmax_multi\u003c/code\u003e 索引。\u003c/p\u003e","id":"16.1-9951c27c653ba69f","identity_text":"Process large timestamp and timestamptz values more sanely in BRIN datetime_minmax_multi_ops indexes (Tomas Vondra) Infinities were mistakenly treated as having distance zero rather than a large distance from other values, causing poor decisions about which entries to merge. Also, finite-but-very-large values (near the endpoints of the representable timestamp range) could result in internal overflows, again causing poor decisions. The index still produces correct results, but is much less efficient than it should be. Reindexing BRIN minmax_multi indexes on timestamp and timestamptz columns is advisable if the column contains, or has contained, infinities or large finite values.","part":"changes","patch_ids":["54c8f086341979006a41b844982c3bcc","b154a139e677d19e4ab71e35b4be09c2"],"related_changes":[{"db_id":"d3325736fffd2357c33d0bbad7349f3c","evidence":{"patch_ids":["54c8f086341979006a41b844982c3bcc","b154a139e677d19e4ab71e35b4be09c2"],"same_day":true,"statement_hash":"4e3053c8c0fa6710166610553b61dd2a37217a30eeacb0c1be6339ec8aa4fbfc"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"在 BRIN datetime_minmax_multi_ops 索引中更合理地处理较大的 timestamp 和 timestamptz 值","url":"/docs/compare/?release=15.5#15.5-89cf161f0d54ab6e","version":"15.5"},{"db_id":"edb997b3349877ecda675f3ae5a9a500","evidence":{"patch_ids":["54c8f086341979006a41b844982c3bcc","b154a139e677d19e4ab71e35b4be09c2"],"same_day":true,"statement_hash":"4e3053c8c0fa6710166610553b61dd2a37217a30eeacb0c1be6339ec8aa4fbfc"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"在 BRIN datetime_minmax_multi_ops 索引中更合理地处理较大的 timestamp 和 timestamptz 值","url":"/docs/compare/?release=14.10#14.10-83b45125eb2d2d2f","version":"14.10"}],"relations":[{"evidence":{"patch_ids":["54c8f086341979006a41b844982c3bcc","b154a139e677d19e4ab71e35b4be09c2"],"same_day":true,"statement_hash":"4e3053c8c0fa6710166610553b61dd2a37217a30eeacb0c1be6339ec8aa4fbfc"},"rule":2,"target":"d3325736fffd2357c33d0bbad7349f3c","type":"equivalent"},{"evidence":{"patch_ids":["54c8f086341979006a41b844982c3bcc","b154a139e677d19e4ab71e35b4be09c2"],"same_day":true,"statement_hash":"4e3053c8c0fa6710166610553b61dd2a37217a30eeacb0c1be6339ec8aa4fbfc"},"rule":2,"target":"edb997b3349877ecda675f3ae5a9a500","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["0635fe02b","497fc9208"],"source_entry_id":"16.1/changes/007","source_hash":"efd9bf0a0714e80efd8ca82ad440d0842c9d4671b7213d44ec86803675a9b93b","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"4e3053c8c0fa6710166610553b61dd2a37217a30eeacb0c1be6339ec8aa4fbfc","text":"在 BRIN datetime_minmax_multi_ops 索引中更合理地处理较大的 timestamp 和 timestamptz 值（Tomas Vondra）§ § 无穷值被错误地视为与其他值距离为零而非较大距离，导致了关于合并哪些条目的错误决策。此外，有限但非常大的值（接近可表示时间戳范围的端点）可能导致内部溢出，同样导致错误决策。索引仍然产生正确的结果，但效率远低于应有的水平。如果列包含或曾经包含无穷值或非常大的有限值，建议重建 timestamp 和 timestamptz 列上的 BRIN minmax_multi 索引。","title":"在 BRIN datetime_minmax_multi_ops 索引中更合理地处理较大的 timestamp 和 timestamptz 值","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["0fa73c5cd","2fbb2fcb0","924e0e2ee","c6cf6d353"],"commit_groups":[["0fa73c5cd","2fbb2fcb0","924e0e2ee","c6cf6d353"]],"commits":["924e0e2ee"],"cves":[],"db_id":"7a7219460b6cde5f0286d2baaf3f3965","html":"\u003cp\u003e避免在包含极端 interval 值的 BRIN \u003ccode\u003einterval_minmax_multi_ops\u003c/code\u003e 索引中出现计算溢出（Tomas Vondra）\u003ca href=\"https://postgr.es/c/924e0e2ee\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e此错误可能在尝试向此类索引插入较大的 interval 值时导致意外失败。\u003c/p\u003e","id":"16.1-fae5c38c5ea997ed","identity_text":"Avoid calculation overflows in BRIN interval_minmax_multi_ops indexes with extreme interval values (Tomas Vondra) This bug might have caused unexpected failures while trying to insert large interval values into such an index.","part":"changes","patch_ids":["f69516fbdcc22c3c9557dcb4756468bb"],"related_changes":[{"db_id":"0d46d6de278474592fd1902949b38c6a","evidence":{"patch_ids":["f69516fbdcc22c3c9557dcb4756468bb"],"same_day":true,"statement_hash":"7060b57fcbbe4f22059beee39769d34361e408eb9d35e77f1b07d7781305f71b"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"避免在包含极端 interval 值的 BRIN interval_minmax_multi_ops 索引中出现计算溢出","url":"/docs/compare/?release=15.5#15.5-dd7cd8df42cba374","version":"15.5"},{"db_id":"ddb61f045493b5688c816ae466be5ed5","evidence":{"patch_ids":["f69516fbdcc22c3c9557dcb4756468bb"],"same_day":true,"statement_hash":"7060b57fcbbe4f22059beee39769d34361e408eb9d35e77f1b07d7781305f71b"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"避免在包含极端 interval 值的 BRIN interval_minmax_multi_ops 索引中出现计算溢出","url":"/docs/compare/?release=14.10#14.10-8cc787a4aeea6139","version":"14.10"}],"relations":[{"evidence":{"patch_ids":["f69516fbdcc22c3c9557dcb4756468bb"],"same_day":true,"statement_hash":"7060b57fcbbe4f22059beee39769d34361e408eb9d35e77f1b07d7781305f71b"},"rule":2,"target":"0d46d6de278474592fd1902949b38c6a","type":"equivalent"},{"evidence":{"patch_ids":["f69516fbdcc22c3c9557dcb4756468bb"],"same_day":true,"statement_hash":"7060b57fcbbe4f22059beee39769d34361e408eb9d35e77f1b07d7781305f71b"},"rule":2,"target":"ddb61f045493b5688c816ae466be5ed5","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["924e0e2ee"],"source_entry_id":"16.1/changes/008","source_hash":"f002383ab235dbc36f714526260c48e391ff41c4d8735177e6efdcb2b9ee66c7","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"7060b57fcbbe4f22059beee39769d34361e408eb9d35e77f1b07d7781305f71b","text":"避免在包含极端 interval 值的 BRIN interval_minmax_multi_ops 索引中出现计算溢出（Tomas Vondra）§ 此错误可能在尝试向此类索引插入较大的 interval 值时导致意外失败。","title":"避免在包含极端 interval 值的 BRIN interval_minmax_multi_ops 索引中出现计算溢出","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["07f261b31","1e81d3e6e","2759924f3","3cc0c2517","45c4b2a3a","595db9e9c","6352f1627","890a73ba3","916adc7c5","cd15bff48","cd259de50","d26f33c32","d9e46dfb7","f0c409d9c"],"commit_groups":[["07f261b31","45c4b2a3a","6352f1627","916adc7c5","cd15bff48","cd259de50","f0c409d9c"],["1e81d3e6e","2759924f3","3cc0c2517","595db9e9c","890a73ba3","d26f33c32","d9e46dfb7"]],"commits":["595db9e9c","6352f1627"],"cves":[],"db_id":"dd77435c0e6125d49df989fe8db335cd","html":"\u003cp\u003e修复具有多个分区键的 hash 分区表的分区步骤生成和运行时分区剪枝（David Rowley）\u003ca href=\"https://postgr.es/c/595db9e9c\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/6352f1627\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e某些涉及其中一个分区键上 \u003ccode\u003eIS NULL\u003c/code\u003e 条件的情况可能导致崩溃。\u003c/p\u003e","id":"16.1-7ec71dacea8cbc6e","identity_text":"Fix partition step generation and runtime partition pruning for hash-partitioned tables with multiple partition keys (David Rowley) Some cases involving an IS NULL condition on one of the partition keys could result in a crash.","part":"changes","patch_ids":["089066ebd8cde9ea0c9008c516ec4609","d19566760a24944db78a2cbec48c31ec"],"related_changes":[{"db_id":"74c67553eecfbe90431e7002fc3628dc","evidence":{"patch_ids":["089066ebd8cde9ea0c9008c516ec4609","d19566760a24944db78a2cbec48c31ec"],"same_day":true,"statement_hash":"e08385007c93dfd84e573ff7ff864aea3c0bc7baacb0f800105d8ccdb99015ef"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复具有多个分区键的 hash 分区表的分区步骤生成和运行时分区剪枝","url":"/docs/compare/?release=15.5#15.5-d7c067d920980424","version":"15.5"},{"db_id":"ad7a4f9421b4ade2c5b3a2ab544c11e0","evidence":{"patch_ids":["089066ebd8cde9ea0c9008c516ec4609","d19566760a24944db78a2cbec48c31ec"],"same_day":true,"statement_hash":"e08385007c93dfd84e573ff7ff864aea3c0bc7baacb0f800105d8ccdb99015ef"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复具有多个分区键的 hash 分区表的分区步骤生成和运行时分区剪枝","url":"/docs/compare/?release=14.10#14.10-09a3fc33a5e18424","version":"14.10"},{"db_id":"1d5d18322fc50f044ed62e35d1dff60e","evidence":{"patch_ids":["089066ebd8cde9ea0c9008c516ec4609","d19566760a24944db78a2cbec48c31ec"],"same_day":true,"statement_hash":"e08385007c93dfd84e573ff7ff864aea3c0bc7baacb0f800105d8ccdb99015ef"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复具有多个分区键的 hash 分区表的分区步骤生成和运行时分区剪枝","url":"/docs/compare/?release=13.13#13.13-8b5517c5a1bf0e21","version":"13.13"},{"db_id":"e4f0b27dd82aad5bd310ed111ff06b69","evidence":{"patch_ids":["089066ebd8cde9ea0c9008c516ec4609","d19566760a24944db78a2cbec48c31ec"],"same_day":true,"statement_hash":"e08385007c93dfd84e573ff7ff864aea3c0bc7baacb0f800105d8ccdb99015ef"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"修复具有多个分区键的 hash 分区表的分区步骤生成和运行时分区剪枝","url":"/docs/compare/?release=12.17#12.17-113a6572c411e1ab","version":"12.17"},{"db_id":"4b5cd2b510bdc0a67c23d65973f635dc","evidence":{"patch_ids":["089066ebd8cde9ea0c9008c516ec4609","d19566760a24944db78a2cbec48c31ec"],"same_day":true,"statement_hash":"e08385007c93dfd84e573ff7ff864aea3c0bc7baacb0f800105d8ccdb99015ef"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"修复具有多个分区键的 hash 分区表的分区步骤生成和运行时分区剪枝","url":"/docs/compare/?release=11.22#11.22-e6f4103effc07989","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["089066ebd8cde9ea0c9008c516ec4609","d19566760a24944db78a2cbec48c31ec"],"same_day":true,"statement_hash":"e08385007c93dfd84e573ff7ff864aea3c0bc7baacb0f800105d8ccdb99015ef"},"rule":2,"target":"1d5d18322fc50f044ed62e35d1dff60e","type":"equivalent"},{"evidence":{"patch_ids":["089066ebd8cde9ea0c9008c516ec4609","d19566760a24944db78a2cbec48c31ec"],"same_day":true,"statement_hash":"e08385007c93dfd84e573ff7ff864aea3c0bc7baacb0f800105d8ccdb99015ef"},"rule":2,"target":"4b5cd2b510bdc0a67c23d65973f635dc","type":"equivalent"},{"evidence":{"patch_ids":["089066ebd8cde9ea0c9008c516ec4609","d19566760a24944db78a2cbec48c31ec"],"same_day":true,"statement_hash":"e08385007c93dfd84e573ff7ff864aea3c0bc7baacb0f800105d8ccdb99015ef"},"rule":2,"target":"74c67553eecfbe90431e7002fc3628dc","type":"equivalent"},{"evidence":{"patch_ids":["089066ebd8cde9ea0c9008c516ec4609","d19566760a24944db78a2cbec48c31ec"],"same_day":true,"statement_hash":"e08385007c93dfd84e573ff7ff864aea3c0bc7baacb0f800105d8ccdb99015ef"},"rule":2,"target":"ad7a4f9421b4ade2c5b3a2ab544c11e0","type":"equivalent"},{"evidence":{"patch_ids":["089066ebd8cde9ea0c9008c516ec4609","d19566760a24944db78a2cbec48c31ec"],"same_day":true,"statement_hash":"e08385007c93dfd84e573ff7ff864aea3c0bc7baacb0f800105d8ccdb99015ef"},"rule":2,"target":"e4f0b27dd82aad5bd310ed111ff06b69","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["595db9e9c","6352f1627"],"source_entry_id":"16.1/changes/009","source_hash":"8b337f05ac716bf3cc36731d5553d6bf478dbcfffffbdbf518dcf3132b50bbde","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"e08385007c93dfd84e573ff7ff864aea3c0bc7baacb0f800105d8ccdb99015ef","text":"修复具有多个分区键的 hash 分区表的分区步骤生成和运行时分区剪枝（David Rowley）§ § 某些涉及其中一个分区键上 IS NULL 条件的情况可能导致崩溃。","title":"修复具有多个分区键的 hash 分区表的分区步骤生成和运行时分区剪枝","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["1d5caec22","3c1a1af91","6d2de076c"],"commit_groups":[["1d5caec22","3c1a1af91","6d2de076c"]],"commits":["6d2de076c"],"cves":[],"db_id":"98e1699da06c1915ca403b15f9198bc9","html":"\u003cp\u003e修复在 \u003ccode\u003eMERGE\u003c/code\u003e 期间对并发更新行的不一致重新检查（Dean Rasheed）\u003ca href=\"https://postgr.es/c/6d2de076c\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e在 \u003ccode\u003eREAD COMMITTED\u003c/code\u003e 模式下，一个更新如果发现其目标行刚被并发事务更新，将对更新后的行重新检查查询的 \u003ccode\u003eWHERE\u003c/code\u003e 条件。\u003ccode\u003eMERGE\u003c/code\u003e 未能确保在此重新检查期间使用其他连接表的正确行，可能导致关于新更新的行是否应再次被 \u003ccode\u003eMERGE\u003c/code\u003e 更新做出错误决策。\u003c/p\u003e","id":"16.1-1ae0bfbeaea33024","identity_text":"Fix inconsistent rechecking of concurrently-updated rows during MERGE (Dean Rasheed) In READ COMMITTED mode, an update that finds that its target row was just updated by a concurrent transaction will recheck the query's WHERE conditions on the updated row. MERGE failed to ensure that the proper rows of other joined tables were used during this recheck, possibly resulting in incorrect decisions about whether the newly-updated row should be updated again by MERGE.","part":"changes","patch_ids":["b5e3a44a6d3d5febb6dc28bd4283e589"],"related_changes":[{"db_id":"00359a0081125484984abc6bf7346bdc","evidence":{"patch_ids":["b5e3a44a6d3d5febb6dc28bd4283e589"],"same_day":true,"statement_hash":"145412d977c1f46171c76668cb30718dc367cb5d56f99478e96a5f772f238523"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复在 MERGE 期间对并发更新行的不一致重新检查","url":"/docs/compare/?release=15.5#15.5-eee14b818a774bdd","version":"15.5"}],"relations":[{"evidence":{"patch_ids":["b5e3a44a6d3d5febb6dc28bd4283e589"],"same_day":true,"statement_hash":"145412d977c1f46171c76668cb30718dc367cb5d56f99478e96a5f772f238523"},"rule":2,"target":"00359a0081125484984abc6bf7346bdc","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["6d2de076c"],"source_entry_id":"16.1/changes/010","source_hash":"5cebb8c18705ff26449a9df681d0bd069e99331cc5ff84a2a666b8cdfba12e73","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"145412d977c1f46171c76668cb30718dc367cb5d56f99478e96a5f772f238523","text":"修复在 MERGE 期间对并发更新行的不一致重新检查（Dean Rasheed）§ 在 READ COMMITTED 模式下，一个更新如果发现其目标行刚被并发事务更新，将对更新后的行重新检查查询的 WHERE 条件。MERGE 未能确保在此重新检查期间使用其他连接表的正确行，可能导致关于新更新的行是否应再次被 MERGE 更新做出错误决策。","title":"修复在 MERGE 期间对并发更新行的不一致重新检查","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["01575ad78","1268e7378","178ee1d85","1f06b7fc6","2bf99b48d","387f9ed0a","8f4a6b9e4","b1444a09d"],"commit_groups":[["01575ad78","178ee1d85"],["1268e7378","387f9ed0a","8f4a6b9e4","b1444a09d"],["1f06b7fc6","2bf99b48d"]],"commits":["178ee1d85","2bf99b48d","b1444a09d"],"cves":[],"db_id":"8322f7d9982b87ba2d9974b584129577","html":"\u003cp\u003e在继承的 \u003ccode\u003eUPDATE\u003c/code\u003e/\u003ccode\u003eDELETE\u003c/code\u003e/\u003ccode\u003eMERGE\u003c/code\u003e 中正确标识目标表，即使父表被约束排除（Amit Langote，Tom Lane）\u003ca href=\"https://postgr.es/c/b1444a09d\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/178ee1d85\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/2bf99b48d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e如果最初指定的表被约束排除，但并非其所有继承后代都被排除，则第一个未被排除的后代会被标识为主目标表。这会导致触发与该表关联的语句级触发器，而不是本应触发的最初指定的表的触发器。在 v16 中，同样的疏忽还可能导致 \u003cspan\u003e“\u003cspan\u003einvalid perminfoindex 0 in RTE with relid NNNN\u003c/span\u003e”\u003c/span\u003e 错误。\u003c/p\u003e","id":"16.1-8d59fdb168b8b653","identity_text":"Correctly identify the target table in an inherited UPDATE/DELETE/MERGE even when the parent table is excluded by constraints (Amit Langote, Tom Lane) If the initially-named table is excluded by constraints, but not all its inheritance descendants are, the first non-excluded descendant was identified as the primary target table. This would lead to firing statement-level triggers associated with that table, rather than the initially-named table as should happen. In v16, the same oversight could also lead to invalid perminfoindex 0 in RTE with relid NNNN errors.","part":"changes","patch_ids":["2e9435c5ff6b647b2e05bfe90186a891","d206fd6a20b245e9b593169ba2614be6","ddc408c57c9415868e91ac402e98520e"],"related_changes":[{"db_id":"d987a075ebd403450d2fb6a4e2e4068e","evidence":{"patch_ids":["2e9435c5ff6b647b2e05bfe90186a891","d206fd6a20b245e9b593169ba2614be6","ddc408c57c9415868e91ac402e98520e"],"same_day":true,"statement_hash":"2945baf49a3fa10572f71ef10fd9b38ae699b64a6fc6318346f2220ab5d40a66"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"在继承的 UPDATE/DELETE/MERGE 中正确标识目标表，即使父表被约束排除","url":"/docs/compare/?release=15.5#15.5-03842d84f3da3534","version":"15.5"},{"db_id":"e611f263f407c7bd86d247f985adceab","evidence":{"patch_ids":["2e9435c5ff6b647b2e05bfe90186a891","d206fd6a20b245e9b593169ba2614be6","ddc408c57c9415868e91ac402e98520e"],"same_day":true,"statement_hash":"2945baf49a3fa10572f71ef10fd9b38ae699b64a6fc6318346f2220ab5d40a66"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"在继承的 UPDATE/DELETE/MERGE 中正确标识目标表，即使父表被约束排除","url":"/docs/compare/?release=14.10#14.10-354d1c23feb774a2","version":"14.10"}],"relations":[{"evidence":{"patch_ids":["2e9435c5ff6b647b2e05bfe90186a891","d206fd6a20b245e9b593169ba2614be6","ddc408c57c9415868e91ac402e98520e"],"same_day":true,"statement_hash":"2945baf49a3fa10572f71ef10fd9b38ae699b64a6fc6318346f2220ab5d40a66"},"rule":2,"target":"d987a075ebd403450d2fb6a4e2e4068e","type":"equivalent"},{"evidence":{"patch_ids":["2e9435c5ff6b647b2e05bfe90186a891","d206fd6a20b245e9b593169ba2614be6","ddc408c57c9415868e91ac402e98520e"],"same_day":true,"statement_hash":"2945baf49a3fa10572f71ef10fd9b38ae699b64a6fc6318346f2220ab5d40a66"},"rule":2,"target":"e611f263f407c7bd86d247f985adceab","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["178ee1d85","2bf99b48d","b1444a09d"],"source_entry_id":"16.1/changes/011","source_hash":"a850748d1d92aa8c2f85211551fdc239f7f6cbd67220d4e4efa79be18b21b47e","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"2945baf49a3fa10572f71ef10fd9b38ae699b64a6fc6318346f2220ab5d40a66","text":"在继承的 UPDATE/DELETE/MERGE 中正确标识目标表，即使父表被约束排除（Amit Langote，Tom Lane）§ § § 如果最初指定的表被约束排除，但并非其所有继承后代都被排除，则第一个未被排除的后代会被标识为主目标表。这会导致触发与该表关联的语句级触发器，而不是本应触发的最初指定的表的触发器。在 v16 中，同样的疏忽还可能导致 “invalid perminfoindex 0 in RTE with relid NNNN” 错误。","title":"在继承的 UPDATE/DELETE/MERGE 中正确标识目标表，即使父表被约束排除","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["3fa81b62e","41486c4aa","714780dcd","7c07305e6","b36d72cbc","cac37c1a1","d4724e94a"],"commit_groups":[["3fa81b62e","41486c4aa","714780dcd","7c07305e6","b36d72cbc","cac37c1a1","d4724e94a"]],"commits":["3fa81b62e"],"cves":[],"db_id":"99d9c6ae915caa3b8dedfed9b19b44db","html":"\u003cp\u003e修复 B-树标记/恢复处理 ScalarArrayOpExpr 子句时的边界情况（Peter Geoghegan）\u003ca href=\"https://postgr.es/c/3fa81b62e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e将索引扫描恢复到先前标记的位置时，如果扫描恰好前进到 ScalarArrayOpExpr（即 \u003ccode\u003eindexcol = ANY(ARRAY[])\u003c/code\u003e）子句的匹配末尾，代码可能会遗漏必要的设置步骤。这可能导致漏掉一些应当被获取的行。\u003c/p\u003e","id":"16.1-dec9cd7f64cd1a27","identity_text":"Fix edge case in btree mark/restore processing of ScalarArrayOpExpr clauses (Peter Geoghegan) When restoring an indexscan to a previously marked position, the code could miss required setup steps if the scan had advanced exactly to the end of the matches for a ScalarArrayOpExpr (that is, an indexcol = ANY(ARRAY[])) clause. This could result in missing some rows that should have been fetched.","part":"changes","patch_ids":["47e71e9e9344a5b195caefd90b827c2a"],"related_changes":[{"db_id":"c80a4dc76428d40d528bacb2ac23edab","evidence":{"patch_ids":["47e71e9e9344a5b195caefd90b827c2a"],"same_day":true,"statement_hash":"41b359d05710c2b9b3ba768c9d230038b2ad62d4314da769abe4ddd64e1da777"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复 B-树标记/恢复处理 ScalarArrayOpExpr 子句时的边界情况","url":"/docs/compare/?release=15.5#15.5-76f04b14320b152f","version":"15.5"},{"db_id":"3092aa3877c8b5881bff66303ac9fba2","evidence":{"patch_ids":["47e71e9e9344a5b195caefd90b827c2a"],"same_day":true,"statement_hash":"41b359d05710c2b9b3ba768c9d230038b2ad62d4314da769abe4ddd64e1da777"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复 B-树标记/恢复处理 ScalarArrayOpExpr 子句时的边界情况","url":"/docs/compare/?release=14.10#14.10-4ee6961756cfacbb","version":"14.10"},{"db_id":"299572bba361d3f89294b6a45f531e0d","evidence":{"patch_ids":["47e71e9e9344a5b195caefd90b827c2a"],"same_day":true,"statement_hash":"41b359d05710c2b9b3ba768c9d230038b2ad62d4314da769abe4ddd64e1da777"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复 B-树标记/恢复处理 ScalarArrayOpExpr 子句时的边界情况","url":"/docs/compare/?release=13.13#13.13-5fe943ad957fdb2a","version":"13.13"},{"db_id":"36784f7db150ca75661df18bbde3c3a9","evidence":{"patch_ids":["47e71e9e9344a5b195caefd90b827c2a"],"same_day":true,"statement_hash":"41b359d05710c2b9b3ba768c9d230038b2ad62d4314da769abe4ddd64e1da777"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"修复 B-树标记/恢复处理 ScalarArrayOpExpr 子句时的边界情况","url":"/docs/compare/?release=12.17#12.17-2350671584e4d32f","version":"12.17"},{"db_id":"20992fc7dd779964133d64b758a4a2b7","evidence":{"patch_ids":["47e71e9e9344a5b195caefd90b827c2a"],"same_day":true,"statement_hash":"41b359d05710c2b9b3ba768c9d230038b2ad62d4314da769abe4ddd64e1da777"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"修复 B-树标记/恢复处理 ScalarArrayOpExpr 子句时的边界情况","url":"/docs/compare/?release=11.22#11.22-ad258f2e16798d9f","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["47e71e9e9344a5b195caefd90b827c2a"],"same_day":true,"statement_hash":"41b359d05710c2b9b3ba768c9d230038b2ad62d4314da769abe4ddd64e1da777"},"rule":2,"target":"20992fc7dd779964133d64b758a4a2b7","type":"equivalent"},{"evidence":{"patch_ids":["47e71e9e9344a5b195caefd90b827c2a"],"same_day":true,"statement_hash":"41b359d05710c2b9b3ba768c9d230038b2ad62d4314da769abe4ddd64e1da777"},"rule":2,"target":"299572bba361d3f89294b6a45f531e0d","type":"equivalent"},{"evidence":{"patch_ids":["47e71e9e9344a5b195caefd90b827c2a"],"same_day":true,"statement_hash":"41b359d05710c2b9b3ba768c9d230038b2ad62d4314da769abe4ddd64e1da777"},"rule":2,"target":"3092aa3877c8b5881bff66303ac9fba2","type":"equivalent"},{"evidence":{"patch_ids":["47e71e9e9344a5b195caefd90b827c2a"],"same_day":true,"statement_hash":"41b359d05710c2b9b3ba768c9d230038b2ad62d4314da769abe4ddd64e1da777"},"rule":2,"target":"36784f7db150ca75661df18bbde3c3a9","type":"equivalent"},{"evidence":{"patch_ids":["47e71e9e9344a5b195caefd90b827c2a"],"same_day":true,"statement_hash":"41b359d05710c2b9b3ba768c9d230038b2ad62d4314da769abe4ddd64e1da777"},"rule":2,"target":"c80a4dc76428d40d528bacb2ac23edab","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["3fa81b62e"],"source_entry_id":"16.1/changes/012","source_hash":"802959fec6763af405c041d71cc889ddd94ac231e45238a2103d19a1dfe7d328","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"41b359d05710c2b9b3ba768c9d230038b2ad62d4314da769abe4ddd64e1da777","text":"修复 B-树标记/恢复处理 ScalarArrayOpExpr 子句时的边界情况（Peter Geoghegan）§ 将索引扫描恢复到先前标记的位置时，如果扫描恰好前进到 ScalarArrayOpExpr（即 indexcol = ANY(ARRAY[])）子句的匹配末尾，代码可能会遗漏必要的设置步骤。这可能导致漏掉一些应当被获取的行。","title":"修复 B-树标记/恢复处理 ScalarArrayOpExpr 子句时的边界情况","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["0b053e78b","31b2b2d72","689af6db6","e4b95b9b0"],"commit_groups":[["0b053e78b","31b2b2d72","689af6db6","e4b95b9b0"]],"commits":["31b2b2d72"],"cves":[],"db_id":"4aaf9b3e07bfd62fabd18100aeb1d490","html":"\u003cp\u003e修复 Memoize 执行中的查询内内存泄漏（Orlov Aleksej，David Rowley）\u003ca href=\"https://postgr.es/c/31b2b2d72\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-ed1602e4f7ed6627","identity_text":"Fix intra-query memory leak in Memoize execution (Orlov Aleksej, David Rowley)","part":"changes","patch_ids":["112f6e8b0243a91500d6048372f6bd00"],"related_changes":[{"db_id":"c1f0f9c6437dda391e6471a7754d99ef","evidence":{"patch_ids":["112f6e8b0243a91500d6048372f6bd00"],"same_day":true,"statement_hash":"5b49a52485f12721aa432756dcb209ebaf025a8bcae1b04db016fd6d3dbb05dd"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复 Memoize 执行中的查询内内存泄漏","url":"/docs/compare/?release=15.5#15.5-b3859e2f65c590f2","version":"15.5"},{"db_id":"0c1229412831f695d79cbf49b0a398ed","evidence":{"patch_ids":["112f6e8b0243a91500d6048372f6bd00"],"same_day":true,"statement_hash":"5b49a52485f12721aa432756dcb209ebaf025a8bcae1b04db016fd6d3dbb05dd"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复 Memoize 执行中的查询内内存泄漏","url":"/docs/compare/?release=14.10#14.10-7ce749d4d9f2e8da","version":"14.10"}],"relations":[{"evidence":{"patch_ids":["112f6e8b0243a91500d6048372f6bd00"],"same_day":true,"statement_hash":"5b49a52485f12721aa432756dcb209ebaf025a8bcae1b04db016fd6d3dbb05dd"},"rule":2,"target":"0c1229412831f695d79cbf49b0a398ed","type":"equivalent"},{"evidence":{"patch_ids":["112f6e8b0243a91500d6048372f6bd00"],"same_day":true,"statement_hash":"5b49a52485f12721aa432756dcb209ebaf025a8bcae1b04db016fd6d3dbb05dd"},"rule":2,"target":"c1f0f9c6437dda391e6471a7754d99ef","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["31b2b2d72"],"source_entry_id":"16.1/changes/013","source_hash":"a197fb89f5ccaf0ab22d5addb5d6438542fd354a0f2e98ae450cd7e9c105086a","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"5b49a52485f12721aa432756dcb209ebaf025a8bcae1b04db016fd6d3dbb05dd","text":"修复 Memoize 执行中的查询内内存泄漏（Orlov Aleksej，David Rowley）§","title":"修复 Memoize 执行中的查询内内存泄漏","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["07494a0df","237f8765d","592cb11fb","5d7515d7d","7ab6971c6","b7684473d","d8d7f282f"],"commit_groups":[["07494a0df","237f8765d","592cb11fb","5d7515d7d","7ab6971c6","b7684473d","d8d7f282f"]],"commits":["07494a0df"],"cves":[],"db_id":"1eaaf9e5f18ad3b83c6dcb987ba8984b","html":"\u003cp\u003e修复当集合返回函数反复返回零行时的查询内内存泄漏（Tom Lane）\u003ca href=\"https://postgr.es/c/07494a0df\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-29bea271ff14aa35","identity_text":"Fix intra-query memory leak when a set-returning function repeatedly returns zero rows (Tom Lane)","part":"changes","patch_ids":["244019edef4e7b67225fc33155d81a6b"],"related_changes":[{"db_id":"84cbb4ef27598e4b190da55f0c5f0327","evidence":{"patch_ids":["244019edef4e7b67225fc33155d81a6b"],"same_day":true,"statement_hash":"2d510e3de1d6b8555ee197040c205f582a3832043b6156d4de7bf7fbd508e495"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复当集合返回函数反复返回零行时的查询内内存泄漏","url":"/docs/compare/?release=15.5#15.5-ba8aed344ac38328","version":"15.5"},{"db_id":"ea280c727dd4689077c1d0dd3078f8bc","evidence":{"patch_ids":["244019edef4e7b67225fc33155d81a6b"],"same_day":true,"statement_hash":"2d510e3de1d6b8555ee197040c205f582a3832043b6156d4de7bf7fbd508e495"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复当集合返回函数反复返回零行时的查询内内存泄漏","url":"/docs/compare/?release=14.10#14.10-de0a828705ad4a21","version":"14.10"},{"db_id":"6a565afc7f22cb799ff93166a170c9e1","evidence":{"patch_ids":["244019edef4e7b67225fc33155d81a6b"],"same_day":true,"statement_hash":"2d510e3de1d6b8555ee197040c205f582a3832043b6156d4de7bf7fbd508e495"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复当集合返回函数反复返回零行时的查询内内存泄漏","url":"/docs/compare/?release=13.13#13.13-79fdb74a9cfee06b","version":"13.13"},{"db_id":"71606f22410fedd4c03802e9a9556fa6","evidence":{"patch_ids":["244019edef4e7b67225fc33155d81a6b"],"same_day":true,"statement_hash":"2d510e3de1d6b8555ee197040c205f582a3832043b6156d4de7bf7fbd508e495"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"修复当集合返回函数反复返回零行时的查询内内存泄漏","url":"/docs/compare/?release=12.17#12.17-8c5f1bacc9c1c67b","version":"12.17"},{"db_id":"7978fcf75eeaa392dc92c6f0387f8e6e","evidence":{"patch_ids":["244019edef4e7b67225fc33155d81a6b"],"same_day":true,"statement_hash":"2d510e3de1d6b8555ee197040c205f582a3832043b6156d4de7bf7fbd508e495"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"修复当集合返回函数反复返回零行时的查询内内存泄漏","url":"/docs/compare/?release=11.22#11.22-ef415ae9cc70191f","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["244019edef4e7b67225fc33155d81a6b"],"same_day":true,"statement_hash":"2d510e3de1d6b8555ee197040c205f582a3832043b6156d4de7bf7fbd508e495"},"rule":2,"target":"6a565afc7f22cb799ff93166a170c9e1","type":"equivalent"},{"evidence":{"patch_ids":["244019edef4e7b67225fc33155d81a6b"],"same_day":true,"statement_hash":"2d510e3de1d6b8555ee197040c205f582a3832043b6156d4de7bf7fbd508e495"},"rule":2,"target":"71606f22410fedd4c03802e9a9556fa6","type":"equivalent"},{"evidence":{"patch_ids":["244019edef4e7b67225fc33155d81a6b"],"same_day":true,"statement_hash":"2d510e3de1d6b8555ee197040c205f582a3832043b6156d4de7bf7fbd508e495"},"rule":2,"target":"7978fcf75eeaa392dc92c6f0387f8e6e","type":"equivalent"},{"evidence":{"patch_ids":["244019edef4e7b67225fc33155d81a6b"],"same_day":true,"statement_hash":"2d510e3de1d6b8555ee197040c205f582a3832043b6156d4de7bf7fbd508e495"},"rule":2,"target":"84cbb4ef27598e4b190da55f0c5f0327","type":"equivalent"},{"evidence":{"patch_ids":["244019edef4e7b67225fc33155d81a6b"],"same_day":true,"statement_hash":"2d510e3de1d6b8555ee197040c205f582a3832043b6156d4de7bf7fbd508e495"},"rule":2,"target":"ea280c727dd4689077c1d0dd3078f8bc","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["07494a0df"],"source_entry_id":"16.1/changes/014","source_hash":"a95123acff82eb5b586c22adaaae55971358ed744461def99aa0f801950a0555","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"2d510e3de1d6b8555ee197040c205f582a3832043b6156d4de7bf7fbd508e495","text":"修复当集合返回函数反复返回零行时的查询内内存泄漏（Tom Lane）§","title":"修复当集合返回函数反复返回零行时的查询内内存泄漏","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["123337079","95f54f0d0","9baabfa38","db00be6d7","e6e50ada0","ec693a3f3","f73fa5a47"],"commit_groups":[["123337079","95f54f0d0","9baabfa38","db00be6d7","e6e50ada0","ec693a3f3","f73fa5a47"]],"commits":["ec693a3f3"],"cves":[],"db_id":"0a39c80cc99224fc1cbe62a64a085e92","html":"\u003cp\u003e修复将 \u003ccode\u003ecursor_to_xmlschema()\u003c/code\u003e 应用于非数据返回 Portal 时的崩溃（Boyu Yang）\u003ca href=\"https://postgr.es/c/ec693a3f3\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-2de9c26979736ac4","identity_text":"Don't crash if cursor_to_xmlschema() is applied to a non-data-returning Portal (Boyu Yang)","part":"changes","patch_ids":["3fae9c8270171214d55f97a0a69433da"],"related_changes":[{"db_id":"2621a5bc48d1d6bf35c2911523953b61","evidence":{"patch_ids":["3fae9c8270171214d55f97a0a69433da"],"same_day":true,"statement_hash":"391ee0dbedc609bbdd8973174757b2af9033b6fd6de885f4cdbb73e203858a46"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复将 cursor_to_xmlschema() 应用于非数据返回 Portal 时的崩溃","url":"/docs/compare/?release=15.5#15.5-df81aa8645d30e8e","version":"15.5"},{"db_id":"6df4fcbb0d469f19c8ff15d2bc8224cd","evidence":{"patch_ids":["3fae9c8270171214d55f97a0a69433da"],"same_day":true,"statement_hash":"391ee0dbedc609bbdd8973174757b2af9033b6fd6de885f4cdbb73e203858a46"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复将 cursor_to_xmlschema() 应用于非数据返回 Portal 时的崩溃","url":"/docs/compare/?release=14.10#14.10-ecd781797d111393","version":"14.10"},{"db_id":"47e43f6287333b6f40d42b450852cbf9","evidence":{"patch_ids":["3fae9c8270171214d55f97a0a69433da"],"same_day":true,"statement_hash":"391ee0dbedc609bbdd8973174757b2af9033b6fd6de885f4cdbb73e203858a46"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复将 cursor_to_xmlschema() 应用于非数据返回 Portal 时的崩溃","url":"/docs/compare/?release=13.13#13.13-7b5f65f97e8630d1","version":"13.13"},{"db_id":"8fe11ba0ed258fd26fbeb318f6ed9aed","evidence":{"patch_ids":["3fae9c8270171214d55f97a0a69433da"],"same_day":true,"statement_hash":"391ee0dbedc609bbdd8973174757b2af9033b6fd6de885f4cdbb73e203858a46"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"修复将 cursor_to_xmlschema() 应用于非数据返回 Portal 时的崩溃","url":"/docs/compare/?release=12.17#12.17-4e3796be34691d72","version":"12.17"},{"db_id":"03ea47b753209e24cddfa116470ed7d2","evidence":{"patch_ids":["3fae9c8270171214d55f97a0a69433da"],"same_day":true,"statement_hash":"391ee0dbedc609bbdd8973174757b2af9033b6fd6de885f4cdbb73e203858a46"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"修复将 cursor_to_xmlschema() 应用于非数据返回 Portal 时的崩溃","url":"/docs/compare/?release=11.22#11.22-34b580c3d31d1a98","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["3fae9c8270171214d55f97a0a69433da"],"same_day":true,"statement_hash":"391ee0dbedc609bbdd8973174757b2af9033b6fd6de885f4cdbb73e203858a46"},"rule":2,"target":"03ea47b753209e24cddfa116470ed7d2","type":"equivalent"},{"evidence":{"patch_ids":["3fae9c8270171214d55f97a0a69433da"],"same_day":true,"statement_hash":"391ee0dbedc609bbdd8973174757b2af9033b6fd6de885f4cdbb73e203858a46"},"rule":2,"target":"2621a5bc48d1d6bf35c2911523953b61","type":"equivalent"},{"evidence":{"patch_ids":["3fae9c8270171214d55f97a0a69433da"],"same_day":true,"statement_hash":"391ee0dbedc609bbdd8973174757b2af9033b6fd6de885f4cdbb73e203858a46"},"rule":2,"target":"47e43f6287333b6f40d42b450852cbf9","type":"equivalent"},{"evidence":{"patch_ids":["3fae9c8270171214d55f97a0a69433da"],"same_day":true,"statement_hash":"391ee0dbedc609bbdd8973174757b2af9033b6fd6de885f4cdbb73e203858a46"},"rule":2,"target":"6df4fcbb0d469f19c8ff15d2bc8224cd","type":"equivalent"},{"evidence":{"patch_ids":["3fae9c8270171214d55f97a0a69433da"],"same_day":true,"statement_hash":"391ee0dbedc609bbdd8973174757b2af9033b6fd6de885f4cdbb73e203858a46"},"rule":2,"target":"8fe11ba0ed258fd26fbeb318f6ed9aed","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["ec693a3f3"],"source_entry_id":"16.1/changes/015","source_hash":"56cd17151818adaee9d4f3b3e8e81d0e564f7773c59fdec98cc854b7aec3fad7","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"391ee0dbedc609bbdd8973174757b2af9033b6fd6de885f4cdbb73e203858a46","text":"修复将 cursor_to_xmlschema() 应用于非数据返回 Portal 时的崩溃（Boyu Yang）§","title":"修复将 cursor_to_xmlschema() 应用于非数据返回 Portal 时的崩溃","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["54ccfd658","8d05be931"],"commit_groups":[["54ccfd658","8d05be931"]],"commits":["8d05be931"],"cves":[],"db_id":"b2d9409f119fa703e9149b7bf8154ec4","html":"\u003cp\u003e修复连续 \u003ccode\u003epg_logical_slot_get_changes()\u003c/code\u003e 调用之间源过滤条件的不当共享（Hou Zhijie）\u003ca href=\"https://postgr.es/c/8d05be931\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e此函数的一次调用所设置的源条件会被后续未指定源参数的调用重复使用。这不是预期的行为。\u003c/p\u003e","id":"16.1-2680d9fab49cc1ff","identity_text":"Fix improper sharing of origin filter condition across successive pg_logical_slot_get_changes() calls (Hou Zhijie) The origin condition set by one call of this function would be re-used by later calls that did not specify the origin argument. This was not intended.","part":"changes","patch_ids":["c9b166c6828c9f5a846a3fd911df5ade"],"related_changes":[],"relations":[],"section":"变更","section_path":["变更"],"source_commits":["8d05be931"],"source_entry_id":"16.1/changes/016","source_hash":"92e77fadf014e8848e5ec6194ece88c625361af080eba5d22c459ab757d871fa","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"399df2c59d3783319a46ba8ab0b7151aac96c2c25bf435c8c1376272038b9c19","text":"修复连续 pg_logical_slot_get_changes() 调用之间源过滤条件的不当共享（Hou Zhijie）§ 此函数的一次调用所设置的源条件会被后续未指定源参数的调用重复使用。这不是预期的行为。","title":"修复连续 pg_logical_slot_get_changes() 调用之间源过滤条件的不当共享","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["136068353","73635b6d6","a98f01c93","b3c8d1d0e","c5988e69f","efcb601d2"],"commit_groups":[["136068353","73635b6d6","a98f01c93","b3c8d1d0e","c5988e69f","efcb601d2"]],"commits":["a98f01c93"],"cves":[],"db_id":"a37711088c428b48c8adb0c58b0b9897","html":"\u003cp\u003e将 \u003ccode\u003epgrowlocks()\u003c/code\u003e 应用于分区表时，抛出预期的错误（David Rowley）\u003ca href=\"https://postgr.es/c/a98f01c93\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e之前会抛出一个不切题的错误 \u003cspan\u003e“\u003cspan\u003eonly heap AM is supported\u003c/span\u003e”\u003c/span\u003e。\u003c/p\u003e","id":"16.1-beef0b8ae89f59c0","identity_text":"Throw the intended error if pgrowlocks() is applied to a partitioned table (David Rowley) Previously, a not-on-point complaint only heap AM is supported would be raised.","part":"changes","patch_ids":["152532cf785c69daf2f0bbc5281a552d"],"related_changes":[{"db_id":"ea71a3a2ad8483e1352a697c20302637","evidence":{"patch_ids":["152532cf785c69daf2f0bbc5281a552d"],"same_day":true,"statement_hash":"366c3c377fac92db6e072867ee3421b575535319976dc79b47a3aeb9ed31fd44"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"将 pgrowlocks() 应用于分区表时，抛出预期的错误","url":"/docs/compare/?release=15.5#15.5-946d94450adb9811","version":"15.5"},{"db_id":"1c45cc4a0520cc8fcee674a34fc57c45","evidence":{"patch_ids":["152532cf785c69daf2f0bbc5281a552d"],"same_day":true,"statement_hash":"366c3c377fac92db6e072867ee3421b575535319976dc79b47a3aeb9ed31fd44"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"将 pgrowlocks() 应用于分区表时，抛出预期的错误","url":"/docs/compare/?release=14.10#14.10-2f0d0b080faed90f","version":"14.10"},{"db_id":"dbcac358631568c01d33aa618dd50d3a","evidence":{"patch_ids":["152532cf785c69daf2f0bbc5281a552d"],"same_day":true,"statement_hash":"366c3c377fac92db6e072867ee3421b575535319976dc79b47a3aeb9ed31fd44"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"将 pgrowlocks() 应用于分区表时，抛出预期的错误","url":"/docs/compare/?release=13.13#13.13-4801f99d6fad28a9","version":"13.13"},{"db_id":"14492f034a1adc9dad5e9747284839e9","evidence":{"patch_ids":["152532cf785c69daf2f0bbc5281a552d"],"same_day":true,"statement_hash":"366c3c377fac92db6e072867ee3421b575535319976dc79b47a3aeb9ed31fd44"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"将 pgrowlocks() 应用于分区表时，抛出预期的错误","url":"/docs/compare/?release=12.17#12.17-6d03bd902ab5bebc","version":"12.17"}],"relations":[{"evidence":{"patch_ids":["152532cf785c69daf2f0bbc5281a552d"],"same_day":true,"statement_hash":"366c3c377fac92db6e072867ee3421b575535319976dc79b47a3aeb9ed31fd44"},"rule":2,"target":"14492f034a1adc9dad5e9747284839e9","type":"equivalent"},{"evidence":{"patch_ids":["152532cf785c69daf2f0bbc5281a552d"],"same_day":true,"statement_hash":"366c3c377fac92db6e072867ee3421b575535319976dc79b47a3aeb9ed31fd44"},"rule":2,"target":"1c45cc4a0520cc8fcee674a34fc57c45","type":"equivalent"},{"evidence":{"patch_ids":["152532cf785c69daf2f0bbc5281a552d"],"same_day":true,"statement_hash":"366c3c377fac92db6e072867ee3421b575535319976dc79b47a3aeb9ed31fd44"},"rule":2,"target":"dbcac358631568c01d33aa618dd50d3a","type":"equivalent"},{"evidence":{"patch_ids":["152532cf785c69daf2f0bbc5281a552d"],"same_day":true,"statement_hash":"366c3c377fac92db6e072867ee3421b575535319976dc79b47a3aeb9ed31fd44"},"rule":2,"target":"ea71a3a2ad8483e1352a697c20302637","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["a98f01c93"],"source_entry_id":"16.1/changes/017","source_hash":"f847dee1541e5bbf4767274278ed39dc59b85252e6042d63078fce812be9d12e","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"366c3c377fac92db6e072867ee3421b575535319976dc79b47a3aeb9ed31fd44","text":"将 pgrowlocks() 应用于分区表时，抛出预期的错误（David Rowley）§ 之前会抛出一个不切题的错误 “only heap AM is supported”。","title":"将 pgrowlocks() 应用于分区表时，抛出预期的错误","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["0a7b183fd","123b0d111","13503eb59","1a368dd3e","975ae0553","bae063db4","e633e9b13"],"commit_groups":[["0a7b183fd","123b0d111","13503eb59","1a368dd3e","975ae0553","bae063db4","e633e9b13"]],"commits":["1a368dd3e"],"cves":[],"db_id":"6f6bd9bf3d6b2d059181b1626295fac0","html":"\u003cp\u003e在各种 SQL 函数中更妥善地处理无效索引（Noah Misch）\u003ca href=\"https://postgr.es/c/1a368dd3e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e如果将 \u003ccode\u003epgstatindex()\u003c/code\u003e、\u003ccode\u003epgstatginindex()\u003c/code\u003e、\u003ccode\u003epgstathashindex()\u003c/code\u003e 或 \u003ccode\u003epgstattuple()\u003c/code\u003e 应用于无效索引，现在会报告错误。如果将 \u003ccode\u003ebrin_desummarize_range()\u003c/code\u003e、\u003ccode\u003ebrin_summarize_new_values()\u003c/code\u003e、\u003ccode\u003ebrin_summarize_range()\u003c/code\u003e 或 \u003ccode\u003egin_clean_pending_list()\u003c/code\u003e 应用于无效索引，则除了报告一条调试级别的消息外不做任何操作。之前这些函数会尝试处理该索引，并可能根据失败的 \u003ccode\u003eCREATE INDEX\u003c/code\u003e 遗留的内容而以奇怪的方式失败。\u003c/p\u003e","id":"16.1-c39d5b58908ea8dc","identity_text":"Handle invalid indexes more cleanly in assorted SQL functions (Noah Misch) Report an error if pgstatindex(), pgstatginindex(), pgstathashindex(), or pgstattuple() is applied to an invalid index. If brin_desummarize_range(), brin_summarize_new_values(), brin_summarize_range(), or gin_clean_pending_list() is applied to an invalid index, do nothing except to report a debug-level message. Formerly these functions attempted to process the index, and might fail in strange ways depending on what the failed CREATE INDEX had left behind.","part":"changes","patch_ids":["de1e1d5d9a90e471a33128b8b9e94054"],"related_changes":[{"db_id":"5760cea3b2fc0cbd33b2c318bff1d956","evidence":{"patch_ids":["de1e1d5d9a90e471a33128b8b9e94054"],"same_day":true,"statement_hash":"e40495e7751cb3788ae7d9760022c7662fa3936ac85e24a46b8afa4723f9e4ef"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"在各种 SQL 函数中更妥善地处理无效索引","url":"/docs/compare/?release=15.5#15.5-ae32a06903153a13","version":"15.5"},{"db_id":"ddab22545d9a9856a3b7bc03af6e7b28","evidence":{"patch_ids":["de1e1d5d9a90e471a33128b8b9e94054"],"same_day":true,"statement_hash":"e40495e7751cb3788ae7d9760022c7662fa3936ac85e24a46b8afa4723f9e4ef"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"在各种 SQL 函数中更妥善地处理无效索引","url":"/docs/compare/?release=14.10#14.10-51f367c21ee6b80a","version":"14.10"},{"db_id":"90756dce89f741b0d6cae5d8361a802f","evidence":{"patch_ids":["de1e1d5d9a90e471a33128b8b9e94054"],"same_day":true,"statement_hash":"e40495e7751cb3788ae7d9760022c7662fa3936ac85e24a46b8afa4723f9e4ef"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"在各种 SQL 函数中更妥善地处理无效索引","url":"/docs/compare/?release=13.13#13.13-97d8cec127c5d858","version":"13.13"},{"db_id":"bb6be4b4c072d18fe950003e6410e30b","evidence":{"patch_ids":["de1e1d5d9a90e471a33128b8b9e94054"],"same_day":true,"statement_hash":"e40495e7751cb3788ae7d9760022c7662fa3936ac85e24a46b8afa4723f9e4ef"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"在各种 SQL 函数中更妥善地处理无效索引","url":"/docs/compare/?release=12.17#12.17-f8da4f21df006b8b","version":"12.17"},{"db_id":"bed85b0094743b91f22f54d4724a6780","evidence":{"patch_ids":["de1e1d5d9a90e471a33128b8b9e94054"],"same_day":true,"statement_hash":"e40495e7751cb3788ae7d9760022c7662fa3936ac85e24a46b8afa4723f9e4ef"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"在各种 SQL 函数中更妥善地处理无效索引","url":"/docs/compare/?release=11.22#11.22-2adbf91d9f6852fd","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["de1e1d5d9a90e471a33128b8b9e94054"],"same_day":true,"statement_hash":"e40495e7751cb3788ae7d9760022c7662fa3936ac85e24a46b8afa4723f9e4ef"},"rule":2,"target":"5760cea3b2fc0cbd33b2c318bff1d956","type":"equivalent"},{"evidence":{"patch_ids":["de1e1d5d9a90e471a33128b8b9e94054"],"same_day":true,"statement_hash":"e40495e7751cb3788ae7d9760022c7662fa3936ac85e24a46b8afa4723f9e4ef"},"rule":2,"target":"90756dce89f741b0d6cae5d8361a802f","type":"equivalent"},{"evidence":{"patch_ids":["de1e1d5d9a90e471a33128b8b9e94054"],"same_day":true,"statement_hash":"e40495e7751cb3788ae7d9760022c7662fa3936ac85e24a46b8afa4723f9e4ef"},"rule":2,"target":"bb6be4b4c072d18fe950003e6410e30b","type":"equivalent"},{"evidence":{"patch_ids":["de1e1d5d9a90e471a33128b8b9e94054"],"same_day":true,"statement_hash":"e40495e7751cb3788ae7d9760022c7662fa3936ac85e24a46b8afa4723f9e4ef"},"rule":2,"target":"bed85b0094743b91f22f54d4724a6780","type":"equivalent"},{"evidence":{"patch_ids":["de1e1d5d9a90e471a33128b8b9e94054"],"same_day":true,"statement_hash":"e40495e7751cb3788ae7d9760022c7662fa3936ac85e24a46b8afa4723f9e4ef"},"rule":2,"target":"ddab22545d9a9856a3b7bc03af6e7b28","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["1a368dd3e"],"source_entry_id":"16.1/changes/018","source_hash":"9b709908be979d5c164d3e641162db7fd8c5cd052167e23dce6766c00298f062","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"e40495e7751cb3788ae7d9760022c7662fa3936ac85e24a46b8afa4723f9e4ef","text":"在各种 SQL 函数中更妥善地处理无效索引（Noah Misch）§ 如果将 pgstatindex()、pgstatginindex()、pgstathashindex() 或 pgstattuple() 应用于无效索引，现在会报告错误。如果将 brin_desummarize_range()、brin_summarize_new_values()、brin_summarize_range() 或 gin_clean_pending_list() 应用于无效索引，则除了报告一条调试级别的消息外不做任何操作。之前这些函数会尝试处理该索引，并可能根据失败的 CREATE INDEX 遗留的内容而以奇怪的方式失败。","title":"在各种 SQL 函数中更妥善地处理无效索引","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["0fb91ed2b","4a81ed29d","52a676ef4","71bb73f60","8465efc1a","a2799f53d","cf1c65070"],"commit_groups":[["0fb91ed2b","4a81ed29d","52a676ef4","71bb73f60","8465efc1a","a2799f53d","cf1c65070"]],"commits":["8465efc1a"],"cves":[],"db_id":"000b458c5d4044168c985184b50e8901","html":"\u003cp\u003e避免在 \u003ccode\u003eto_tsvector()\u003c/code\u003e 处理长输入时过早的内存分配失败（Tom Lane）\u003ca href=\"https://postgr.es/c/8465efc1a\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-3a434bbd0ed13313","identity_text":"Avoid premature memory allocation failure with long inputs to to_tsvector() (Tom Lane)","part":"changes","patch_ids":["7bbd8463c1b0e94fd15c9bde36851982"],"related_changes":[{"db_id":"f7c6137246c93ebe47becf690e9086b5","evidence":{"patch_ids":["7bbd8463c1b0e94fd15c9bde36851982"],"same_day":true,"statement_hash":"99657a354179d2b27f9df4630e0948eaa99c6e1cb898b910ab7afbbe4faac8e6"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"避免在 to_tsvector() 处理长输入时过早的内存分配失败","url":"/docs/compare/?release=15.5#15.5-dfe0c4d6a142e3f4","version":"15.5"},{"db_id":"6030ae0532a7fbbd10d9c4d0acf02729","evidence":{"patch_ids":["7bbd8463c1b0e94fd15c9bde36851982"],"same_day":true,"statement_hash":"99657a354179d2b27f9df4630e0948eaa99c6e1cb898b910ab7afbbe4faac8e6"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"避免在 to_tsvector() 处理长输入时过早的内存分配失败","url":"/docs/compare/?release=14.10#14.10-5ffe2108757d20cf","version":"14.10"},{"db_id":"5acfa40be0a1324cfe5c678298fb13b1","evidence":{"patch_ids":["7bbd8463c1b0e94fd15c9bde36851982"],"same_day":true,"statement_hash":"99657a354179d2b27f9df4630e0948eaa99c6e1cb898b910ab7afbbe4faac8e6"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"避免在 to_tsvector() 处理长输入时过早的内存分配失败","url":"/docs/compare/?release=13.13#13.13-2217206f0303295b","version":"13.13"},{"db_id":"55c88a39eb5628209721f0e344d52e51","evidence":{"patch_ids":["7bbd8463c1b0e94fd15c9bde36851982"],"same_day":true,"statement_hash":"99657a354179d2b27f9df4630e0948eaa99c6e1cb898b910ab7afbbe4faac8e6"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"避免在 to_tsvector() 处理长输入时过早的内存分配失败","url":"/docs/compare/?release=12.17#12.17-b076375b4b43d5cd","version":"12.17"},{"db_id":"a98abf05063bf8b1063dcdd1645ab2d0","evidence":{"patch_ids":["7bbd8463c1b0e94fd15c9bde36851982"],"same_day":true,"statement_hash":"99657a354179d2b27f9df4630e0948eaa99c6e1cb898b910ab7afbbe4faac8e6"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"避免在 to_tsvector() 处理长输入时过早的内存分配失败","url":"/docs/compare/?release=11.22#11.22-0510e66909f90a1b","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["7bbd8463c1b0e94fd15c9bde36851982"],"same_day":true,"statement_hash":"99657a354179d2b27f9df4630e0948eaa99c6e1cb898b910ab7afbbe4faac8e6"},"rule":2,"target":"55c88a39eb5628209721f0e344d52e51","type":"equivalent"},{"evidence":{"patch_ids":["7bbd8463c1b0e94fd15c9bde36851982"],"same_day":true,"statement_hash":"99657a354179d2b27f9df4630e0948eaa99c6e1cb898b910ab7afbbe4faac8e6"},"rule":2,"target":"5acfa40be0a1324cfe5c678298fb13b1","type":"equivalent"},{"evidence":{"patch_ids":["7bbd8463c1b0e94fd15c9bde36851982"],"same_day":true,"statement_hash":"99657a354179d2b27f9df4630e0948eaa99c6e1cb898b910ab7afbbe4faac8e6"},"rule":2,"target":"6030ae0532a7fbbd10d9c4d0acf02729","type":"equivalent"},{"evidence":{"patch_ids":["7bbd8463c1b0e94fd15c9bde36851982"],"same_day":true,"statement_hash":"99657a354179d2b27f9df4630e0948eaa99c6e1cb898b910ab7afbbe4faac8e6"},"rule":2,"target":"a98abf05063bf8b1063dcdd1645ab2d0","type":"equivalent"},{"evidence":{"patch_ids":["7bbd8463c1b0e94fd15c9bde36851982"],"same_day":true,"statement_hash":"99657a354179d2b27f9df4630e0948eaa99c6e1cb898b910ab7afbbe4faac8e6"},"rule":2,"target":"f7c6137246c93ebe47becf690e9086b5","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["8465efc1a"],"source_entry_id":"16.1/changes/019","source_hash":"90e90c693915ac03f3403aac6521fa67c9293b1170eba287ce6970f0d1e2a079","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"99657a354179d2b27f9df4630e0948eaa99c6e1cb898b910ab7afbbe4faac8e6","text":"避免在 to_tsvector() 处理长输入时过早的内存分配失败（Tom Lane）§","title":"避免在 to_tsvector() 处理长输入时过早的内存分配失败","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["2296bc362","55e188a15","5b7b38246","5c34a7374","7a310cae0","9da153846","cf12c4fd2"],"commit_groups":[["2296bc362","55e188a15","5b7b38246","5c34a7374","7a310cae0","9da153846","cf12c4fd2"]],"commits":["5c34a7374"],"cves":[],"db_id":"59381a536e7291208784c809c9c9e0cc","html":"\u003cp\u003e修复 \u003ccode\u003etsvectorrecv()\u003c/code\u003e 中构造的 \u003ccode\u003etsvector\u003c/code\u003e 的过度分配（Denis Erokhin）\u003ca href=\"https://postgr.es/c/5c34a7374\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e如果传入的向量包含位置数据，二进制接收函数会在完成的 \u003ccode\u003etsvector\u003c/code\u003e 中留下浪费的空间（大约等于位置数据的大小）。在极端情况下，这可能导致对于发出时在长度限制内的向量产生 \u003cspan\u003e“\u003cspan\u003emaximum total lexeme length exceeded\u003c/span\u003e”\u003c/span\u003e 失败。无论如何都可能导致磁盘空间浪费。\u003c/p\u003e","id":"16.1-13bc6e4ee0766fc0","identity_text":"Fix over-allocation of the constructed tsvector in tsvectorrecv() (Denis Erokhin) If the incoming vector includes position data, the binary receive function left wasted space (roughly equal to the size of the position data) in the finished tsvector. In extreme cases this could lead to maximum total lexeme length exceeded failures for vectors that were under the length limit when emitted. In any case it could lead to wasted space on-disk.","part":"changes","patch_ids":["6bce57963dffafae7182a081da49f9cf"],"related_changes":[{"db_id":"c87deb30836d63b994932914def691de","evidence":{"patch_ids":["6bce57963dffafae7182a081da49f9cf"],"same_day":true,"statement_hash":"a9dad01c949f171609c4387c6c1ecabac5e030199b6bef4f35d80eba338e480b"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复 tsvectorrecv() 中构造的 tsvector 的过度分配","url":"/docs/compare/?release=15.5#15.5-e14ea9365b33d315","version":"15.5"},{"db_id":"5fc2d01ad8a45a50dae5390c0a2fb8f2","evidence":{"patch_ids":["6bce57963dffafae7182a081da49f9cf"],"same_day":true,"statement_hash":"a9dad01c949f171609c4387c6c1ecabac5e030199b6bef4f35d80eba338e480b"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复 tsvectorrecv() 中构造的 tsvector 的过度分配","url":"/docs/compare/?release=14.10#14.10-62827871225c4dd6","version":"14.10"},{"db_id":"ecb904f26661489d6402b3e395fcddd0","evidence":{"patch_ids":["6bce57963dffafae7182a081da49f9cf"],"same_day":true,"statement_hash":"a9dad01c949f171609c4387c6c1ecabac5e030199b6bef4f35d80eba338e480b"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复 tsvectorrecv() 中构造的 tsvector 的过度分配","url":"/docs/compare/?release=13.13#13.13-a07b47b98e571426","version":"13.13"},{"db_id":"fd4783d09e517c6ae5c42a0f39721922","evidence":{"patch_ids":["6bce57963dffafae7182a081da49f9cf"],"same_day":true,"statement_hash":"a9dad01c949f171609c4387c6c1ecabac5e030199b6bef4f35d80eba338e480b"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"修复 tsvectorrecv() 中构造的 tsvector 的过度分配","url":"/docs/compare/?release=12.17#12.17-9883ddcf96fed1c1","version":"12.17"},{"db_id":"7fc7f03e22fd8b8b15cbc0bf24471683","evidence":{"patch_ids":["6bce57963dffafae7182a081da49f9cf"],"same_day":true,"statement_hash":"a9dad01c949f171609c4387c6c1ecabac5e030199b6bef4f35d80eba338e480b"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"修复 tsvectorrecv() 中构造的 tsvector 的过度分配","url":"/docs/compare/?release=11.22#11.22-398e609952029aae","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["6bce57963dffafae7182a081da49f9cf"],"same_day":true,"statement_hash":"a9dad01c949f171609c4387c6c1ecabac5e030199b6bef4f35d80eba338e480b"},"rule":2,"target":"5fc2d01ad8a45a50dae5390c0a2fb8f2","type":"equivalent"},{"evidence":{"patch_ids":["6bce57963dffafae7182a081da49f9cf"],"same_day":true,"statement_hash":"a9dad01c949f171609c4387c6c1ecabac5e030199b6bef4f35d80eba338e480b"},"rule":2,"target":"7fc7f03e22fd8b8b15cbc0bf24471683","type":"equivalent"},{"evidence":{"patch_ids":["6bce57963dffafae7182a081da49f9cf"],"same_day":true,"statement_hash":"a9dad01c949f171609c4387c6c1ecabac5e030199b6bef4f35d80eba338e480b"},"rule":2,"target":"c87deb30836d63b994932914def691de","type":"equivalent"},{"evidence":{"patch_ids":["6bce57963dffafae7182a081da49f9cf"],"same_day":true,"statement_hash":"a9dad01c949f171609c4387c6c1ecabac5e030199b6bef4f35d80eba338e480b"},"rule":2,"target":"ecb904f26661489d6402b3e395fcddd0","type":"equivalent"},{"evidence":{"patch_ids":["6bce57963dffafae7182a081da49f9cf"],"same_day":true,"statement_hash":"a9dad01c949f171609c4387c6c1ecabac5e030199b6bef4f35d80eba338e480b"},"rule":2,"target":"fd4783d09e517c6ae5c42a0f39721922","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["5c34a7374"],"source_entry_id":"16.1/changes/020","source_hash":"294dbed5d5c47cded3ce3893c35d457828cd4031ae0a680a92c6b35f302e33e1","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"a9dad01c949f171609c4387c6c1ecabac5e030199b6bef4f35d80eba338e480b","text":"修复 tsvectorrecv() 中构造的 tsvector 的过度分配（Denis Erokhin）§ 如果传入的向量包含位置数据，二进制接收函数会在完成的 tsvector 中留下浪费的空间（大约等于位置数据的大小）。在极端情况下，这可能导致对于发出时在长度限制内的向量产生 “maximum total lexeme length exceeded” 失败。无论如何都可能导致磁盘空间浪费。","title":"修复 tsvectorrecv() 中构造的 tsvector 的过度分配","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["2c63dc035","817669ea2","985ac5ce2","9b103f861","cfa4eba02"],"commit_groups":[["2c63dc035","817669ea2","985ac5ce2","9b103f861","cfa4eba02"]],"commits":["cfa4eba02"],"cves":[],"db_id":"71092b06384fa60d2620cf9898bcb83b","html":"\u003cp\u003e改进对损坏的 PGLZ 压缩数据的检查（Flavien Guedez）\u003ca href=\"https://postgr.es/c/cfa4eba02\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-aa262152ca332e13","identity_text":"Improve checks for corrupt PGLZ compressed data (Flavien Guedez)","part":"changes","patch_ids":["1741d93967df184ccdd1d4a6a398e317"],"related_changes":[{"db_id":"8cc7351035a797c6025ec99004a78074","evidence":{"patch_ids":["1741d93967df184ccdd1d4a6a398e317"],"same_day":true,"statement_hash":"376e0ff79d717a1f737b64123dffc6633d2de3292433146e651e3137f240dd47"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"改进对损坏的 PGLZ 压缩数据的检查","url":"/docs/compare/?release=15.5#15.5-124499f9eb37b98c","version":"15.5"},{"db_id":"1f9fef774baf82c12f756f38d340117d","evidence":{"patch_ids":["1741d93967df184ccdd1d4a6a398e317"],"same_day":true,"statement_hash":"376e0ff79d717a1f737b64123dffc6633d2de3292433146e651e3137f240dd47"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"改进对损坏的 PGLZ 压缩数据的检查","url":"/docs/compare/?release=14.10#14.10-ce1f5e488c3056b8","version":"14.10"},{"db_id":"0489fc842a2b1c58a08777eb6ac0fa6c","evidence":{"patch_ids":["1741d93967df184ccdd1d4a6a398e317"],"same_day":true,"statement_hash":"376e0ff79d717a1f737b64123dffc6633d2de3292433146e651e3137f240dd47"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"改进对损坏的 PGLZ 压缩数据的检查","url":"/docs/compare/?release=13.13#13.13-0b06a58f18f74b17","version":"13.13"}],"relations":[{"evidence":{"patch_ids":["1741d93967df184ccdd1d4a6a398e317"],"same_day":true,"statement_hash":"376e0ff79d717a1f737b64123dffc6633d2de3292433146e651e3137f240dd47"},"rule":2,"target":"0489fc842a2b1c58a08777eb6ac0fa6c","type":"equivalent"},{"evidence":{"patch_ids":["1741d93967df184ccdd1d4a6a398e317"],"same_day":true,"statement_hash":"376e0ff79d717a1f737b64123dffc6633d2de3292433146e651e3137f240dd47"},"rule":2,"target":"1f9fef774baf82c12f756f38d340117d","type":"equivalent"},{"evidence":{"patch_ids":["1741d93967df184ccdd1d4a6a398e317"],"same_day":true,"statement_hash":"376e0ff79d717a1f737b64123dffc6633d2de3292433146e651e3137f240dd47"},"rule":2,"target":"8cc7351035a797c6025ec99004a78074","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["cfa4eba02"],"source_entry_id":"16.1/changes/021","source_hash":"99a0adf73ed437f518a96a7bd563c9af3c24c08f60abc20d036d636b6b265e8b","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"376e0ff79d717a1f737b64123dffc6633d2de3292433146e651e3137f240dd47","text":"改进对损坏的 PGLZ 压缩数据的检查（Flavien Guedez）§","title":"改进对损坏的 PGLZ 压缩数据的检查","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["a81e5516f","f062cddaf"],"commit_groups":[["a81e5516f","f062cddaf"]],"commits":["a81e5516f"],"cves":[],"db_id":"13f556b65037e7304b626ae3806cbe82","html":"\u003cp\u003e修复 \u003ccode\u003eALTER SUBSCRIPTION\u003c/code\u003e，使对 \u003ccode\u003erun_as_owner\u003c/code\u003e 选项的命令更改实际生效（Hou Zhijie）\u003ca href=\"https://postgr.es/c/a81e5516f\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-3a26b95c9f21ba79","identity_text":"Fix ALTER SUBSCRIPTION so that a commanded change in the run_as_owner option is actually applied (Hou Zhijie)","part":"changes","patch_ids":["94de4cbcdfbfa8ba2e6e069314b60327"],"related_changes":[],"relations":[],"section":"变更","section_path":["变更"],"source_commits":["a81e5516f"],"source_entry_id":"16.1/changes/022","source_hash":"6ff2211a8ca3209d23487dc39ee49522dfc6c73e1e8ef33da7a7826fc3e4eea6","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"267d2be51f4e79ca93ed7ac014aa8b95a49c36965687cdf7b11f5e48365747bd","text":"修复 ALTER SUBSCRIPTION，使对 run_as_owner 选项的命令更改实际生效（Hou Zhijie）§","title":"修复 ALTER SUBSCRIPTION，使对 run_as_owner 选项的命令更改实际生效","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["0002feb82","22655aa23"],"commit_groups":[["0002feb82","22655aa23"]],"commits":["0002feb82"],"cves":[],"db_id":"0f5ac1d87dd6faf2730723d282d3507e","html":"\u003cp\u003e修复向分区表的批量表插入（Andres Freund）\u003ca href=\"https://postgr.es/c/0002feb82\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e跨分区不当共享插入状态可能导致 \u003ccode\u003eCOPY FROM\u003c/code\u003e 期间的失败，通常表现为 \u003cspan\u003e“\u003cspan\u003ecould not read block NNNN in file XXXX: read only 0 of 8192 bytes\u003c/span\u003e”\u003c/span\u003e 错误。\u003c/p\u003e","id":"16.1-a890fd19f6dc50a4","identity_text":"Fix bulk table insertion into partitioned tables (Andres Freund) Improper sharing of insertion state across partitions could result in failures during COPY FROM, typically manifesting as could not read block NNNN in file XXXX: read only 0 of 8192 bytes errors.","part":"changes","patch_ids":["c52d9511ff3d839984069acfe2584077"],"related_changes":[],"relations":[],"section":"变更","section_path":["变更"],"source_commits":["0002feb82"],"source_entry_id":"16.1/changes/023","source_hash":"aa0df2173190a1245d00cb5e75abdd8b4f7b506d4d6adf6d98d0c1814c16b779","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"ca3cf04094a037efb2f04550d4a478ab41ef5029c316cb9b3a6b3613b082f29b","text":"修复向分区表的批量表插入（Andres Freund）§ 跨分区不当共享插入状态可能导致 COPY FROM 期间的失败，通常表现为 “could not read block NNNN in file XXXX: read only 0 of 8192 bytes” 错误。","title":"修复向分区表的批量表插入","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["276393f53","910eb61b2"],"commit_groups":[["276393f53","910eb61b2"]],"commits":["910eb61b2"],"cves":[],"db_id":"cac9736a6dcbdf3c871b89e253e5e9e2","html":"\u003cp\u003e在 \u003ccode\u003eCOPY FROM\u003c/code\u003e 中，避免计算命令不需要的列默认值（Laurenz Albe）\u003ca href=\"https://postgr.es/c/910eb61b2\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e如果默认值对于该列实际上无效，或者默认表达式在当前执行上下文中会失败，这可以避免可能的错误。此类边界情况有时会在恢复转储时出现。之前的版本在此情况下不会失败，因此防止 v16 这样做。\u003c/p\u003e","id":"16.1-eaeb43dadd2766ed","identity_text":"In COPY FROM, avoid evaluating column default values that will not be needed by the command (Laurenz Albe) This avoids a possible error if the default value isn't actually valid for the column, or if the default's expression would fail in the current execution context. Such edge cases sometimes arise while restoring dumps, for example. Previous releases did not fail in this situation, so prevent v16 from doing so.","part":"changes","patch_ids":["f9a2545ac129503ec0f67146f6ae009b"],"related_changes":[],"relations":[],"section":"变更","section_path":["变更"],"source_commits":["910eb61b2"],"source_entry_id":"16.1/changes/024","source_hash":"7baf8bf72e5dd1d702ebb534b7098b3500c9197be6c1f6923909a2a484accce9","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"9ee82b9ec455473b610001bd8abbd0e2424315734ae4f50cf543faac42ab21f2","text":"在 COPY FROM 中，避免计算命令不需要的列默认值（Laurenz Albe）§ 如果默认值对于该列实际上无效，或者默认表达式在当前执行上下文中会失败，这可以避免可能的错误。此类边界情况有时会在恢复转储时出现。之前的版本在此情况下不会失败，因此防止 v16 这样做。","title":"在 COPY FROM 中，避免计算命令不需要的列默认值","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["95fd5c89f","a715c0212","d8a09939a","ea0e7cd6b"],"commit_groups":[["95fd5c89f","a715c0212","d8a09939a","ea0e7cd6b"]],"commits":["ea0e7cd6b"],"cves":[],"db_id":"0638eabc74ed6a234b59ea8cc3976587","html":"\u003cp\u003e在 \u003ccode\u003eCOPY FROM\u003c/code\u003e 中，当需要不支持的编码转换时干净地失败（Tom Lane）\u003ca href=\"https://postgr.es/c/ea0e7cd6b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e最近的重构意外地移除了预期的错误检查，导致显示 \u003cspan\u003e“\u003cspan\u003ecache lookup failed for function 0\u003c/span\u003e”\u003c/span\u003e 而非有用的错误消息。\u003c/p\u003e","id":"16.1-a29ff43ac2eb2535","identity_text":"In COPY FROM, fail cleanly when an unsupported encoding conversion is needed (Tom Lane) Recent refactoring accidentally removed the intended error check for this, such that it ended in cache lookup failed for function 0 instead of a useful error message.","part":"changes","patch_ids":["8a2c3dd9b4c0ccf96cd046c1ed398d6e"],"related_changes":[{"db_id":"eedfb9d94f990e6e8af3dfddc838e58a","evidence":{"patch_ids":["8a2c3dd9b4c0ccf96cd046c1ed398d6e"],"same_day":true,"statement_hash":"90b612f4d96a5c3c42a98f84aa4fd3a5b99687123d4e80c21abc2c959e5b1ac1"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"在 COPY FROM 中，当需要不支持的编码转换时干净地失败","url":"/docs/compare/?release=15.5#15.5-18f281375aa70b40","version":"15.5"},{"db_id":"58345bdbdc05d0bc9de24c7d2ede9fd7","evidence":{"patch_ids":["8a2c3dd9b4c0ccf96cd046c1ed398d6e"],"same_day":true,"statement_hash":"90b612f4d96a5c3c42a98f84aa4fd3a5b99687123d4e80c21abc2c959e5b1ac1"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"在 COPY FROM 中，当需要不支持的编码转换时干净地失败","url":"/docs/compare/?release=14.10#14.10-20bc347ab7711845","version":"14.10"}],"relations":[{"evidence":{"patch_ids":["8a2c3dd9b4c0ccf96cd046c1ed398d6e"],"same_day":true,"statement_hash":"90b612f4d96a5c3c42a98f84aa4fd3a5b99687123d4e80c21abc2c959e5b1ac1"},"rule":2,"target":"58345bdbdc05d0bc9de24c7d2ede9fd7","type":"equivalent"},{"evidence":{"patch_ids":["8a2c3dd9b4c0ccf96cd046c1ed398d6e"],"same_day":true,"statement_hash":"90b612f4d96a5c3c42a98f84aa4fd3a5b99687123d4e80c21abc2c959e5b1ac1"},"rule":2,"target":"eedfb9d94f990e6e8af3dfddc838e58a","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["ea0e7cd6b"],"source_entry_id":"16.1/changes/025","source_hash":"d3431335aecf24b7741699826fe01fd954283a00e565204dd03ca9ea73d14007","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"90b612f4d96a5c3c42a98f84aa4fd3a5b99687123d4e80c21abc2c959e5b1ac1","text":"在 COPY FROM 中，当需要不支持的编码转换时干净地失败（Tom Lane）§ 最近的重构意外地移除了预期的错误检查，导致显示 “cache lookup failed for function 0” 而非有用的错误消息。","title":"在 COPY FROM 中，当需要不支持的编码转换时干净地失败","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["137227c6d","47c0f00cf","65810fc6d","6e1cca511","7704a1a72","82063edd4","ae33659d4"],"commit_groups":[["137227c6d","47c0f00cf","65810fc6d","6e1cca511","7704a1a72","82063edd4","ae33659d4"]],"commits":["82063edd4"],"cves":[],"db_id":"9c3cee52848b8c6493f34682b1872615","html":"\u003cp\u003e避免在 \u003ccode\u003eEXPLAIN\u003c/code\u003e 中，当标记为由 \u003ccode\u003eEXPLAIN\u003c/code\u003e 显示的参数具有 NULL 启动时值时发生崩溃（Xing Guo，Aleksander Alekseev，Tom Lane）\u003ca href=\"https://postgr.es/c/82063edd4\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e没有内置参数符合此描述，但扩展可以定义此类参数。\u003c/p\u003e","id":"16.1-a38eec1a0d654ac8","identity_text":"Avoid crash in EXPLAIN if a parameter marked to be displayed by EXPLAIN has a NULL boot-time value (Xing Guo, Aleksander Alekseev, Tom Lane) No built-in parameter fits this description, but an extension could define such a parameter.","part":"changes","patch_ids":["db9cb6e54672e12ca6a5690536edb283"],"related_changes":[{"db_id":"ed131854c44aa976a38ce3b448861a96","evidence":{"patch_ids":["db9cb6e54672e12ca6a5690536edb283"],"same_day":true,"statement_hash":"5fed92b774d62537d533a638909f2d8fcb35a87cb163cfc0f6a3e03aeb8733c0"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"避免在 EXPLAIN 中，当标记为由 EXPLAIN 显示的参数具有 NULL 启动时值时发生崩溃","url":"/docs/compare/?release=15.5#15.5-c981e8975ec273bb","version":"15.5"},{"db_id":"402f8fbb582b049d49cb639f137c7d21","evidence":{"patch_ids":["db9cb6e54672e12ca6a5690536edb283"],"same_day":true,"statement_hash":"5fed92b774d62537d533a638909f2d8fcb35a87cb163cfc0f6a3e03aeb8733c0"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"避免在 EXPLAIN 中，当标记为由 EXPLAIN 显示的参数具有 NULL 启动时值时发生崩溃","url":"/docs/compare/?release=14.10#14.10-a03d26669de89f68","version":"14.10"},{"db_id":"c082f950476dcdc3b153213829f7f87e","evidence":{"patch_ids":["db9cb6e54672e12ca6a5690536edb283"],"same_day":true,"statement_hash":"5fed92b774d62537d533a638909f2d8fcb35a87cb163cfc0f6a3e03aeb8733c0"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"避免在 EXPLAIN 中，当标记为由 EXPLAIN 显示的参数具有 NULL 启动时值时发生崩溃","url":"/docs/compare/?release=13.13#13.13-9ea046baaca2754a","version":"13.13"},{"db_id":"fa2e40cac871ac177af8d24ec1a895ac","evidence":{"patch_ids":["db9cb6e54672e12ca6a5690536edb283"],"same_day":true,"statement_hash":"5fed92b774d62537d533a638909f2d8fcb35a87cb163cfc0f6a3e03aeb8733c0"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"避免在 EXPLAIN 中，当标记为由 EXPLAIN 显示的参数具有 NULL 启动时值时发生崩溃","url":"/docs/compare/?release=12.17#12.17-876012bf6d39eed4","version":"12.17"}],"relations":[{"evidence":{"patch_ids":["db9cb6e54672e12ca6a5690536edb283"],"same_day":true,"statement_hash":"5fed92b774d62537d533a638909f2d8fcb35a87cb163cfc0f6a3e03aeb8733c0"},"rule":2,"target":"402f8fbb582b049d49cb639f137c7d21","type":"equivalent"},{"evidence":{"patch_ids":["db9cb6e54672e12ca6a5690536edb283"],"same_day":true,"statement_hash":"5fed92b774d62537d533a638909f2d8fcb35a87cb163cfc0f6a3e03aeb8733c0"},"rule":2,"target":"c082f950476dcdc3b153213829f7f87e","type":"equivalent"},{"evidence":{"patch_ids":["db9cb6e54672e12ca6a5690536edb283"],"same_day":true,"statement_hash":"5fed92b774d62537d533a638909f2d8fcb35a87cb163cfc0f6a3e03aeb8733c0"},"rule":2,"target":"ed131854c44aa976a38ce3b448861a96","type":"equivalent"},{"evidence":{"patch_ids":["db9cb6e54672e12ca6a5690536edb283"],"same_day":true,"statement_hash":"5fed92b774d62537d533a638909f2d8fcb35a87cb163cfc0f6a3e03aeb8733c0"},"rule":2,"target":"fa2e40cac871ac177af8d24ec1a895ac","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["82063edd4"],"source_entry_id":"16.1/changes/026","source_hash":"a84cb1f991631f0d1db95d14cdd6cf28c0b406e5834ffc887da6532abf3eb859","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"5fed92b774d62537d533a638909f2d8fcb35a87cb163cfc0f6a3e03aeb8733c0","text":"避免在 EXPLAIN 中，当标记为由 EXPLAIN 显示的参数具有 NULL 启动时值时发生崩溃（Xing Guo，Aleksander Alekseev，Tom Lane）§ 没有内置参数符合此描述，但扩展可以定义此类参数。","title":"避免在 EXPLAIN 中，当标记为由 EXPLAIN 显示的参数具有 NULL 启动时值时发生崩溃","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["07eb22a77","0d1a7cd14","1e678175c","54b208f90","57e6e861d","a295684b8","f6e1ee3cf"],"commit_groups":[["07eb22a77","0d1a7cd14","1e678175c","54b208f90","57e6e861d","a295684b8","f6e1ee3cf"]],"commits":["57e6e861d"],"cves":[],"db_id":"407d669577583d994c8a923628cfb466","html":"\u003cp\u003e确保在删除 \u003ccode\u003eON COMMIT DROP\u003c/code\u003e 临时表时拥有快照（Tom Lane）\u003ca href=\"https://postgr.es/c/57e6e861d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e这可以防止当临时表的某些目录条目的字段宽度足够大而需要 toast 时（例如非常复杂的 \u003ccode\u003eCHECK\u003c/code\u003e 条件）可能出现的异常行为。\u003c/p\u003e","id":"16.1-dc4a298e2ddbebfd","identity_text":"Ensure we have a snapshot while dropping ON COMMIT DROP temp tables (Tom Lane) This prevents possible misbehavior if any catalog entries for the temp tables have fields wide enough to require toasting (such as a very complex CHECK condition).","part":"changes","patch_ids":["c55225c904210c85f5efed9b6a1e3263"],"related_changes":[{"db_id":"2b62b18d82a9ef200e53901779e106f2","evidence":{"patch_ids":["c55225c904210c85f5efed9b6a1e3263"],"same_day":true,"statement_hash":"24ef383d53726d9d6fbca1c28aacb3c6dab535178409e21304b16e951fd54801"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"确保在删除 ON COMMIT DROP 临时表时拥有快照","url":"/docs/compare/?release=15.5#15.5-9ef8dfc29466c041","version":"15.5"},{"db_id":"4b62dcb740a8b6624d22c52faad9538f","evidence":{"patch_ids":["c55225c904210c85f5efed9b6a1e3263"],"same_day":true,"statement_hash":"24ef383d53726d9d6fbca1c28aacb3c6dab535178409e21304b16e951fd54801"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"确保在删除 ON COMMIT DROP 临时表时拥有快照","url":"/docs/compare/?release=14.10#14.10-043a9a7d186900ec","version":"14.10"},{"db_id":"8b6727c81f63fe1001b5db3297261daf","evidence":{"patch_ids":["c55225c904210c85f5efed9b6a1e3263"],"same_day":true,"statement_hash":"24ef383d53726d9d6fbca1c28aacb3c6dab535178409e21304b16e951fd54801"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"确保在删除 ON COMMIT DROP 临时表时拥有快照","url":"/docs/compare/?release=13.13#13.13-0f256716aa6265f6","version":"13.13"},{"db_id":"4cbb3e8dcbce0228fedd00e60cc0d38e","evidence":{"patch_ids":["c55225c904210c85f5efed9b6a1e3263"],"same_day":true,"statement_hash":"24ef383d53726d9d6fbca1c28aacb3c6dab535178409e21304b16e951fd54801"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"确保在删除 ON COMMIT DROP 临时表时拥有快照","url":"/docs/compare/?release=12.17#12.17-e19e21b82f0c9b3f","version":"12.17"},{"db_id":"8b39165ae7d3eb4017dc155244906002","evidence":{"patch_ids":["c55225c904210c85f5efed9b6a1e3263"],"same_day":true,"statement_hash":"24ef383d53726d9d6fbca1c28aacb3c6dab535178409e21304b16e951fd54801"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"确保在删除 ON COMMIT DROP 临时表时拥有快照","url":"/docs/compare/?release=11.22#11.22-5fb1657482018dac","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["c55225c904210c85f5efed9b6a1e3263"],"same_day":true,"statement_hash":"24ef383d53726d9d6fbca1c28aacb3c6dab535178409e21304b16e951fd54801"},"rule":2,"target":"2b62b18d82a9ef200e53901779e106f2","type":"equivalent"},{"evidence":{"patch_ids":["c55225c904210c85f5efed9b6a1e3263"],"same_day":true,"statement_hash":"24ef383d53726d9d6fbca1c28aacb3c6dab535178409e21304b16e951fd54801"},"rule":2,"target":"4b62dcb740a8b6624d22c52faad9538f","type":"equivalent"},{"evidence":{"patch_ids":["c55225c904210c85f5efed9b6a1e3263"],"same_day":true,"statement_hash":"24ef383d53726d9d6fbca1c28aacb3c6dab535178409e21304b16e951fd54801"},"rule":2,"target":"4cbb3e8dcbce0228fedd00e60cc0d38e","type":"equivalent"},{"evidence":{"patch_ids":["c55225c904210c85f5efed9b6a1e3263"],"same_day":true,"statement_hash":"24ef383d53726d9d6fbca1c28aacb3c6dab535178409e21304b16e951fd54801"},"rule":2,"target":"8b39165ae7d3eb4017dc155244906002","type":"equivalent"},{"evidence":{"patch_ids":["c55225c904210c85f5efed9b6a1e3263"],"same_day":true,"statement_hash":"24ef383d53726d9d6fbca1c28aacb3c6dab535178409e21304b16e951fd54801"},"rule":2,"target":"8b6727c81f63fe1001b5db3297261daf","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["57e6e861d"],"source_entry_id":"16.1/changes/027","source_hash":"248401e1662a4ea82d8f59c8f683edb3bb0661a42193b722bcc2ac24cd752f45","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"24ef383d53726d9d6fbca1c28aacb3c6dab535178409e21304b16e951fd54801","text":"确保在删除 ON COMMIT DROP 临时表时拥有快照（Tom Lane）§ 这可以防止当临时表的某些目录条目的字段宽度足够大而需要 toast 时（例如非常复杂的 CHECK 条件）可能出现的异常行为。","title":"确保在删除 ON COMMIT DROP 临时表时拥有快照","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["0e32652a7","54fc9dca5","555bc89c9","97550c071","ac1dfc303","bc322c73c","c9265ae80","d0e7f95b4","e2e169042","ebc093fa6","ee06199fc"],"commit_groups":[["0e32652a7","555bc89c9","bc322c73c","ebc093fa6"],["54fc9dca5","97550c071","ac1dfc303","c9265ae80","d0e7f95b4","e2e169042","ee06199fc"]],"commits":["ee06199fc"],"cves":[],"db_id":"18e7bd1ad49b965b86d9d78ab6bf85ba","html":"\u003cp\u003e避免在 \u003ccode\u003esystem()\u003c/code\u003e 刚刚 fork 的子进程中对关闭信号的不当响应（Nathan Bossart）\u003ca href=\"https://postgr.es/c/ee06199fc\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e此修复避免了一个竞争条件：由 \u003ccode\u003esystem()\u003c/code\u003e fork 出来但尚未 exec 目标子程序的子进程可能接收并处理原本发给父服务器进程的信号。这将导致重复的清理操作，后果不佳。\u003c/p\u003e","id":"16.1-ef271e3f084fd9c4","identity_text":"Avoid improper response to shutdown signals in child processes just forked by system() (Nathan Bossart) This fix avoids a race condition in which a child process that has been forked off by system(), but hasn't yet exec'd the intended child program, might receive and act on a signal intended for the parent server process. That would lead to duplicate cleanup actions being performed, which will not end well.","part":"changes","patch_ids":["020e563d2e8c3f57c72b9597fd089c82","ac576f30d6734990ee5451f8c6c1cdc6"],"related_changes":[{"db_id":"37627097c59ef26d03af9618bfb0558a","evidence":{"patch_ids":["020e563d2e8c3f57c72b9597fd089c82","ac576f30d6734990ee5451f8c6c1cdc6"],"same_day":true,"statement_hash":"983d3d4a55c5cd7696079d1f6baf1403abb2a93dcaa8644ae89a6ca2a6338b84"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"避免在 system() 刚刚 fork 的子进程中对关闭信号的不当响应","url":"/docs/compare/?release=15.5#15.5-2d3248a46971eb29","version":"15.5"},{"db_id":"3a09791126686461e747c0dd65a2078a","evidence":{"patch_ids":["020e563d2e8c3f57c72b9597fd089c82","ac576f30d6734990ee5451f8c6c1cdc6"],"same_day":true,"statement_hash":"983d3d4a55c5cd7696079d1f6baf1403abb2a93dcaa8644ae89a6ca2a6338b84"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"避免在 system() 刚刚 fork 的子进程中对关闭信号的不当响应","url":"/docs/compare/?release=14.10#14.10-57d9602e7daaba86","version":"14.10"},{"db_id":"033f701f7a26ba319512b1c4dfeb5ee1","evidence":{"patch_ids":["020e563d2e8c3f57c72b9597fd089c82","ac576f30d6734990ee5451f8c6c1cdc6"],"same_day":true,"statement_hash":"983d3d4a55c5cd7696079d1f6baf1403abb2a93dcaa8644ae89a6ca2a6338b84"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"避免在 system() 刚刚 fork 的子进程中对关闭信号的不当响应","url":"/docs/compare/?release=13.13#13.13-38c971e1223bb141","version":"13.13"},{"db_id":"82b3b1253b45baff6df74b7d093a3736","evidence":{"patch_ids":["020e563d2e8c3f57c72b9597fd089c82","ac576f30d6734990ee5451f8c6c1cdc6"],"same_day":true,"statement_hash":"983d3d4a55c5cd7696079d1f6baf1403abb2a93dcaa8644ae89a6ca2a6338b84"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"避免在 system() 刚刚 fork 的子进程中对关闭信号的不当响应","url":"/docs/compare/?release=12.17#12.17-cd86f26da1424957","version":"12.17"},{"db_id":"d8c01110f01b4e8bcb6266e806adf7b0","evidence":{"patch_ids":["020e563d2e8c3f57c72b9597fd089c82","ac576f30d6734990ee5451f8c6c1cdc6"],"same_day":true,"statement_hash":"983d3d4a55c5cd7696079d1f6baf1403abb2a93dcaa8644ae89a6ca2a6338b84"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"避免在 system() 刚刚 fork 的子进程中对关闭信号的不当响应","url":"/docs/compare/?release=11.22#11.22-a268e941230868b8","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["020e563d2e8c3f57c72b9597fd089c82","ac576f30d6734990ee5451f8c6c1cdc6"],"same_day":true,"statement_hash":"983d3d4a55c5cd7696079d1f6baf1403abb2a93dcaa8644ae89a6ca2a6338b84"},"rule":2,"target":"033f701f7a26ba319512b1c4dfeb5ee1","type":"equivalent"},{"evidence":{"patch_ids":["020e563d2e8c3f57c72b9597fd089c82","ac576f30d6734990ee5451f8c6c1cdc6"],"same_day":true,"statement_hash":"983d3d4a55c5cd7696079d1f6baf1403abb2a93dcaa8644ae89a6ca2a6338b84"},"rule":2,"target":"37627097c59ef26d03af9618bfb0558a","type":"equivalent"},{"evidence":{"patch_ids":["020e563d2e8c3f57c72b9597fd089c82","ac576f30d6734990ee5451f8c6c1cdc6"],"same_day":true,"statement_hash":"983d3d4a55c5cd7696079d1f6baf1403abb2a93dcaa8644ae89a6ca2a6338b84"},"rule":2,"target":"3a09791126686461e747c0dd65a2078a","type":"equivalent"},{"evidence":{"patch_ids":["020e563d2e8c3f57c72b9597fd089c82","ac576f30d6734990ee5451f8c6c1cdc6"],"same_day":true,"statement_hash":"983d3d4a55c5cd7696079d1f6baf1403abb2a93dcaa8644ae89a6ca2a6338b84"},"rule":2,"target":"82b3b1253b45baff6df74b7d093a3736","type":"equivalent"},{"evidence":{"patch_ids":["020e563d2e8c3f57c72b9597fd089c82","ac576f30d6734990ee5451f8c6c1cdc6"],"same_day":true,"statement_hash":"983d3d4a55c5cd7696079d1f6baf1403abb2a93dcaa8644ae89a6ca2a6338b84"},"rule":2,"target":"d8c01110f01b4e8bcb6266e806adf7b0","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["555bc89c9","ee06199fc"],"source_entry_id":"16.1/changes/028","source_hash":"6c871c2d720fa799c8da5a3cda1070a04b61c8b60a824d58d6e798c0e1e687e5","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"983d3d4a55c5cd7696079d1f6baf1403abb2a93dcaa8644ae89a6ca2a6338b84","text":"避免在 system() 刚刚 fork 的子进程中对关闭信号的不当响应（Nathan Bossart）§ 此修复避免了一个竞争条件：由 system() fork 出来但尚未 exec 目标子程序的子进程可能接收并处理原本发给父服务器进程的信号。这将导致重复的清理操作，后果不佳。","title":"避免在 system() 刚刚 fork 的子进程中对关闭信号的不当响应","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["43c979086","5725e4ebe","5e39884d3","63a582222","67060be3d","dc75748a9"],"commit_groups":[["43c979086","5725e4ebe","5e39884d3","63a582222","67060be3d","dc75748a9"]],"commits":["5725e4ebe"],"cves":[],"db_id":"2aed2e6c8bc311238f4f5c9a6d764468","html":"\u003cp\u003e处理前端程序中 \u003ccode\u003epg_control\u003c/code\u003e 的撕裂读取（Thomas Munro）\u003ca href=\"https://postgr.es/c/5725e4ebe\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e在某些文件系统上，当服务器并发写入 \u003ccode\u003epg_control\u003c/code\u003e 时，读取该文件可能不是原子操作。这可以通过无效的 CRC 来检测。现在在报告错误之前会重试几次以查看文件是否变为有效。\u003c/p\u003e","id":"16.1-d3933311eb81045c","identity_text":"Cope with torn reads of pg_control in frontend programs (Thomas Munro) On some file systems, reading pg_control may not be an atomic action when the server concurrently writes that file. This is detectable via a bad CRC. Retry a few times to see if the file becomes valid before we report error.","part":"changes","patch_ids":["9fc294bfeafe9138d877c88cc7a9123f"],"related_changes":[{"db_id":"2b0f32989fe28b5feb764a12a1e483c0","evidence":{"patch_ids":["9fc294bfeafe9138d877c88cc7a9123f"],"same_day":true,"statement_hash":"0a9493fc5fa963db45149ab87bf2f35549cad2cc8f007f00ec077e686921f1ed"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"处理前端程序中 pg_control 的撕裂读取","url":"/docs/compare/?release=15.5#15.5-7e718a6b14550c44","version":"15.5"},{"db_id":"d1b19018b9230ecd474a081c16df3aee","evidence":{"patch_ids":["9fc294bfeafe9138d877c88cc7a9123f"],"same_day":true,"statement_hash":"0a9493fc5fa963db45149ab87bf2f35549cad2cc8f007f00ec077e686921f1ed"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"处理前端程序中 pg_control 的撕裂读取","url":"/docs/compare/?release=14.10#14.10-53baf7fd24177a2c","version":"14.10"},{"db_id":"d9bf0b903f5115a4e404da89b7d8298a","evidence":{"patch_ids":["9fc294bfeafe9138d877c88cc7a9123f"],"same_day":true,"statement_hash":"0a9493fc5fa963db45149ab87bf2f35549cad2cc8f007f00ec077e686921f1ed"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"处理前端程序中 pg_control 的撕裂读取","url":"/docs/compare/?release=13.13#13.13-c5f7f1cc760623bf","version":"13.13"},{"db_id":"1c4370d23701d45f35875358360f8270","evidence":{"patch_ids":["9fc294bfeafe9138d877c88cc7a9123f"],"same_day":true,"statement_hash":"0a9493fc5fa963db45149ab87bf2f35549cad2cc8f007f00ec077e686921f1ed"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"处理前端程序中 pg_control 的撕裂读取","url":"/docs/compare/?release=12.17#12.17-4e6f6a5b3a7d8b70","version":"12.17"}],"relations":[{"evidence":{"patch_ids":["9fc294bfeafe9138d877c88cc7a9123f"],"same_day":true,"statement_hash":"0a9493fc5fa963db45149ab87bf2f35549cad2cc8f007f00ec077e686921f1ed"},"rule":2,"target":"1c4370d23701d45f35875358360f8270","type":"equivalent"},{"evidence":{"patch_ids":["9fc294bfeafe9138d877c88cc7a9123f"],"same_day":true,"statement_hash":"0a9493fc5fa963db45149ab87bf2f35549cad2cc8f007f00ec077e686921f1ed"},"rule":2,"target":"2b0f32989fe28b5feb764a12a1e483c0","type":"equivalent"},{"evidence":{"patch_ids":["9fc294bfeafe9138d877c88cc7a9123f"],"same_day":true,"statement_hash":"0a9493fc5fa963db45149ab87bf2f35549cad2cc8f007f00ec077e686921f1ed"},"rule":2,"target":"d1b19018b9230ecd474a081c16df3aee","type":"equivalent"},{"evidence":{"patch_ids":["9fc294bfeafe9138d877c88cc7a9123f"],"same_day":true,"statement_hash":"0a9493fc5fa963db45149ab87bf2f35549cad2cc8f007f00ec077e686921f1ed"},"rule":2,"target":"d9bf0b903f5115a4e404da89b7d8298a","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["5725e4ebe"],"source_entry_id":"16.1/changes/029","source_hash":"c956281b1c0d17ab4eca93b5eff650b669d2bcef5e4278b8e17cf5ea3ccf6605","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"0a9493fc5fa963db45149ab87bf2f35549cad2cc8f007f00ec077e686921f1ed","text":"处理前端程序中 pg_control 的撕裂读取（Thomas Munro）§ 在某些文件系统上，当服务器并发写入 pg_control 时，读取该文件可能不是原子操作。这可以通过无效的 CRC 来检测。现在在报告错误之前会重试几次以查看文件是否变为有效。","title":"处理前端程序中 pg_control 的撕裂读取","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["2371432cd","606be8a35","637e86ecc","a56fe5cf0","ae9da357b","c558e6fd9","f1634c968"],"commit_groups":[["2371432cd","606be8a35","637e86ecc","a56fe5cf0","ae9da357b","c558e6fd9","f1634c968"]],"commits":["2371432cd"],"cves":[],"db_id":"250fa1d7beb1bc326fd6d8fa82753615","html":"\u003cp\u003e避免在相关 SQL 函数中对 \u003ccode\u003epg_control\u003c/code\u003e 的撕裂读取（Thomas Munro）\u003ca href=\"https://postgr.es/c/2371432cd\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e在读取 \u003ccode\u003epg_control\u003c/code\u003e 之前获取适当的锁，以确保获得该文件的一致视图。\u003c/p\u003e","id":"16.1-aab675f6119e32be","identity_text":"Avoid torn reads of pg_control in relevant SQL functions (Thomas Munro) Acquire the appropriate lock before reading pg_control, to ensure we get a consistent view of that file.","part":"changes","patch_ids":["d67f4445b83644d5a53d5ccfbddd5589"],"related_changes":[{"db_id":"74fca8055e2e50da58aa180c287110ad","evidence":{"patch_ids":["d67f4445b83644d5a53d5ccfbddd5589"],"same_day":true,"statement_hash":"aa71ec65e193fb08b29d2704a19128805872cede43991d458e0c5bb1afcbda16"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"避免在相关 SQL 函数中对 pg_control 的撕裂读取","url":"/docs/compare/?release=15.5#15.5-59f381aab979034a","version":"15.5"},{"db_id":"774bcf5dde9193debb738b2014eb881f","evidence":{"patch_ids":["d67f4445b83644d5a53d5ccfbddd5589"],"same_day":true,"statement_hash":"aa71ec65e193fb08b29d2704a19128805872cede43991d458e0c5bb1afcbda16"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"避免在相关 SQL 函数中对 pg_control 的撕裂读取","url":"/docs/compare/?release=14.10#14.10-3f872020ab5a3531","version":"14.10"},{"db_id":"0c67b181e69bcc974c6d7854c72f2fb6","evidence":{"patch_ids":["d67f4445b83644d5a53d5ccfbddd5589"],"same_day":true,"statement_hash":"aa71ec65e193fb08b29d2704a19128805872cede43991d458e0c5bb1afcbda16"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"避免在相关 SQL 函数中对 pg_control 的撕裂读取","url":"/docs/compare/?release=13.13#13.13-c4e624e4cba926f3","version":"13.13"},{"db_id":"a6df5b569e7d40c0018f25f07eee2679","evidence":{"patch_ids":["d67f4445b83644d5a53d5ccfbddd5589"],"same_day":true,"statement_hash":"aa71ec65e193fb08b29d2704a19128805872cede43991d458e0c5bb1afcbda16"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"避免在相关 SQL 函数中对 pg_control 的撕裂读取","url":"/docs/compare/?release=12.17#12.17-4154cad8425b2490","version":"12.17"},{"db_id":"4aa535a7d8a738ca8b634def86561904","evidence":{"patch_ids":["d67f4445b83644d5a53d5ccfbddd5589"],"same_day":true,"statement_hash":"aa71ec65e193fb08b29d2704a19128805872cede43991d458e0c5bb1afcbda16"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"避免在相关 SQL 函数中对 pg_control 的撕裂读取","url":"/docs/compare/?release=11.22#11.22-11b0f4811f381186","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["d67f4445b83644d5a53d5ccfbddd5589"],"same_day":true,"statement_hash":"aa71ec65e193fb08b29d2704a19128805872cede43991d458e0c5bb1afcbda16"},"rule":2,"target":"0c67b181e69bcc974c6d7854c72f2fb6","type":"equivalent"},{"evidence":{"patch_ids":["d67f4445b83644d5a53d5ccfbddd5589"],"same_day":true,"statement_hash":"aa71ec65e193fb08b29d2704a19128805872cede43991d458e0c5bb1afcbda16"},"rule":2,"target":"4aa535a7d8a738ca8b634def86561904","type":"equivalent"},{"evidence":{"patch_ids":["d67f4445b83644d5a53d5ccfbddd5589"],"same_day":true,"statement_hash":"aa71ec65e193fb08b29d2704a19128805872cede43991d458e0c5bb1afcbda16"},"rule":2,"target":"74fca8055e2e50da58aa180c287110ad","type":"equivalent"},{"evidence":{"patch_ids":["d67f4445b83644d5a53d5ccfbddd5589"],"same_day":true,"statement_hash":"aa71ec65e193fb08b29d2704a19128805872cede43991d458e0c5bb1afcbda16"},"rule":2,"target":"774bcf5dde9193debb738b2014eb881f","type":"equivalent"},{"evidence":{"patch_ids":["d67f4445b83644d5a53d5ccfbddd5589"],"same_day":true,"statement_hash":"aa71ec65e193fb08b29d2704a19128805872cede43991d458e0c5bb1afcbda16"},"rule":2,"target":"a6df5b569e7d40c0018f25f07eee2679","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["2371432cd"],"source_entry_id":"16.1/changes/030","source_hash":"68e3eb64006075a9e6b2e0a11157cc21f6703720e515c1ff701f25d1f94fd5ee","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"aa71ec65e193fb08b29d2704a19128805872cede43991d458e0c5bb1afcbda16","text":"避免在相关 SQL 函数中对 pg_control 的撕裂读取（Thomas Munro）§ 在读取 pg_control 之前获取适当的锁，以确保获得该文件的一致视图。","title":"避免在相关 SQL 函数中对 pg_control 的撕裂读取","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["9154ededf","d8a295389"],"commit_groups":[["9154ededf","d8a295389"]],"commits":["9154ededf"],"cves":[],"db_id":"758e72cfbf62a2675143bab4cd147991","html":"\u003cp\u003e修复在规划带有 \u003ccode\u003eORDER BY\u003c/code\u003e 或 \u003ccode\u003eDISTINCT\u003c/code\u003e 选项的聚合函数时出现的 \u003cspan\u003e“\u003cspan\u003ecould not find pathkey item to sort\u003c/span\u003e”\u003c/span\u003e 错误（David Rowley）\u003ca href=\"https://postgr.es/c/9154ededf\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-72b665346a46a560","identity_text":"Fix could not find pathkey item to sort errors occurring while planning aggregate functions with ORDER BY or DISTINCT options (David Rowley)","part":"changes","patch_ids":["b57991fb6e8335892c54ac587bf1d1c7"],"related_changes":[],"relations":[],"section":"变更","section_path":["变更"],"source_commits":["9154ededf"],"source_entry_id":"16.1/changes/031","source_hash":"fa593ce7e025c084d4b4662a23b0dc2de1434148db3e10cda9d4c500af010c9d","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"7ca96db32e8b1992e993d535ba521bc426b49502a784782aca2433f78c0d10b4","text":"修复在规划带有 ORDER BY 或 DISTINCT 选项的聚合函数时出现的 “could not find pathkey item to sort” 错误（David Rowley）§","title":"修复在规划带有 ORDER BY 或 DISTINCT 选项的聚合函数时出现的 “could not find pathkey item to sort” 错误","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["75f31a3f2","95e91da66","9b3900cdb","a0b013625","a956bd3fa","f91c87b31"],"commit_groups":[["75f31a3f2","95e91da66","9b3900cdb","a0b013625","a956bd3fa","f91c87b31"]],"commits":["75f31a3f2"],"cves":[],"db_id":"99bfcc92586904dc2cdcaf30e96c72e1","html":"\u003cp\u003e避免计算后端活动字符串数组大小时的整数溢出（Jakub Wartak）\u003ca href=\"https://postgr.es/c/75f31a3f2\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e在 64 位机器上，我们允许 \u003ccode\u003etrack_activity_query_size\u003c/code\u003e 的值大到足以在乘以允许的连接数时导致 32 位溢出。然而，实际分配每个后端本地数组的代码对此不够谨慎，导致数组分配不正确。\u003c/p\u003e","id":"16.1-9792979ed6190d7b","identity_text":"Avoid integer overflow when computing size of backend activity string array (Jakub Wartak) On 64-bit machines we will allow values of track_activity_query_size large enough to cause 32-bit overflow when multiplied by the allowed number of connections. The code actually allocating the per-backend local array was careless about this though, and allocated the array incorrectly.","part":"changes","patch_ids":["46c4e8ba92be13fd6488a0d629a4c25d"],"related_changes":[{"db_id":"ed4cc484d13babb5a5c068f95fea6c79","evidence":{"patch_ids":["46c4e8ba92be13fd6488a0d629a4c25d"],"same_day":true,"statement_hash":"8134673c40ff201f08ac108e602e19112aac9d8bace6f4000590946b43993f87"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"避免计算后端活动字符串数组大小时的整数溢出","url":"/docs/compare/?release=15.5#15.5-75496837be222e84","version":"15.5"},{"db_id":"86f661d67a291cdaaba7d905f23a8784","evidence":{"patch_ids":["46c4e8ba92be13fd6488a0d629a4c25d"],"same_day":true,"statement_hash":"8134673c40ff201f08ac108e602e19112aac9d8bace6f4000590946b43993f87"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"避免计算后端活动字符串数组大小时的整数溢出","url":"/docs/compare/?release=14.10#14.10-333f69f76f49f87a","version":"14.10"},{"db_id":"bf3781d62695a4da2886551e25f093c2","evidence":{"patch_ids":["46c4e8ba92be13fd6488a0d629a4c25d"],"same_day":true,"statement_hash":"8134673c40ff201f08ac108e602e19112aac9d8bace6f4000590946b43993f87"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"避免计算后端活动字符串数组大小时的整数溢出","url":"/docs/compare/?release=13.13#13.13-d210c182143d4a2a","version":"13.13"},{"db_id":"c2b17c108ca10ffae19fc1881e1675e9","evidence":{"patch_ids":["46c4e8ba92be13fd6488a0d629a4c25d"],"same_day":true,"statement_hash":"8134673c40ff201f08ac108e602e19112aac9d8bace6f4000590946b43993f87"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"避免计算后端活动字符串数组大小时的整数溢出","url":"/docs/compare/?release=12.17#12.17-05a140849df1b343","version":"12.17"}],"relations":[{"evidence":{"patch_ids":["46c4e8ba92be13fd6488a0d629a4c25d"],"same_day":true,"statement_hash":"8134673c40ff201f08ac108e602e19112aac9d8bace6f4000590946b43993f87"},"rule":2,"target":"86f661d67a291cdaaba7d905f23a8784","type":"equivalent"},{"evidence":{"patch_ids":["46c4e8ba92be13fd6488a0d629a4c25d"],"same_day":true,"statement_hash":"8134673c40ff201f08ac108e602e19112aac9d8bace6f4000590946b43993f87"},"rule":2,"target":"bf3781d62695a4da2886551e25f093c2","type":"equivalent"},{"evidence":{"patch_ids":["46c4e8ba92be13fd6488a0d629a4c25d"],"same_day":true,"statement_hash":"8134673c40ff201f08ac108e602e19112aac9d8bace6f4000590946b43993f87"},"rule":2,"target":"c2b17c108ca10ffae19fc1881e1675e9","type":"equivalent"},{"evidence":{"patch_ids":["46c4e8ba92be13fd6488a0d629a4c25d"],"same_day":true,"statement_hash":"8134673c40ff201f08ac108e602e19112aac9d8bace6f4000590946b43993f87"},"rule":2,"target":"ed4cc484d13babb5a5c068f95fea6c79","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["75f31a3f2"],"source_entry_id":"16.1/changes/032","source_hash":"308c6943d4255fbb6daf483e0b8d07cb683ac707b0a93d0e2d5ff400eaa6343c","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"8134673c40ff201f08ac108e602e19112aac9d8bace6f4000590946b43993f87","text":"避免计算后端活动字符串数组大小时的整数溢出（Jakub Wartak）§ 在 64 位机器上，我们允许 track_activity_query_size 的值大到足以在乘以允许的连接数时导致 32 位溢出。然而，实际分配每个后端本地数组的代码对此不够谨慎，导致数组分配不正确。","title":"避免计算后端活动字符串数组大小时的整数溢出","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["2d4f99bc6","5ae245664","992d2ca81","c181f2e2b","ed9247cd7"],"commit_groups":[["2d4f99bc6","5ae245664","992d2ca81","c181f2e2b","ed9247cd7"]],"commits":["992d2ca81"],"cves":[],"db_id":"b2cf0429fb83e1683a752f6c88341176","html":"\u003cp\u003e修复在继承表上执行 \u003ccode\u003eANALYZE\u003c/code\u003e 时短暂显示不一致的进度统计信息的问题（Heikki Linnakangas）\u003ca href=\"https://postgr.es/c/992d2ca81\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e块级别的计数器应在更新当前关系字段的同时重置为零。\u003c/p\u003e","id":"16.1-219c13f32aab94e0","identity_text":"Fix briefly showing inconsistent progress statistics for ANALYZE on inherited tables (Heikki Linnakangas) The block-level counters should be reset to zero at the same time we update the current-relation field.","part":"changes","patch_ids":["fb3db28284746e71ade490dd44b04d90"],"related_changes":[{"db_id":"d3e873296184e51f9badc05d554234eb","evidence":{"patch_ids":["fb3db28284746e71ade490dd44b04d90"],"same_day":true,"statement_hash":"3f3611ce9429eaabf1c46835ef931ed377946db82d92ee67fa60d64d5e2b98de"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复在继承表上执行 ANALYZE 时短暂显示不一致的进度统计信息的问题","url":"/docs/compare/?release=15.5#15.5-2c510de9de0126b0","version":"15.5"},{"db_id":"3e6301563d8b6f5deb51bd8d2a76467b","evidence":{"patch_ids":["fb3db28284746e71ade490dd44b04d90"],"same_day":true,"statement_hash":"3f3611ce9429eaabf1c46835ef931ed377946db82d92ee67fa60d64d5e2b98de"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复在继承表上执行 ANALYZE 时短暂显示不一致的进度统计信息的问题","url":"/docs/compare/?release=14.10#14.10-e9c7138faa92d9df","version":"14.10"},{"db_id":"d47cbf61bbae75cbdd9fccab5d410683","evidence":{"patch_ids":["fb3db28284746e71ade490dd44b04d90"],"same_day":true,"statement_hash":"3f3611ce9429eaabf1c46835ef931ed377946db82d92ee67fa60d64d5e2b98de"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复在继承表上执行 ANALYZE 时短暂显示不一致的进度统计信息的问题","url":"/docs/compare/?release=13.13#13.13-06f73ea6b2c20c9b","version":"13.13"}],"relations":[{"evidence":{"patch_ids":["fb3db28284746e71ade490dd44b04d90"],"same_day":true,"statement_hash":"3f3611ce9429eaabf1c46835ef931ed377946db82d92ee67fa60d64d5e2b98de"},"rule":2,"target":"3e6301563d8b6f5deb51bd8d2a76467b","type":"equivalent"},{"evidence":{"patch_ids":["fb3db28284746e71ade490dd44b04d90"],"same_day":true,"statement_hash":"3f3611ce9429eaabf1c46835ef931ed377946db82d92ee67fa60d64d5e2b98de"},"rule":2,"target":"d3e873296184e51f9badc05d554234eb","type":"equivalent"},{"evidence":{"patch_ids":["fb3db28284746e71ade490dd44b04d90"],"same_day":true,"statement_hash":"3f3611ce9429eaabf1c46835ef931ed377946db82d92ee67fa60d64d5e2b98de"},"rule":2,"target":"d47cbf61bbae75cbdd9fccab5d410683","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["992d2ca81"],"source_entry_id":"16.1/changes/033","source_hash":"5b26cca312fb758b31ea2c7528d2e0a20c901356679a9cba2214a785a456ed4c","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"3f3611ce9429eaabf1c46835ef931ed377946db82d92ee67fa60d64d5e2b98de","text":"修复在继承表上执行 ANALYZE 时短暂显示不一致的进度统计信息的问题（Heikki Linnakangas）§ 块级别的计数器应在更新当前关系字段的同时重置为零。","title":"修复在继承表上执行 ANALYZE 时短暂显示不一致的进度统计信息的问题","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["0684d1949","4a97a43a7","594001864","e64c733bb"],"commit_groups":[["0684d1949","4a97a43a7","594001864","e64c733bb"]],"commits":["4a97a43a7"],"cves":[],"db_id":"ba7050d4fb45b86d8cb4128edd2f7faf","html":"\u003cp\u003e修复后台写入器未将其 WAL 写入报告给统计计数器的问题（Nazir Bilal Yavuz）\u003ca href=\"https://postgr.es/c/4a97a43a7\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-65d8e82095353606","identity_text":"Fix the background writer to report any WAL writes it makes to the statistics counters (Nazir Bilal Yavuz)","part":"changes","patch_ids":["9da3f272b8d54d3634977d476657bfa2"],"related_changes":[{"db_id":"5196d330263bc0d2eedff1740498fd79","evidence":{"patch_ids":["9da3f272b8d54d3634977d476657bfa2"],"same_day":true,"statement_hash":"72b0dfd3d0fd9ee7d1d1ba924b8d4f880587fab7d3803fba5d6d8c8170c3423b"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复后台写入器未将其 WAL 写入报告给统计计数器的问题","url":"/docs/compare/?release=15.5#15.5-c829fbb3d50df948","version":"15.5"},{"db_id":"d30730476e35305f1aad73640f563c66","evidence":{"patch_ids":["9da3f272b8d54d3634977d476657bfa2"],"same_day":true,"statement_hash":"72b0dfd3d0fd9ee7d1d1ba924b8d4f880587fab7d3803fba5d6d8c8170c3423b"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复后台写入器未将其 WAL 写入报告给统计计数器的问题","url":"/docs/compare/?release=14.10#14.10-8729ca6f45d472eb","version":"14.10"}],"relations":[{"evidence":{"patch_ids":["9da3f272b8d54d3634977d476657bfa2"],"same_day":true,"statement_hash":"72b0dfd3d0fd9ee7d1d1ba924b8d4f880587fab7d3803fba5d6d8c8170c3423b"},"rule":2,"target":"5196d330263bc0d2eedff1740498fd79","type":"equivalent"},{"evidence":{"patch_ids":["9da3f272b8d54d3634977d476657bfa2"],"same_day":true,"statement_hash":"72b0dfd3d0fd9ee7d1d1ba924b8d4f880587fab7d3803fba5d6d8c8170c3423b"},"rule":2,"target":"d30730476e35305f1aad73640f563c66","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["4a97a43a7"],"source_entry_id":"16.1/changes/034","source_hash":"0ca5eb482829bba002b4664363c9c4f3c7275ec3d6e83b981e45e3c244b42b64","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"72b0dfd3d0fd9ee7d1d1ba924b8d4f880587fab7d3803fba5d6d8c8170c3423b","text":"修复后台写入器未将其 WAL 写入报告给统计计数器的问题（Nazir Bilal Yavuz）§","title":"修复后台写入器未将其 WAL 写入报告给统计计数器的问题","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["280f70221","802fcb9ed","e221c0bef"],"commit_groups":[["280f70221","802fcb9ed","e221c0bef"]],"commits":["280f70221"],"cves":[],"db_id":"07103065e4d28fe90e6907de186d3534","html":"\u003cp\u003e修复 \u003ccode\u003epgstat_report_wal()\u003c/code\u003e 中关于强制刷新行为的混淆（Ryoga Yoshida，Michael Paquier）\u003ca href=\"https://postgr.es/c/280f70221\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e这可能导致在关闭时丢失某些关于 WAL I/O 的统计信息。\u003c/p\u003e","id":"16.1-84da3c9473eb97ed","identity_text":"Fix confusion about forced-flush behavior in pgstat_report_wal() (Ryoga Yoshida, Michael Paquier) This could result in some statistics about WAL I/O being forgotten in a shutdown.","part":"changes","patch_ids":["bcc70799691f1b87110d3ab1bbbc598d"],"related_changes":[{"db_id":"defca0c80c6cc57f25260a051e6de054","evidence":{"patch_ids":["bcc70799691f1b87110d3ab1bbbc598d"],"same_day":true,"statement_hash":"c05253bb8e571a4c13d0caaab92b3fc1cacb91866d2403937d10597922b89eee"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复 pgstat_report_wal() 中关于强制刷新行为的混淆","url":"/docs/compare/?release=15.5#15.5-c2c94464e3a5be86","version":"15.5"}],"relations":[{"evidence":{"patch_ids":["bcc70799691f1b87110d3ab1bbbc598d"],"same_day":true,"statement_hash":"c05253bb8e571a4c13d0caaab92b3fc1cacb91866d2403937d10597922b89eee"},"rule":2,"target":"defca0c80c6cc57f25260a051e6de054","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["280f70221"],"source_entry_id":"16.1/changes/035","source_hash":"7eba8b37264b550198c52bfc98d434c4e46f979c1bd583bcba7f4e127b15f9bb","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"c05253bb8e571a4c13d0caaab92b3fc1cacb91866d2403937d10597922b89eee","text":"修复 pgstat_report_wal() 中关于强制刷新行为的混淆（Ryoga Yoshida，Michael Paquier）§ 这可能导致在关闭时丢失某些关于 WAL I/O 的统计信息。","title":"修复 pgstat_report_wal() 中关于强制刷新行为的混淆","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["7369798a8","c4758649b"],"commit_groups":[["7369798a8","c4758649b"]],"commits":["c4758649b"],"cves":[],"db_id":"b17222cb728fc30d2ddb95984b695671","html":"\u003cp\u003e修复临时表扩展的统计跟踪（Karina Litskevich，Andres Freund）\u003ca href=\"https://postgr.es/c/c4758649b\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e这些被计为普通表写入，而它们应该被计为临时表写入。\u003c/p\u003e","id":"16.1-e117945ed9e56ee1","identity_text":"Fix statistics tracking of temporary-table extensions (Karina Litskevich, Andres Freund) These were counted as normal-table writes when they should be counted as temp-table writes.","part":"changes","patch_ids":["aedf02c369f8a6a6217a56ba2ad93df8"],"related_changes":[],"relations":[],"section":"变更","section_path":["变更"],"source_commits":["c4758649b"],"source_entry_id":"16.1/changes/036","source_hash":"56f268c345672164561c51da458374fa45a8aafd468199cb4163bb3bd2ced1ae","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"e059b0da980edca7bcaee1cb39dc72302f86090d743158062cf045dc308211bf","text":"修复临时表扩展的统计跟踪（Karina Litskevich，Andres Freund）§ 这些被计为普通表写入，而它们应该被计为临时表写入。","title":"修复临时表扩展的统计跟踪","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["2308f18c0","d17ffc734"],"commit_groups":[["2308f18c0","d17ffc734"]],"commits":["2308f18c0"],"cves":[],"db_id":"1967317dda7fd19cf6159b69951726f3","html":"\u003cp\u003e当启用 \u003ccode\u003etrack_io_timing\u003c/code\u003e 时，将关系扩展操作所花费的时间包括为写入时间（Nazir Bilal Yavuz）\u003ca href=\"https://postgr.es/c/2308f18c0\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-71c6e8785e44f73d","identity_text":"When track_io_timing is enabled, include the time taken by relation extension operations as write time (Nazir Bilal Yavuz)","part":"changes","patch_ids":["1e35df545619f04d8b8884fe0d939598"],"related_changes":[],"relations":[],"section":"变更","section_path":["变更"],"source_commits":["2308f18c0"],"source_entry_id":"16.1/changes/037","source_hash":"cec37f4f807800e80cc1d6c4818eb36ca738f7b08cfcfb2b1dc4ec91752a8350","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"f060608d338809ac30181ab0f3a285e1f13a168734d964d9f564465e8da716a9","text":"当启用 track_io_timing 时，将关系扩展操作所花费的时间包括为写入时间（Nazir Bilal Yavuz）§","title":"当启用 track_io_timing 时，将关系扩展操作所花费的时间包括为写入时间","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["055f786ea","0e59266a5","4435a8d5d","5cff431bc","8cfc3e80b","dc8d72c1c","fdc7cf73b"],"commit_groups":[["055f786ea","0e59266a5","4435a8d5d","5cff431bc","8cfc3e80b","dc8d72c1c","fdc7cf73b"]],"commits":["055f786ea"],"cves":[],"db_id":"1a54405fa5176bd9ebd24191c281a464","html":"\u003cp\u003e跟踪缓存的 \u003ccode\u003eCALL\u003c/code\u003e 语句的依赖关系，并在需要时重新规划（Tom Lane）\u003ca href=\"https://postgr.es/c/055f786ea\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003eDDL 命令，例如替换已内联到 \u003ccode\u003eCALL\u003c/code\u003e 参数中的函数，可能需要重新规划已被 PL/pgSQL 缓存的 \u003ccode\u003eCALL\u003c/code\u003e。之前这不会发生，导致异常行为或诸如 \u003cspan\u003e“\u003cspan\u003ecache lookup failed\u003c/span\u003e”\u003c/span\u003e 之类的奇怪错误。\u003c/p\u003e","id":"16.1-53fe25698f0531de","identity_text":"Track the dependencies of cached CALL statements, and re-plan them when needed (Tom Lane) DDL commands, such as replacement of a function that has been inlined into a CALL argument, can create the need to re-plan a CALL that has been cached by PL/pgSQL. That was not happening, leading to misbehavior or strange errors such as cache lookup failed.","part":"changes","patch_ids":["d151b170f74e32a11350e7a972ecb744"],"related_changes":[{"db_id":"ad0b3fc1bbdac02757099b54bb9285a2","evidence":{"patch_ids":["d151b170f74e32a11350e7a972ecb744"],"same_day":true,"statement_hash":"dd5031bfee679f826d6e6229ff8033d590ea9374c21617cb2ba371befb7bb52d"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"跟踪缓存的 CALL 语句的依赖关系，并在需要时重新规划","url":"/docs/compare/?release=15.5#15.5-403795d62ed47dc9","version":"15.5"},{"db_id":"692df1745c276b8c3864e5516fb90ba9","evidence":{"patch_ids":["d151b170f74e32a11350e7a972ecb744"],"same_day":true,"statement_hash":"dd5031bfee679f826d6e6229ff8033d590ea9374c21617cb2ba371befb7bb52d"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"跟踪缓存的 CALL 语句的依赖关系，并在需要时重新规划","url":"/docs/compare/?release=14.10#14.10-99539adad1f5e03e","version":"14.10"},{"db_id":"1487d17841c67993807ed04e30095f60","evidence":{"patch_ids":["d151b170f74e32a11350e7a972ecb744"],"same_day":true,"statement_hash":"dd5031bfee679f826d6e6229ff8033d590ea9374c21617cb2ba371befb7bb52d"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"跟踪缓存的 CALL 语句的依赖关系，并在需要时重新规划","url":"/docs/compare/?release=13.13#13.13-5727dc84e6114285","version":"13.13"},{"db_id":"dc2f8e49dc4349ed41293a0c0de418dc","evidence":{"patch_ids":["d151b170f74e32a11350e7a972ecb744"],"same_day":true,"statement_hash":"dd5031bfee679f826d6e6229ff8033d590ea9374c21617cb2ba371befb7bb52d"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"跟踪缓存的 CALL 语句的依赖关系，并在需要时重新规划","url":"/docs/compare/?release=12.17#12.17-18a160825faa46e2","version":"12.17"},{"db_id":"2a752703d690e6ef32e7c330fe8735e4","evidence":{"patch_ids":["d151b170f74e32a11350e7a972ecb744"],"same_day":true,"statement_hash":"dd5031bfee679f826d6e6229ff8033d590ea9374c21617cb2ba371befb7bb52d"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"跟踪缓存的 CALL 语句的依赖关系，并在需要时重新规划","url":"/docs/compare/?release=11.22#11.22-5840fa89fa55fdde","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["d151b170f74e32a11350e7a972ecb744"],"same_day":true,"statement_hash":"dd5031bfee679f826d6e6229ff8033d590ea9374c21617cb2ba371befb7bb52d"},"rule":2,"target":"1487d17841c67993807ed04e30095f60","type":"equivalent"},{"evidence":{"patch_ids":["d151b170f74e32a11350e7a972ecb744"],"same_day":true,"statement_hash":"dd5031bfee679f826d6e6229ff8033d590ea9374c21617cb2ba371befb7bb52d"},"rule":2,"target":"2a752703d690e6ef32e7c330fe8735e4","type":"equivalent"},{"evidence":{"patch_ids":["d151b170f74e32a11350e7a972ecb744"],"same_day":true,"statement_hash":"dd5031bfee679f826d6e6229ff8033d590ea9374c21617cb2ba371befb7bb52d"},"rule":2,"target":"692df1745c276b8c3864e5516fb90ba9","type":"equivalent"},{"evidence":{"patch_ids":["d151b170f74e32a11350e7a972ecb744"],"same_day":true,"statement_hash":"dd5031bfee679f826d6e6229ff8033d590ea9374c21617cb2ba371befb7bb52d"},"rule":2,"target":"ad0b3fc1bbdac02757099b54bb9285a2","type":"equivalent"},{"evidence":{"patch_ids":["d151b170f74e32a11350e7a972ecb744"],"same_day":true,"statement_hash":"dd5031bfee679f826d6e6229ff8033d590ea9374c21617cb2ba371befb7bb52d"},"rule":2,"target":"dc2f8e49dc4349ed41293a0c0de418dc","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["055f786ea"],"source_entry_id":"16.1/changes/038","source_hash":"491ebc5ecc4270953f36dbfd3f8bf524dab8792ad3062d5ce8c678e4681d17ea","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"dd5031bfee679f826d6e6229ff8033d590ea9374c21617cb2ba371befb7bb52d","text":"跟踪缓存的 CALL 语句的依赖关系，并在需要时重新规划（Tom Lane）§ DDL 命令，例如替换已内联到 CALL 参数中的函数，可能需要重新规划已被 PL/pgSQL 缓存的 CALL。之前这不会发生，导致异常行为或诸如 “cache lookup failed” 之类的奇怪错误。","title":"跟踪缓存的 CALL 语句的依赖关系，并在需要时重新规划","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["5f3aa309a","9dc85806d","f720875a4"],"commit_groups":[["5f3aa309a","9dc85806d","f720875a4"]],"commits":["f720875a4"],"cves":[],"db_id":"777d48a6d41a0785aa095851f724a67e","html":"\u003cp\u003e避免在 OpenSSL 连接设置出错后可能出现的释放空指针崩溃（Sergey Shinderuk）\u003ca href=\"https://postgr.es/c/f720875a4\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-d781faf23402e916","identity_text":"Avoid a possible pfree-a-NULL-pointer crash after an error in OpenSSL connection setup (Sergey Shinderuk)","part":"changes","patch_ids":["b955e59d371f996f2047880f4548833f"],"related_changes":[{"db_id":"61320957e6d25e0c3958a56d76373ef4","evidence":{"patch_ids":["b955e59d371f996f2047880f4548833f"],"same_day":true,"statement_hash":"c0c4cc9bf1173a44de3c74ca64b9bcb5d0856a9e797347e3bbd442b3d45f0a0c"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"避免在 OpenSSL 连接设置出错后可能出现的释放空指针崩溃","url":"/docs/compare/?release=15.5#15.5-b527df82d1256624","version":"15.5"}],"relations":[{"evidence":{"patch_ids":["b955e59d371f996f2047880f4548833f"],"same_day":true,"statement_hash":"c0c4cc9bf1173a44de3c74ca64b9bcb5d0856a9e797347e3bbd442b3d45f0a0c"},"rule":2,"target":"61320957e6d25e0c3958a56d76373ef4","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["f720875a4"],"source_entry_id":"16.1/changes/039","source_hash":"5c64ed69654ba291441d724a7ef029561f4a2c9e62f26e5315a4d7d0a6ed8a9a","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"c0c4cc9bf1173a44de3c74ca64b9bcb5d0856a9e797347e3bbd442b3d45f0a0c","text":"避免在 OpenSSL 连接设置出错后可能出现的释放空指针崩溃（Sergey Shinderuk）§","title":"避免在 OpenSSL 连接设置出错后可能出现的释放空指针崩溃","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["2679a107a","53630f12d","a374f6c61","ae13f8166","c5b7f791d","d29812c0c","e0e492e5a"],"commit_groups":[["2679a107a","53630f12d","a374f6c61","ae13f8166","c5b7f791d","d29812c0c","e0e492e5a"]],"commits":["53630f12d"],"cves":[],"db_id":"de062e943406b60706de3315a3e15ec2","html":"\u003cp\u003e在检查来自外层查询级别的 \u003ccode\u003eRECORD\u003c/code\u003e 类型 Var 时正确跟踪嵌套深度（Richard Guo）\u003ca href=\"https://postgr.es/c/53630f12d\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e此疏忽可能导致断言失败、核心转储或 \u003cspan\u003e“\u003cspan\u003ebogus varno\u003c/span\u003e”\u003c/span\u003e 错误。\u003c/p\u003e","id":"16.1-4a41a2ad5044435c","identity_text":"Track nesting depth correctly when inspecting RECORD-type Vars from outer query levels (Richard Guo) This oversight could lead to assertion failures, core dumps, or bogus varno errors.","part":"changes","patch_ids":["d0431e23c35a94d06e5d2a44329bd4fd"],"related_changes":[{"db_id":"6f7e94fa742ac9471ae0f083e0bd93c5","evidence":{"patch_ids":["d0431e23c35a94d06e5d2a44329bd4fd"],"same_day":true,"statement_hash":"ed22c3e1611610362e0e152644637c66398c1a021cb333c32021e27ad5ea82c5"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"在检查来自外层查询级别的 RECORD 类型 Var 时正确跟踪嵌套深度","url":"/docs/compare/?release=15.5#15.5-a93342167b4a8f59","version":"15.5"},{"db_id":"32c57fccf9f6e9a420b936606481cb9d","evidence":{"patch_ids":["d0431e23c35a94d06e5d2a44329bd4fd"],"same_day":true,"statement_hash":"ed22c3e1611610362e0e152644637c66398c1a021cb333c32021e27ad5ea82c5"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"在检查来自外层查询级别的 RECORD 类型 Var 时正确跟踪嵌套深度","url":"/docs/compare/?release=14.10#14.10-a7ffa9c9c2063f77","version":"14.10"},{"db_id":"668a42c014ec775f8a0391b69f6073a1","evidence":{"patch_ids":["d0431e23c35a94d06e5d2a44329bd4fd"],"same_day":true,"statement_hash":"ed22c3e1611610362e0e152644637c66398c1a021cb333c32021e27ad5ea82c5"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"在检查来自外层查询级别的 RECORD 类型 Var 时正确跟踪嵌套深度","url":"/docs/compare/?release=13.13#13.13-2f6038f57a449d11","version":"13.13"},{"db_id":"6681232cbaaa0eefc8e6e3e9ff6db27b","evidence":{"patch_ids":["d0431e23c35a94d06e5d2a44329bd4fd"],"same_day":true,"statement_hash":"ed22c3e1611610362e0e152644637c66398c1a021cb333c32021e27ad5ea82c5"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"在检查来自外层查询级别的 RECORD 类型 Var 时正确跟踪嵌套深度","url":"/docs/compare/?release=12.17#12.17-e7f9f1a9d6318f25","version":"12.17"},{"db_id":"3543945bead243c78fada851f46cd9a8","evidence":{"patch_ids":["d0431e23c35a94d06e5d2a44329bd4fd"],"same_day":true,"statement_hash":"ed22c3e1611610362e0e152644637c66398c1a021cb333c32021e27ad5ea82c5"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"在检查来自外层查询级别的 RECORD 类型 Var 时正确跟踪嵌套深度","url":"/docs/compare/?release=11.22#11.22-89e2243631bbbdab","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["d0431e23c35a94d06e5d2a44329bd4fd"],"same_day":true,"statement_hash":"ed22c3e1611610362e0e152644637c66398c1a021cb333c32021e27ad5ea82c5"},"rule":2,"target":"32c57fccf9f6e9a420b936606481cb9d","type":"equivalent"},{"evidence":{"patch_ids":["d0431e23c35a94d06e5d2a44329bd4fd"],"same_day":true,"statement_hash":"ed22c3e1611610362e0e152644637c66398c1a021cb333c32021e27ad5ea82c5"},"rule":2,"target":"3543945bead243c78fada851f46cd9a8","type":"equivalent"},{"evidence":{"patch_ids":["d0431e23c35a94d06e5d2a44329bd4fd"],"same_day":true,"statement_hash":"ed22c3e1611610362e0e152644637c66398c1a021cb333c32021e27ad5ea82c5"},"rule":2,"target":"6681232cbaaa0eefc8e6e3e9ff6db27b","type":"equivalent"},{"evidence":{"patch_ids":["d0431e23c35a94d06e5d2a44329bd4fd"],"same_day":true,"statement_hash":"ed22c3e1611610362e0e152644637c66398c1a021cb333c32021e27ad5ea82c5"},"rule":2,"target":"668a42c014ec775f8a0391b69f6073a1","type":"equivalent"},{"evidence":{"patch_ids":["d0431e23c35a94d06e5d2a44329bd4fd"],"same_day":true,"statement_hash":"ed22c3e1611610362e0e152644637c66398c1a021cb333c32021e27ad5ea82c5"},"rule":2,"target":"6f7e94fa742ac9471ae0f083e0bd93c5","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["53630f12d"],"source_entry_id":"16.1/changes/040","source_hash":"ecc5f94e52a990a6c3c327665e740c317fdcaf7afcb392a9df60afd434aa7540","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"ed22c3e1611610362e0e152644637c66398c1a021cb333c32021e27ad5ea82c5","text":"在检查来自外层查询级别的 RECORD 类型 Var 时正确跟踪嵌套深度（Richard Guo）§ 此疏忽可能导致断言失败、核心转储或 “bogus varno” 错误。","title":"在检查来自外层查询级别的 RECORD 类型 Var 时正确跟踪嵌套深度","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["17a3f1c34","1a6900e58","6341cb0b0","ee3a551e9"],"commit_groups":[["17a3f1c34","1a6900e58","6341cb0b0","ee3a551e9"]],"commits":["1a6900e58"],"cves":[],"db_id":"9d2ebeeaa50f0e54830dcbdd57e44a6c","html":"\u003cp\u003e跟踪 ScalarArrayOpExpr 计划节点的 hash 函数和求反器函数依赖（David Rowley）\u003ca href=\"https://postgr.es/c/1a6900e58\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e在大多数情况下，此疏忽是无害的，因为这些函数不太可能在节点的原始操作符仍然存在的情况下消失。\u003c/p\u003e","id":"16.1-222ab318852dc4d9","identity_text":"Track hash function and negator function dependencies of ScalarArrayOpExpr plan nodes (David Rowley) In most cases this oversight was harmless, since these functions would be unlikely to disappear while the node's original operator remains present.","part":"changes","patch_ids":["6564e7b295e4ab5cd641ceba0a1ec372"],"related_changes":[{"db_id":"80641a4d9aa4be4ad98d10f5e604efd4","evidence":{"patch_ids":["6564e7b295e4ab5cd641ceba0a1ec372"],"same_day":true,"statement_hash":"531bdb6d257fbabc4187f6855f1704efd8f6f0636cb991e12e289ed498b5a2e7"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"跟踪 ScalarArrayOpExpr 计划节点的 hash 函数和求反器函数依赖","url":"/docs/compare/?release=15.5#15.5-a2c661593cfc7258","version":"15.5"},{"db_id":"3c7ce03c1edc15cfcc03eec0496a4f65","evidence":{"patch_ids":["6564e7b295e4ab5cd641ceba0a1ec372"],"same_day":true,"statement_hash":"531bdb6d257fbabc4187f6855f1704efd8f6f0636cb991e12e289ed498b5a2e7"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"跟踪 ScalarArrayOpExpr 计划节点的 hash 函数和求反器函数依赖","url":"/docs/compare/?release=14.10#14.10-b4079d8f6e9a790f","version":"14.10"}],"relations":[{"evidence":{"patch_ids":["6564e7b295e4ab5cd641ceba0a1ec372"],"same_day":true,"statement_hash":"531bdb6d257fbabc4187f6855f1704efd8f6f0636cb991e12e289ed498b5a2e7"},"rule":2,"target":"3c7ce03c1edc15cfcc03eec0496a4f65","type":"equivalent"},{"evidence":{"patch_ids":["6564e7b295e4ab5cd641ceba0a1ec372"],"same_day":true,"statement_hash":"531bdb6d257fbabc4187f6855f1704efd8f6f0636cb991e12e289ed498b5a2e7"},"rule":2,"target":"80641a4d9aa4be4ad98d10f5e604efd4","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["1a6900e58"],"source_entry_id":"16.1/changes/041","source_hash":"1b7974dac12b6ef084da759a87ae4ab37402db5dc130cde39f9781bf2ae8f73b","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"531bdb6d257fbabc4187f6855f1704efd8f6f0636cb991e12e289ed498b5a2e7","text":"跟踪 ScalarArrayOpExpr 计划节点的 hash 函数和求反器函数依赖（David Rowley）§ 在大多数情况下，此疏忽是无害的，因为这些函数不太可能在节点的原始操作符仍然存在的情况下消失。","title":"跟踪 ScalarArrayOpExpr 计划节点的 hash 函数和求反器函数依赖","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["012b80ad2","189097db8","3acd0599b","6ae57f190","a26cc0334","e2452c2a6","f899c7f1e"],"commit_groups":[["012b80ad2","189097db8","3acd0599b","6ae57f190","a26cc0334","e2452c2a6","f899c7f1e"]],"commits":["f899c7f1e"],"cves":[],"db_id":"abcf78ff4896829a223d6bd208a2bac9","html":"\u003cp\u003e修复 \u003ccode\u003eRECORD\u003c/code\u003e 类型缓存管理中的错误处理缺陷（Thomas Munro）\u003ca href=\"https://postgr.es/c/f899c7f1e\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e在恰好错误的时刻发生内存不足错误可能留下不一致的状态，导致无限循环。\u003c/p\u003e","id":"16.1-4d43e955504f9b2c","identity_text":"Fix error-handling bug in RECORD type cache management (Thomas Munro) An out-of-memory error occurring at just the wrong point could leave behind inconsistent state that would lead to an infinite loop.","part":"changes","patch_ids":["bbf959dd25503d44fc5ee4ef269d9cf7"],"related_changes":[{"db_id":"9882582fb6ef445bf02faa87dfe6a449","evidence":{"patch_ids":["bbf959dd25503d44fc5ee4ef269d9cf7"],"same_day":true,"statement_hash":"17077e598b1ef6286532fd602659aa82d4553bd9227344cb2ee73c167037d140"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复 RECORD 类型缓存管理中的错误处理缺陷","url":"/docs/compare/?release=15.5#15.5-e0bd9b7bba1f6589","version":"15.5"},{"db_id":"2fcc7bae682d51d098cfc6d7ef138251","evidence":{"patch_ids":["bbf959dd25503d44fc5ee4ef269d9cf7"],"same_day":true,"statement_hash":"17077e598b1ef6286532fd602659aa82d4553bd9227344cb2ee73c167037d140"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复 RECORD 类型缓存管理中的错误处理缺陷","url":"/docs/compare/?release=14.10#14.10-a5edc6f259fe7be1","version":"14.10"},{"db_id":"c1c2f245a542a9a8db7a2809a754c0f5","evidence":{"patch_ids":["bbf959dd25503d44fc5ee4ef269d9cf7"],"same_day":true,"statement_hash":"17077e598b1ef6286532fd602659aa82d4553bd9227344cb2ee73c167037d140"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复 RECORD 类型缓存管理中的错误处理缺陷","url":"/docs/compare/?release=13.13#13.13-3b79c57cf291a492","version":"13.13"},{"db_id":"630afa85073551ecc72f86b2e3e040f1","evidence":{"patch_ids":["bbf959dd25503d44fc5ee4ef269d9cf7"],"same_day":true,"statement_hash":"17077e598b1ef6286532fd602659aa82d4553bd9227344cb2ee73c167037d140"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"修复 RECORD 类型缓存管理中的错误处理缺陷","url":"/docs/compare/?release=12.17#12.17-2b68d14bd314992e","version":"12.17"},{"db_id":"910734a753f9130250b124d177eb2480","evidence":{"patch_ids":["bbf959dd25503d44fc5ee4ef269d9cf7"],"same_day":true,"statement_hash":"17077e598b1ef6286532fd602659aa82d4553bd9227344cb2ee73c167037d140"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"修复 RECORD 类型缓存管理中的错误处理缺陷","url":"/docs/compare/?release=11.22#11.22-7e85b60791b00239","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["bbf959dd25503d44fc5ee4ef269d9cf7"],"same_day":true,"statement_hash":"17077e598b1ef6286532fd602659aa82d4553bd9227344cb2ee73c167037d140"},"rule":2,"target":"2fcc7bae682d51d098cfc6d7ef138251","type":"equivalent"},{"evidence":{"patch_ids":["bbf959dd25503d44fc5ee4ef269d9cf7"],"same_day":true,"statement_hash":"17077e598b1ef6286532fd602659aa82d4553bd9227344cb2ee73c167037d140"},"rule":2,"target":"630afa85073551ecc72f86b2e3e040f1","type":"equivalent"},{"evidence":{"patch_ids":["bbf959dd25503d44fc5ee4ef269d9cf7"],"same_day":true,"statement_hash":"17077e598b1ef6286532fd602659aa82d4553bd9227344cb2ee73c167037d140"},"rule":2,"target":"910734a753f9130250b124d177eb2480","type":"equivalent"},{"evidence":{"patch_ids":["bbf959dd25503d44fc5ee4ef269d9cf7"],"same_day":true,"statement_hash":"17077e598b1ef6286532fd602659aa82d4553bd9227344cb2ee73c167037d140"},"rule":2,"target":"9882582fb6ef445bf02faa87dfe6a449","type":"equivalent"},{"evidence":{"patch_ids":["bbf959dd25503d44fc5ee4ef269d9cf7"],"same_day":true,"statement_hash":"17077e598b1ef6286532fd602659aa82d4553bd9227344cb2ee73c167037d140"},"rule":2,"target":"c1c2f245a542a9a8db7a2809a754c0f5","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["f899c7f1e"],"source_entry_id":"16.1/changes/042","source_hash":"9bd108c377914d7dc5f88fff2fbf72e5d79039ffc121b46735623d3ab6b21305","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"17077e598b1ef6286532fd602659aa82d4553bd9227344cb2ee73c167037d140","text":"修复 RECORD 类型缓存管理中的错误处理缺陷（Thomas Munro）§ 在恰好错误的时刻发生内存不足错误可能留下不一致的状态，导致无限循环。","title":"修复 RECORD 类型缓存管理中的错误处理缺陷","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["22b2e6e9d","6103d2cca","6b18b3fe2","a06efbc3a","afc79591d","baeb8542c"],"commit_groups":[["22b2e6e9d","6103d2cca","6b18b3fe2","a06efbc3a","afc79591d","baeb8542c"]],"commits":["a06efbc3a"],"cves":[],"db_id":"924ed59f280b8496af52812d7e73f312","html":"\u003cp\u003e在读取 WAL 时将内存不足失败视为致命错误（Michael Paquier）\u003ca href=\"https://postgr.es/c/a06efbc3a\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e之前这会被视为无效数据条件，导致得出已到达 WAL 末尾的错误结论，这是不正确的，并可能导致不一致的 WAL 重放。\u003c/p\u003e","id":"16.1-8306001262c52c26","identity_text":"Treat out-of-memory failures as fatal while reading WAL (Michael Paquier) Previously this would be treated as a bogus-data condition, leading to the conclusion that we'd reached the end of WAL, which is incorrect and could lead to inconsistent WAL replay.","part":"changes","patch_ids":["e0cd1caa7b990696a26bffd398107706"],"related_changes":[{"db_id":"f27ae374968ad2ef5b6d7308dfd8005d","evidence":{"patch_ids":["e0cd1caa7b990696a26bffd398107706"],"same_day":true,"statement_hash":"c4a360afd0ef3f2e40471ae51900a86dfedf9aab849358fe7e862c88cf7e4f82"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"在读取 WAL 时将内存不足失败视为致命错误","url":"/docs/compare/?release=15.5#15.5-00ba9a51cc134fd1","version":"15.5"},{"db_id":"231b2502cd1c1fd8494fd7267c6c0d39","evidence":{"patch_ids":["e0cd1caa7b990696a26bffd398107706"],"same_day":true,"statement_hash":"c4a360afd0ef3f2e40471ae51900a86dfedf9aab849358fe7e862c88cf7e4f82"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"在读取 WAL 时将内存不足失败视为致命错误","url":"/docs/compare/?release=14.10#14.10-4bb88aac730e5527","version":"14.10"},{"db_id":"d7bbacba367f2ca38cfb8e5f94e4d33f","evidence":{"patch_ids":["e0cd1caa7b990696a26bffd398107706"],"same_day":true,"statement_hash":"c4a360afd0ef3f2e40471ae51900a86dfedf9aab849358fe7e862c88cf7e4f82"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"在读取 WAL 时将内存不足失败视为致命错误","url":"/docs/compare/?release=13.13#13.13-aea4bfe5fb481401","version":"13.13"},{"db_id":"cd22b8ea2b2ac4b8d5e4405e84404ce7","evidence":{"patch_ids":["e0cd1caa7b990696a26bffd398107706"],"same_day":true,"statement_hash":"c4a360afd0ef3f2e40471ae51900a86dfedf9aab849358fe7e862c88cf7e4f82"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"在读取 WAL 时将内存不足失败视为致命错误","url":"/docs/compare/?release=12.17#12.17-df91a4fb3747f0dd","version":"12.17"}],"relations":[{"evidence":{"patch_ids":["e0cd1caa7b990696a26bffd398107706"],"same_day":true,"statement_hash":"c4a360afd0ef3f2e40471ae51900a86dfedf9aab849358fe7e862c88cf7e4f82"},"rule":2,"target":"231b2502cd1c1fd8494fd7267c6c0d39","type":"equivalent"},{"evidence":{"patch_ids":["e0cd1caa7b990696a26bffd398107706"],"same_day":true,"statement_hash":"c4a360afd0ef3f2e40471ae51900a86dfedf9aab849358fe7e862c88cf7e4f82"},"rule":2,"target":"cd22b8ea2b2ac4b8d5e4405e84404ce7","type":"equivalent"},{"evidence":{"patch_ids":["e0cd1caa7b990696a26bffd398107706"],"same_day":true,"statement_hash":"c4a360afd0ef3f2e40471ae51900a86dfedf9aab849358fe7e862c88cf7e4f82"},"rule":2,"target":"d7bbacba367f2ca38cfb8e5f94e4d33f","type":"equivalent"},{"evidence":{"patch_ids":["e0cd1caa7b990696a26bffd398107706"],"same_day":true,"statement_hash":"c4a360afd0ef3f2e40471ae51900a86dfedf9aab849358fe7e862c88cf7e4f82"},"rule":2,"target":"f27ae374968ad2ef5b6d7308dfd8005d","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["a06efbc3a"],"source_entry_id":"16.1/changes/043","source_hash":"e896cba3b72f2ad594b7a7da6fe4be6f065c367430a33d0c3868a39483060f78","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"c4a360afd0ef3f2e40471ae51900a86dfedf9aab849358fe7e862c88cf7e4f82","text":"在读取 WAL 时将内存不足失败视为致命错误（Michael Paquier）§ 之前这会被视为无效数据条件，导致得出已到达 WAL 末尾的错误结论，这是不正确的，并可能导致不一致的 WAL 重放。","title":"在读取 WAL 时将内存不足失败视为致命错误","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["10d0591ea","3ce3b53d7","3d413c5a7","45d1fe8b5","6606c5716","99d334a18","bae868caf","bde2f1847","becfbdd6c","ce497f648","e8f3c0687","f4d152edd"],"commit_groups":[["10d0591ea","3d413c5a7","45d1fe8b5","99d334a18","bde2f1847","becfbdd6c"],["3ce3b53d7","6606c5716","bae868caf","ce497f648","e8f3c0687","f4d152edd"]],"commits":["10d0591ea","ce497f648"],"cves":[],"db_id":"8249086131bbf4442f00c9cb7ce768b7","html":"\u003cp\u003e修复由于尝试基于伪造的 WAL 记录长度字段分配内存而可能导致的恢复失败（Thomas Munro，Michael Paquier）\u003ca href=\"https://postgr.es/c/ce497f648\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/10d0591ea\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-47ae7e27ddaa78ae","identity_text":"Fix possible recovery failure due to trying to allocate memory based on a bogus WAL record length field (Thomas Munro, Michael Paquier)","part":"changes","patch_ids":["3ac70aec4a3d322fb8eca31faa35495a","7af0183d45d69154b21fce5aaec6012e"],"related_changes":[{"db_id":"5004130fcb4304366ea010e2c901d0b8","evidence":{"patch_ids":["3ac70aec4a3d322fb8eca31faa35495a","7af0183d45d69154b21fce5aaec6012e"],"same_day":true,"statement_hash":"981b89cb590f8cf3d268832df888519833e301c9bb4639e48a4446874d6ee462"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复由于尝试基于伪造的 WAL 记录长度字段分配内存而可能导致的恢复失败","url":"/docs/compare/?release=15.5#15.5-d38ad77c68ecbf25","version":"15.5"},{"db_id":"748d9725b1c95e20bfde7341b50118d6","evidence":{"patch_ids":["3ac70aec4a3d322fb8eca31faa35495a","7af0183d45d69154b21fce5aaec6012e"],"same_day":true,"statement_hash":"981b89cb590f8cf3d268832df888519833e301c9bb4639e48a4446874d6ee462"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复由于尝试基于伪造的 WAL 记录长度字段分配内存而可能导致的恢复失败","url":"/docs/compare/?release=14.10#14.10-cbbd8b35d8741c7d","version":"14.10"},{"db_id":"91f04dc5a72f326bf424fd40f971cdf4","evidence":{"patch_ids":["3ac70aec4a3d322fb8eca31faa35495a","7af0183d45d69154b21fce5aaec6012e"],"same_day":true,"statement_hash":"981b89cb590f8cf3d268832df888519833e301c9bb4639e48a4446874d6ee462"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复由于尝试基于伪造的 WAL 记录长度字段分配内存而可能导致的恢复失败","url":"/docs/compare/?release=13.13#13.13-ccba0a02f3a0b778","version":"13.13"},{"db_id":"49d4d72ae184d3224ccd2f9b47c0044e","evidence":{"patch_ids":["3ac70aec4a3d322fb8eca31faa35495a","7af0183d45d69154b21fce5aaec6012e"],"same_day":true,"statement_hash":"981b89cb590f8cf3d268832df888519833e301c9bb4639e48a4446874d6ee462"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"修复由于尝试基于伪造的 WAL 记录长度字段分配内存而可能导致的恢复失败","url":"/docs/compare/?release=12.17#12.17-9f3ef1d61e26e57f","version":"12.17"}],"relations":[{"evidence":{"patch_ids":["3ac70aec4a3d322fb8eca31faa35495a","7af0183d45d69154b21fce5aaec6012e"],"same_day":true,"statement_hash":"981b89cb590f8cf3d268832df888519833e301c9bb4639e48a4446874d6ee462"},"rule":2,"target":"49d4d72ae184d3224ccd2f9b47c0044e","type":"equivalent"},{"evidence":{"patch_ids":["3ac70aec4a3d322fb8eca31faa35495a","7af0183d45d69154b21fce5aaec6012e"],"same_day":true,"statement_hash":"981b89cb590f8cf3d268832df888519833e301c9bb4639e48a4446874d6ee462"},"rule":2,"target":"5004130fcb4304366ea010e2c901d0b8","type":"equivalent"},{"evidence":{"patch_ids":["3ac70aec4a3d322fb8eca31faa35495a","7af0183d45d69154b21fce5aaec6012e"],"same_day":true,"statement_hash":"981b89cb590f8cf3d268832df888519833e301c9bb4639e48a4446874d6ee462"},"rule":2,"target":"748d9725b1c95e20bfde7341b50118d6","type":"equivalent"},{"evidence":{"patch_ids":["3ac70aec4a3d322fb8eca31faa35495a","7af0183d45d69154b21fce5aaec6012e"],"same_day":true,"statement_hash":"981b89cb590f8cf3d268832df888519833e301c9bb4639e48a4446874d6ee462"},"rule":2,"target":"91f04dc5a72f326bf424fd40f971cdf4","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["10d0591ea","ce497f648"],"source_entry_id":"16.1/changes/044","source_hash":"2b5c51cd7c173b0b3e8e1c3e57f63be36e7869156c286f976395a96bd2771339","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"981b89cb590f8cf3d268832df888519833e301c9bb4639e48a4446874d6ee462","text":"修复由于尝试基于伪造的 WAL 记录长度字段分配内存而可能导致的恢复失败（Thomas Munro，Michael Paquier）§ §","title":"修复由于尝试基于伪造的 WAL 记录长度字段分配内存而可能导致的恢复失败","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["174ccda5e","dab889d60","f72790b29","fb9a16a1a"],"commit_groups":[["174ccda5e","dab889d60","f72790b29","fb9a16a1a"]],"commits":["174ccda5e"],"cves":[],"db_id":"25ff89a9f3c791b5ec7dab98e355e5b1","html":"\u003cp\u003e修复在 Windows 上当 \u003ccode\u003emin_dynamic_shared_memory\u003c/code\u003e 设置为大于零时出现的 \u003cspan\u003e“\u003cspan\u003ecould not duplicate handle\u003c/span\u003e”\u003c/span\u003e 错误（Thomas Munro）\u003ca href=\"https://postgr.es/c/174ccda5e\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-056b9900bc9ba8b7","identity_text":"Fix could not duplicate handle error occurring on Windows when min_dynamic_shared_memory is set above zero (Thomas Munro)","part":"changes","patch_ids":["9b32a326813dca8a7097380bd649b45f"],"related_changes":[{"db_id":"f237abef09a3b9371f9787e2658d8bac","evidence":{"patch_ids":["9b32a326813dca8a7097380bd649b45f"],"same_day":true,"statement_hash":"d5966f80aaf08196b907f0e0cd0cedc3507476a7a6358fad2a5dda4824573029"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复在 Windows 上当 min_dynamic_shared_memory 设置为大于零时出现的 “could not duplicate handle” 错误","url":"/docs/compare/?release=15.5#15.5-18df127c15cb90e3","version":"15.5"},{"db_id":"c47e7fa87a6bb0e08b6d7f311798c87e","evidence":{"patch_ids":["9b32a326813dca8a7097380bd649b45f"],"same_day":true,"statement_hash":"d5966f80aaf08196b907f0e0cd0cedc3507476a7a6358fad2a5dda4824573029"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复在 Windows 上当 min_dynamic_shared_memory 设置为大于零时出现的 “could not duplicate handle” 错误","url":"/docs/compare/?release=14.10#14.10-78822e51b67b3c99","version":"14.10"}],"relations":[{"evidence":{"patch_ids":["9b32a326813dca8a7097380bd649b45f"],"same_day":true,"statement_hash":"d5966f80aaf08196b907f0e0cd0cedc3507476a7a6358fad2a5dda4824573029"},"rule":2,"target":"c47e7fa87a6bb0e08b6d7f311798c87e","type":"equivalent"},{"evidence":{"patch_ids":["9b32a326813dca8a7097380bd649b45f"],"same_day":true,"statement_hash":"d5966f80aaf08196b907f0e0cd0cedc3507476a7a6358fad2a5dda4824573029"},"rule":2,"target":"f237abef09a3b9371f9787e2658d8bac","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["174ccda5e"],"source_entry_id":"16.1/changes/045","source_hash":"42e39c100070f325d0e0ccf920db6adbfd297a66282be14043a6d9115c92e4d3","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"d5966f80aaf08196b907f0e0cd0cedc3507476a7a6358fad2a5dda4824573029","text":"修复在 Windows 上当 min_dynamic_shared_memory 设置为大于零时出现的 “could not duplicate handle” 错误（Thomas Munro）§","title":"修复在 Windows 上当 min_dynamic_shared_memory 设置为大于零时出现的 “could not duplicate handle” 错误","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["04f0baa85","469d367be","6615bb95a","6dbd01b9f","b8963e8a2","b9bb02620","ef74c7197"],"commit_groups":[["04f0baa85","469d367be","6615bb95a","6dbd01b9f","b8963e8a2","b9bb02620","ef74c7197"]],"commits":["b8963e8a2"],"cves":[],"db_id":"9c4e097c80c1eef302393ab83faa30d0","html":"\u003cp\u003e修复 \u003ccode\u003eGenericXLogFinish\u003c/code\u003e 中的操作顺序（Jeff Davis）\u003ca href=\"https://postgr.es/c/b8963e8a2\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e此代码在将更改的缓冲区标记为脏之前就写入了 WAL，违反了崩溃安全所需的条件。核心代码没有使用此函数，但扩展会使用（例如 \u003ccode\u003econtrib/bloom\u003c/code\u003e）。\u003c/p\u003e","id":"16.1-72777bf5de245f48","identity_text":"Fix order of operations in GenericXLogFinish (Jeff Davis) This code violated the conditions required for crash safety by writing WAL before marking changed buffers dirty. No core code uses this function, but extensions do (contrib/bloom does, for example).","part":"changes","patch_ids":["bd7a3a85904058e4f6abbcb11bd32d98"],"related_changes":[{"db_id":"61c6c32100c65d4d9d08a4413658ba0f","evidence":{"patch_ids":["bd7a3a85904058e4f6abbcb11bd32d98"],"same_day":true,"statement_hash":"3e2d6b47b23e0718b47d04b72cc261397b203df51ccde3c8f15f94d9fb1aa837"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复 GenericXLogFinish 中的操作顺序","url":"/docs/compare/?release=15.5#15.5-b61125b63eca15d5","version":"15.5"},{"db_id":"7c32d87e6f3b8249150f2af273bec934","evidence":{"patch_ids":["bd7a3a85904058e4f6abbcb11bd32d98"],"same_day":true,"statement_hash":"3e2d6b47b23e0718b47d04b72cc261397b203df51ccde3c8f15f94d9fb1aa837"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复 GenericXLogFinish 中的操作顺序","url":"/docs/compare/?release=14.10#14.10-81ee2f2d5ac943e8","version":"14.10"},{"db_id":"56fdcd2471815966a9406016d8f155ab","evidence":{"patch_ids":["bd7a3a85904058e4f6abbcb11bd32d98"],"same_day":true,"statement_hash":"3e2d6b47b23e0718b47d04b72cc261397b203df51ccde3c8f15f94d9fb1aa837"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复 GenericXLogFinish 中的操作顺序","url":"/docs/compare/?release=13.13#13.13-890e26d7eda46482","version":"13.13"},{"db_id":"9ef966ebe248441ad6aea22f52558ddd","evidence":{"patch_ids":["bd7a3a85904058e4f6abbcb11bd32d98"],"same_day":true,"statement_hash":"3e2d6b47b23e0718b47d04b72cc261397b203df51ccde3c8f15f94d9fb1aa837"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"修复 GenericXLogFinish 中的操作顺序","url":"/docs/compare/?release=12.17#12.17-6a91fdf5f6e9563a","version":"12.17"},{"db_id":"1b180e1797c4a541539d23793d66203b","evidence":{"patch_ids":["bd7a3a85904058e4f6abbcb11bd32d98"],"same_day":true,"statement_hash":"3e2d6b47b23e0718b47d04b72cc261397b203df51ccde3c8f15f94d9fb1aa837"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"修复 GenericXLogFinish 中的操作顺序","url":"/docs/compare/?release=11.22#11.22-ac099ca027ebfb60","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["bd7a3a85904058e4f6abbcb11bd32d98"],"same_day":true,"statement_hash":"3e2d6b47b23e0718b47d04b72cc261397b203df51ccde3c8f15f94d9fb1aa837"},"rule":2,"target":"1b180e1797c4a541539d23793d66203b","type":"equivalent"},{"evidence":{"patch_ids":["bd7a3a85904058e4f6abbcb11bd32d98"],"same_day":true,"statement_hash":"3e2d6b47b23e0718b47d04b72cc261397b203df51ccde3c8f15f94d9fb1aa837"},"rule":2,"target":"56fdcd2471815966a9406016d8f155ab","type":"equivalent"},{"evidence":{"patch_ids":["bd7a3a85904058e4f6abbcb11bd32d98"],"same_day":true,"statement_hash":"3e2d6b47b23e0718b47d04b72cc261397b203df51ccde3c8f15f94d9fb1aa837"},"rule":2,"target":"61c6c32100c65d4d9d08a4413658ba0f","type":"equivalent"},{"evidence":{"patch_ids":["bd7a3a85904058e4f6abbcb11bd32d98"],"same_day":true,"statement_hash":"3e2d6b47b23e0718b47d04b72cc261397b203df51ccde3c8f15f94d9fb1aa837"},"rule":2,"target":"7c32d87e6f3b8249150f2af273bec934","type":"equivalent"},{"evidence":{"patch_ids":["bd7a3a85904058e4f6abbcb11bd32d98"],"same_day":true,"statement_hash":"3e2d6b47b23e0718b47d04b72cc261397b203df51ccde3c8f15f94d9fb1aa837"},"rule":2,"target":"9ef966ebe248441ad6aea22f52558ddd","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["b8963e8a2"],"source_entry_id":"16.1/changes/046","source_hash":"691c1ba23fd3d7d68f1721352dadd0d1a79f4673316df289d05f92cc221a5f33","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"3e2d6b47b23e0718b47d04b72cc261397b203df51ccde3c8f15f94d9fb1aa837","text":"修复 GenericXLogFinish 中的操作顺序（Jeff Davis）§ 此代码在将更改的缓冲区标记为脏之前就写入了 WAL，违反了崩溃安全所需的条件。核心代码没有使用此函数，但扩展会使用（例如 contrib/bloom）。","title":"修复 GenericXLogFinish 中的操作顺序","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["35e8ba3e5","99d27e55c","9e0ce80f3","af5b3c3d1","bb65f3c1b","ddded779a","f171430f0"],"commit_groups":[["35e8ba3e5","99d27e55c","9e0ce80f3","af5b3c3d1","bb65f3c1b","ddded779a","f171430f0"]],"commits":["f171430f0"],"cves":[],"db_id":"6dc31139b4d2be5a1c3158dfce7a85db","html":"\u003cp\u003e移除 PL/Python 异常处理中的不正确断言（Alexander Lakhin）\u003ca href=\"https://postgr.es/c/f171430f0\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-cd267753f991b20a","identity_text":"Remove incorrect assertion in PL/Python exception handling (Alexander Lakhin)","part":"changes","patch_ids":["f0046a383d3185a6acedaad23f9124f3"],"related_changes":[{"db_id":"058fe6702eb481fceca693a6258232fc","evidence":{"patch_ids":["f0046a383d3185a6acedaad23f9124f3"],"same_day":true,"statement_hash":"01d474392eb4f3d384a5e0c5defe7b8069be3a823b5254c8af32036ddb6a05da"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"移除 PL/Python 异常处理中的不正确断言","url":"/docs/compare/?release=15.5#15.5-78a4e8e99c9e6113","version":"15.5"},{"db_id":"34f72232f88d2c8113b147b4b4c60849","evidence":{"patch_ids":["f0046a383d3185a6acedaad23f9124f3"],"same_day":true,"statement_hash":"01d474392eb4f3d384a5e0c5defe7b8069be3a823b5254c8af32036ddb6a05da"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"移除 PL/Python 异常处理中的不正确断言","url":"/docs/compare/?release=14.10#14.10-65007d3672492eeb","version":"14.10"},{"db_id":"d70e749ac35cbe2c8c0511280d6cf413","evidence":{"patch_ids":["f0046a383d3185a6acedaad23f9124f3"],"same_day":true,"statement_hash":"01d474392eb4f3d384a5e0c5defe7b8069be3a823b5254c8af32036ddb6a05da"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"移除 PL/Python 异常处理中的不正确断言","url":"/docs/compare/?release=13.13#13.13-cda9e50b8904a42d","version":"13.13"},{"db_id":"89486b43985b6f630fb1088659e7311e","evidence":{"patch_ids":["f0046a383d3185a6acedaad23f9124f3"],"same_day":true,"statement_hash":"01d474392eb4f3d384a5e0c5defe7b8069be3a823b5254c8af32036ddb6a05da"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"移除 PL/Python 异常处理中的不正确断言","url":"/docs/compare/?release=12.17#12.17-732682fbbdf2b9af","version":"12.17"},{"db_id":"acb9055b5bb405c50411e57d9654dc8d","evidence":{"patch_ids":["f0046a383d3185a6acedaad23f9124f3"],"same_day":true,"statement_hash":"01d474392eb4f3d384a5e0c5defe7b8069be3a823b5254c8af32036ddb6a05da"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"移除 PL/Python 异常处理中的不正确断言","url":"/docs/compare/?release=11.22#11.22-3de32ca5a816f3f3","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["f0046a383d3185a6acedaad23f9124f3"],"same_day":true,"statement_hash":"01d474392eb4f3d384a5e0c5defe7b8069be3a823b5254c8af32036ddb6a05da"},"rule":2,"target":"058fe6702eb481fceca693a6258232fc","type":"equivalent"},{"evidence":{"patch_ids":["f0046a383d3185a6acedaad23f9124f3"],"same_day":true,"statement_hash":"01d474392eb4f3d384a5e0c5defe7b8069be3a823b5254c8af32036ddb6a05da"},"rule":2,"target":"34f72232f88d2c8113b147b4b4c60849","type":"equivalent"},{"evidence":{"patch_ids":["f0046a383d3185a6acedaad23f9124f3"],"same_day":true,"statement_hash":"01d474392eb4f3d384a5e0c5defe7b8069be3a823b5254c8af32036ddb6a05da"},"rule":2,"target":"89486b43985b6f630fb1088659e7311e","type":"equivalent"},{"evidence":{"patch_ids":["f0046a383d3185a6acedaad23f9124f3"],"same_day":true,"statement_hash":"01d474392eb4f3d384a5e0c5defe7b8069be3a823b5254c8af32036ddb6a05da"},"rule":2,"target":"acb9055b5bb405c50411e57d9654dc8d","type":"equivalent"},{"evidence":{"patch_ids":["f0046a383d3185a6acedaad23f9124f3"],"same_day":true,"statement_hash":"01d474392eb4f3d384a5e0c5defe7b8069be3a823b5254c8af32036ddb6a05da"},"rule":2,"target":"d70e749ac35cbe2c8c0511280d6cf413","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["f171430f0"],"source_entry_id":"16.1/changes/047","source_hash":"74ba749c3c70c2e6c91220c8501a0d5d98a0c66cf465e0f2e8f3d6f58697de8f","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"01d474392eb4f3d384a5e0c5defe7b8069be3a823b5254c8af32036ddb6a05da","text":"移除 PL/Python 异常处理中的不正确断言（Alexander Lakhin）§","title":"移除 PL/Python 异常处理中的不正确断言","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["5ba4cc309","67738dbf9"],"commit_groups":[["5ba4cc309","67738dbf9"]],"commits":["67738dbf9"],"cves":[],"db_id":"edd0213c5d064a3750b4d734e0b955a2","html":"\u003cp\u003e修复 \u003cspan\u003epg_dump\u003c/span\u003e 以导出订阅的新 \u003ccode\u003erun_as_owner\u003c/code\u003e 选项（Philip Warner）\u003ca href=\"https://postgr.es/c/67738dbf9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e由于此疏忽，订阅总是以 \u003ccode\u003erun_as_owner\u003c/code\u003e 设置为 \u003ccode\u003efalse\u003c/code\u003e 恢复，这与它们在 v16 之前版本中的行为不等价。\u003c/p\u003e","id":"16.1-595c1ed7bff49833","identity_text":"Fix pg_dump to dump the new run_as_owner option of subscriptions (Philip Warner) Due to this oversight, subscriptions would always be restored with run_as_owner set to false, which is not equivalent to their behavior in pre-v16 releases.","part":"changes","patch_ids":["d8c1e90fc0309fa8a5bcd6f4baa8a282"],"related_changes":[],"relations":[],"section":"变更","section_path":["变更"],"source_commits":["67738dbf9"],"source_entry_id":"16.1/changes/048","source_hash":"2a5c6e2003d8d07fb50ad9955668c2bc3b3ed4bd59026e59a1653286547fb0fb","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"1bce373d3d8d566ecdc7025c89ec36a998b6a010c948bc2e8788221eb40daad8","text":"修复 pg_dump 以导出订阅的新 run_as_owner 选项（Philip Warner）§ 由于此疏忽，订阅总是以 run_as_owner 设置为 false 恢复，这与它们在 v16 之前版本中的行为不等价。","title":"修复 pg_dump 以导出订阅的新 run_as_owner 选项","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["06c0c3688","10e705bd2","295953f8b","4f16152d9","829d91cc6","aaaf8fbb6","c02f29758"],"commit_groups":[["06c0c3688","10e705bd2","295953f8b","4f16152d9","829d91cc6","aaaf8fbb6","c02f29758"]],"commits":["aaaf8fbb6"],"cves":[],"db_id":"79a645f700a7b01c2d229d8683ebf8bd","html":"\u003cp\u003e修复 \u003cspan\u003epg_restore\u003c/span\u003e，使选择性恢复能够同时包含所选表的表级和列级 ACL（Euler Taveira，Tom Lane）\u003ca href=\"https://postgr.es/c/aaaf8fbb6\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e之前，如果两种类型都存在，只会恢复表级 ACL。\u003c/p\u003e","id":"16.1-5d47a28a721967e8","identity_text":"Fix pg_restore so that selective restores will include both table-level and column-level ACLs for selected tables (Euler Taveira, Tom Lane) Formerly, only the table-level ACL would get restored if both types were present.","part":"changes","patch_ids":["d238d50d2ce73e23100077ffc68351c6"],"related_changes":[{"db_id":"302558461ac2a969704eef7bf95cbe35","evidence":{"patch_ids":["d238d50d2ce73e23100077ffc68351c6"],"same_day":true,"statement_hash":"b05820049ad07c5c1774cdf1156749061d13db40589d9a7b23ac017653b3077d"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复 pg_restore，使选择性恢复能够同时包含所选表的表级和列级 ACL","url":"/docs/compare/?release=15.5#15.5-549c3330a7fad7e3","version":"15.5"},{"db_id":"412661ef133221630648dbf55e99b490","evidence":{"patch_ids":["d238d50d2ce73e23100077ffc68351c6"],"same_day":true,"statement_hash":"b05820049ad07c5c1774cdf1156749061d13db40589d9a7b23ac017653b3077d"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复 pg_restore，使选择性恢复能够同时包含所选表的表级和列级 ACL","url":"/docs/compare/?release=14.10#14.10-617e833763ff8b6f","version":"14.10"},{"db_id":"2131547ac59bcdc4724160a3181219de","evidence":{"patch_ids":["d238d50d2ce73e23100077ffc68351c6"],"same_day":true,"statement_hash":"b05820049ad07c5c1774cdf1156749061d13db40589d9a7b23ac017653b3077d"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复 pg_restore，使选择性恢复能够同时包含所选表的表级和列级 ACL","url":"/docs/compare/?release=13.13#13.13-e02f7a923efb86f8","version":"13.13"},{"db_id":"9d58445bcb9ee4aa696ca5ff7fa07a34","evidence":{"patch_ids":["d238d50d2ce73e23100077ffc68351c6"],"same_day":true,"statement_hash":"b05820049ad07c5c1774cdf1156749061d13db40589d9a7b23ac017653b3077d"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"修复 pg_restore，使选择性恢复能够同时包含所选表的表级和列级 ACL","url":"/docs/compare/?release=12.17#12.17-5c437003fa0fbcb1","version":"12.17"},{"db_id":"4282f9960890427dc1256f8d24bda6fa","evidence":{"patch_ids":["d238d50d2ce73e23100077ffc68351c6"],"same_day":true,"statement_hash":"b05820049ad07c5c1774cdf1156749061d13db40589d9a7b23ac017653b3077d"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"修复 pg_restore，使选择性恢复能够同时包含所选表的表级和列级 ACL","url":"/docs/compare/?release=11.22#11.22-a6785b91c5a52928","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["d238d50d2ce73e23100077ffc68351c6"],"same_day":true,"statement_hash":"b05820049ad07c5c1774cdf1156749061d13db40589d9a7b23ac017653b3077d"},"rule":2,"target":"2131547ac59bcdc4724160a3181219de","type":"equivalent"},{"evidence":{"patch_ids":["d238d50d2ce73e23100077ffc68351c6"],"same_day":true,"statement_hash":"b05820049ad07c5c1774cdf1156749061d13db40589d9a7b23ac017653b3077d"},"rule":2,"target":"302558461ac2a969704eef7bf95cbe35","type":"equivalent"},{"evidence":{"patch_ids":["d238d50d2ce73e23100077ffc68351c6"],"same_day":true,"statement_hash":"b05820049ad07c5c1774cdf1156749061d13db40589d9a7b23ac017653b3077d"},"rule":2,"target":"412661ef133221630648dbf55e99b490","type":"equivalent"},{"evidence":{"patch_ids":["d238d50d2ce73e23100077ffc68351c6"],"same_day":true,"statement_hash":"b05820049ad07c5c1774cdf1156749061d13db40589d9a7b23ac017653b3077d"},"rule":2,"target":"4282f9960890427dc1256f8d24bda6fa","type":"equivalent"},{"evidence":{"patch_ids":["d238d50d2ce73e23100077ffc68351c6"],"same_day":true,"statement_hash":"b05820049ad07c5c1774cdf1156749061d13db40589d9a7b23ac017653b3077d"},"rule":2,"target":"9d58445bcb9ee4aa696ca5ff7fa07a34","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["aaaf8fbb6"],"source_entry_id":"16.1/changes/049","source_hash":"4905f0916cba2a1a99a20dd634c8c6f44553f9524cbea0bcdb77fa7d6926df23","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"b05820049ad07c5c1774cdf1156749061d13db40589d9a7b23ac017653b3077d","text":"修复 pg_restore，使选择性恢复能够同时包含所选表的表级和列级 ACL（Euler Taveira，Tom Lane）§ 之前，如果两种类型都存在，只会恢复表级 ACL。","title":"修复 pg_restore，使选择性恢复能够同时包含所选表的表级和列级 ACL","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["04d2d605f","26c291a15","2e3dc8c14","2f1f49975","8845d8597","af9f6cd1d","d3246a2ad","d3946c4f6","f9280e77e","fb9ddd0fa"],"commit_groups":[["04d2d605f","2f1f49975","d3246a2ad","f9280e77e"],["26c291a15","2e3dc8c14","8845d8597","af9f6cd1d","d3946c4f6","fb9ddd0fa"]],"commits":["fb9ddd0fa"],"cves":[],"db_id":"71e659f8c6a94b7dd48a713a2e518e67","html":"\u003cp\u003e在 \u003cspan\u003epg_upgrade\u003c/span\u003e 中增加对 \u003ccode\u003eabstime\u003c/code\u003e、\u003ccode\u003ereltime\u003c/code\u003e 和 \u003ccode\u003etinterval\u003c/code\u003e 数据类型使用的检查（Álvaro Herrera）\u003ca href=\"https://postgr.es/c/fb9ddd0fa\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e这些过时的数据类型已在 \u003cspan\u003ePostgreSQL\u003c/span\u003e 版本 12 中移除，因此在声称旧数据库可以升级之前，需要确保其中不存在这些类型。\u003c/p\u003e","id":"16.1-c1d8d960116d5e87","identity_text":"Add logic to pg_upgrade to check for use of abstime, reltime, and tinterval data types (Álvaro Herrera) These obsolete data types were removed in PostgreSQL version 12, so check to make sure they aren't present in an older database before claiming it can be upgraded.","part":"changes","patch_ids":["43a1ed48fc62c2947dcac628a0151d55","b2ca49ee08f96b4d11d4b0e6a5ce188a"],"related_changes":[{"db_id":"92a09069bcdae1953f673d61387c7759","evidence":{"patch_ids":["43a1ed48fc62c2947dcac628a0151d55","b2ca49ee08f96b4d11d4b0e6a5ce188a"],"same_day":true,"statement_hash":"71bc3276811f888d0cdd4651e0ce6a448f4f01967be5ec907cb502dce38cd12b"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"在 pg_upgrade 中增加对 abstime、reltime 和 tinterval 数据类型使用的检查","url":"/docs/compare/?release=15.5#15.5-7741975398eafd84","version":"15.5"},{"db_id":"e934bd8e8a629227e415bcebc458f138","evidence":{"patch_ids":["43a1ed48fc62c2947dcac628a0151d55","b2ca49ee08f96b4d11d4b0e6a5ce188a"],"same_day":true,"statement_hash":"71bc3276811f888d0cdd4651e0ce6a448f4f01967be5ec907cb502dce38cd12b"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"在 pg_upgrade 中增加对 abstime、reltime 和 tinterval 数据类型使用的检查","url":"/docs/compare/?release=14.10#14.10-0cd79d030bed6a99","version":"14.10"},{"db_id":"c8dba6be7269bdd8b6f8ff01e36654aa","evidence":{"patch_ids":["43a1ed48fc62c2947dcac628a0151d55","b2ca49ee08f96b4d11d4b0e6a5ce188a"],"same_day":true,"statement_hash":"71bc3276811f888d0cdd4651e0ce6a448f4f01967be5ec907cb502dce38cd12b"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"在 pg_upgrade 中增加对 abstime、reltime 和 tinterval 数据类型使用的检查","url":"/docs/compare/?release=13.13#13.13-bb62ba10fd7c97c1","version":"13.13"},{"db_id":"2366052a8cfbeca59f12ac9cfb94f3f2","evidence":{"patch_ids":["43a1ed48fc62c2947dcac628a0151d55","b2ca49ee08f96b4d11d4b0e6a5ce188a"],"same_day":true,"statement_hash":"71bc3276811f888d0cdd4651e0ce6a448f4f01967be5ec907cb502dce38cd12b"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"在 pg_upgrade 中增加对 abstime、reltime 和 tinterval 数据类型使用的检查","url":"/docs/compare/?release=12.17#12.17-67296bd96b86db1c","version":"12.17"}],"relations":[{"evidence":{"patch_ids":["43a1ed48fc62c2947dcac628a0151d55","b2ca49ee08f96b4d11d4b0e6a5ce188a"],"same_day":true,"statement_hash":"71bc3276811f888d0cdd4651e0ce6a448f4f01967be5ec907cb502dce38cd12b"},"rule":2,"target":"2366052a8cfbeca59f12ac9cfb94f3f2","type":"equivalent"},{"evidence":{"patch_ids":["43a1ed48fc62c2947dcac628a0151d55","b2ca49ee08f96b4d11d4b0e6a5ce188a"],"same_day":true,"statement_hash":"71bc3276811f888d0cdd4651e0ce6a448f4f01967be5ec907cb502dce38cd12b"},"rule":2,"target":"92a09069bcdae1953f673d61387c7759","type":"equivalent"},{"evidence":{"patch_ids":["43a1ed48fc62c2947dcac628a0151d55","b2ca49ee08f96b4d11d4b0e6a5ce188a"],"same_day":true,"statement_hash":"71bc3276811f888d0cdd4651e0ce6a448f4f01967be5ec907cb502dce38cd12b"},"rule":2,"target":"c8dba6be7269bdd8b6f8ff01e36654aa","type":"equivalent"},{"evidence":{"patch_ids":["43a1ed48fc62c2947dcac628a0151d55","b2ca49ee08f96b4d11d4b0e6a5ce188a"],"same_day":true,"statement_hash":"71bc3276811f888d0cdd4651e0ce6a448f4f01967be5ec907cb502dce38cd12b"},"rule":2,"target":"e934bd8e8a629227e415bcebc458f138","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["04d2d605f","fb9ddd0fa"],"source_entry_id":"16.1/changes/050","source_hash":"5c147780a6e99448393efdff76b2deeaad309d4ac591a9c1bf84024a5c3c5d79","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"71bc3276811f888d0cdd4651e0ce6a448f4f01967be5ec907cb502dce38cd12b","text":"在 pg_upgrade 中增加对 abstime、reltime 和 tinterval 数据类型使用的检查（Álvaro Herrera）§ 这些过时的数据类型已在 PostgreSQL 版本 12 中移除，因此在声称旧数据库可以升级之前，需要确保其中不存在这些类型。","title":"在 pg_upgrade 中增加对 abstime、reltime 和 tinterval 数据类型使用的检查","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["06ff06484","0df88a686","1102f4ece","3895e9153","73cda80a3","90ebcc32d"],"commit_groups":[["06ff06484","0df88a686","1102f4ece","3895e9153","73cda80a3","90ebcc32d"]],"commits":["06ff06484"],"cves":[],"db_id":"452ee86caa83537e7fe60788bbced011","html":"\u003cp\u003e避免在 Windows 上 \u003cspan\u003epgbench\u003c/span\u003e 中出现虚假的 \u003cspan\u003e“\u003cspan\u003etoo many client connections\u003c/span\u003e”\u003c/span\u003e 错误（Noah Misch）\u003ca href=\"https://postgr.es/c/06ff06484\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-a61c39eab88cd512","identity_text":"Avoid false too many client connections errors in pgbench on Windows (Noah Misch)","part":"changes","patch_ids":["2780294901b7130574a563777cc21dfc"],"related_changes":[{"db_id":"dbe51dcd9f16cad59ba344580fc951eb","evidence":{"patch_ids":["2780294901b7130574a563777cc21dfc"],"same_day":true,"statement_hash":"7f543108fe43115146bd742aaf5ca5711921405f567676aa9577423b18d8a309"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"避免在 Windows 上 pgbench 中出现虚假的 “too many client connections” 错误","url":"/docs/compare/?release=15.5#15.5-0315882f787cb411","version":"15.5"},{"db_id":"7bf19e30aa9fa1cd754182099c0c376d","evidence":{"patch_ids":["2780294901b7130574a563777cc21dfc"],"same_day":true,"statement_hash":"7f543108fe43115146bd742aaf5ca5711921405f567676aa9577423b18d8a309"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"避免在 Windows 上 pgbench 中出现虚假的 “too many client connections” 错误","url":"/docs/compare/?release=14.10#14.10-59536d62f0a0878a","version":"14.10"},{"db_id":"519c47e3c8ca694821b66282cc378d09","evidence":{"patch_ids":["2780294901b7130574a563777cc21dfc"],"same_day":true,"statement_hash":"7f543108fe43115146bd742aaf5ca5711921405f567676aa9577423b18d8a309"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"避免在 Windows 上 pgbench 中出现虚假的 “too many client connections” 错误","url":"/docs/compare/?release=13.13#13.13-817cd05fa68a0e3e","version":"13.13"},{"db_id":"a209dfb1e56931cd8e7c716c2530701c","evidence":{"patch_ids":["2780294901b7130574a563777cc21dfc"],"same_day":true,"statement_hash":"7f543108fe43115146bd742aaf5ca5711921405f567676aa9577423b18d8a309"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"避免在 Windows 上 pgbench 中出现虚假的 “too many client connections” 错误","url":"/docs/compare/?release=12.17#12.17-882e6ba253904a4e","version":"12.17"}],"relations":[{"evidence":{"patch_ids":["2780294901b7130574a563777cc21dfc"],"same_day":true,"statement_hash":"7f543108fe43115146bd742aaf5ca5711921405f567676aa9577423b18d8a309"},"rule":2,"target":"519c47e3c8ca694821b66282cc378d09","type":"equivalent"},{"evidence":{"patch_ids":["2780294901b7130574a563777cc21dfc"],"same_day":true,"statement_hash":"7f543108fe43115146bd742aaf5ca5711921405f567676aa9577423b18d8a309"},"rule":2,"target":"7bf19e30aa9fa1cd754182099c0c376d","type":"equivalent"},{"evidence":{"patch_ids":["2780294901b7130574a563777cc21dfc"],"same_day":true,"statement_hash":"7f543108fe43115146bd742aaf5ca5711921405f567676aa9577423b18d8a309"},"rule":2,"target":"a209dfb1e56931cd8e7c716c2530701c","type":"equivalent"},{"evidence":{"patch_ids":["2780294901b7130574a563777cc21dfc"],"same_day":true,"statement_hash":"7f543108fe43115146bd742aaf5ca5711921405f567676aa9577423b18d8a309"},"rule":2,"target":"dbe51dcd9f16cad59ba344580fc951eb","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["06ff06484"],"source_entry_id":"16.1/changes/051","source_hash":"3f9998f077ae6c6ed3d69dbee95c5ff9d15c083d224ed22b8258891b788e002b","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"7f543108fe43115146bd742aaf5ca5711921405f567676aa9577423b18d8a309","text":"避免在 Windows 上 pgbench 中出现虚假的 “too many client connections” 错误（Noah Misch）§","title":"避免在 Windows 上 pgbench 中出现虚假的 “too many client connections” 错误","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["2143d96dc","fb56a1811"],"commit_groups":[["2143d96dc","fb56a1811"]],"commits":["2143d96dc"],"cves":[],"db_id":"b7ce9273b22feb9e1a24e9c00073bd09","html":"\u003cp\u003e修复 \u003cspan\u003evacuumdb\u003c/span\u003e 对多个 \u003ccode\u003e-N\u003c/code\u003e 开关的处理（Nathan Bossart，Kuwamura Masaki）\u003ca href=\"https://postgr.es/c/2143d96dc\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e多个 \u003ccode\u003e-N\u003c/code\u003e 开关应该排除多个模式中的表，但实际上由于生成查询的错误构造而没有排除任何内容。\u003c/p\u003e","id":"16.1-8a60fad6e5683ab1","identity_text":"Fix vacuumdb's handling of multiple -N switches (Nathan Bossart, Kuwamura Masaki) Multiple -N switches should exclude tables in multiple schemas, but in fact excluded nothing due to faulty construction of a generated query.","part":"changes","patch_ids":["5e1cacb82faeb2426fe43dcc423c26ca"],"related_changes":[],"relations":[],"section":"变更","section_path":["变更"],"source_commits":["2143d96dc"],"source_entry_id":"16.1/changes/052","source_hash":"69e08d0b0dea4b1a5eb4940fe35ddebbba3b6e930544daef19ad33e79c3efa46","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"00d37ddfd0ef1225e5c0f12b2ee070362fd3a3e06aa744f8ac34eb1383335e86","text":"修复 vacuumdb 对多个 -N 开关的处理（Nathan Bossart，Kuwamura Masaki）§ 多个 -N 开关应该排除多个模式中的表，但实际上由于生成查询的错误构造而没有排除任何内容。","title":"修复 vacuumdb 对多个 -N 开关的处理","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["5cfba1ad6","f7dbdab05"],"commit_groups":[["5cfba1ad6","f7dbdab05"]],"commits":["f7dbdab05"],"cves":[],"db_id":"feffd52fb1a0bdfc11bee6f63e3eee1c","html":"\u003cp\u003e修复 \u003cspan\u003evacuumdb\u003c/span\u003e 以在仅分析模式下遵守其 \u003ccode\u003e--buffer-usage-limit\u003c/code\u003e 选项（Ryoga Yoshida，David Rowley）\u003ca href=\"https://postgr.es/c/f7dbdab05\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-86d8a18359ce430a","identity_text":"Fix vacuumdb to honor its --buffer-usage-limit option in analyze-only mode (Ryoga Yoshida, David Rowley)","part":"changes","patch_ids":["834ca0a635c3d0b6f051ab8ab258128a"],"related_changes":[],"relations":[],"section":"变更","section_path":["变更"],"source_commits":["f7dbdab05"],"source_entry_id":"16.1/changes/053","source_hash":"915edda0add7d7574a20a05d556f168a8ecfeb2830104de81e7b81105b0e48c0","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"631914895bc9a6c809d813b1bede2aaf9297cf99b2b85dbf9ef8d7805e12d6d5","text":"修复 vacuumdb 以在仅分析模式下遵守其 --buffer-usage-limit 选项（Ryoga Yoshida，David Rowley）§","title":"修复 vacuumdb 以在仅分析模式下遵守其 --buffer-usage-limit 选项","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["3a205c916","3c6a05b80","42496cba6","6ec9e9975","6f81386a9","e04509f32","f31ccb575"],"commit_groups":[["3a205c916","3c6a05b80","42496cba6","6ec9e9975","6f81386a9","e04509f32","f31ccb575"]],"commits":["3c6a05b80"],"cves":[],"db_id":"5b53a5f229384f927f774cef448e3568","html":"\u003cp\u003e在 \u003ccode\u003econtrib/amcheck\u003c/code\u003e 中，不将被中断的页面删除报告为损坏（Noah Misch）\u003ca href=\"https://postgr.es/c/3c6a05b80\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e此修复防止了 \u003cspan\u003e“\u003cspan\u003ethe first child of leftmost target page is not leftmost of its level\u003c/span\u003e”\u003c/span\u003e、\u003cspan\u003e“\u003cspan\u003eblock NNNN is not leftmost\u003c/span\u003e”\u003c/span\u003e 或 \u003cspan\u003e“\u003cspan\u003eleft link/right link pair in index XXXX not in agreement\u003c/span\u003e”\u003c/span\u003e 的误报。这些误报出现在 \u003cspan\u003eamcheck\u003c/span\u003e 在未完成的 B-树索引页面删除之后且 \u003ccode\u003eVACUUM\u003c/code\u003e 清理之前运行时。\u003c/p\u003e","id":"16.1-3342797ee931fa2c","identity_text":"In contrib/amcheck, do not report interrupted page deletion as corruption (Noah Misch) This fix prevents false-positive reports of the first child of leftmost target page is not leftmost of its level, block NNNN is not leftmost or left link/right link pair in index XXXX not in agreement. They appeared if amcheck ran after an unfinished btree index page deletion and before VACUUM had cleaned things up.","part":"changes","patch_ids":["83e4ef6619cef4f609a760ec0e92abdb"],"related_changes":[{"db_id":"9dedd63a3f50409489e06df7f677c3b7","evidence":{"patch_ids":["83e4ef6619cef4f609a760ec0e92abdb"],"same_day":true,"statement_hash":"7ebcabb4b48af0667c3ecf2e967b8c18202814693e8d0ae24f0bb2d495893386"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"在 contrib/amcheck 中，不将被中断的页面删除报告为损坏","url":"/docs/compare/?release=15.5#15.5-d3dfba334e6bf911","version":"15.5"},{"db_id":"7f89c62ce761a8e710280306b63c9382","evidence":{"patch_ids":["83e4ef6619cef4f609a760ec0e92abdb"],"same_day":true,"statement_hash":"7ebcabb4b48af0667c3ecf2e967b8c18202814693e8d0ae24f0bb2d495893386"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"在 contrib/amcheck 中，不将被中断的页面删除报告为损坏","url":"/docs/compare/?release=14.10#14.10-e607fc00fb438959","version":"14.10"},{"db_id":"be9f4bfaaa3e6a9ddd97ed2186e07557","evidence":{"patch_ids":["83e4ef6619cef4f609a760ec0e92abdb"],"same_day":true,"statement_hash":"7ebcabb4b48af0667c3ecf2e967b8c18202814693e8d0ae24f0bb2d495893386"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"在 contrib/amcheck 中，不将被中断的页面删除报告为损坏","url":"/docs/compare/?release=13.13#13.13-1b550f07f47d6f74","version":"13.13"},{"db_id":"d8ee619b4c02cdf238c242b7c84cf8d2","evidence":{"patch_ids":["83e4ef6619cef4f609a760ec0e92abdb"],"same_day":true,"statement_hash":"7ebcabb4b48af0667c3ecf2e967b8c18202814693e8d0ae24f0bb2d495893386"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"在 contrib/amcheck 中，不将被中断的页面删除报告为损坏","url":"/docs/compare/?release=12.17#12.17-13ecc152d9ad3e91","version":"12.17"},{"db_id":"fd41839d53181a54d5cc23a74741f5d5","evidence":{"patch_ids":["83e4ef6619cef4f609a760ec0e92abdb"],"same_day":true,"statement_hash":"7ebcabb4b48af0667c3ecf2e967b8c18202814693e8d0ae24f0bb2d495893386"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"在 contrib/amcheck 中，不将被中断的页面删除报告为损坏","url":"/docs/compare/?release=11.22#11.22-cc2d47c4bfbbe3a1","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["83e4ef6619cef4f609a760ec0e92abdb"],"same_day":true,"statement_hash":"7ebcabb4b48af0667c3ecf2e967b8c18202814693e8d0ae24f0bb2d495893386"},"rule":2,"target":"7f89c62ce761a8e710280306b63c9382","type":"equivalent"},{"evidence":{"patch_ids":["83e4ef6619cef4f609a760ec0e92abdb"],"same_day":true,"statement_hash":"7ebcabb4b48af0667c3ecf2e967b8c18202814693e8d0ae24f0bb2d495893386"},"rule":2,"target":"9dedd63a3f50409489e06df7f677c3b7","type":"equivalent"},{"evidence":{"patch_ids":["83e4ef6619cef4f609a760ec0e92abdb"],"same_day":true,"statement_hash":"7ebcabb4b48af0667c3ecf2e967b8c18202814693e8d0ae24f0bb2d495893386"},"rule":2,"target":"be9f4bfaaa3e6a9ddd97ed2186e07557","type":"equivalent"},{"evidence":{"patch_ids":["83e4ef6619cef4f609a760ec0e92abdb"],"same_day":true,"statement_hash":"7ebcabb4b48af0667c3ecf2e967b8c18202814693e8d0ae24f0bb2d495893386"},"rule":2,"target":"d8ee619b4c02cdf238c242b7c84cf8d2","type":"equivalent"},{"evidence":{"patch_ids":["83e4ef6619cef4f609a760ec0e92abdb"],"same_day":true,"statement_hash":"7ebcabb4b48af0667c3ecf2e967b8c18202814693e8d0ae24f0bb2d495893386"},"rule":2,"target":"fd41839d53181a54d5cc23a74741f5d5","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["3c6a05b80"],"source_entry_id":"16.1/changes/054","source_hash":"8941402a24d572b05ff86eb58466f191168bb0738a61609d6c2dc587cf4df778","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"7ebcabb4b48af0667c3ecf2e967b8c18202814693e8d0ae24f0bb2d495893386","text":"在 contrib/amcheck 中，不将被中断的页面删除报告为损坏（Noah Misch）§ 此修复防止了 “the first child of leftmost target page is not leftmost of its level”、“block NNNN is not leftmost” 或 “left link/right link pair in index XXXX not in agreement” 的误报。这些误报出现在 amcheck 在未完成的 B-树索引页面删除之后且 VACUUM 清理之前运行时。","title":"在 contrib/amcheck 中，不将被中断的页面删除报告为损坏","variants":[],"version":"16.1"},{"also_in":[],"category":"bugfix","category_label":"Bug fixes","commit_aliases":["162b38a06","35e6a5c20","5f0691839","849172ff4","ab73a37e9","c804ffb56","f7cd7b265"],"commit_groups":[["162b38a06","35e6a5c20","5f0691839","849172ff4","ab73a37e9","c804ffb56","f7cd7b265"]],"commits":["ab73a37e9"],"cves":[],"db_id":"832af3b39b90b210fd007494ada7f758","html":"\u003cp\u003e修复 \u003ccode\u003econtrib/btree_gin\u003c/code\u003e 在 \u003ccode\u003einterval\u003c/code\u003e 列上的索引在执行使用 \u003ccode\u003e\u0026lt;\u003c/code\u003e 或 \u003ccode\u003e\u0026lt;=\u003c/code\u003e 操作符的索引扫描时的失败（Dean Rasheed）\u003ca href=\"https://postgr.es/c/ab73a37e9\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e这样的索引扫描无法返回所有应返回的条目。\u003c/p\u003e","id":"16.1-8115689a73bc7d1f","identity_text":"Fix failure of contrib/btree_gin indexes on interval columns, when an indexscan using the \u003c or \u003c= operator is performed (Dean Rasheed) Such an indexscan failed to return all the entries it should.","part":"changes","patch_ids":["84f913c6297a057f16db346fb67300e4"],"related_changes":[{"db_id":"66554317a5f4f755259d5ad20ed1f836","evidence":{"patch_ids":["84f913c6297a057f16db346fb67300e4"],"same_day":true,"statement_hash":"3e66f075a51be5c57dd3a33105154071359cdead98207ece255868bd85b5d860"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"修复 contrib/btree_gin 在 interval 列上的索引在执行使用 \u003c 或 \u003c= 操作符的索引扫描时的失败","url":"/docs/compare/?release=15.5#15.5-2a495edd80d13e4f","version":"15.5"},{"db_id":"fd219a1293f00b8394656ea647581882","evidence":{"patch_ids":["84f913c6297a057f16db346fb67300e4"],"same_day":true,"statement_hash":"3e66f075a51be5c57dd3a33105154071359cdead98207ece255868bd85b5d860"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"修复 contrib/btree_gin 在 interval 列上的索引在执行使用 \u003c 或 \u003c= 操作符的索引扫描时的失败","url":"/docs/compare/?release=14.10#14.10-27d139caec78ff29","version":"14.10"},{"db_id":"009cea7e5da099d3bd27cbff559d4cf1","evidence":{"patch_ids":["84f913c6297a057f16db346fb67300e4"],"same_day":true,"statement_hash":"3e66f075a51be5c57dd3a33105154071359cdead98207ece255868bd85b5d860"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"修复 contrib/btree_gin 在 interval 列上的索引在执行使用 \u003c 或 \u003c= 操作符的索引扫描时的失败","url":"/docs/compare/?release=13.13#13.13-0d781e1d4bb8887d","version":"13.13"},{"db_id":"09fc75bafe53c1f45ccee66e736cd192","evidence":{"patch_ids":["84f913c6297a057f16db346fb67300e4"],"same_day":true,"statement_hash":"3e66f075a51be5c57dd3a33105154071359cdead98207ece255868bd85b5d860"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"修复 contrib/btree_gin 在 interval 列上的索引在执行使用 \u003c 或 \u003c= 操作符的索引扫描时的失败","url":"/docs/compare/?release=12.17#12.17-3cf6de6fa066c547","version":"12.17"},{"db_id":"46be902eb6dad47c512aed47256cc3a6","evidence":{"patch_ids":["84f913c6297a057f16db346fb67300e4"],"same_day":true,"statement_hash":"3e66f075a51be5c57dd3a33105154071359cdead98207ece255868bd85b5d860"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"修复 contrib/btree_gin 在 interval 列上的索引在执行使用 \u003c 或 \u003c= 操作符的索引扫描时的失败","url":"/docs/compare/?release=11.22#11.22-1fa757aba0c130ab","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["84f913c6297a057f16db346fb67300e4"],"same_day":true,"statement_hash":"3e66f075a51be5c57dd3a33105154071359cdead98207ece255868bd85b5d860"},"rule":2,"target":"009cea7e5da099d3bd27cbff559d4cf1","type":"equivalent"},{"evidence":{"patch_ids":["84f913c6297a057f16db346fb67300e4"],"same_day":true,"statement_hash":"3e66f075a51be5c57dd3a33105154071359cdead98207ece255868bd85b5d860"},"rule":2,"target":"09fc75bafe53c1f45ccee66e736cd192","type":"equivalent"},{"evidence":{"patch_ids":["84f913c6297a057f16db346fb67300e4"],"same_day":true,"statement_hash":"3e66f075a51be5c57dd3a33105154071359cdead98207ece255868bd85b5d860"},"rule":2,"target":"46be902eb6dad47c512aed47256cc3a6","type":"equivalent"},{"evidence":{"patch_ids":["84f913c6297a057f16db346fb67300e4"],"same_day":true,"statement_hash":"3e66f075a51be5c57dd3a33105154071359cdead98207ece255868bd85b5d860"},"rule":2,"target":"66554317a5f4f755259d5ad20ed1f836","type":"equivalent"},{"evidence":{"patch_ids":["84f913c6297a057f16db346fb67300e4"],"same_day":true,"statement_hash":"3e66f075a51be5c57dd3a33105154071359cdead98207ece255868bd85b5d860"},"rule":2,"target":"fd219a1293f00b8394656ea647581882","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["ab73a37e9"],"source_entry_id":"16.1/changes/055","source_hash":"be9c8ef6a1165705d29295d23e38c94c9e202569e0d4f41a25c5197c11ea5e38","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"3e66f075a51be5c57dd3a33105154071359cdead98207ece255868bd85b5d860","text":"修复 contrib/btree_gin 在 interval 列上的索引在执行使用 \u003c 或 \u003c= 操作符的索引扫描时的失败（Dean Rasheed）§ 这样的索引扫描无法返回所有应返回的条目。","title":"修复 contrib/btree_gin 在 interval 列上的索引在执行使用 \u003c 或 \u003c= 操作符的索引扫描时的失败","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["0a8b7d5c1","15ddc9725","37d5babb5","53c4dabe1","60596f148","74d19ec09","76200e5ee","774185056","7c070e224","7da915e33","82d9a782a","981292c19","9ad986276","b2e097788","b60e3ac76","d701f0d1f","ee3e4c41f","eed1feb3f","f28956b23","f90b4a846"],"commit_groups":[["0a8b7d5c1","53c4dabe1","76200e5ee","774185056","7da915e33","b60e3ac76"],["15ddc9725","37d5babb5","74d19ec09","82d9a782a","eed1feb3f","f28956b23"],["60596f148","981292c19","b2e097788","d701f0d1f","ee3e4c41f","f90b4a846"],["7c070e224","9ad986276"]],"commits":["60596f148","74d19ec09","774185056"],"cves":[],"db_id":"44ecc0dade5b0c9fb36d888323f1cd01","html":"\u003cp\u003e增加对 LLVM 16 和 17 的支持（Thomas Munro，Dmitry Dolgov）\u003ca href=\"https://postgr.es/c/774185056\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/74d19ec09\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/60596f148\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-9a90d9e624c911ab","identity_text":"Add support for LLVM 16 and 17 (Thomas Munro, Dmitry Dolgov)","part":"changes","patch_ids":["4608433d39e69599bbd1c2e12efe2bc8","4f39a7e788fa268757ebae21b3399a4b","5a7a440eec4f7b5c085a254917051668","cd2a51aad46e6f425ca90312af1a85b1"],"related_changes":[{"db_id":"e08f9c82df7e0b6b2778678bfb0c8430","evidence":{"patch_ids":["4608433d39e69599bbd1c2e12efe2bc8","4f39a7e788fa268757ebae21b3399a4b","5a7a440eec4f7b5c085a254917051668","cd2a51aad46e6f425ca90312af1a85b1"],"same_day":true,"statement_hash":"5de6078d4566df4986d303e091aa16a8f18761e85570fe824aae0e1cbfe20668"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"增加对 LLVM 16 和 17 的支持","url":"/docs/compare/?release=15.5#15.5-6d4b5936d4e70748","version":"15.5"},{"db_id":"69cccc8d5d144e56463fb7e8dcdd5ab6","evidence":{"patch_ids":["4608433d39e69599bbd1c2e12efe2bc8","4f39a7e788fa268757ebae21b3399a4b","5a7a440eec4f7b5c085a254917051668","cd2a51aad46e6f425ca90312af1a85b1"],"same_day":true,"statement_hash":"5de6078d4566df4986d303e091aa16a8f18761e85570fe824aae0e1cbfe20668"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"增加对 LLVM 16 和 17 的支持","url":"/docs/compare/?release=14.10#14.10-f21e24bd3b01232a","version":"14.10"},{"db_id":"e8a52c776d10ff6d7c6f4744d3c9a2a0","evidence":{"patch_ids":["4608433d39e69599bbd1c2e12efe2bc8","4f39a7e788fa268757ebae21b3399a4b","5a7a440eec4f7b5c085a254917051668","cd2a51aad46e6f425ca90312af1a85b1"],"same_day":true,"statement_hash":"5de6078d4566df4986d303e091aa16a8f18761e85570fe824aae0e1cbfe20668"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"增加对 LLVM 16 和 17 的支持","url":"/docs/compare/?release=13.13#13.13-f44a327a7a0e285d","version":"13.13"},{"db_id":"007c120ddb57b6841e60b1f23de49af5","evidence":{"patch_ids":["4608433d39e69599bbd1c2e12efe2bc8","4f39a7e788fa268757ebae21b3399a4b","5a7a440eec4f7b5c085a254917051668","cd2a51aad46e6f425ca90312af1a85b1"],"same_day":true,"statement_hash":"5de6078d4566df4986d303e091aa16a8f18761e85570fe824aae0e1cbfe20668"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"增加对 LLVM 16 和 17 的支持","url":"/docs/compare/?release=12.17#12.17-d04e0431486236ad","version":"12.17"}],"relations":[{"evidence":{"patch_ids":["4608433d39e69599bbd1c2e12efe2bc8","4f39a7e788fa268757ebae21b3399a4b","5a7a440eec4f7b5c085a254917051668","cd2a51aad46e6f425ca90312af1a85b1"],"same_day":true,"statement_hash":"5de6078d4566df4986d303e091aa16a8f18761e85570fe824aae0e1cbfe20668"},"rule":2,"target":"007c120ddb57b6841e60b1f23de49af5","type":"equivalent"},{"evidence":{"patch_ids":["4608433d39e69599bbd1c2e12efe2bc8","4f39a7e788fa268757ebae21b3399a4b","5a7a440eec4f7b5c085a254917051668","cd2a51aad46e6f425ca90312af1a85b1"],"same_day":true,"statement_hash":"5de6078d4566df4986d303e091aa16a8f18761e85570fe824aae0e1cbfe20668"},"rule":2,"target":"69cccc8d5d144e56463fb7e8dcdd5ab6","type":"equivalent"},{"evidence":{"patch_ids":["4608433d39e69599bbd1c2e12efe2bc8","4f39a7e788fa268757ebae21b3399a4b","5a7a440eec4f7b5c085a254917051668","cd2a51aad46e6f425ca90312af1a85b1"],"same_day":true,"statement_hash":"5de6078d4566df4986d303e091aa16a8f18761e85570fe824aae0e1cbfe20668"},"rule":2,"target":"e08f9c82df7e0b6b2778678bfb0c8430","type":"equivalent"},{"evidence":{"patch_ids":["4608433d39e69599bbd1c2e12efe2bc8","4f39a7e788fa268757ebae21b3399a4b","5a7a440eec4f7b5c085a254917051668","cd2a51aad46e6f425ca90312af1a85b1"],"same_day":true,"statement_hash":"5de6078d4566df4986d303e091aa16a8f18761e85570fe824aae0e1cbfe20668"},"rule":2,"target":"e8a52c776d10ff6d7c6f4744d3c9a2a0","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["60596f148","74d19ec09","774185056","7c070e224"],"source_entry_id":"16.1/changes/056","source_hash":"02ef8c5e3bb2f1357be5cc9760f94002069dc93068cf46c90a7adbf61cb036de","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"5de6078d4566df4986d303e091aa16a8f18761e85570fe824aae0e1cbfe20668","text":"增加对 LLVM 16 和 17 的支持（Thomas Munro，Dmitry Dolgov）§ § §","title":"增加对 LLVM 16 和 17 的支持","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["06843df4a","0e0de20c8","1b64e374c","3aa021b29","4d10fda52","53cc19bfa","5d60e8ed3","75c562653","78f17fb97","abe423712","be3398ea1","d8ceb98e4","e73d6a0df","e9d1560d3"],"commit_groups":[["06843df4a","1b64e374c","4d10fda52","75c562653","be3398ea1","d8ceb98e4","e9d1560d3"],["0e0de20c8","3aa021b29","53cc19bfa","5d60e8ed3","78f17fb97","abe423712","e73d6a0df"]],"commits":["75c562653","e73d6a0df"],"cves":[],"db_id":"fcb39f9d3a410ab1f0380fa857afcba4","html":"\u003cp\u003e消除在最新 \u003cspan\u003emacOS\u003c/span\u003e 上的各种编译时警告（Tom Lane）\u003ca href=\"https://postgr.es/c/75c562653\"\u003e§\u003c/a\u003e \u003ca href=\"https://postgr.es/c/e73d6a0df\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e\u003cspan\u003eXcode 15\u003c/span\u003e（随 \u003cspan\u003emacOS Sonoma\u003c/span\u003e 发布）改变了链接器的行为方式，在构建 \u003cspan\u003ePostgreSQL\u003c/span\u003e 时导致许多重复库警告。这些警告是无害的，但很烦人，因此避免两次引用相同的库。同时移除了 \u003ccode\u003e-multiply_defined suppress\u003c/code\u003e 链接器选项的使用，该选项显然长期以来一直没有实际作用，而现在使用它会引发警告。\u003c/p\u003e","id":"16.1-bb1be8b973b8c1e7","identity_text":"Suppress assorted build-time warnings on recent macOS (Tom Lane) Xcode 15 (released with macOS Sonoma) changed the linker's behavior in a way that causes many duplicate-library warnings while building PostgreSQL. These were harmless, but they're annoying so avoid citing the same libraries twice. Also remove use of the -multiply_defined suppress linker switch, which apparently has been a no-op for a long time, and is now actively complained of.","part":"changes","patch_ids":["a81aa1a96ae2547ce0a8a861dc1f36ec","dfa8ace78adca8f45321650020e39d4b"],"related_changes":[{"db_id":"889e1c2830937ade620da8228f2e65f1","evidence":{"patch_ids":["a81aa1a96ae2547ce0a8a861dc1f36ec","dfa8ace78adca8f45321650020e39d4b"],"same_day":true,"statement_hash":"d5073e3f085ec763f28cd688ba22d86ad1daa8518a3db095e50181b6dd5f78da"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"消除在最新 macOS 上的各种编译时警告","url":"/docs/compare/?release=15.5#15.5-573d44f59425776a","version":"15.5"},{"db_id":"85d46f943149d90e88baded142b84a7e","evidence":{"patch_ids":["a81aa1a96ae2547ce0a8a861dc1f36ec","dfa8ace78adca8f45321650020e39d4b"],"same_day":true,"statement_hash":"d5073e3f085ec763f28cd688ba22d86ad1daa8518a3db095e50181b6dd5f78da"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"消除在最新 macOS 上的各种编译时警告","url":"/docs/compare/?release=14.10#14.10-f02a51ad63ec6450","version":"14.10"},{"db_id":"102539bf06fb66ec5b1425b9816b45ad","evidence":{"patch_ids":["a81aa1a96ae2547ce0a8a861dc1f36ec","dfa8ace78adca8f45321650020e39d4b"],"same_day":true,"statement_hash":"d5073e3f085ec763f28cd688ba22d86ad1daa8518a3db095e50181b6dd5f78da"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"消除在最新 macOS 上的各种编译时警告","url":"/docs/compare/?release=13.13#13.13-f188fa0b88c1c38d","version":"13.13"},{"db_id":"da7113d399b310b7c7ad431af069368a","evidence":{"patch_ids":["a81aa1a96ae2547ce0a8a861dc1f36ec","dfa8ace78adca8f45321650020e39d4b"],"same_day":true,"statement_hash":"d5073e3f085ec763f28cd688ba22d86ad1daa8518a3db095e50181b6dd5f78da"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"消除在最新 macOS 上的各种编译时警告","url":"/docs/compare/?release=12.17#12.17-11c5a66bc2fc6633","version":"12.17"},{"db_id":"fe1c4f5f7923ecd141d97844c567cca5","evidence":{"patch_ids":["a81aa1a96ae2547ce0a8a861dc1f36ec","dfa8ace78adca8f45321650020e39d4b"],"same_day":true,"statement_hash":"d5073e3f085ec763f28cd688ba22d86ad1daa8518a3db095e50181b6dd5f78da"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"消除在最新 macOS 上的各种编译时警告","url":"/docs/compare/?release=11.22#11.22-37043fae46d4141e","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["a81aa1a96ae2547ce0a8a861dc1f36ec","dfa8ace78adca8f45321650020e39d4b"],"same_day":true,"statement_hash":"d5073e3f085ec763f28cd688ba22d86ad1daa8518a3db095e50181b6dd5f78da"},"rule":2,"target":"102539bf06fb66ec5b1425b9816b45ad","type":"equivalent"},{"evidence":{"patch_ids":["a81aa1a96ae2547ce0a8a861dc1f36ec","dfa8ace78adca8f45321650020e39d4b"],"same_day":true,"statement_hash":"d5073e3f085ec763f28cd688ba22d86ad1daa8518a3db095e50181b6dd5f78da"},"rule":2,"target":"85d46f943149d90e88baded142b84a7e","type":"equivalent"},{"evidence":{"patch_ids":["a81aa1a96ae2547ce0a8a861dc1f36ec","dfa8ace78adca8f45321650020e39d4b"],"same_day":true,"statement_hash":"d5073e3f085ec763f28cd688ba22d86ad1daa8518a3db095e50181b6dd5f78da"},"rule":2,"target":"889e1c2830937ade620da8228f2e65f1","type":"equivalent"},{"evidence":{"patch_ids":["a81aa1a96ae2547ce0a8a861dc1f36ec","dfa8ace78adca8f45321650020e39d4b"],"same_day":true,"statement_hash":"d5073e3f085ec763f28cd688ba22d86ad1daa8518a3db095e50181b6dd5f78da"},"rule":2,"target":"da7113d399b310b7c7ad431af069368a","type":"equivalent"},{"evidence":{"patch_ids":["a81aa1a96ae2547ce0a8a861dc1f36ec","dfa8ace78adca8f45321650020e39d4b"],"same_day":true,"statement_hash":"d5073e3f085ec763f28cd688ba22d86ad1daa8518a3db095e50181b6dd5f78da"},"rule":2,"target":"fe1c4f5f7923ecd141d97844c567cca5","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["75c562653","e73d6a0df"],"source_entry_id":"16.1/changes/057","source_hash":"95037638df3650a0a342686296a8455f3fca0706cbaec7c3166872a83f92a420","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"d5073e3f085ec763f28cd688ba22d86ad1daa8518a3db095e50181b6dd5f78da","text":"消除在最新 macOS 上的各种编译时警告（Tom Lane）§ § Xcode 15（随 macOS Sonoma 发布）改变了链接器的行为方式，在构建 PostgreSQL 时导致许多重复库警告。这些警告是无害的，但很烦人，因此避免两次引用相同的库。同时移除了 -multiply_defined suppress 链接器选项的使用，该选项显然长期以来一直没有实际作用，而现在使用它会引发警告。","title":"消除在最新 macOS 上的各种编译时警告","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["641db601b","6fc3a138b","8a9e4e84e","a64b8b035","e4d7ad30f"],"commit_groups":[["641db601b","6fc3a138b","8a9e4e84e","a64b8b035","e4d7ad30f"]],"commits":["641db601b"],"cves":[],"db_id":"7ea8e184a9d5a011bfb13752213bd32b","html":"\u003cp\u003e在构建 \u003ccode\u003econtrib/unaccent\u003c/code\u003e 的规则文件时，如果未指定 \u003ccode\u003e--with-python\u003c/code\u003e 且未设置 make 变量 \u003ccode\u003ePYTHON\u003c/code\u003e，则回退使用 \u003ccode\u003epython\u003c/code\u003e（Japin Li）\u003ca href=\"https://postgr.es/c/641db601b\"\u003e§\u003c/a\u003e\u003c/p\u003e","id":"16.1-9fad64249102cc9d","identity_text":"When building contrib/unaccent's rules file, fall back to using python if --with-python was not given and make variable PYTHON was not set (Japin Li)","part":"changes","patch_ids":["821d296a7cd70265386a728132cfdc85"],"related_changes":[{"db_id":"8d63636360a6339258306bc5258862d5","evidence":{"patch_ids":["821d296a7cd70265386a728132cfdc85"],"same_day":true,"statement_hash":"3360b3093e02d388f54ecaf0d840b5324c3d55111d7efc9a2616b4c261135df2"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"在构建 contrib/unaccent 的规则文件时，如果未指定 --with-python 且未设置 make 变量 PYTHON，则回退使用 python","url":"/docs/compare/?release=15.5#15.5-45c63fa0de4d8037","version":"15.5"},{"db_id":"6be5d9258a4392f257e4b57e7bbb4779","evidence":{"patch_ids":["821d296a7cd70265386a728132cfdc85"],"same_day":true,"statement_hash":"3360b3093e02d388f54ecaf0d840b5324c3d55111d7efc9a2616b4c261135df2"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"在构建 contrib/unaccent 的规则文件时，如果未指定 --with-python 且未设置 make 变量 PYTHON，则回退使用 python","url":"/docs/compare/?release=14.10#14.10-44b0d97fcadf1394","version":"14.10"},{"db_id":"c3277e3b4c740929fd0d9250ff487646","evidence":{"patch_ids":["821d296a7cd70265386a728132cfdc85"],"same_day":true,"statement_hash":"3360b3093e02d388f54ecaf0d840b5324c3d55111d7efc9a2616b4c261135df2"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"在构建 contrib/unaccent 的规则文件时，如果未指定 --with-python 且未设置 make 变量 PYTHON，则回退使用 python","url":"/docs/compare/?release=13.13#13.13-d954362300fbe0ac","version":"13.13"}],"relations":[{"evidence":{"patch_ids":["821d296a7cd70265386a728132cfdc85"],"same_day":true,"statement_hash":"3360b3093e02d388f54ecaf0d840b5324c3d55111d7efc9a2616b4c261135df2"},"rule":2,"target":"6be5d9258a4392f257e4b57e7bbb4779","type":"equivalent"},{"evidence":{"patch_ids":["821d296a7cd70265386a728132cfdc85"],"same_day":true,"statement_hash":"3360b3093e02d388f54ecaf0d840b5324c3d55111d7efc9a2616b4c261135df2"},"rule":2,"target":"8d63636360a6339258306bc5258862d5","type":"equivalent"},{"evidence":{"patch_ids":["821d296a7cd70265386a728132cfdc85"],"same_day":true,"statement_hash":"3360b3093e02d388f54ecaf0d840b5324c3d55111d7efc9a2616b4c261135df2"},"rule":2,"target":"c3277e3b4c740929fd0d9250ff487646","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["641db601b"],"source_entry_id":"16.1/changes/058","source_hash":"7356013388b19f0c896e27b16c1b77b7f4a617d942384bc2601c5eec270000a9","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"3360b3093e02d388f54ecaf0d840b5324c3d55111d7efc9a2616b4c261135df2","text":"在构建 contrib/unaccent 的规则文件时，如果未指定 --with-python 且未设置 make 变量 PYTHON，则回退使用 python（Japin Li）§","title":"在构建 contrib/unaccent 的规则文件时，如果未指定 --with-python 且未设置 make 变量 PYTHON，则回退使用 python","variants":[],"version":"16.1"},{"also_in":[],"category":"improvement","category_label":"Improvements","commit_aliases":["5fd3e06f6","64fc5e005","7180bb827","85b98a70b","877e7b4b9","d1537afe3","d94612873"],"commit_groups":[["5fd3e06f6","64fc5e005","7180bb827","85b98a70b","877e7b4b9","d1537afe3","d94612873"]],"commits":["d1537afe3"],"cves":[],"db_id":"c429f287435f5b1df7af6656dc93551b","html":"\u003cp\u003e从默认时区缩写列表中移除 \u003ccode\u003ePHOT\u003c/code\u003e（凤凰群岛时间）（Tom Lane）\u003ca href=\"https://postgr.es/c/d1537afe3\"\u003e§\u003c/a\u003e\u003c/p\u003e\n\u003cp\u003e此缩写在默认列表中的存在可能导致在最新的 Debian 和 Ubuntu 发行版上出现失败，因为它们不再默认安装底层的 tzdb 条目。由于这是一个为总人口约二十几人的区域编造的缩写，不太可能有人会需要它。如果确有需要，可以通过自定义缩写文件将其恢复。\u003c/p\u003e","id":"16.1-1048d42027c633a6","identity_text":"Remove PHOT (Phoenix Islands Time) from the default timezone abbreviations list (Tom Lane) Presence of this abbreviation in the default list can cause failures on recent Debian and Ubuntu releases, as they no longer install the underlying tzdb entry by default. Since this is a made-up abbreviation for a zone with a total human population of about two dozen, it seems unlikely that anyone will miss it. If someone does, they can put it back via a custom abbreviations file.","part":"changes","patch_ids":["79a37f33965b630e4855cf1b088ef313"],"related_changes":[{"db_id":"78e5b63be8e6fc998c544962dec09060","evidence":{"patch_ids":["79a37f33965b630e4855cf1b088ef313"],"same_day":true,"statement_hash":"a21c95d62798a694d7c948c29830aab551934419bd30490543c0db905acbb1fb"},"kind":"equivalent","label":"15.5","source_url":"/docs/release/15.5/#ZH-AUTO-RELEASE-15-SECT2-26","title":"从默认时区缩写列表中移除 PHOT（凤凰群岛时间）","url":"/docs/compare/?release=15.5#15.5-e2fdb9dea45c2a7a","version":"15.5"},{"db_id":"9d05fe698b687521b65a8d507805d6f6","evidence":{"patch_ids":["79a37f33965b630e4855cf1b088ef313"],"same_day":true,"statement_hash":"a21c95d62798a694d7c948c29830aab551934419bd30490543c0db905acbb1fb"},"kind":"equivalent","label":"14.10","source_url":"/docs/release/14.10/#ZH-AUTO-RELEASE-14-SECT2-26","title":"从默认时区缩写列表中移除 PHOT（凤凰群岛时间）","url":"/docs/compare/?release=14.10#14.10-1fe926f2cab932ac","version":"14.10"},{"db_id":"37f077348d48792ab5a99605c76f4879","evidence":{"patch_ids":["79a37f33965b630e4855cf1b088ef313"],"same_day":true,"statement_hash":"a21c95d62798a694d7c948c29830aab551934419bd30490543c0db905acbb1fb"},"kind":"equivalent","label":"13.13","source_url":"/docs/release/13.13/#id-1.11.6.16.5","title":"从默认时区缩写列表中移除 PHOT（凤凰群岛时间）","url":"/docs/compare/?release=13.13#13.13-59a69b1162d8ee8f","version":"13.13"},{"db_id":"e91e4da87fd96755be1025d6215001e1","evidence":{"patch_ids":["79a37f33965b630e4855cf1b088ef313"],"same_day":true,"statement_hash":"a21c95d62798a694d7c948c29830aab551934419bd30490543c0db905acbb1fb"},"kind":"equivalent","label":"12.17","source_url":"/docs/release/12.17/#id-1.11.6.11.5","title":"从默认时区缩写列表中移除 PHOT（凤凰群岛时间）","url":"/docs/compare/?release=12.17#12.17-b2cb4bd88c7010bb","version":"12.17"},{"db_id":"ee1c4e2e95e7bdf271c3b5b74f84d081","evidence":{"patch_ids":["79a37f33965b630e4855cf1b088ef313"],"same_day":true,"statement_hash":"a21c95d62798a694d7c948c29830aab551934419bd30490543c0db905acbb1fb"},"kind":"equivalent","label":"11.22","source_url":"/docs/release/11.22/#id-1.11.6.5.6","title":"从默认时区缩写列表中移除 PHOT（凤凰群岛时间）","url":"/docs/compare/?release=11.22#11.22-45a39d1e39ad25ed","version":"11.22"}],"relations":[{"evidence":{"patch_ids":["79a37f33965b630e4855cf1b088ef313"],"same_day":true,"statement_hash":"a21c95d62798a694d7c948c29830aab551934419bd30490543c0db905acbb1fb"},"rule":2,"target":"37f077348d48792ab5a99605c76f4879","type":"equivalent"},{"evidence":{"patch_ids":["79a37f33965b630e4855cf1b088ef313"],"same_day":true,"statement_hash":"a21c95d62798a694d7c948c29830aab551934419bd30490543c0db905acbb1fb"},"rule":2,"target":"78e5b63be8e6fc998c544962dec09060","type":"equivalent"},{"evidence":{"patch_ids":["79a37f33965b630e4855cf1b088ef313"],"same_day":true,"statement_hash":"a21c95d62798a694d7c948c29830aab551934419bd30490543c0db905acbb1fb"},"rule":2,"target":"9d05fe698b687521b65a8d507805d6f6","type":"equivalent"},{"evidence":{"patch_ids":["79a37f33965b630e4855cf1b088ef313"],"same_day":true,"statement_hash":"a21c95d62798a694d7c948c29830aab551934419bd30490543c0db905acbb1fb"},"rule":2,"target":"e91e4da87fd96755be1025d6215001e1","type":"equivalent"},{"evidence":{"patch_ids":["79a37f33965b630e4855cf1b088ef313"],"same_day":true,"statement_hash":"a21c95d62798a694d7c948c29830aab551934419bd30490543c0db905acbb1fb"},"rule":2,"target":"ee1c4e2e95e7bdf271c3b5b74f84d081","type":"equivalent"}],"section":"变更","section_path":["变更"],"source_commits":["d1537afe3"],"source_entry_id":"16.1/changes/059","source_hash":"ff302b3b26fa46b9d87a501fae524f7d948e4cdab78e70e0786e323c210c6809","source_url":"/docs/release/16.1/#RELEASE-16-1-CHANGES","statement_hash":"a21c95d62798a694d7c948c29830aab551934419bd30490543c0db905acbb1fb","text":"从默认时区缩写列表中移除 PHOT（凤凰群岛时间）（Tom Lane）§ 此缩写在默认列表中的存在可能导致在最新的 Debian 和 Ubuntu 发行版上出现失败，因为它们不再默认安装底层的 tzdb 条目。由于这是一个为总人口约二十几人的区域编造的缩写，不太可能有人会需要它。如果确有需要，可以通过自定义缩写文件将其恢复。","title":"从默认时区缩写列表中移除 PHOT（凤凰群岛时间）","variants":[],"version":"16.1"}],"entry_count":59,"eol":"2028-11-09","eol_date":"2028-11-09","label":"16.1","major":"16","manual":"16","manual_build":"16.15","manual_url":"/docs/16/release-16-1.html","migration_html":"\u003cp\u003e对于运行 16.X 的用户，不需要执行导出/恢复。\u003c/p\u003e\n\u003cp\u003e但是，已发现若干错误可能导致特定类型的索引产生错误的搜索结果或不必要的低效。建议在安装此更新后对可能受影响的索引执行 \u003ccode\u003eREINDEX\u003c/code\u003e。请参阅下面的第四到第七条变更日志条目。\u003c/p\u003e","minor":1,"placeholder":false,"source_as_of":"","source_url":"/docs/release/16.1/","status":"stable","status_label":"Supported","support_days":760,"supported":true,"version":"16.1"}],"mode":"release","release_count":1,"remaining_cves":[],"security_as_of":"2026-09-26","security_regressions":[],"source_as_of":"2026-09-26","stats":[{"count":59,"key":"all","label":"All changes"},{"count":0,"key":"feature","label":"Features"},{"count":28,"key":"bugfix","label":"Bug fixes"},{"count":3,"key":"security","label":"Security"},{"count":0,"key":"performance","label":"Performance"},{"count":0,"key":"compatibility","label":"Compatibility"},{"count":28,"key":"improvement","label":"Improvements"}],"to_release":{"age_days":1067,"build":"16.1","changes_count":59,"compatibility_count":0,"content_hash":"62c73002569d60f9b018256836ce4baa47367fb23cff88dbe0286ed92bbe8494","date":"2023-11-09","date_text":"2023-11-09","doc_git":"","doc_loaded_at":"2026-09-26T02:56:37.084400","entry_count":59,"eol":"2028-11-09","eol_date":"2028-11-09","label":"16.1","major":"16","manual":"16","manual_build":"16.15","manual_url":"/docs/16/release-16-1.html","migration_html":"\u003cp\u003e对于运行 16.X 的用户，不需要执行导出/恢复。\u003c/p\u003e\n\u003cp\u003e但是，已发现若干错误可能导致特定类型的索引产生错误的搜索结果或不必要的低效。建议在安装此更新后对可能受影响的索引执行 \u003ccode\u003eREINDEX\u003c/code\u003e。请参阅下面的第四到第七条变更日志条目。\u003c/p\u003e","minor":1,"placeholder":false,"source_as_of":"","source_url":"/docs/release/16.1/","status":"stable","status_label":"Supported","support_days":760,"supported":true,"version":"16.1"},"total":59,"warnings":[]}