From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | mlw <markw(at)mohawksoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Suggestions please: names for function cachabilityattributes |
Date: | 2002-04-03 18:29:40 |
Message-ID: | 11268.1017858580@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
It occurs to me that we also need a better term for the overall concept.
"cacheability" has misled at least two people (that I can recall) into
thinking that we maintain some kind of function result cache --- which
is not true, and if it were true we'd need the term "cacheable" for
control parameters for the cache, which this categorization is not.
I am thinking that "mutability" might be a good starting point instead
of "cacheability". This leads immediately to what seems like a fairly
reasonable set of names:
pg_proc column: promutable or proismutable
case 1: "immutable"
case 2: "mutable", or perhaps "stable"
case 3: "volatile"
Thoughts?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-04-03 18:41:14 | Re: Re : Solaris Performance - Profiling (Solved) |
Previous Message | Tom Lane | 2002-04-03 17:38:06 | Re: Suggestions please: names for function cachabilityattributes |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2002-04-03 18:36:33 | Re: timeout implementation issues |
Previous Message | Hervé Piedvache | 2002-04-03 18:01:43 | PSQL completion !? v7.2.1 |