| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, 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 15:17:54 |
| Message-ID: | 27654.1256051874@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2009-10-20 15:48:59 | Re: Could postgres be much cleaner if a future release skipped backward compatibility? |
| Previous Message | Andrew Dunstan | 2009-10-20 15:13:19 | Re: UTF8 with BOM support in psql |