Configuration parameter

jit_dump_bitcode — PostgreSQL configuration parameter

Category Developer Options

Writes the generated LLVM IR out to the file system, inside data_directory.

At a glance

Property Value
Parameter jit_dump_bitcode
Category Developer Options
Default (see documentation)
Value type boolean (on/off)
Change scope Per-session (SET)
Available in PostgreSQL 12, 13, 14, 15, 16, 17, 18, 19 (added in 12)

What it does

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 quoted from the official PostgreSQL documentation.)

How to apply a change

Can be set per session with SET, per role/database with ALTER ROLE/DATABASE ... SET, or globally in postgresql.conf.

Inspect the current value and source with SHOW jit_dump_bitcode; or SELECT name, setting, unit, context, source FROM pg_settings WHERE name = 'jit_dump_bitcode';.

Tuning guidance

This is a developer and debugging aid, not a performance knob. Leave it at the default in production; enable it only temporarily, on a non-production or carefully controlled system, while diagnosing a specific problem. Several options in this group add overhead, generate large volumes of log output, or can damage data if misused — turn them off again as soon as the investigation is done.

Reference

PostgreSQL documentation — jit_dump_bitcode.

Keep going

Related & next steps

Was this helpful?

← All configuration parameters