Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
Skip to content

Commit fc1ca6b

Browse files
JelteFCommitfest Bot
authored and
Commitfest Bot
committed
Reduce DEBUG level of catcache refreshing messages
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.
1 parent c3eda50 commit fc1ca6b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/backend/utils/cache/catcache.c

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -988,7 +988,7 @@ RehashCatCache(CatCache *cp)
988988
int newnbuckets;
989989
int i;
990990

991-
elog(DEBUG1, "rehashing catalog cache id %d for %s; %d tups, %d buckets",
991+
elog(DEBUG5, "rehashing catalog cache id %d for %s; %d tups, %d buckets",
992992
cp->id, cp->cc_relname, cp->cc_ntup, cp->cc_nbuckets);
993993

994994
/* Allocate a new, larger, hash table. */
@@ -1026,7 +1026,7 @@ RehashCatCacheLists(CatCache *cp)
10261026
int newnbuckets;
10271027
int i;
10281028

1029-
elog(DEBUG1, "rehashing catalog cache id %d for %s; %d lists, %d buckets",
1029+
elog(DEBUG5, "rehashing catalog cache id %d for %s; %d lists, %d buckets",
10301030
cp->id, cp->cc_relname, cp->cc_nlist, cp->cc_nlbuckets);
10311031

10321032
/* Allocate a new, larger, hash table. */

0 commit comments

Comments
 (0)