Re: Application name patch - v4
От | Robert Haas |
---|---|
Тема | Re: Application name patch - v4 |
Дата | |
Msg-id | 603c8f070911301338m461957d0n96a8cfef25ebb51b@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Application name patch - v4 (Dimitri Fontaine <dfontaine@hi-media.com>) |
Ответы |
Re: Application name patch - v4
|
Список | pgsql-hackers |
On Mon, Nov 30, 2009 at 4:11 PM, Dimitri Fontaine <dfontaine@hi-media.com> wrote: > Le 30 nov. 2009 à 00:25, Tom Lane a écrit : >> The thing is that the libpq API treats application_name as a *property >> of the connection*. > > Oh. Yeah. > >> We could add a third keyword, say SET DEFAULT, that would have the >> behavior of setting the value in a fashion that would persist across >> resets. I'm not sure that DEFAULT is exactly le mot juste here, but >> agreeing on a keyword would probably be the hardest part of making it >> happen. > > I vaguely remember you explaining how hard it would be to be able to predict the value we RESET to as soon as we add thisor that possibility. That's very vague, sorry, but only leaves a bad impression on the keyword choice (bikeshedding,I should open a club). > > So what about SET CONNECTION application_name TO 'whatever'? I still don't really understand why we wouldn't want RESET ALL to reset the application name. In what circumstances would you want the application name to stay the same across a RESET ALL? ...Robert
В списке pgsql-hackers по дате отправления: