| From: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Performance problems |
| Date: | 2003-04-25 15:46:44 |
| Message-ID: | 200304252116.44974.shridhar_daithankar@nospam.persistent.co.in |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Friday 25 April 2003 21:13, Dennis Gearon wrote:
> You know,
> It'd be nice if there was a system table, or command that showed the
> number and/or percentage of tuples needing to be vacuumed. If table are
> only affected by tuples formerly in them, then the table/function could
> show the value per table. If any discarded tuples affect all tables, then a
> global table/function would be warranted.
>
> A minimally compute intensive chron job or ON DELETE trigger could then
> call vacuum full at a certain percentage. Also, what kind of memory
> management ( in the postgres application ) could be written that pushes
> deleted/unused tuples out of any caches or scopes to at least lengthen the
> time between vacuums?
Why don't you take a look at pgavd? It will periodically connect to database
and check if it needs vacuum. just that it won't issue vacuum full because it
locks table and IMO only administrator should do it.
http://gborg.postgresql.org/project/pgavd/projdisplay.php
Shridhar
| From | Date | Subject | |
|---|---|---|---|
| Next Message | marco | 2003-04-25 15:55:43 | Re: Performance problems |
| Previous Message | Dennis Gearon | 2003-04-25 15:43:23 | Re: Performance problems |