Skip site navigation (1) Skip section navigation (2)

Re: Application name patch - v4

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Dimitri Fontaine <dfontaine(at)hi-media(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Dave Page <dpage(at)pgadmin(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Application name patch - v4
Date: 2009-11-30 23:59:09
Message-ID: 200911302359.nAUNx9H02437@momjian.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Robert Haas wrote:
> On Mon, Nov 30, 2009 at 4:54 PM, Dimitri Fontaine
> <dfontaine(at)hi-media(dot)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.

Uh, what does it mean to reset the application name?  Are you resetting
it to what it was before the session started, or to a blank string?

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

In response to

pgsql-hackers by date

Next:From: Tom LaneDate: 2009-12-01 00:11:13
Subject: Re: Application name patch - v4
Previous:From: Simon RiggsDate: 2009-11-30 23:28:21
Subject: Re: Block-level CRC checks

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group