Re: postgresql transaction id monitoring with nagios - Mailing list pgsql-performance

From Bruno Wolff III
Subject Re: postgresql transaction id monitoring with nagios
Date
Msg-id 20060502201928.GB14674@wolff.to
Whole thread Raw
In response to Re: postgresql transaction id monitoring with nagios  ("Tony Wasson" <ajwasson@gmail.com>)
Responses Re: postgresql transaction id monitoring with nagios  ("Tony Wasson" <ajwasson@gmail.com>)
List pgsql-performance
On Tue, May 02, 2006 at 12:06:30 -0700,
  Tony Wasson <ajwasson@gmail.com> wrote:
>
> Ah thanks, it's a bug in my understanding of the thresholds.
>
> "With the standard freezing policy, the age column will start at one
> billion for a freshly-vacuumed database."
>
> So essentially, 1B is normal, 2B is the max. The logic is now..
>
> The script detects a wrap at 2 billion. It starts warning once one or
> more databases show an age over 1.5 billion transactions. It reports
> critical at 1.75B transactions.
>
> If anyone else understands differently, hit me with a clue bat.

Isn't this obsolete now anyway? I am pretty sure 8.1 has safeguards against
wrap around.

pgsql-performance by date:

Previous
From: "Jim C. Nasby"
Date:
Subject: Re: Why so slow?
Next
From: Tom Lane
Date:
Subject: Re: Why is plan (and performance) different on partitioned table?