Re: compute_query_id and pg_stat_statements

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: compute_query_id and pg_stat_statements
Date: 2021-04-25 16:17:42
Message-ID: 20210425161742.jczixbwvojlsf2wx@nol
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Sun, Apr 25, 2021 at 11:39:55AM -0400, Tom Lane wrote:
> I agree repeated warnings would be bad news. I was wondering if we could
> arrange a single warning at the time pg_stat_statements is preloaded into
> the postmaster. In this way, if you tried to use a configuration file
> that used to work, you'd hopefully get some notice about why it no longer
> does what you want. Also, if you are preloading pg_stat_statements, it
> seems reasonable to assume that you'd like the global value of the flag
> to be "on", even if there are use-cases for transiently disabling it.

What about people who wants to use pg_stat_statements but are not ok with our
query_id heuristics and use a third-party plugin for that?

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Yura Sokolov 2021-04-25 17:03:11 Re: Use simplehash.h instead of dynahash in SMgr
Previous Message Tom Lane 2021-04-25 15:39:55 Re: compute_query_id and pg_stat_statements