From: | Tom Lane <tgl> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql/src/backend/commands (trigger.c) |
Date: | 2000-06-30 07:04:17 |
Message-ID: | 200006300704.e5U74Hi96520@hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Date: Friday, June 30, 2000 @ 03:04:17
Author: tgl
Update of /home/projects/pgsql/cvsroot/pgsql/src/backend/commands
from hub.org:/home/projects/pgsql/tmp/cvs-serv96341/backend/commands
Modified Files:
trigger.c
----------------------------- Log Message -----------------------------
Use a private memory context to store rule information in each relcache
entry that has rules. This allows us to release the rule parsetrees
on relcache flush without needing a working freeObject() routine.
Formerly, the rule trees were leaked permanently at relcache flush.
Also, clean up handling of rule creation and deletion --- there was
not sufficient locking of the relation being modified, and there was
no reliable notification of other backends that a relcache reload
was needed. Also, clean up relcache.c code so that scans of system
tables needed to load a relcache entry are done in the caller's
memory context, not in CacheMemoryContext. This prevents any
un-pfreed memory from those scans from becoming a permanent memory
leak.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-06-30 07:04:22 | pgsql/src/backend/catalog (index.c) |
Previous Message | Tom Lane | 2000-06-30 07:04:16 | pgsql/src/backend/utils/cache (relcache.c) |