Re: New GUC to sample log queries - Mailing list pgsql-hackers

From Dmitry Dolgov
Subject Re: New GUC to sample log queries
Date
Msg-id CA+q6zcVQsqB5thfW9LsJpJ0mWvardiJWBKdvyAdbVFXGxqCxPg@mail.gmail.com
Whole thread Raw
In response to Re: New GUC to sample log queries  (Adrien Nayrat <adrien.nayrat@anayrat.info>)
Responses Re: New GUC to sample log queries
List pgsql-hackers
> On Sun, 18 Nov 2018 at 10:52, Adrien Nayrat <adrien.nayrat@anayrat.info>
> wrote:
>
> For me, the question is how to name this GUC? Is "log_sample_rate" is enough?
> I am not sure because it is only related to queries logged by
> log_min_duration_statements.

Since it's hard to come up with a concise name that will mention sampling rate
in the context of min_duration_statement, I think it's fine to name this
configuration "log_sample_rate", as long as it's dependency from
log_min_duration_statements is clearly explained in the documentation.


pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: [HACKERS] pgbench - allow to store select results intovariables
Next
From: Shay Rojansky
Date:
Subject: [PATCH] Allow UNLISTEN during recovery