On Wed, 2009-10-14 at 18:44 +0200, Magnus Hagander wrote: > On Wed, Oct 14, 2009 at 18:39, Dave Page <dp...@pgadmin.org> wrote: > > On Wed, Oct 14, 2009 at 5:37 PM, Eric B. Ridge <e...@tcdi.com> wrote: > >> On Oct 13, 2009, at 11:02 AM, Dave Page wrote: > >> > >>> A useful feature found in other DBMSs such as MS SQL Server that has > >>> been requested on these lists a few times, is the ability for a client > >>> application to report its name to the server. > >> > >> I've been following this thread closely and haven't seen mention of > >> including the setting as part of the process name, so a 'ps' (on Unix) > >> would > >> display it. Thoughts? > > > > Isn't that cluttered enough already? > > +1 for pg_stat_activity but not 'os' output.
+1 to output application name in pg_stat_activity and also accessible to pg_stat_statements. We want to be able to set the application name *after* connection, so that session pool users can be more easily identified. Note that this *must* be set *after* connection, not during connection. So for me, the ability to set the application name at connection time is a related but separate feature - and a much less valuable one at that. ISTM much of the complexity discussed relates to this second feature. Let's just concentrate on getting the connection-pool-identification aspect of this done right and then maybe add second part later. -- Simon Riggs www.2ndQuadrant.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
