Mike Mascari wrote:
> Tom Lane wrote:
>>Uh, what exactly does it buy you to involve an environment variable
>>in this process? I think it just adds fragility. (For example,
>>exposing setenv to the user creates the risk that he'll overwrite
>>something of importance, like PATH.)
>
> Actually, I meant that setenv() and getenv() would only be used to
> store the memory address of a privately manipulated variable map. I
> did not mean that it should actually be used to store and retrieve the
> variables themselves. If there is already a way to palloc() memory
> using a key that lives for the lifetime of a backend, then that's
> obviously the way to go. I was proceeding under the assumption that
> there wasn't.
It's been a long time since I've used global variables. Sorry...
Mike Mascari
[EMAIL PROTECTED]
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
