Re: patch: shared session variables

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: patch: shared session variables
Date: 2012-08-30 19:01:11
Message-ID: CA+Tgmoa0uMYyB8EZ9kAw_iUsjyH6g668cSOJzAOUqm9NMW6hsQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 30, 2012 at 2:18 PM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> 2012/8/30 Robert Haas <robertmhaas(at)gmail(dot)com>:
>> On Tue, Aug 14, 2012 at 3:46 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>>> patch that implements "shared" client/server session variables
>>
>> I don't really see what we can do with this that we can't do without this.
>
> a motivation for this patch was discussion about parametrised DO
> statement - and simple possibility of access to host variables (psql)
> variables from server - PL scripts.
>
> It is based on Tom's and Magnus's ideas - it is secure, because only
> variables explicitly mentioned in shared namespace are "shared".

Sure, but you could get to the same place by issuing a SET command for
just the particular variable you want to use with DO. You don't
really need a magic facility for it.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-08-30 19:05:36 Re: Proof of concept: auto updatable views
Previous Message Robert Haas 2012-08-30 18:58:30 Re: Wiki link for max_connections? (Fwd: Re: [ADMIN] PostgreSQL oom_adj postmaster process to -17)