| From: | Mike Mascari <mascarm(at)mascari(dot)com> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | Mark Wilson <mark(at)mediasculpt(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: database session variables |
| Date: | 2002-10-02 02:16:09 |
| Message-ID: | 3D9A56E9.8020602@mascari.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Martijn van Oosterhout wrote:
> On Wed, Oct 02, 2002 at 01:48:46PM +1200, Mark Wilson wrote:
>
>>Thanks Martijin,
>>
>>It sounds like the process_id is the 'correct' name for what I was calling
>>session_id, and is what I want. To answer your question, Oracle lets you
>>have session specific variables, via package variables.
>
>
> Hmm, the client can get it using $conn->backendPID in perl or PQbackendPID
> in C. I don't know how you do it from the backend itself.
Why not write a little server-side C function to return the
result of getpid()?
Mike Mascari
mascarm(at)mascari(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Wilson | 2002-10-02 02:21:34 | Re: database session variables |
| Previous Message | Justin Clift | 2002-10-02 02:07:46 | Re: PostgreSQL Website : advocacy.postgresql.org |