Revert "Add log_statement_sample_rate parameter"
authorTomas Vondra
Sun, 4 Aug 2019 18:29:00 +0000 (20:29 +0200)
committerTomas Vondra
Sun, 4 Aug 2019 21:37:44 +0000 (23:37 +0200)
commitd5f53a8e26caf7931db6ad3939cd34d36ea54d91
tree6854c50fd5af3639ae2d88101c069fe84896778e
parentd8453ccfbfd6bb1782e71beb28acf4025a9a01ce
Revert "Add log_statement_sample_rate parameter"

This reverts commit 88bdbd3f746049834ae3cc972e6e650586ec3c9d.

As committed, statement sampling used the existing duration threshold
(log_min_duration_statement) when decide which statements to sample.
The issue is that even the longest statements are subject to sampling,
and so may not end up logged. An improvement was proposed, introducing
a second duration threshold, but it would not be backwards compatible.
So we've decided to revert this feature - the separate threshold should
be part of the feature itself.

Discussion: https://postgr.es/m/CAFj8pRDS8tQ3Wviw9%3DAvODyUciPSrGeMhJi_WPE%2BEB8%2B4gLL-Q%40mail.gmail.com
doc/src/sgml/config.sgml
src/backend/tcop/postgres.c
src/backend/utils/misc/guc.c
src/backend/utils/misc/postgresql.conf.sample
src/include/utils/guc.h