Skip site navigation (1) Skip section navigation (2)

Re: How to Trigger An Automtic Vacuum on Selected Tables

From: "Dario" <dario_d_s(at)unitech(dot)com(dot)ar>
To: <pgsql-performance(at)postgresql(dot)org>
Subject: Re: How to Trigger An Automtic Vacuum on Selected Tables
Date: 2005-09-30 00:05:45
Message-ID: MHEDJHCKDNOEHJKHIOCJAEPCCHAA.dario_d_s@unitech.com.ar (view raw or flat)
Thread:
Lists: pgsql-performance
Autovacuum does exactly what I understood you want :-)

-----Mensaje original-----
De: pgsql-performance-owner(at)postgresql(dot)org
[mailto:pgsql-performance-owner(at)postgresql(dot)org]En nombre de Lane Van
Ingen
Enviado el: jueves, 29 de septiembre de 2005 20:06
Para: pgsql-performance(at)postgresql(dot)org
Asunto: [PERFORM] How to Trigger An Automtic Vacuum on Selected Tables


I am running version 8.0.1 on Windows 2003. I have an application that
subjects PostgreSQL to sudden bursts of activity at times which cannot be
predicted. The bursts are significant enough to cause performance
degradation, which can be fixed by a 'vacuum analyze'.

I am aware of the existence and contents of tables like pg_class.

QUESTION: I would like to trigger a vacuum analyze process on a table
whenever it gets a large enough burst of activity to warrant it. Using the
data in pg_class (like the number of pages the system found the last time it
was vacuumed / analyzed), I would like to compare those statistics to
current size, and trigger a vacuum/analyze on a table if needed.

Does anyone know of any available tools, or an approach I could use, to
determine what the CURRENT SIZE is ?



---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
       choose an index scan if your joining column's datatypes do not
       match


In response to

pgsql-performance by date

Next:From: DarioDate: 2005-09-30 00:22:42
Subject: Re: Is There Any Way ....
Previous:From: Lane Van IngenDate: 2005-09-29 23:21:08
Subject: Is There Any Way ....

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group