On Wed, Apr 7, 2010 at 5:30 AM, Dave Page <dp...@pgadmin.org> wrote: > On Wed, Apr 7, 2010 at 10:16 AM, Magnus Hagander <mag...@hagander.net> wrote: >> Uh, why fallback_application_name? Isn't this the *exact* usecase >> where "application_name" should be used? At least for the two apps - >> fallback_app_name might be correct for dblink. >> >> And yes, I think it's a good idea to set it for at least pgbench and >> oid2name. > > For pgbench, I can imagine scenarios where you might want to override > the name in a script - for example, if you're trying to simulate an > environment with multiple workload types running against the same > database.
Agreed. >> I think that's a pretty bad idea in general. But if we do, then it >> should at least never override something that's specified - we need to >> keep the ability for tools like psql and pgadmin to set it, regardless >> of what they happen to have as argv[0]. > > We discussed that during the development of the patch - the original > idea was to default to argv[0] if no other value was set, but > apparently there's no portable way to get at argv[0] from within > libpq, even if you ignore Windows. That's true, and I also agree with Magnus's commenet that it's a bad idea anyway. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
