On Dienstag, 8. April 2008 paul rivers wrote:
> I don't see a direct way to monitor bloat from pg_stat*. If I'm
> wrong, please set me straight.
>
> For example, monitoring index bloat would involve deciding how many
> pages an index would ideally consume, based on either sampling the
> table yourself or raiding stats, and making assumptions. Then you'd
> compare to actual (or approximated actual) and decide if you were
> within whatever threshold you think is OK.
If there's no rule of thumb, how could you manually decide on actions,
other than by reading from a crystal ball?
Also, if there are no tools, almost no admin can/will do anything.
Except for the specialist having too much free time to dig into the db
just for fun and reading tons of pg_stat* tables and values *g*
As most won't have that funny time, tools which show possible problems
or performance losses would greatly help.
On Dienstag, 8. April 2008 Jeff Frost wrote:
> I don't know about rrd graphing it, but there are some great nagios
> plugins for this at http://bucardo.org/nagios
>
> You could have a look at the queries used in those and roll your own
> mrtg plugins. If you do, please share.
Thank you. I'll have a look at that nagios plugins.
mfg zmi
--
// Michael Monnerie, Ing.BSc ----- http://it-management.at
// Tel: 0676/846 914 666 .network.your.ideas.
// PGP Key: "curl -s http://zmi.at/zmi.asc | gpg --import"
// Fingerprint: AC19 F9D5 36ED CD8A EF38 500E CE14 91F7 1C12 09B4
// Keyserver: www.keyserver.net Key-ID: 1C1209B4