From: | "Tony Wasson" <ajwasson(at)gmail(dot)com> |
---|---|
To: | "Vivek Khera" <vivek(at)khera(dot)org> |
Cc: | "Pgsql performance" <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: postgresql transaction id monitoring with nagios |
Date: | 2006-05-02 19:06:30 |
Message-ID: | 6d8daee30605021206h8170a48w94670b5d23633a72@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On 5/2/06, Vivek Khera <vivek(at)khera(dot)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.
Attachment | Content-Type | Size |
---|---|---|
check_pg_transactionids.pl | application/x-perl | 1.8 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-05-02 19:07:41 | Re: postgresql transaction id monitoring with nagios |
Previous Message | Alvaro Herrera | 2006-05-02 19:03:40 | Re: postgresql transaction id monitoring with nagios |