Skip site navigation (1) Skip section navigation (2)

Re: New statistics for WAL buffer dirty writes

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Euler Taveira <euler(at)timbira(dot)com>, Satoshi Nagayasu <snaga(at)uptime(dot)jp>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: New statistics for WAL buffer dirty writes
Date: 2012-07-29 19:48:53
Message-ID: CA+U5nM+e7ahT5gM6gsK+NPFzdcbCs38iH0zCsqp1fnNEDa863w@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On 7 July 2012 18:06, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> Sure, but I doubt that would be as informative as this.  It's no big deal if you hit 100% every once in a while; what you really want to know is whether it's happening once per second or once per week.

Agreed.

I can't see an easy way of recording the high water mark % and I'm not
sure how we'd use it if we had it.

Let's just track how often we run out of space because that is when
bad things happen, not before.

-- 
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

pgsql-hackers by date

Next:From: Achim DommaDate: 2012-07-30 12:33:39
Subject: Passing tabular data around using python functions
Previous:From: Peter GeogheganDate: 2012-07-29 15:39:21
Subject: Help me develop new commit_delay advice

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group