Re: Add parameter jit_warn_above_fraction

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, David Rowley <dgrowleyml(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add parameter jit_warn_above_fraction
Date: 2022-04-09 16:43:08
Message-ID: YlG3nLH2jFHnJmEx@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Sat, Apr 09, 2022 at 12:31:23PM -0400, Tom Lane wrote:
> Julien Rouhaud <rjuju123(at)gmail(dot)com> writes:
> > On Sat, Apr 09, 2022 at 10:42:12AM -0400, Tom Lane wrote:
> >> Also, good luck with "looking in the logs", because by default
> >> WARNING-level messages don't go to the postmaster log.
> > I must be missing something because by default log_min_messages is WARNING, and
> > AFAICS I do get WARNING-level messages in some vanilla cluster logs, using
> > vanilla .psqlrc.
> Ah, sorry, I was looking at the wrong thing namely
> log_min_error_statement. The point still holds though: if we emit this
> at level WARNING, what will get logged is just the bare message and not
> the statement that triggered it. How useful do you think that will be?

Ah right, I did miss that "small detail". And of course I agree, as-is that
would be entirely useless and it should be LOG, like the rest of similar

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message David G. Johnston 2022-04-09 16:49:57 Re: How about a psql backslash command to show GUCs?
Previous Message Andrew Dunstan 2022-04-09 16:34:40 Re: Mingw task for Cirrus CI