Re: Client application name
| От | Dave Page |
|---|---|
| Тема | Re: Client application name |
| Дата | |
| Msg-id | 937d27e10910130845g2b9c758aj1a8df767fd309ea6@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Client application name (Andrew Dunstan <andrew@dunslane.net>) |
| Ответы |
Re: Client application name
|
| Список | pgsql-hackers |
On Tue, Oct 13, 2009 at 4:34 PM, Andrew Dunstan <andrew@dunslane.net> wrote:
>
> From time to time people ask for "scalar variable" facility. ISTM what
> you're trying to do is just a special case of that. Maybe we could approach
> it by providing a builtin (and non-removable) custom_variable_classes entry
> ('pg_variables'?). Then you could have clients safely do:
>
> set pg_variables.client_name = 'blurfl';
>
> And I'm sure other people would find interesting uses for such a gadget.
I'm not sure that's really related to this - for example, we wouldn't
want to push everything in the custom class through the logger or into
per-backend shared memory, which would mean special-casing this
particular variable for which doing those things is the primary use
case.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: