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

Re: Application name patch - v4

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: Andres Freund <andres(at)anarazel(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Dimitri Fontaine <dfontaine(at)hi-media(dot)com>
Subject: Re: Application name patch - v4
Date: 2009-12-01 09:16:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
Dave Page wrote:
> Upthread, Tom suggested a new 'SET DEFAULT ...' variant of SET which
> could be used to set the default GUC value that RESET would revert to.
> This seems to me to be the ideal solution, and I'd somewhat hesitantly
> volunteer to work on it (hesitantly as it means touching the parser
> and other areas of the code I currently have no experience of).

If an application can do SET DEFAULT, how does the connection pooler
*really* reset the value back to what it was?

  Heikki Linnakangas

In response to


pgsql-hackers by date

Next:From: Dave PageDate: 2009-12-01 09:18:39
Subject: Re: Application name patch - v4
Previous:From: Andres FreundDate: 2009-12-01 09:11:49
Subject: Re: Application name patch - v4

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