Re: Application name patch - v4 - Mailing list pgsql-hackers

From Heikki Linnakangas
Subject Re: Application name patch - v4
Date
Msg-id 4B14DEFD.5000902@enterprisedb.com
Whole thread Raw
In response to Re: Application name patch - v4  (Dave Page <dpage@pgadmin.org>)
Responses Re: Application name patch - v4  (Dave Page <dpage@pgadmin.org>)
Re: Application name patch - v4  (Andres Freund <andres@anarazel.de>)
Re: Application name patch - v4  (Marko Kreen <markokr@gmail.com>)
List 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


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Application name patch - v4
Next
From: Dave Page
Date:
Subject: Re: Application name patch - v4