| From: | Gilles Darold <gilles(at)darold(dot)net> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: idea: log_statement_sample_rate - bottom limit for sampling |
| Date: | 2019-06-06 08:48:28 |
| Message-ID: | 98149a08-4aa9-466d-672b-62a378715efb@darold.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Le 06/06/2019 à 10:38, Pavel Stehule a écrit :
> Hi
>
> I like the idea of sampling slow statements via
> log_statement_sample_rate. But I miss some parameter that can ensure
> so every query executed over this limit is logged.
>
> Can we introduce new option
>
> log_statement_sampling_limit
>
> The query with execution time over this limit is logged every time.
>
> What do you think about this?
>
> Regards
>
> Pavel
+1, log_min_duration_statement is modulated by log_statement_sample_rate
that mean that there is no more way to log all statements over a certain
duration limit. log_statement_sampling_limit might probably always be
upper than log_min_duration_statement.
--
Gilles Darold
http://www.darold.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Etsuro Fujita | 2019-06-06 08:58:00 | Re: postgres_fdw: oddity in costing presorted foreign scans with local stats |
| Previous Message | Pavel Stehule | 2019-06-06 08:38:04 | idea: log_statement_sample_rate - bottom limit for sampling |