evtcache: EventTriggerCache vs Event Trigger Cache
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-05-04T11:38:26Z
Lists: pgsql-hackers
When reading a memory contexts log I realized that we have this: LOG: level: 2; EventTriggerCache: 8192 total in 1 blocks; 7928 free (4 chunks); 264 used LOG: level: 3; Event Trigger Cache: 8192 total in 1 blocks; 2616 free (0 chunks); 5576 used The reason is that BuildEventTriggerCache sets up a context "EventTriggerCache" which house a hash named "Event Trigger Cache" which in turn creates a context with the table name. I think it makes sense that these share the same name, but I think it would be less confusing if they also shared the same spelling whitespace-wise. Any reason to not rename the hash EventTriggerCache to make the logging a tiny bit easier to read and grep? -- Daniel Gustafsson
Commits
-
Rename EVT cache hash to make context name unique
- a77d39d5f4b9 17.0 landed