| Type: | bool |
| Default: | off |
| Context: | superuser |
| Restart: | false |
Causes the duration of every completed statement to be logged. The default is off. Only superusers can change this setting.
For clients using extended query protocol, durations of the Parse, Bind, and Execute steps are logged independently.
The difference between enabling log_duration and setting log_min_duration_statement to zero is that exceeding log_min_duration_statement forces the text of the query to be logged, but this option doesn't. Thus, if log_duration is on and log_min_duration_statement has a positive value, all durations are logged but the query text is included only for statements exceeding the threshold. This behavior can be useful for gathering statistics in high-load installations.
Recommendations
Useful for performance analysis.
On StackOverflow
- Impact of log_duration in PostgreSQL performance
- Windows tool to analyze PostgreSQL log files
- Postgres not logging all queries, despite logging the duration
- filebeat Grok for postgres log file not work
- Duration logged but not the statement -- postgresql. Are there any specific queries for this behavior?
On pgsql-hackers
- Re: Problems around compute_query_id
- Re: Asynchronous and "direct" IO support for PostgreSQL.
- RE: [PATCH] New default role allowing to change per-role/database settings
- Re: Delegating superuser tasks to new security roles (Was: Granting control of SUSET gucs to non-superusers)
- Problems around compute_query_id