Dave Page escreveu: > On Wed, Oct 14, 2009 at 3:42 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: >> Sure. I'm envisioning that what the env variable or connection option >> actually does is cause libpq to include a SET command for a GUC >> variable in the initial connection request packet. Compare, say, >> PGCLIENTENCODING -> client_encoding. > > So you can now do any of the following to set the application name: > > - Set $PGAPPLICATIONNAME on the client, prior to connection. > - Include 'application_name=MyCoolApp' in the PQconnectdb connection string. > - Use SET application_name > Works for me.
> Currently though, pg_dump and psql (and presumably their close > friends) use PQsetdbLogin to establish their connection. Would it be > preferred if I: > > a) Added PQsetdbLogin2() with an additional option for the application > name (my guess is 'no'). > b) Updated the apps to use PQconnectdb > c) Something else? > My prefered option is (b). But it should be a separate patch. -- Euler Taveira de Oliveira http://www.timbira.com/ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
