pg.ddx.io  pgsql-committers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Daniel Gustafsson <dgustafsson@postgresql.org>
To: pgsql-committers@lists.postgresql.org
Subject: pgsql: Rename EVT cache hash to make context name unique
Date: Wed, 05 Jul 2023 07:01:25 +0000
Message-ID: <E1qGwVx-001zR1-Ls@gemulon.postgresql.org> (raw)

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(-)



Message-ID: <E1qGwVx-001zR1-Ls@gemulon.postgresql.org>
Permalink:  ../E1qGwVx-001zR1-Ls@gemulon.postgresql.org/
Also on:    postgresql.org/message-id/E1qGwVx-001zR1-Ls@gemulon.postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-committers@postgresql.org
  Cc: dgustafsson@postgresql.org, pgsql-committers@lists.postgresql.org
  Subject: Re: pgsql: Rename EVT cache hash to make context name unique
  In-Reply-To: <E1qGwVx-001zR1-Ls@gemulon.postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox