I am full agreement with proposal. I love it!!
(1) const or constant
(2) cacheable
(3) volatile
P.S.
Tom: My mail doesn't reach you. As an AT&T user, you block my machine's IP
address with the anti-spam blocking. :-(
Tom Lane wrote:
>
> Since I'm about to have to edit pg_proc.h to add a namesp
mlw <[EMAIL PROTECTED]> writes:
> (1) const or constant
> (2) cacheable
> (3) volatile
I was wondering about "const" for case 1, also. I think there is some
precedent for using "const" with this meaning in other programming
languages. "volatile" for case 3 seems reasonable.
> Tom: My mail does
I am full agreement with proposal. I love it!!
(1) const or constant
(2) cacheable
(3) volatile
P.S.
Tom: My mail doesn't reach you. As an AT&T user, you block my machine's IP
address with the anti-spam blocking. :-(
---(end of broadcast)---
TIP
* Tom Lane ([EMAIL PROTECTED]) [020402 16:42]:
> Since I'm about to have to edit pg_proc.h to add a namespace column,
> I thought this would be a good time to revise the current proiscachable
> column into the three-way cachability distinction we've discussed
> before. But I need some names for t
My 2 cents.
Level 1. with (isCachableStatic)
Level 2. with (isCachableDynamic)
Level 3. default
In my mind (isCachable) sounds like level 1
On Tuesday 02 April 2002 03:40 pm, Tom Lane wrote:
> Since I'm about to have to edit pg_proc.h to add a namespace column,
> I thought this would be a good
