On Thu, Mar 09, 2006 at 08:13:30AM -0500, mcelroy, tim wrote:
> charts showing system and in this case DB performance. I'm basically just
> using the out-of-the-box defaults in my postgresql.conf file and that seems
Ugh... the default config won't get you far. Take a look here:
http://www.powerpo
Title: RE: [PERFORM] pg_reset_stats + cache I/O %
Sorry I realized your fears :)
PostgreSQL is a new (last four months) install here and I'm responsible for it. Great DB and I enjoy working with it a lot and learning the nuances of it. Keep in mind that the management are
On Wed, Mar 08, 2006 at 01:35:35PM -0500, mcelroy, tim wrote:
> I actually need this info as I was tasked by management to provide it. Not
> sure if they understand that or not, I do but management does like to see
> how well the system and its components are performing. Also, I would
> utilize t
Title: RE: [PERFORM] pg_reset_stats + cache I/O %
I actually need this info as I was tasked by management to provide it. Not sure if they understand that or not, I do but management does like to see how well the system and its components are performing. Also, I would utilize these results
k you,
> Tim
>
> -Original Message-
> From: Tom Lane [mailto:[EMAIL PROTECTED]
> 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 %
>
Title: RE: [PERFORM] pg_reset_stats + cache I/O %
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
"mcelroy, tim" <[EMAIL PROTECTED]> 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 summi
Title: pg_reset_stats + cache I/O %
Good afternoon,
Relatively new to PostgreSQL and have been assigned the task of capturing cache I/O % hits. I figured out (thanks to other posts) how to turn on the capture and what stats to (kind of) capture. I did find a view in the archives as shown be
