| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proof concept - access to session variables on client side |
| Date: | 2012-06-26 19:33:33 |
| Message-ID: | CAHyXU0x0bz8CXHwqo29z35LA7T3Ts3u0a0BMu8g=M7etM7hcxw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 26, 2012 at 3:05 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> But with a small change to psql they could, without the need for a
> whole new type of variable. For example, psql could set all those
> variable as "psql.<commandlinevarname>", which could then be accessed
> from the DO PL code just fine.
That's a really neat idea.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2012-06-26 19:42:38 | Re: proof concept - access to session variables on client side |
| Previous Message | Nils Goroll | 2012-06-26 19:06:02 | Re: why roll-your-own s_lock? / improving scalability |