Re: Add parameter jit_warn_above_fraction - Mailing list pgsql-hackers

From Julien Rouhaud
Subject Re: Add parameter jit_warn_above_fraction
Date
Msg-id YlG3nLH2jFHnJmEx@jrouhaud
Whole thread Raw
In response to Re: Add parameter jit_warn_above_fraction  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Add parameter jit_warn_above_fraction  (Ibrar Ahmed <ibrar.ahmad@gmail.com>)
List pgsql-hackers
On Sat, Apr 09, 2022 at 12:31:23PM -0400, Tom Lane wrote:
> Julien Rouhaud <rjuju123@gmail.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
features.



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Mingw task for Cirrus CI
Next
From: "David G. Johnston"
Date:
Subject: Re: How about a psql backslash command to show GUCs?