Tom Lane b41f4ab8c4 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.		2000-06-30 07:04:23 +00:00
..
locks.h	Add:	2000-01-26 05:58:53 +00:00
prs2lock.h	Add:	2000-01-26 05:58:53 +00:00
rewriteDefine.h	Add:	2000-01-26 05:58:53 +00:00
rewriteHandler.h	Add:	2000-01-26 05:58:53 +00:00
rewriteManip.h	Ye-old pgindent run. Same 4-space tabs.	2000-04-12 17:17:23 +00:00
rewriteRemove.h	Add:	2000-01-26 05:58:53 +00:00
rewriteSupport.h	Use a private memory context to store rule information in each relcache	2000-06-30 07:04:23 +00:00