Re: Application name patch - v4
От | Robert Haas |
---|---|
Тема | Re: Application name patch - v4 |
Дата | |
Msg-id | 603c8f070911301406r2920fd84re8d4f89996f488b3@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Application name patch - v4 (Dimitri Fontaine <dfontaine@hi-media.com>) |
Ответы |
Re: Application name patch - v4
Re: Application name patch - v4 |
Список | pgsql-hackers |
On Mon, Nov 30, 2009 at 4:54 PM, Dimitri Fontaine <dfontaine@hi-media.com> wrote: > Le 30 nov. 2009 à 22:38, Robert Haas a écrit : >> 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? > > I can't see any use case, but SET/RESET is tied to SESSION whereas application_name is a CONNECTION property. So it's ahard sell that reseting the session will change connection properties. Is there any technical difference between a connection property and a session property? If so, what is it? ISTM that the only time you're likely going to use RESET ALL is in a connection pooling environment, and that if you're in a connection pooling environment you probably want to reset the application name along with everything else. I might be wrong, but that's how it seems to me at first blush. ...Robert
В списке pgsql-hackers по дате отправления: