On 5/2/06, Dan Harris <[EMAIL PROTECTED]> wrote:
My database is used primarily in an OLAP-type environment. Sometimes my
users get a little carried away and find some way to slip past the
sanity filters in the applications and end up bogging down the server
with queries that run for hours and ho
On 5/2/06, Bruno Wolff III <[EMAIL PROTECTED]> wrote:
On Tue, May 02, 2006 at 12:06:30 -0700,
Tony Wasson <[EMAIL PROTECTED]> wrote:
>
> Ah thanks, it's a bug in my understanding of the thresholds.
>
> "With the standard freezing policy, the age column will st
On 5/2/06, Vivek Khera <[EMAIL PROTECTED]> 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 ho
ransactions. It reports
critical at 1.5B transactions. I hope everyone out there is vacuuming
*all* databases often.
Hope some of you can use this script!
Tony Wasson
check_pg_transactionids.pl
Description: Perl program
---(end of broadcast)---
TIP 2:
On 9/28/05, Matthew Nuzum <[EMAIL PROTECTED]> wrote:
> On 9/28/05, Arnau <[EMAIL PROTECTED]> wrote:
> > Hi all,
> >
> >I have been "googling" a bit searching info about a way to monitor
> > postgresql (CPU & Memory, num processes, ... ) and I haven't found
> > anything relevant. I'm using munin
