Re: Application name patch - v4
Dave Page <dpage@pgadmin.org>
From: Dave Page <dpage@pgadmin.org>
To: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
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:18:39Z
Lists: pgsql-hackers
On Tue, Dec 1, 2009 at 9:16 AM, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> wrote: > 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? There has to be some level of trust here :-). As the alternative would involve bumping the fe-be protocol version, it seems like a reasonable approach to me. -- Dave Page EnterpriseDB UK: http://www.enterprisedb.com