Re: Application name patch - v2 - Mailing list pgsql-hackers

From Dave Page
Subject Re: Application name patch - v2
Date
Msg-id 937d27e10910190739n4f6e486ar56ecf330b0896d2a@mail.gmail.com
Whole thread Raw
In response to Re: Application name patch - v2  (David Fetter <david@fetter.org>)
Responses Re: Application name patch - v2
List pgsql-hackers
On Mon, Oct 19, 2009 at 3:17 PM, David Fetter <david@fetter.org> wrote:

> Could you point to a reference for this?  It could help the rest of us
> see what you're aiming for even better :)

Sure. Here's a nice example from SQL Server as well as related doc links:

http://blog.benhall.me.uk/2007/10/sql-connection-application-name.html
http://msdn.microsoft.com/en-us/library/ms189770.aspx
http://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring%28VS.85%29.aspx

Kris pointed out the JDBC usage of this (and some related properties):

http://archives.postgresql.org/pgsql-hackers/2009-10/msg00726.php

Similar features are available in Oracle:

http://download.oracle.com/docs/cd/B10501_01/appdev.920/a96612/d_appin2.htm
http://www.dba-oracle.com/security/the_client_identifier.htm (in this
case, it is considered a security/auditing feature)



--
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Application name patch - v2
Next
From: Tom Lane
Date:
Subject: Re: Application name patch - v2