DB Internals AtlasPostgreSQL 18.6 Home About

Parameter · Developer Options

jit_debugging_support

Register JIT-compiled functions with debugger.

  • Default: off
  • Type: bool
  • Applies: New connections (superuser)

In plain words

JIT-compiled code is generated at run time, so a debugger normally sees it as anonymous memory. With this on, the LLVM JIT tells GDB about each generated function, so backtraces through JIT code show readable names.

For DBAs and operators

Only effective when PostgreSQL was built with LLVM support and the LLVM version provides the GDB JIT interface. It must be set before the session starts (superuser-backend context: in postgresql.conf or via PGOPTIONS="-c jit_debugging_support=on" by a superuser). There is a small cost for each compiled function. Useful together with core dumps when investigating crashes inside JIT code; otherwise the quickest workaround for a suspected JIT bug is jit = off.

Developer option: meant for debugging and testing PostgreSQL itself. Leave it at the default on production servers unless a specific diagnosis calls for it.

How to change it

Applies at connection start; superusers can also pass it as a connection option.

See it in context

JIT compilation

Related parameters

jit_profiling_support jit_dump_bitcode jit

All Developer Options parameters