Re: Add pg_stat_autovacuum_priority - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: Add pg_stat_autovacuum_priority
Date
Msg-id adbGfTMw8BiHDMnM@nathan
Whole thread Raw
In response to Re: Add pg_stat_autovacuum_priority  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Add pg_stat_autovacuum_priority
List pgsql-hackers
On Wed, Apr 08, 2026 at 03:21:38PM -0400, Tom Lane wrote:
> Nathan Bossart <nathandbossart@gmail.com> writes:
>> FWIW that elog() shouldn't be emitting anything from the view, unless
>> something is broken.
> 
> [ looks again... ]  Oh, you mean because pg_stat_get_autovacuum_scores
> passes 0 for elevel instead of any of the valid elevel constants.
> Can you say "undocumented cowboy hack"?  I'd be happier if we added
> something like "#define LOG_NEVER 0  /* Never emit this message */"
> to elog.h and used that.

Yeah... I should've done that originally.  Here's a patch that I'll apply
in the next day or so, barring objections.

-- 
nathan

Attachment

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: s/pg_attribute_always_inline/pg_always_inline/?
Next
From: Nathan Bossart
Date:
Subject: Re: Add pg_stat_autovacuum_priority