Re: New GUC to sample log queries

Adrien NAYRAT <adrien.nayrat@anayrat.info>

From: Adrien Nayrat <adrien.nayrat@anayrat.info>

To: Robert Haas <robertmhaas@gmail.com>, Vik Fearing <vik.fearing@2ndquadrant.com>

Cc: Michael Paquier <michael@paquier.xyz>, David Rowley <david.rowley@2ndquadrant.com>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>

Date: 2018-07-16T20:19:11Z

Lists: pgsql-hackers

On 07/16/2018 05:24 PM, Robert Haas wrote:
> On Sun, Jul 15, 2018 at 6:53 AM, Vik Fearing
> <vik.fearing@2ndquadrant.com> wrote:
>> Hmm.  Not sure if that last word should be _sample, _sampling, _rate, or
>> a combination of those.
> 
> +1 for rate or sample_rate.  I think "sample" or "sampling" without
> "rate" will not be very clear.
> 

Thanks,

After reading this mail :
https://www.postgresql.org/message-id/20180710183828.GB3890%40telsasoft.com

I wonder if this GUC could be used for theses logging method?
log_statement_stats
log_parser_stats
log_planner_stats
log_executor_stats



-- 
Adrien

Commits

Use pg_strong_random() to select each server process's random seed.
- 4203842a1cd0 12.0 landed
Use a separate random seed for SQL random()/setseed() functions.
- 6645ad6bdd81 12.0 landed
Marginal performance hacking in erand48.c.
- 6b9bba2df8d4 12.0 landed
Fix latent problem with pg_jrand48().
- e09046641114 12.0 landed
- f256995e33d2 10.7 landed
- d58e01f8abe2 11.2 landed
Silence compiler warning
- 9dc122585551 12.0 landed
Add log_statement_sample_rate parameter
- 88bdbd3f7460 12.0 landed