aboutsummaryrefslogtreecommitdiff
path: root/contrib/intarray/_int_gist.c
diff options
context:
space:
mode:
authorTomas Vondra <tomas.vondra@postgresql.org>2019-08-04 20:29:00 +0200
committerTomas Vondra <tomas.vondra@postgresql.org>2019-08-04 23:37:44 +0200
commitd5f53a8e26caf7931db6ad3939cd34d36ea54d91 (patch)
tree6854c50fd5af3639ae2d88101c069fe84896778e /contrib/intarray/_int_gist.c
parentd8453ccfbfd6bb1782e71beb28acf4025a9a01ce (diff)
downloadpostgresql-d5f53a8e26caf7931db6ad3939cd34d36ea54d91.tar.gz
postgresql-d5f53a8e26caf7931db6ad3939cd34d36ea54d91.zip
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
Diffstat (limited to 'contrib/intarray/_int_gist.c')
0 files changed, 0 insertions, 0 deletions