On Wed, Feb 4, 2015 at 8:08 AM, Stephen Frost <sfrost@snowman.net> wrote:
> Apologies for the confusion- the client isn't using it to determine if
> there's activity. They're using it exactly as it's intended, as I
> understand it- to check and see if the number of rollbacks is
> signifigant compared to the number of commits. The issue is that, with
> databases that have little activity, you can end up with a commit ratio
> of 50% or less. Perhaps check_postgres could have an option to only
> complain when some minimum number of transactions has been reached..
That sounds like a much better idea. pg_dump isn't really doing
anything wrong here, so "fixing" it feels like the wrong solution.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
