From: | Hervé Piedvache <herve(at)elma(dot)fr> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | vacuum log are difficult to read ... |
Date: | 2004-03-12 16:17:21 |
Message-ID: | 200403121717.21384.herve@elma.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
I know that we have more and more details to show, during vacuum analyze ...
but since v7.4.x it's not really easy to read quicly a vacuum analyze to see
important points ... like elapsed time or number of tupples deleted...
I would like to know first if you could make an effort about this ... only for
human use ... ;o)
And also if it's possible to have a report of the abnormal situations ... may
be something like the point I had once, with the number of pages for the
table really cheaper than the pages of my index for the same table ...
Is it possible in a vacuum also to get informations about the quality of the
parameters of the database .. for example the size of some parameters that
are not in adequation with the data (pages, size of index etc.) we have in
reality ... I don't know if my request is possible, but if so it could be a
good opportunity for some tuning points, isn't it ?
I hope I'm clear with my demand ;o)
Regards,
--
Hervé Piedvache
Elma Ingénierie Informatique
6 rue du Faubourg Saint-Honoré
F-75008 - Paris - France
Pho. 33-144949901
Fax. 33-144949902
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-03-12 16:23:14 | Re: Performance and WAL on big inserts/updates |
Previous Message | Robert Treat | 2004-03-12 15:56:40 | Re: The Name Game: postgresql.net vs. pgfoundry.org |