Hallöchen!
Andreas Kretschmer writes:
> Torsten Bronger wrote:
>
>> I need statistics about the PG server load. At the moment, I use
>> for this
>>
>> SELECT tup_returned + tup_fetched + tup_inserted + tup_updated +
>> tup_deleted FROM
Hallöchen!
hubert depesz lubaczewski writes:
> On Sun, Jul 25, 2010 at 12:15:06PM +0200, Torsten Bronger wrote:
>
>> I need statistics about the PG server load. At the moment, I use
>> for this
>>
>> SELECT tup_returned + tup_fetched + tup_inserted + tup_upda
If a "row" is one dataset (one user account, one blog entry, one
comment etc), I expect two or three orders of magnitude less. Is my
SQL statement nevertheless a good way to measure how busy the server
is?
Tschö,
Torsten.
--
Torsten Bronger, aquisgrana, europa vetus
Hallöchen!
Torsten Bronger writes:
> Yesterday I ported a web app to PG. Every 10 minutes, a cron job
> scanned the log files of MySQL and generated a plot showing the
> queries/sec for the last 24h. (Admittedly queries/sec is not the
> holy grail of DB statistics.)
>
> B
moment I just
do the same with PG's log file, with
log_statement_stats = on
But to generate these plots is costly (e.g. I don't need all the
lines starting with !), and to interpret them is equally costly. Do
you have a suggestion for a better approach?
Tschö,
Torsten.
--
Torst
Hallöchen!
Torsten Bronger writes:
> [...] Currently, I experiment with
>
> SELECT tup_returned + tup_fetched + tup_inserted + tup_updated +
> tup_deleted FROM pg_stat_database WHERE datname='chantal';
Stangely, the statistics coming out of it are extremely high. I
j
Hallöchen!
Joshua D. Drake writes:
> On Fri, 2009-02-20 at 17:11 +0100, Torsten Bronger wrote:
>
>> Yesterday I ported a web app to PG. Every 10 minutes, a cron job
>> scanned the log files of MySQL and generated a plot showing the
>> queries/sec for the last 24h. (A
moment I just
do the same with PG's log file, with
log_statement_stats = on
But to generate these plots is costly (e.g. I don't need all the
lines starting with !), and to interpret them is equally costly. Do
you have a suggestion for a better approach?
Tschö,
Torsten.
--
Torst
