Re: [HACKERS] pg_stat_activity.application_name

2009-08-10 Thread Peter Eisentraut
On Monday 10 August 2009 08:39:17 Jaime Casanova wrote: > On Fri, Jul 17, 2009 at 3:19 AM, Peter Eisentraut wrote: > > On Thursday 16 July 2009 22:08:25 Kevin Grittner wrote: > >> On the admin list there was a request for an application name > >> column in pg_stat_activity. > >> > >> http://archive

Re: [HACKERS] pg_stat_activity.application_name

2009-08-09 Thread Jaime Casanova
On Fri, Jul 17, 2009 at 3:19 AM, Peter Eisentraut wrote: > On Thursday 16 July 2009 22:08:25 Kevin Grittner wrote: >> On the admin list there was a request for an application name >> column in pg_stat_activity. >> >> http://archives.postgresql.org/pgsql-admin/2009-07/msg00095.php >> >> This is avai

Re: [HACKERS] pg_stat_activity.application_name

2009-07-20 Thread Jaime Casanova
On Fri, Jul 17, 2009 at 9:58 AM, Kevin Grittner wrote: > Peter Eisentraut wrote: > >> A facility to show it in the logs (via log_line_prefix probably) >> would also be useful. > > Agreed. > ah! that seems a lot more useful. at least, i currently use logs to identify malformed or bad-performant qu

Re: [HACKERS] pg_stat_activity.application_name

2009-07-17 Thread Kevin Grittner
Peter Eisentraut wrote: > A facility to show it in the logs (via log_line_prefix probably) > would also be useful. Agreed. -Kevin -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers

Re: [HACKERS] pg_stat_activity.application_name

2009-07-17 Thread Peter Eisentraut
On Thursday 16 July 2009 22:08:25 Kevin Grittner wrote: > On the admin list there was a request for an application name > column in pg_stat_activity. > > http://archives.postgresql.org/pgsql-admin/2009-07/msg00095.php > > This is available in a lot of other DBMS products, can be useful to > DBAs, a

Re: [HACKERS] pg_stat_activity.application_name

2009-07-16 Thread Heikki Linnakangas
Kevin Grittner wrote: > We would probably want to modify psql, pg_dump, etc. to put the > application name into this connection property, at least by default. > We may want to add a command-line switch to allow user override -- to > provide something more detailed. For example, > --application-na

Re: [HACKERS] pg_stat_activity.application_name

2009-07-16 Thread Kevin Grittner
Greg Stark wrote: > Kevin Grittner wrote: >> On the admin list there was a request for an application name >> column in pg_stat_activity. >> >> http://archives.postgresql.org/pgsql-admin/2009-07/msg00095.php >> >> This is available in a lot of other DBMS products, can be useful to >> DBAs, and see

Re: [HACKERS] pg_stat_activity.application_name

2009-07-16 Thread Greg Stark
On Thu, Jul 16, 2009 at 8:08 PM, Kevin Grittner wrote: > On the admin list there was a request for an application name > column in pg_stat_activity. > > http://archives.postgresql.org/pgsql-admin/2009-07/msg00095.php > > This is available in a lot of other DBMS products, can be useful to > DBAs, an

Re: [HACKERS] pg_stat_activity.application_name

2009-07-16 Thread Kevin Grittner
Jaime Casanova wrote: > Kevin Grittner wrote: >> On the admin list there was a request for an application name >> column in pg_stat_activity. > ah? how do you implement that? and what's the use case for? It would be passed as a connection property. (If that's not feasible, perhaps a session

Re: [HACKERS] pg_stat_activity.application_name

2009-07-16 Thread Jaime Casanova
On Thu, Jul 16, 2009 at 2:08 PM, Kevin Grittner wrote: > On the admin list there was a request for an application name > column in pg_stat_activity. > > http://archives.postgresql.org/pgsql-admin/2009-07/msg00095.php > > This is available in a lot of other DBMS products, can be useful to > DBAs, an