| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | "Massa, Harald Armin" <chef(at)ghum(dot)de>, Dave Page <dpage(at)pgadmin(dot)org> |
| Subject: | Re: Client application name |
| Date: | 2009-10-13 16:49:13 |
| Message-ID: | 200910131849.14248.andres@anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tuesday 13 October 2009 18:30:54 Massa, Harald Armin wrote:
> >I can have libpq look at the environment as it does for
> >PGCLIENTENCODING, but I'd certainly like to be able to use the
> >connection string as well, as environment variables are not really the
> another challenge with the Environment variable: they are (at least on
> windows) usually set for one logged on user.
> And ususally I have pg_admin, python for development, psql and my
> application all connected to the same PostgreSQL server.
> I would love to see 4 different application names, and not the value of one
> environment-variable. that argv[0] that was somewhere in this thread looked
> nice :)
Well, those applications could set it themselves...
Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2009-10-13 16:55:35 | Re: Client application name |
| Previous Message | Dave Page | 2009-10-13 16:43:42 | Re: Wire protocol docs |