If LLVM has the required functionality, register generated functions with GDB.
At a glance
| Property | Value |
|---|---|
| Parameter | jit_debugging_support |
| 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
If LLVM has the required functionality, register generated functions with GDB. This makes debugging easier. The default setting is off. Only superusers and users with the appropriate SET privilege can change this parameter at session start, and it cannot be changed at all within a session.
(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_debugging_support; or SELECT name, setting, unit, context, source FROM pg_settings WHERE name = 'jit_debugging_support';.
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.