Horton

Re: Application name patch - v4

Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>

View thread View on postgr.es
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Dave Page <dpage@pgadmin.org>
Cc: Andres Freund <andres@anarazel.de>, pgsql-hackers <pgsql-hackers@postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>, Robert Haas <robertmhaas@gmail.com>, Dimitri Fontaine <dfontaine@hi-media.com>
Date: 2009-12-01T09:16:45Z
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
  EnterpriseDB   http://www.enterprisedb.com