Re: Problems around compute_query_id - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: Problems around compute_query_id
Date
Msg-id 20210412084324.gv2csxjdnswp7tfv@nol
Whole thread Raw
In response to Re: Problems around compute_query_id  (Julien Rouhaud <rjuju123@gmail.com>)
List pgsql-hackers
On Mon, Apr 12, 2021 at 03:26:33PM +0800, Julien Rouhaud wrote:
> On Mon, Apr 12, 2021 at 09:20:07AM +0200, Michael Banck wrote:
> > 
> > What about log_statement_sample_rate ? Does compute_query_id have the
> > same problem with that?
> 
> No, log_statement_sample_rate samples log_min_duration_statements, not
> log_statements so it works as expected.

While on that topic, it's probably worth mentioning that log_duration is now
way more useful if you have the queryid in you log_line_prefix.  It avoids to
log the full query text while still being able to know what was the underlying
normalized query by dumping the content of pg_stat_statements.



pgsql-hackers by date:

Previous
From: Virender Singla
Date:
Subject: vacuum freeze - possible improvements
Next
From: Amit Kapila
Date:
Subject: Re: Replication slot stats misgivings