Re: pg_reset_stats + cache I/O %

Поиск
Список
Период
Сортировка
От mcelroy, tim
Тема Re: pg_reset_stats + cache I/O %
Дата
Msg-id 0C4841B42F87D51195BD00B0D020F5CB044B241C@morpheus.bostonstock.com
обсуждение исходный текст
Ответ на pg_reset_stats + cache I/O %  ("mcelroy, tim" <tim.mcelroy@bostonstock.com>)
Ответы Re: pg_reset_stats + cache I/O %  ("Jim C. Nasby" <jnasby@pervasive.com>)
Список pgsql-performance

Thanks Tom, sorry I neglected to copy the list on my previous email.....

Does this query make sense and is it valid for an accurate cache % hit ratio for the entire DB?  I would assume I could use the same logic with other views such as pg_stat_user_tables to get a per table ratio?

SELECT 100 - round((blks_hit::numeric / (blks_hit::numeric + blks_read::numeric)) * 100,2)
AS "Cache % Hit"
FROM pg_stat_database
WHERE datname = 'Fix1';

<RETURNS>

Cache % Hit
--------------------
       98.06
(1 row)

Thank you,
Tim

 -----Original Message-----
From:   Tom Lane [mailto:tgl@sss.pgh.pa.us]
Sent:   Tuesday, March 07, 2006 2:37 PM
To:     mcelroy, tim
Cc:     'pgsql-performance@postgresql.org'
Subject:        Re: [PERFORM] pg_reset_stats + cache I/O %

"mcelroy, tim" <tim.mcelroy@bostonstock.com> writes:
> ERROR:  function round(double precision, integer) does not exist

Try coercing to numeric instead of float.  Also, it'd be a good idea to
put that coercion outside the sum()'s instead of inside --- summing
bigints is probably noticeably faster than summing numerics.

                        regards, tom lane

В списке pgsql-performance по дате отправления:

Предыдущее
От: "Matthew Nuzum"
Дата:
Сообщение: Re: Postgres on VPS - how much is enough?
Следующее
От: Ruben Rubio Rey
Дата:
Сообщение: Is good idea an array of 365 elements in a cell of a table, in order to perform searchs?