On Mon, Dec 19, 2011 at 11:13:57PM -0500, Tom Lane wrote: > Noah Misch <n...@leadboat.com> writes: > > I created a function that does this in a loop: > > > HeapTuple t; > > > CatalogCacheFlushCatalog(ProcedureRelationId); > > t = SearchSysCache1(PROCOID, ObjectIdGetDatum(42) /* int4in */); > > if (!HeapTupleIsValid(t)) > > elog(ERROR, "cache lookup failed for function 42"); > > ReleaseSysCache(t); > > ... but this performance test seems to me to be entirely misguided, > because it's testing a situation that isn't going to occur much in the > field, precisely because the syscache should prevent constant reloads of > the same syscache entry.
> [ideas for more-realistic tests] Granted, but I don't hope to reliably measure a change in a macro-benchmark after seeing a rickety 2% change in a micro-benchmark. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
