{"Entry":{"collection":"guc","key":"jit_dump_bitcode","name":"jit_dump_bitcode","aliases":[],"metadata":{"baseline":false,"boot_human":"Not specified","boot_val":null,"category":"Developer Options","category_zh":"","changed_in":[],"changes":[{"documentation_changed":false,"fields":{},"from":"10","status":"added","to":"11"},{"documentation_changed":true,"fields":{},"from":"14","status":"changed","to":"15"}],"content_hash":"c0baaa1dff3b82e9f7c0b648c79f9e1d5e07de07dc34169e9e400732f24d6042","context":"","default_changed_in":[],"default_history":[{"from":"11","to":"19","value":"off"}],"derived_content_hash":"94876cec766a583a3e046b05d232ce5f77c6159b3d6d27620f09e4ac64704824","documentation_refresh":{"batch":"20261113","original_source_rev":"wiki-repair-20261023:dbce02ff73b8590b8ad60b3794a863d73e2b5922fc880fecdba56bd609ead509","versions":{"14":"14.25","15":"15.20","16":"16.16","17":"17.12","18":"18.7","19":"19rc2"}},"editorial":{"advice":{"olap":"Long analytical runs can amplify jit_dump_bitcode's debug overhead and artifacts. Prefer standard EXPLAIN and statistics first, and isolate any developer experiment from normal users.","oltp":"Do not tune production OLTP with jit_dump_bitcode. Enable it only for a bounded reproduction with an owner, log/disk budget, rollback condition, and evidence-capture plan; restore the default immediately afterward.","small":"Keep jit_dump_bitcode at its upstream default. A small host has less spare CPU, disk, connection, and log capacity for developer instrumentation."},"mechanism":["jit_dump_bitcode writes generated LLVM IR/bitcode files inside data_directory for queries that actually run JIT. It exists to inspect and reproduce JIT compiler behavior.","It does not activate JIT and produces nothing when no query crosses the JIT gates. Generated artifacts can accumulate, consume disk, and contain details derived from executed expressions.","Only a tightly controlled debugging session should enable it; files require explicit collection and cleanup. Its superuser context permits an authorized session change without a server restart."],"pitfalls":["Leaving jit_dump_bitcode enabled after the bounded diagnostic or recovery task.","Running the experiment on the only copy of production data.","Underestimating log, core-file, temporary-file, WAL, CPU, or connection-slot amplification.","Treating a server that merely starts or completes a query as proof that data and behavior are correct."],"references":[{"title":"PostgreSQL 19 Beta 4: jit_dump_bitcode","url":"https://www.postgresql.org/docs/19/runtime-config-developer.html#GUC-JIT-DUMP-BITCODE"},{"title":"PostgreSQL 19 release notes","url":"https://www.postgresql.org/docs/19/release-19.html"}],"related":["jit","jit_above_cost","jit_debugging_support","jit_profiling_support","data_directory"],"summary":"jit_dump_bitcode — Write out LLVM bitcode to facilitate JIT debugging. Observed in PG11–19 Beta 4; its last measured boot default is off in PG19 Beta 4, with superuser context. This is a beta-snapshot fact and can change before PostgreSQL 19 GA."},"enumvals":[],"first_version":"11","group":"Developer Options","group_slug":"developer","imported_at":"2026-09-27T17:57:31.42918+08:00","intro_commit":{"authored_at":"2018-03-22T11:05:22-07:00","discussion":["https://postgr.es/m/20170901064131.tazjxwus3k2w3ybh@alap3.anarazel.de"],"hash":"b96d550eb03cfdb000def70912ec840dbe7f67da","subject":"Support for optimizing and emitting code in LLVM JIT provider.","url":"https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b96d550eb03cfdb000def70912ec840dbe7f67da"},"key":"jit_dump_bitcode","last_version":"20","max_val":"","min_val":"","name":"jit_dump_bitcode","position":193,"present_in":["11","12","13","14","15","16","17","18","19","20"],"repair_provenance":{"original_source_revision":"english-manuals:b64c5a5bb5201adc4a6df5f7e46b65b5f002f939fdb8da6fa9250d722f8552aa","receipt_sha256":"2147f35563d0fee5b60f371fab4a169da3fbdf0f940266b3caaf59fc603621c2","repair":"wiki-repair-20261023"},"short_desc":"Writes the generated LLVM IR out to the file system, inside data_directory.","short_desc_zh":"","source_rev":"wiki-repair-20261023:dbce02ff73b8590b8ad60b3794a863d73e2b5922fc880fecdba56bd609ead509","unit":"","vartype":"bool"}},"Definition":{"Collection":"guc","Key":"jit_dump_bitcode","SourceDatabase":"center","Version":"18","SourceTable":"guc","SourceKey":"jit_dump_bitcode","SourceRevision":"wiki-repair-20261023:dbce02ff73b8590b8ad60b3794a863d73e2b5922fc880fecdba56bd609ead509","Facts":{"boot_val":"off","category":"Developer Options","context":"superuser","description":"Writes the generated LLVM IR out to the file system, inside data_directory. This is only useful for working on the internals of the JIT implementation. The default setting is off. Only superusers and users with the appropriate SET privilege can change this setting.","description_zh":"将生成的 LLVM IR 写入文件系统，位于 data_directory 内。这仅对开发 JIT 的内部实现有用。默认设置为 off。只有超级用户和具有适当 SET 权限的用户才能更改此设置。","description_zh_html":"\u003cp\u003e\n        将生成的 \u003cspan class=\"productname\"\u003eLLVM\u003c/span\u003e IR 写入文件系统，位于 \u003ca class=\"xref\" href=\"/zh/docs/18/runtime-config-file-locations.html#GUC-DATA-DIRECTORY\"\u003edata_directory\u003c/a\u003e 内。这仅对开发 JIT 的内部实现有用。默认设置为 \u003ccode class=\"literal\"\u003eoff\u003c/code\u003e。只有超级用户和具有适当 \u003ccode class=\"literal\"\u003eSET\u003c/code\u003e 权限的用户才能更改此设置。\n       \u003c/p\u003e","doc":{"anchor":"GUC-JIT-DUMP-BITCODE","file":"runtime-config-developer.html","lang":"en","sha256":"a3f6a107ed6ba4edaf6df03e52f4a469bd09350d545e4ff419e62844025ec1cf","slug":"18"},"doc_html":"\u003cp\u003e\n        Writes the generated \u003cspan class=\"productname\"\u003eLLVM\u003c/span\u003e IR out to the\n        file system, inside \u003ca class=\"xref\" href=\"/docs/18/runtime-config-file-locations.html#GUC-DATA-DIRECTORY\"\u003edata_directory\u003c/a\u003e. This is only\n        useful for working on the internals of the JIT implementation.\n        The default setting is \u003ccode class=\"literal\"\u003eoff\u003c/code\u003e.\n        Only superusers and users with the appropriate \u003ccode class=\"literal\"\u003eSET\u003c/code\u003e\n        privilege can change this setting.\n       \u003c/p\u003e","doc_same_as":"","documentation_revision":{"inputs":[{"file":"runtime-config-developer.html","kind":"same-version-reviewed-manual","locale":"en","sha256":"a3f6a107ed6ba4edaf6df03e52f4a469bd09350d545e4ff419e62844025ec1cf","version":"18.7"},{"file":"runtime-config-developer.html","kind":"same-version-reviewed-manual","locale":"zh-Hans","sha256":"e7e22aa5738a1d376b84af1adca796c5e14746266733f925eb50c3ef86a50655","version":"18.7"}],"release":"18.7","runtime_remeasured":false,"source_revision":"pgdoc:b9f0e7232f60f380d642ac9b99226606c254b552"},"documented":true,"enumvals":null,"extra_desc":null,"lang":"en","max_val":null,"metadata_version":"18","min_val":null,"name":"jit_dump_bitcode","short_desc":"Write out LLVM bitcode to facilitate JIT debugging.","source":"pg-settings-source-snapshot","translation_provenance":{"inputs":[{"kind":"current-pgdoc-translation","path":"/Users/vonng/pgsty/pgdoc/zh/18/html/runtime-config-developer.html","sha256":"3c08bf624188bbb0733dc7854e61c0c251c2578311ac3dc8fa626ab21b7911d1"}],"kind":"same-version-pgdoc","locale":"zh-Hans","source_revision":"b1b500221dbe5437cfca004d6b04d3f6e422765d","version":"18"},"unit":null,"vartype":"bool","zh_from":"same-version-manual"},"ManualEvidence":{"doc":{"anchor":"GUC-JIT-DUMP-BITCODE","file":"runtime-config-developer.html","lang":"en","sha256":"a3f6a107ed6ba4edaf6df03e52f4a469bd09350d545e4ff419e62844025ec1cf","slug":"18"}},"MeasuredEvidence":{"metadata_version":"18"}},"Text":{"Collection":"guc","Key":"jit_dump_bitcode","SourceDatabase":"center","Version":"18","Locale":"en","Title":"jit_dump_bitcode","Summary":"Writes the generated LLVM IR out to the file system, inside data_directory. This is only useful for working on the internals of the JIT implementation. The default setting is off. Only superusers and users with the appropriate SET privilege can change this setting.","BodyHTML":"\u003cp\u003e\n        Writes the generated \u003cspan\u003eLLVM\u003c/span\u003e IR out to the\n        file system, inside \u003ca href=\"/docs/18/runtime-config-file-locations.html#GUC-DATA-DIRECTORY\" rel=\"nofollow\"\u003edata_directory\u003c/a\u003e. This is only\n        useful for working on the internals of the JIT implementation.\n        The default setting is \u003ccode\u003eoff\u003c/code\u003e.\n        Only superusers and users with the appropriate \u003ccode\u003eSET\u003c/code\u003e\n        privilege can change this setting.\n       \u003c/p\u003e","SourceRevision":"wiki-repair-20261023:dbce02ff73b8590b8ad60b3794a863d73e2b5922fc880fecdba56bd609ead509","ContentHash":"bf758f01610ec29b25b2b0b8dd82e9ceeb984900750b48aa8578b390fc7b8de2","Payload":{"description":"Writes the generated LLVM IR out to the file system, inside data_directory. This is only useful for working on the internals of the JIT implementation. The default setting is off. Only superusers and users with the appropriate SET privilege can change this setting."}},"RequestedLocale":"en","Fallback":false,"Versions":["11","12","13","14","15","16","17","18","19","20"],"Locales":["en","zh-Hans"],"Signatures":null,"Spellings":null,"SQLState":null,"Evidence":null}