Re: idea: log_statement_sample_rate - bottom limit for sampling

From: Adrien Nayrat <adrien(dot)nayrat(at)anayrat(dot)info>
To: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: idea: log_statement_sample_rate - bottom limit for sampling
Date: 2019-11-06 19:00:57
Message-ID: 3d67278c-3e8f-6ef4-4950-eb5e7a4411de@anayrat.info
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/6/19 7:21 PM, Tomas Vondra wrote:
> I've pushed the reworked version of log_statement_sample_rate patch [1].
> If I understand correctly, that makes this patch unnecessary, and we
> should mark it as rejected. Or do we still need it?

Yes, the goal of this patch was to disable sampling and log all queries whose
duration exceed log_statement_sample_limit.

For now it is possible just with log_min_duration_statement which log all
queries whose duration exceed it.

--
Adrien

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2019-11-06 19:22:55 Re: idea: log_statement_sample_rate - bottom limit for sampling
Previous Message Bruce Momjian 2019-11-06 18:59:35 Re: Does 'instead of delete' trigger support modification of OLD