| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | "Magnus Hagander" <magnus(at)hagander(dot)net>, "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>, "Harald Armin Massa" <chef(at)ghum(dot)de>, "Dave Page" <dpage(at)pgadmin(dot)org>, "pgsql-hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Application name patch - v2 |
| Date: | 2009-10-20 22:22:45 |
| Message-ID: | 6333.1256077365@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
> Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> For java, it doesn't even go through libpq, so it wouldn't be set
>> for it. And I'd expect the JDBC driver to set it based on Something
>> Reasonable (TM) that it can get the information about. After all,
>> this thing was listed in the JDBC spec somebody said...
> I can't see a good way to get a meaningful default from within the
> bowels of the JDBC driver, unless it's taking a system property or
> environment variable.
[ scratches head... ] I thought the JDBC spec already said exactly how
one would set this. Why would we go to significant effort to make it
behave contrary to spec?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2009-10-20 22:59:56 | Re: alpha2 release notes |
| Previous Message | Tom Lane | 2009-10-20 22:18:50 | Re: Going, going, GUCs! |