Sets the fraction of transactions whose statements are all logged, in addition to statements logged for other reasons. It applies to each new transaction regardless of its statements' durations. Sampling is stochastic, for example
0.1 means there is statistically one chance in ten that any given transaction will be logged.
log_transaction_sample_rate can be helpful to construct a sample of transactions. The default is
0, meaning not to log statements from any additional transactions. Setting this to
1 logs all statements of all transactions. Only superusers can change this setting.
Like all statement-logging options, this option can add significant overhead.
- Java Hibernate insert hypertable in timescaledb is very slow
- Why does "explain analyzing" this query fnish fast (showing a parallel plan), while running the actual query without "explain analyze" doesn't?
- PostgreSQL 13 sometimes works but sometimes huge execution time
- Error: self signed certificate when doing a migration to production