Mike Mascari <mascarm@xxxxxxxxxxx> writes: > In the past, one hack would be to use setenv() and getenv() of the > backend to implement these functions. What about a contrib module that: 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.) regards, tom lane
