pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Mike Mascari <mascarm@mascari.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Richard Huxton <dev@archonet.com>
Cc: Lista dyskusyjna pgsql-general <pgsql-general@postgresql.org>
Subject: Re: PG + PHP, was Re: Zend survey result about dbms...
Date: Sat, 20 Sep 2003 18:37:51 -0400
Message-ID: <3F6CD6BF.5030206@mascari.com> (raw)
In-Reply-To: <29970.1064096941@sss.pgh.pa.us>
References: <000501c37e9e$0ecffc70$4701a8c0@marek>
	<20022.1063984707@sss.pgh.pa.us>
	<200309201248.54484.dev@archonet.com>
	<23474.1064069400@sss.pgh.pa.us>
	<3F6CD248.8040006@mascari.com>
	<29970.1064096941@sss.pgh.pa.us>

Tom Lane wrote:

> Mike Mascari <mascarm@mascari.com> 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.)

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.

Mike Mascari
mascarm@mascari.com





view thread (7+ messages)  latest in thread

Message-ID: <3F6CD6BF.5030206@mascari.com>
Permalink:  ../3F6CD6BF.5030206@mascari.com/
Also on:    postgresql.org/message-id/3F6CD6BF.5030206@mascari.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: mascarm@mascari.com, tgl@sss.pgh.pa.us, dev@archonet.com, pgsql-general@postgresql.org
  Subject: Re: PG + PHP, was Re: Zend survey result about dbms...
  In-Reply-To: <3F6CD6BF.5030206@mascari.com>
  References: <000501c37e9e$0ecffc70$4701a8c0@marek> <20022.1063984707@sss.pgh.pa.us> <200309201248.54484.dev@archonet.com> <23474.1064069400@sss.pgh.pa.us> <3F6CD248.8040006@mascari.com> <29970.1064096941@sss.pgh.pa.us> <3F6CD6BF.5030206@mascari.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox