Re: Application name patch - v4

Robert Haas <robertmhaas@gmail.com>

From: Robert Haas <robertmhaas@gmail.com>
To: Dimitri Fontaine <dfontaine@hi-media.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, Dave Page <dpage@pgadmin.org>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2009-11-30T22:06:12Z
Lists: 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 a hard 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