Re: Client application name

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Dave Page <dpage(at)pgadmin(dot)org>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Client application name
Date: 2009-10-13 15:11:29
Message-ID: 4AD498A1.4080609@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dave Page wrote:
> My questions to the group are:
>
> - Is my approach reasonable?
> - What interface should I include in libpq?
>
> On the second question, obviously the user can call SET to set a
> value, as I've done for now in psql, however in other DBMSs, it may be
> set in the connection string. My feeling would be to do that, and
> possibly add PQsetApplicationName(PGconn *conn, char *name) and char
> *PQapplicationName(PGconn *conn);. What do others think?
>
>

Doing it with a GUC will not be nearly so useful as having it in the
wire protocol, IMNSHO. Just one example: it wouldn't be present in
connection records, because it wouldn't be set yet.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2009-10-13 15:13:09 Re: Client application name
Previous Message Alvaro Herrera 2009-10-13 15:06:30 Re: Client application name