select open change scope Open full search

PG.CENTER connects PostgreSQL documentation, reference, and ecosystem knowledge. Maintained by Pigsty.

CONFIGURATION / REPORTING AND LOGGING

update_process_title

Read PG 18 manual ↗

Enables updating of the process title every time a new SQL command is received by the server.

Type
bool
Context
superuser
Measured default
on
Unit
Metadata snapshot
18

Definition PG 18 manual

Enables updating of the process title every time a new SQL command is received by the server. This setting defaults to on on most platforms, but it defaults to off on Windows due to that platform's larger overhead for updating the process title. Only superusers and users with the appropriate SET privilege can change this setting.

Measured default history
Version intervalDefault
9.0 – 19on
Analysis & operational context

Authored guidance from the GUC source snapshot; the version-specific manual above is the definition reference. View source ↗

How it works

update_process_title updates the process title to show the active SQL command. Enables updating of the process title every time a new SQL command is received by the server. When supported by the operating system, PostgreSQL rewrites each backend's process title as commands change, making current activity visible to tools such as ps.

update_process_title is a SUPERUSER-context setting. Superuser or a role granted the appropriate SET privilege can change it for a session, while ALTER ROLE or ALTER DATABASE can establish a default for future sessions.

Process titles complement application_name, cluster_name, pg_stat_activity, and log_line_prefix, allowing operating-system observations to be joined with database activity.

Operational considerations

Changing update_process_title in one session and assuming role defaults, database defaults, or other pooled sessions changed with it.

Putting secrets or unbounded high-cardinality data into operator-visible process labels.

Using inconsistent cluster, application, and process labels that cannot be joined across monitoring systems.

Changing update_process_title globally without a rollback plan and a client or operational compatibility test.

Workload guidance

OLAP: Preserve update_process_title so long jobs can be attributed from operating-system and PostgreSQL views; use application_name for finer job identity.

OLTP: Keep update_process_title enabled or populated for operator clarity unless profiling proves material overhead. Use stable, non-secret labels that match monitoring inventory.

SMALL: Do not tune update_process_title for capacity. Its observability value normally outweighs negligible overhead, but avoid high-cardinality or sensitive labels.

Version history 4
  1. PG 14 → 15changed
  2. PG 13 → 14changed
  3. PG 9.5 → 9.6changed
  4. PG 9.4 → 9.5changed

Related entries

Further reading

Definition snapshot: english-manuals:cb025050f1bbcd2fb996f77f176… · English manual source