From: Tony Wasson <ajwasson@gmail.com>
To: Bruno Wolff III <bruno@wolff.to>
To: Tony Wasson <ajwasson@gmail.com>
To: Vivek Khera <vivek@khera.org>
To: Pgsql performance <pgsql-performance@postgresql.org>
Subject: Re: postgresql transaction id monitoring with nagios
Date: Tue, 2 May 2006 13:50:43 -0700
Message-ID: <6d8daee30605021350p4172bbc5w7ecf87573099abd9@mail.gmail.com> (raw)
In-Reply-To: <20060502201928.GB14674@wolff.to>
References: <6d8daee30605021126o7b44e255q552dcdc676c565bf@mail.gmail.com>
<628A837A-9718-46BB-85D7-8A63BBB1CA32@khera.org>
<6d8daee30605021206h8170a48w94670b5d23633a72@mail.gmail.com>
<20060502201928.GB14674@wolff.to>
On 5/2/06, Bruno Wolff III <bruno@wolff.to> wrote:
> 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.
My motivation was primarily to monitor some existing PostgreSQL 8.0
servers. I'm not convinced it is "safe" to stop worrying about
transaction ids even on an 8.1 box.
It is comforting that 8.1 does safeguard against wraparound in at
least 2 ways. First, it emits a warnings during the last 10 million
transactions. If you manage to ignore all those, posgresql will shut
down before a wraparound. I think PostgreSQL does everything correctly
there, but I suspect someone will run into the shut down daemon
problem.
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: ajwasson@gmail.com, bruno@wolff.to, vivek@khera.org
Subject: Re: postgresql transaction id monitoring with nagios
In-Reply-To: <6d8daee30605021350p4172bbc5w7ecf87573099abd9@mail.gmail.com>
* 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