From: Bruno Wolff III <bruno@wolff.to>
To: Tony Wasson <ajwasson@gmail.com>
Cc: Vivek Khera <vivek@khera.org>
Cc: Pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: postgresql transaction id monitoring with nagios
Date: Tue, 2 May 2006 15:19:29 -0500
Message-ID: <20060502201928.GB14674@wolff.to> (raw)
In-Reply-To: <6d8daee30605021206h8170a48w94670b5d23633a72@mail.gmail.com>
References: <6d8daee30605021126o7b44e255q552dcdc676c565bf@mail.gmail.com>
<628A837A-9718-46BB-85D7-8A63BBB1CA32@khera.org>
<6d8daee30605021206h8170a48w94670b5d23633a72@mail.gmail.com>
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: bruno@wolff.to, ajwasson@gmail.com, vivek@khera.org
Subject: Re: postgresql transaction id monitoring with nagios
In-Reply-To: <20060502201928.GB14674@wolff.to>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox