| From: | Alvaro Herrera <alvherre(at)commandprompt(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:03:40 |
| Message-ID: | 20060502190340.GG15291@surnet.cl |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Vivek Khera 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.
That's right, because a database's age is only decremented in
database-wide vacuums. (Wow, who wouldn't want a person-wide vacuum if
it did the same thing ...)
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tony Wasson | 2006-05-02 19:06:30 | Re: postgresql transaction id monitoring with nagios |
| Previous Message | Vivek Khera | 2006-05-02 18:50:04 | Re: postgresql transaction id monitoring with nagios |