Re: Application name patch - v2

2009/10/20 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> writes:
>> Tom Lane wrote:
>>> It would be a seriously bad idea for this to behave one way on some
>>> platforms and differently on others.
>
>> Why would that be so bad? On platforms that support getting argv[0],
>> you'd get "mycoolapp" in the application name by default. On others,
>> you'd get something like "unknown libpq app".
>
> Right, and if your software is written to depend on the appname being
> set a particular way, you suddenly find you have a portability problem.
> I don't think we should be in the business of creating hidden vendor
> lock-ins.

If your application depends on it being set properly, then have the
application set it. This would just be a *default*, you could still
override it - and should if it's really that important to your
application.

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?

--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/