| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Dave Page <dpage(at)pgadmin(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:22:13 |
| Message-ID: | 200912011022.14098.andres@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tuesday 01 December 2009 10:16:45 Heikki Linnakangas 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?
Why does it need to? SET DEFAULT should imho only be allowed for values whcih
can be set during connection initiation. For those it can simply issue the
sets anyway.
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2009-12-01 09:30:03 | Re: Application name patch - v4 |
| Previous Message | Dave Page | 2009-12-01 09:18:39 | Re: Application name patch - v4 |