| From: | Dave Page <dpage(at)pgadmin(dot)org> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Application name patch - v3 |
| Date: | 2009-10-22 13:07:13 |
| Message-ID: | 937d27e10910220607h4238f2dei777d8678c6a7b5f6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Updated patch attached. Per discussion, this:
- Changes the envvar name to PGAPPNAME
- Removes support for setting application_name in the startup packet,
and instead sends an explicit SET command as part of the connection
setup in PQconnectPoll. In order to avoid adding to the
application-visible connection states, this is overloaded on the
CONNECTION_SETENV state which is only used in the v2 protocol at
present and seems like an ideal fit for such a similar use.
Other features are as per the last version.
--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com
PGDay.EU 2009 Conference: http://2009.pgday.eu/start
| Attachment | Content-Type | Size |
|---|---|---|
| appname-v3.diff | application/octet-stream | 38.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2009-10-22 13:59:20 | client_lc_messages |
| Previous Message | Rod Taylor | 2009-10-22 12:40:31 | Re: Using views for row-level access control is leaky |