{"format": 1, "mode": "release", "from_release": null, "to_release": {"date": "2015-06-12", "build": "9.1.18", "major": "9.1", "minor": 18, "manual": "9.1", "status": "stable", "doc_git": "", "version": "9.1.18", "eol_date": "2016-10-27", "date_text": "2015-06-12", "supported": false, "manual_url": "/docs/9.1/release-9-1-18.html", "source_url": "/docs/release/9.1.18/", "entry_count": 2, "placeholder": false, "content_hash": "09e1d5ebee6cb62a0501251abc5b76a2de66df89b733e13dd8faf47401b17d50", "manual_build": "9.1.24", "source_as_of": "", "changes_count": 2, "doc_loaded_at": "2026-09-26T02:56:47.783417", "migration_html": "<p>对于运行 9.1.X 的用户，不需要进行转储/恢复。</p>\n<p>不过，如果你是从早于 9.1.16 的版本升级，请参见<a href=\"/docs/9.1/release-9-1-16.html\" title=\"E.9. 版本 9.1.16\">第 E.9 节</a>。</p>", "compatibility_count": 0, "label": "9.1.18", "status_label": "历史版本", "eol": "2016-10-27", "age_days": 4128, "support_days": -3625}, "groups": [{"date": "2015-06-12", "build": "9.1.18", "major": "9.1", "minor": 18, "manual": "9.1", "status": "stable", "doc_git": "", "version": "9.1.18", "eol_date": "2016-10-27", "date_text": "2015-06-12", "supported": false, "manual_url": "/docs/9.1/release-9-1-18.html", "source_url": "/docs/release/9.1.18/", "entry_count": 2, "placeholder": false, "content_hash": "09e1d5ebee6cb62a0501251abc5b76a2de66df89b733e13dd8faf47401b17d50", "manual_build": "9.1.24", "source_as_of": "", "changes_count": 2, "doc_loaded_at": "2026-09-26T02:56:47.783417", "migration_html": "<p>对于运行 9.1.X 的用户，不需要进行转储/恢复。</p>\n<p>不过，如果你是从早于 9.1.16 的版本升级，请参见<a href=\"/docs/9.1/release-9-1-16.html\" title=\"E.9. 版本 9.1.16\">第 E.9 节</a>。</p>", "compatibility_count": 0, "label": "9.1.18", "status_label": "历史版本", "eol": "2016-10-27", "age_days": 4128, "support_days": -3625, "entries": [{"id": "9.1.18-2138cf0f137fffce", "cves": [], "html": "<p>修复罕见的未能使关系缓存 init 文件失效的问题（Tom Lane）</p>\n<p>在并发活动时序恰好不对的情况下，对系统目录执行<code>VACUUM FULL</code>可能无法更新用于避免新会话缓存加载工作的<span>“<span>init 文件</span>”</span>。这将导致后续会话完全无法访问该目录。这是一个非常古老的缺陷，但它极难触发，直到最近才出现可复现的案例。</p>", "text": "修复罕见的未能使关系缓存 init 文件失效的问题（Tom Lane） 在并发活动时序恰好不对的情况下，对系统目录执行VACUUM FULL可能无法更新用于避免新会话缓存加载工作的“init 文件”。这将导致后续会话完全无法访问该目录。这是一个非常古老的缺陷，但它极难触发，直到最近才出现可复现的案例。", "title": "修复罕见的未能使关系缓存 init 文件失效的问题", "commits": [], "section": "变更", "category": "bugfix", "source_url": "/docs/release/9.1.18/#id-1.11.6.11.5", "source_hash": "6bec1b27e4a7c93b00f27640abe8cfeea45f0bff3dcdb265af25580efcb2a989", "section_path": ["变更"], "commit_groups": [], "identity_text": "Fix rare failure to invalidate relation cache init file (Tom Lane) With just the wrong timing of concurrent activity, a VACUUM FULL on a system catalog might fail to update the init file that's used to avoid cache-loading work for new sessions. This would result in later sessions being unable to access that catalog at all. This is a very ancient bug, but it's so hard to trigger that no reproducible case had been seen until recently.", "commit_aliases": [], "source_commits": [], "source_entry_id": "9.1.18/changes/001", "db_id": "421f0e5f53c1b534c1a5d7e5c3ddaeb1", "patch_ids": [], "statement_hash": "cbd29ab3677162dd8eee0c8fdae7218663c03b789800db751346403cb4a7e91d", "relations": [{"rule": 2, "type": "equivalent", "target": "56559e80e5e318ceb4a1514c01179a96", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "cbd29ab3677162dd8eee0c8fdae7218663c03b789800db751346403cb4a7e91d"}}, {"rule": 2, "type": "equivalent", "target": "62f6eb8f9354ed2084e2a04aba92b9a4", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "cbd29ab3677162dd8eee0c8fdae7218663c03b789800db751346403cb4a7e91d"}}, {"rule": 2, "type": "equivalent", "target": "d00ab3b80fd0fe3a84d1b02a94bfcd79", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "cbd29ab3677162dd8eee0c8fdae7218663c03b789800db751346403cb4a7e91d"}}, {"rule": 2, "type": "equivalent", "target": "e08881035a5c62a2921de58daddb199c", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "cbd29ab3677162dd8eee0c8fdae7218663c03b789800db751346403cb4a7e91d"}}], "version": "9.1.18", "category_label": "BUG 修复", "also_in": [], "variants": [], "related_changes": [{"db_id": "e08881035a5c62a2921de58daddb199c", "kind": "equivalent", "version": "9.4.4", "label": "9.4.4", "title": "修复罕见的未能使关系缓存 init 文件失效的问题", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "cbd29ab3677162dd8eee0c8fdae7218663c03b789800db751346403cb4a7e91d"}, "url": "/docs/compare/?release=9.4.4#9.4.4-2138cf0f137fffce", "source_url": "/docs/release/9.4.4/#id-1.11.6.27.5"}, {"db_id": "d00ab3b80fd0fe3a84d1b02a94bfcd79", "kind": "equivalent", "version": "9.3.9", "label": "9.3.9", "title": "修复罕见的未能使关系缓存 init 文件失效的问题", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "cbd29ab3677162dd8eee0c8fdae7218663c03b789800db751346403cb4a7e91d"}, "url": "/docs/compare/?release=9.3.9#9.3.9-2138cf0f137fffce", "source_url": "/docs/release/9.3.9/#id-1.11.6.21.5"}, {"db_id": "62f6eb8f9354ed2084e2a04aba92b9a4", "kind": "equivalent", "version": "9.2.13", "label": "9.2.13", "title": "修复罕见的未能使关系缓存 init 文件失效的问题", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "cbd29ab3677162dd8eee0c8fdae7218663c03b789800db751346403cb4a7e91d"}, "url": "/docs/compare/?release=9.2.13#9.2.13-2138cf0f137fffce", "source_url": "/docs/release/9.2.13/#id-1.11.6.16.5"}, {"db_id": "56559e80e5e318ceb4a1514c01179a96", "kind": "equivalent", "version": "9.0.22", "label": "9.0.22", "title": "修复罕见的未能使关系缓存 init 文件失效的问题", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "cbd29ab3677162dd8eee0c8fdae7218663c03b789800db751346403cb4a7e91d"}, "url": "/docs/compare/?release=9.0.22#9.0.22-2138cf0f137fffce", "source_url": "/docs/release/9.0.22/#id-1.11.6.6.6"}]}, {"id": "9.1.18-bf7732cf950a1492", "cves": [], "html": "<p>避免传入会话与<code>CREATE/DROP DATABASE</code>之间的死锁（Tom Lane）</p>\n<p>在作为<code>DROP DATABASE</code>命令目标或<code>CREATE DATABASE</code>命令模板的数据库中启动的新会话，可能导致该命令等待五秒后失败，即使新会话本会在此之前退出。</p>", "text": "避免传入会话与CREATE/DROP DATABASE之间的死锁（Tom Lane） 在作为DROP DATABASE命令目标或CREATE DATABASE命令模板的数据库中启动的新会话，可能导致该命令等待五秒后失败，即使新会话本会在此之前退出。", "title": "避免传入会话与CREATE/DROP DATABASE之间的死锁", "commits": [], "section": "变更", "category": "bugfix", "source_url": "/docs/release/9.1.18/#id-1.11.6.11.5", "source_hash": "5955b77e7598b41a798cbf651d54231093f0a28da1857ce4d5be305b763ca703", "section_path": ["变更"], "commit_groups": [], "identity_text": "Avoid deadlock between incoming sessions and CREATE/DROP DATABASE (Tom Lane) A new session starting in a database that is the target of a DROP DATABASE command, or is the template for a CREATE DATABASE command, could cause the command to wait for five seconds and then fail, even if the new session would have exited before that.", "commit_aliases": [], "source_commits": [], "source_entry_id": "9.1.18/changes/002", "db_id": "7f208fa7a3abd0837b1466c4a8f65e61", "patch_ids": [], "statement_hash": "9cfac8d41ed5419bd18a7efcbaf8feb78254029ffd3c6f0dd8c9d0f63a21a496", "relations": [{"rule": 2, "type": "equivalent", "target": "29b698d5466f021dc8611d5d25ef7a31", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "9cfac8d41ed5419bd18a7efcbaf8feb78254029ffd3c6f0dd8c9d0f63a21a496"}}, {"rule": 2, "type": "equivalent", "target": "324abd755d98fe477c7962eab7502c58", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "9cfac8d41ed5419bd18a7efcbaf8feb78254029ffd3c6f0dd8c9d0f63a21a496"}}, {"rule": 2, "type": "equivalent", "target": "9bfc180a71dd7d167b27c33f605fed9e", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "9cfac8d41ed5419bd18a7efcbaf8feb78254029ffd3c6f0dd8c9d0f63a21a496"}}, {"rule": 2, "type": "equivalent", "target": "c17918b133f9aac5297f7d0675245278", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "9cfac8d41ed5419bd18a7efcbaf8feb78254029ffd3c6f0dd8c9d0f63a21a496"}}], "version": "9.1.18", "category_label": "BUG 修复", "also_in": [], "variants": [], "related_changes": [{"db_id": "c17918b133f9aac5297f7d0675245278", "kind": "equivalent", "version": "9.4.4", "label": "9.4.4", "title": "避免传入会话与CREATE/DROP DATABASE之间的死锁", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "9cfac8d41ed5419bd18a7efcbaf8feb78254029ffd3c6f0dd8c9d0f63a21a496"}, "url": "/docs/compare/?release=9.4.4#9.4.4-bf7732cf950a1492", "source_url": "/docs/release/9.4.4/#id-1.11.6.27.5"}, {"db_id": "324abd755d98fe477c7962eab7502c58", "kind": "equivalent", "version": "9.3.9", "label": "9.3.9", "title": "避免传入会话与CREATE/DROP DATABASE之间的死锁", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "9cfac8d41ed5419bd18a7efcbaf8feb78254029ffd3c6f0dd8c9d0f63a21a496"}, "url": "/docs/compare/?release=9.3.9#9.3.9-bf7732cf950a1492", "source_url": "/docs/release/9.3.9/#id-1.11.6.21.5"}, {"db_id": "29b698d5466f021dc8611d5d25ef7a31", "kind": "equivalent", "version": "9.2.13", "label": "9.2.13", "title": "避免传入会话与CREATE/DROP DATABASE之间的死锁", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "9cfac8d41ed5419bd18a7efcbaf8feb78254029ffd3c6f0dd8c9d0f63a21a496"}, "url": "/docs/compare/?release=9.2.13#9.2.13-bf7732cf950a1492", "source_url": "/docs/release/9.2.13/#id-1.11.6.16.5"}, {"db_id": "9bfc180a71dd7d167b27c33f605fed9e", "kind": "equivalent", "version": "9.0.22", "label": "9.0.22", "title": "避免传入会话与CREATE/DROP DATABASE之间的死锁", "evidence": {"same_day": true, "patch_ids": [], "statement_hash": "9cfac8d41ed5419bd18a7efcbaf8feb78254029ffd3c6f0dd8c9d0f63a21a496"}, "url": "/docs/compare/?release=9.0.22#9.0.22-bf7732cf950a1492", "source_url": "/docs/release/9.0.22/#id-1.11.6.6.6"}]}]}], "stats": [{"key": "all", "label": "全部变更", "count": 2}, {"key": "feature", "label": "新功能", "count": 0}, {"key": "bugfix", "label": "BUG 修复", "count": 2}, {"key": "security", "label": "安全相关", "count": 0}, {"key": "performance", "label": "性能改进", "count": 0}, {"key": "compatibility", "label": "兼容性变化", "count": 0}, {"key": "improvement", "label": "其他改进", "count": 0}], "total": 2, "release_count": 1, "cross_major": false, "cve_count": 0, "cves": [], "cve_available": true, "remaining_cves": [], "security_regressions": [], "warnings": [], "candidate_count": 2, "already_in_source_count": 0, "duplicate_count": 0, "excluded_count": 0, "exclusions": [], "source_as_of": "2026-09-26", "security_as_of": "2026-09-26"}