Re: Reduce DEBUG level of catcache refreshing messages - Mailing list pgsql-hackers

From Fabrízio de Royes Mello
Subject Re: Reduce DEBUG level of catcache refreshing messages
Date
Msg-id CAFcNs+owQqemL3ttZ0tDLitpFQmSu+g6G8dWVUsfQNp0BW=_jg@mail.gmail.com
Whole thread Raw
In response to Reduce DEBUG level of catcache refreshing messages  ("Jelte Fennema-Nio" <postgres@jeltef.nl>)
List pgsql-hackers

On Fri, May 30, 2025 at 9:33 AM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
When testing extensions using pgregress, it can be useful to introduce
some new DEBUG logs which are specific to the extension and change the
log level during part of the of the test.

There's a problem though: Often a "rehashing catalog cache ..." debug
message will also show up in those cases. It's not always possible to
predict when these messages show, and when they do their contents can
easily change if changes are made to an unrelated test or when run
against a different Postgres version. This change lowers the log level
of these messages to DEBUG5, so that they can be ignored while still
showing other (more predictable) DEBUG messages.


This is a very good idea. In TimescaleDB we filter out such kind of output in order to not end up with flaky test outputs.

The patch LGTM.

--
Fabrízio de Royes Mello

pgsql-hackers by date:

Previous
From: Andrey Borodin
Date:
Subject: Re: Persist injection points across server restarts
Next
From: Tom Lane
Date:
Subject: Re: Reduce DEBUG level of catcache refreshing messages