Re: Reduce DEBUG level of catcache refreshing messages

2025-05-30 Thread Tom Lane
Jelte Fennema-Nio writes: > On Fri, 30 May 2025 at 16:38, Tom Lane wrote: >> But if we could have *some* kind of explainable basis for >> assigning DEBUGn levels, I think our lives would be better. > Agreed. I'll start with a concrete proposal then: > DEBUG1 is reserved for usage by extensions

Re: Reduce DEBUG level of catcache refreshing messages

2025-05-30 Thread Jelte Fennema-Nio
On Fri, 30 May 2025 at 16:38, Tom Lane wrote: > I don't have an opinion about the merits of this exact change, but > I wish somebody would go through all our DEBUGn messages and come up > with some coherent proposal for what the various levels should be > used for. Right now I think those choices

Re: Reduce DEBUG level of catcache refreshing messages

2025-05-30 Thread Fabrízio de Royes Mello
On Fri, May 30, 2025 at 9:33 AM Jelte Fennema-Nio 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 c

Re: Reduce DEBUG level of catcache refreshing messages

2025-05-30 Thread Tom Lane
"Jelte Fennema-Nio" writes: > 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 > messa