From: | "Dave Page" <dpage(at)postgresql(dot)org> |
---|---|
To: | "Tony Caduto" <tony_caduto(at)amsoftwaredesign(dot)com> |
Cc: | "Harald Armin Massa" <haraldarminmassa(at)gmail(dot)com>, "Jeffrey Melloy" <melloyj(at)alliancetechnologies(dot)net>, harding(dot)ian(at)gmail(dot)com, guillermoariast(at)linuxwaves(dot)com, pgsql-general(at)postgresql(dot)org |
Subject: | Re: is there a tracking trace tool like the "SQL Analizer |
Date: | 2007-01-09 19:55:22 |
Message-ID: | 200701091955220000@341925390 |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> ------- Original Message -------
> From: Tony Caduto <tony_caduto(at)amsoftwaredesign(dot)com>
> To: Harald Armin Massa <haraldarminmassa(at)gmail(dot)com>
> Sent: 1/9/07, 7:15:52 PM
> Subject: Re: [GENERAL] is there a tracking trace tool like the "SQL Analizer"
>
> Harald Armin Massa wrote:
> > Jeffrey,
> >
> >> Not exactly. SQL Analyzer also includes live monitoring of whatever
> >> queries
> >> are coming into the database. You can achieve something similar by
> >> enabling
> >> query logging in the settings.
> >
> > that is within Tools / View Server Status of pgAdmin III
> >
> > Of course, Query Command String has to be enabled on the server; and
> > the security implications of that setting have to be considered before
> > :)
> >
> > best wishes,
> >
> > Harald
> Hi,
> I may be wrong but:
> Enabling query logging (in the options dialog) will only log the SQL
> pgAdmin III sends to the server, it will not capture the query for a
> selected process
> in the server status dialog.
That's not what Harald was referring to. The server status dialog monitors the entire server via pg_stat*.
/D
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Marlowe | 2007-01-09 20:01:34 | Re: ERROR: invalid memory alloc request size, and others |
Previous Message | Ben | 2007-01-09 19:50:31 | index creation on 7.3 |