diff options
| author | Tomas Vondra <tomas.vondra@postgresql.org> | 2019-08-04 20:29:00 +0200 |
|---|---|---|
| committer | Tomas Vondra <tomas.vondra@postgresql.org> | 2019-08-04 23:38:27 +0200 |
| commit | 75506195da81d75597a4025b72f8367e6c45f60d (patch) | |
| tree | 55d6df111735a0710ce13d2b831deb3f1e83d728 /src/backend/access/gist/gistget.c | |
| parent | 4f9ed8f3c5ef0034c98dd34549f85d8c72aab9ad (diff) | |
| download | postgresql-75506195da81d75597a4025b72f8367e6c45f60d.tar.gz | |
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 'src/backend/access/gist/gistget.c')
0 files changed, 0 insertions, 0 deletions