| From: | Vincenzo Romano <vincenzo(dot)romano(at)notorand(dot)it> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: [9.0] On temporary tables |
| Date: | 2010-09-30 14:25:48 |
| Message-ID: | AANLkTim9BJQjOFepe53Y8m3E8TLZT5+vN6GGfV7XPqqu@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
2010/9/30 Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>:
> Hello
>>> but if you need a session variables, then you can use a plperl
>>>
>>> http://www.postgresql.org/docs/9.0/static/plperl-global.html
>>
>> I will look into this. What I need is a set of variable for each connection.
>>
>
> understand - attention - session variables are nice but problematic
> when you use some form of connection pooling
I do know I'll need to be careful, even without connection pooling.
What'd be a different solution to implement session variables?
Just PLPERL?
--
Vincenzo Romano at NotOrAnd Information Technologies
Software Hardware Networking Training Support Security
--
NON QVIETIS MARIBVS NAVTA PERITVS
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Farber | 2010-09-30 14:34:47 | Working around in-statement with temporary tables |
| Previous Message | Pavel Stehule | 2010-09-30 14:13:45 | Re: [9.0] On temporary tables |