mirror of
https://github.com/postgres/postgres.git
synced 2025-06-26 12:21:12 +03:00
b41f4ab8c4
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.
77 lines
2.3 KiB
C
77 lines
2.3 KiB
C
/*-------------------------------------------------------------------------
|
|
*
|
|
* rewriteSupport.c
|
|
*
|
|
*
|
|
* Portions Copyright (c) 1996-2000, PostgreSQL, Inc
|
|
* Portions Copyright (c) 1994, Regents of the University of California
|
|
*
|
|
*
|
|
* IDENTIFICATION
|
|
* $Header: /cvsroot/pgsql/src/backend/rewrite/rewriteSupport.c,v 1.43 2000/06/30 07:04:23 tgl Exp $
|
|
*
|
|
*-------------------------------------------------------------------------
|
|
*/
|
|
#include "postgres.h"
|
|
|
|
#include "access/heapam.h"
|
|
#include "catalog/catname.h"
|
|
#include "catalog/indexing.h"
|
|
#include "rewrite/rewriteSupport.h"
|
|
#include "utils/catcache.h"
|
|
#include "utils/syscache.h"
|
|
|
|
|
|
int
|
|
IsDefinedRewriteRule(char *ruleName)
|
|
{
|
|
HeapTuple tuple;
|
|
|
|
tuple = SearchSysCacheTuple(RULENAME,
|
|
PointerGetDatum(ruleName),
|
|
0, 0, 0);
|
|
return HeapTupleIsValid(tuple);
|
|
}
|
|
|
|
/*
|
|
* setRelhasrulesInRelation
|
|
* Set the value of the relation's relhasrules field in pg_class.
|
|
*
|
|
* NOTE: caller should be holding an appropriate lock on the relation.
|
|
*
|
|
* NOTE: an important side-effect of this operation is that an SI invalidation
|
|
* message is sent out to all backends --- including me --- causing relcache
|
|
* entries to be flushed or updated with the new set of rules for the table.
|
|
* Therefore, we execute the update even if relhasrules has the right value
|
|
* already. Possible future improvement: skip the disk update and just send
|
|
* an SI message in that case.
|
|
*/
|
|
void
|
|
setRelhasrulesInRelation(Oid relationId, bool relhasrules)
|
|
{
|
|
Relation relationRelation;
|
|
HeapTuple tuple;
|
|
Relation idescs[Num_pg_class_indices];
|
|
|
|
/*
|
|
* Find the tuple to update in pg_class, using syscache for the lookup.
|
|
*/
|
|
relationRelation = heap_openr(RelationRelationName, RowExclusiveLock);
|
|
tuple = SearchSysCacheTupleCopy(RELOID,
|
|
ObjectIdGetDatum(relationId),
|
|
0, 0, 0);
|
|
Assert(HeapTupleIsValid(tuple));
|
|
|
|
/* Do the update */
|
|
((Form_pg_class) GETSTRUCT(tuple))->relhasrules = relhasrules;
|
|
heap_update(relationRelation, &tuple->t_self, tuple, NULL);
|
|
|
|
/* Keep the catalog indices up to date */
|
|
CatalogOpenIndices(Num_pg_class_indices, Name_pg_class_indices, idescs);
|
|
CatalogIndexInsert(idescs, Num_pg_class_indices, relationRelation, tuple);
|
|
CatalogCloseIndices(Num_pg_class_indices, idescs);
|
|
|
|
heap_freetuple(tuple);
|
|
heap_close(relationRelation, RowExclusiveLock);
|
|
}
|