pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tony Wasson <ajwasson@gmail.com>
To: 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 12:06:30 -0700
Message-ID: <6d8daee30605021206h8170a48w94670b5d23633a72@mail.gmail.com> (raw)
In-Reply-To: <628A837A-9718-46BB-85D7-8A63BBB1CA32@khera.org>
References: <6d8daee30605021126o7b44e255q552dcdc676c565bf@mail.gmail.com>
	<628A837A-9718-46BB-85D7-8A63BBB1CA32@khera.org>

On 5/2/06, Vivek Khera <vivek@khera.org> wrote:
>
> On May 2, 2006, at 2:26 PM, Tony Wasson wrote:
>
> > The script detects a wrap at 2 billion. It starts warning once one or
> > more databases show an age over 1 billion transactions. It reports
> > critical at 1.5B transactions. I hope everyone out there is vacuuming
> > *all* databases often.
>
> Something seems wrong... I just ran your script against my
> development database server which is vacuumed daily and it said I was
> 53% of the way to 2B.  Seemed strange to me, so I re-ran "vacuum -a -
> z" to vacuum all databases (as superuser), reran the script and got
> the same answer.

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.

Attachments:

  check_pg_transactionids.pl (application/x-perl, 1.8K) download

view thread (10+ messages)  latest in thread

Message-ID: <6d8daee30605021206h8170a48w94670b5d23633a72@mail.gmail.com>
Permalink:  ../6d8daee30605021206h8170a48w94670b5d23633a72@mail.gmail.com/
Also on:    postgresql.org/message-id/6d8daee30605021206h8170a48w94670b5d23633a72@mail.gmail.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: ajwasson@gmail.com, vivek@khera.org
  Subject: Re: postgresql transaction id monitoring with nagios
  In-Reply-To: <6d8daee30605021206h8170a48w94670b5d23633a72@mail.gmail.com>
  References: <6d8daee30605021126o7b44e255q552dcdc676c565bf@mail.gmail.com> <628A837A-9718-46BB-85D7-8A63BBB1CA32@khera.org> <6d8daee30605021206h8170a48w94670b5d23633a72@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