Possible micro-optimization in CacheInvalidateHeapTuple

CacheInvalidateHeapTuple currently does the following tests first; would there be a performance improvement to testing
thesystem relation case first? We're almost never in bootstrap mode, so that test is almost always a waste. Is there
anyreason not to switch the two?
 
/* Do nothing during bootstrap */if (IsBootstrapProcessingMode())    return;
/* * We only need to worry about invalidation for tuples that are in system * relations; user-relation tuples are never
incatcaches and can't affect * the relcache either. */if (!IsSystemRelation(relation))    return;
 
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com