pgsql: Rename EVT cache hash to make context name unique

From: Daniel Gustafsson <dgustafsson(at)postgresql(dot)org>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Rename EVT cache hash to make context name unique
Date: 2023-07-05 07:01:25
Message-ID: E1qGwVx-001zR1-Ls@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Rename EVT cache hash to make context name unique

BuildEventTriggerCache sets up a context "EventTriggerCache" which
house a hash named "Event Trigger Cache", which in turn creates a
context with the table name. This generated log output for memory
context dumps like below:

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

This renames the hash to ensure that the hash context has a unique
name for easier log reading and debugging.

Discussion: https://postgr.es/m/5EDC969E-CAE3-4CBD-965E-3B8A1294CFA4@yesql.se

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/a77d39d5f4b97c7d08e6786429d69eae5baec48e

Modified Files
--------------
src/backend/utils/cache/evtcache.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Heikki Linnakangas 2023-07-05 07:03:06 pgsql: Change example in pgindent README on "/*-----" comments.
Previous Message Masahiko Sawada 2023-07-05 05:54:42 pgsql: pgstat: fix subscription stats entry leak.