On Tue, Oct 13, 2009 at 12:05 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Dave Page <dp...@pgadmin.org> writes: >> - Is my approach reasonable? >> - What interface should I include in libpq? > > I thought the plan was to have libpq look at an environment variable, > compare PGCLIENTENCODING for example. I'm not convinced psql should be > involved in the logic at all --- if it is, there definitely must be a > way for scripts to override the "psql" value. In general the place that > is most reasonable to set the value might be several software levels up > from libpq, which is what makes the environment-variable approach > attractive.
What happens if we want to change the application name after the fact? Consider the case where there is a connection pooler between the database and application, for example. ...Robert -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
