pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Problems monitoring DB activity
5+ messages / 3 participants
[nested] [flat]

* Problems monitoring DB activity
@ 2004-10-08 13:54  Doug Y <dylists@ptd.net>
  0 siblings, 1 reply; 5+ messages in thread

From: Doug Y @ 2004-10-08 13:54 UTC (permalink / raw)
  To: pgsql-admin

Hello,

When I do the following:

SELECT * FROM pg_catalog.pg_stat_activity;

The current_query and query_start columns are always empty. Obviously 
this makes it hard to monitor problems with the various admin tools, etc.

I'm guessing there's a setting or something that needs updated, I just 
need a point in the right direction. DB is 7.4.2

Thanks



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Problems monitoring DB activity
@ 2004-10-08 14:11  Michael Fuhr <mike@fuhr.org>
  parent: Doug Y <dylists@ptd.net>
  0 siblings, 1 reply; 5+ messages in thread

From: Michael Fuhr @ 2004-10-08 14:11 UTC (permalink / raw)
  To: Doug Y <dylists@ptd.net>; +Cc: pgsql-admin

On Fri, Oct 08, 2004 at 09:54:08AM -0400, Doug Y wrote:
> 
> SELECT * FROM pg_catalog.pg_stat_activity;
> 
> The current_query and query_start columns are always empty. Obviously 
> this makes it hard to monitor problems with the various admin tools, etc.

Does postgresql.conf have stats_command_string = true?

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Problems monitoring DB activity
@ 2004-10-08 14:46  Doug Y <dylists@ptd.net>
  parent: Michael Fuhr <mike@fuhr.org>
  0 siblings, 1 reply; 5+ messages in thread

From: Doug Y @ 2004-10-08 14:46 UTC (permalink / raw)
  To: Michael Fuhr <mike@fuhr.org>; +Cc: pgsql-admin

Michael Fuhr wrote:

>On Fri, Oct 08, 2004 at 09:54:08AM -0400, Doug Y wrote:
>  
>
>>SELECT * FROM pg_catalog.pg_stat_activity;
>>
>>The current_query and query_start columns are always empty. Obviously 
>>this makes it hard to monitor problems with the various admin tools, etc.
>>    
>>
>
>Does postgresql.conf have stats_command_string = true?
>
Thanks, setting that did the trick....  whats the performance hit for 
having it enabled?



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Problems monitoring DB activity
@ 2004-10-08 15:14  Michael Fuhr <mike@fuhr.org>
  parent: Doug Y <dylists@ptd.net>
  0 siblings, 0 replies; 5+ messages in thread

From: Michael Fuhr @ 2004-10-08 15:14 UTC (permalink / raw)
  To: Doug Y <dylists@ptd.net>; +Cc: pgsql-admin

On Fri, Oct 08, 2004 at 10:46:56AM -0400, Doug Y wrote:
> Michael Fuhr wrote:
> >
> >Does postgresql.conf have stats_command_string = true?
> >
> Thanks, setting that did the trick....  whats the performance hit for 
> having it enabled?

I haven't done any tests to determine the performance penalty; maybe
one of the developers or somebody who's done some benchmarks can
comment.

The "Annotated postgresql.conf and Global User Configuration (GUC)
Guide"[1] says that "Enabling statistics collection costs a small
amount of time per query, but is invaluable for debugging and
performance tuning."

[1] http://www.varlena.com/varlena/GeneralBits/Tidbits/annotated_conf_e.html

-- 
Michael Fuhr
http://www.fuhr.org/~mfuhr/



^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: Problems monitoring DB activity
@ 2004-10-08 15:50  Goulet, Dick <DGoulet@vicr.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Goulet, Dick @ 2004-10-08 15:50 UTC (permalink / raw)
  To: Michael Fuhr <mike@fuhr.org>; Doug Y <dylists@ptd.net>; +Cc: pgsql-admin

Sounds like the Oracle parameter TIMED_STATISTICS.  Costs you soo little
in performance, but saves you a pile in troubleshooting.  Many DBA's
still set it to false to "save the expense".  Nice to know the same
exists here. 


Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA
-----Original Message-----
From: Michael Fuhr [mailto:mike@fuhr.org] 
Sent: Friday, October 08, 2004 11:15 AM
To: Doug Y
Cc: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] Problems monitoring DB activity

On Fri, Oct 08, 2004 at 10:46:56AM -0400, Doug Y wrote:
> Michael Fuhr wrote:
> >
> >Does postgresql.conf have stats_command_string = true?
> >
> Thanks, setting that did the trick....  whats the performance hit for 
> having it enabled?

I haven't done any tests to determine the performance penalty; maybe one
of the developers or somebody who's done some benchmarks can comment.

The "Annotated postgresql.conf and Global User Configuration (GUC)
Guide"[1] says that "Enabling statistics collection costs a small amount
of time per query, but is invaluable for debugging and performance
tuning."

[1]
http://www.varlena.com/varlena/GeneralBits/Tidbits/annotated_conf_e.html

--
Michael Fuhr
http://www.fuhr.org/~mfuhr/

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

               http://www.postgresql.org/docs/faqs/FAQ.html



^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2004-10-08 15:50 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2004-10-08 13:54 Problems monitoring DB activity Doug Y <dylists@ptd.net>
2004-10-08 14:11 ` Michael Fuhr <mike@fuhr.org>
2004-10-08 14:46   ` Doug Y <dylists@ptd.net>
2004-10-08 15:14     ` Michael Fuhr <mike@fuhr.org>
2004-10-08 15:50 Re: Problems monitoring DB activity Goulet, Dick <DGoulet@vicr.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox