| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Magnus Hagander <magnus(at)hagander(dot)net> |
| Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, "Massa, Harald Armin" <chef(at)ghum(dot)de>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Application name patch - v2 |
| Date: | 2009-10-20 16:16:42 |
| Message-ID: | 1577.1256055402@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> Also, how many platforms can't we do this on? If we have BSD and
> Windows covered already. on linux, I believe you can easily read it
> out of /proc/self/cmdline, no?
Writing a pile of platform-specific code for this is simply insane from
a support point of view. The feature is NOT worth it. Especially not
since the typical result will be something quite uninformative like
"psql" or "java". The cases that are actually useful are the ones where
the application sets it. I don't think we should have a default at all
--- you don't set it, you don't get a name.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2009-10-20 16:18:25 | Re: Application name patch - v2 |
| Previous Message | Pavel Stehule | 2009-10-20 16:13:41 | Re: Controlling changes in plpgsql variable resolution |