By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
464,779 Members | 1,269 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 464,779 IT Pros & Developers. It's quick & easy.

strategies for optimising common lookups etc

P: n/a

Hi all, apologies if this is a dumb question - not really sure where to look
for this kind of stuff...

I have a frequently called stored procedure that needs to access some
"configuration" information to determine how it should behave.

Currently I have the configuration information in its own table, and the sp
does a lookup "select item from config where pk = ...".

I am wondering whether there is any way to "cache" the result of a lookup
across instances of the stored procedure call? The configuration value will
rarely change, and as the procedure is called often it seems a bit of a waste
of resources looking it up each time the procedure is run.

Is this the sort of thing that internal variables would handle (by that I mean
using "set" and "show")?

TIA
Martin

--
Martin Hart
Arnclan Limited
53 Union Street
Dunstable, Beds
LU6 1EX
http://www.arnclanit.com
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Nov 11 '05 #1
Share this question for a faster answer!
Share on Google+

This discussion thread is closed

Replies have been disabled for this discussion.