pg.ddx.io pgsql-admin@postgresql.org mailing list archive
help / color / mirror / Atom feedDoes anyone have a script to monitor if FSM settings are sufficient?
2+ messages / 2 participants
[nested] [flat]
* Does anyone have a script to monitor if FSM settings are sufficient?
@ 2005-01-30 01:50 Ron Mayer <rm_pg@cheapcomplexdevices.com>
0 siblings, 1 reply; 2+ messages in thread
From: Ron Mayer @ 2005-01-30 01:50 UTC (permalink / raw)
To: pgsql-admin
I may be implementing a database at a customer's site that would
ideally run administration free for a year or so -- or at least
be able to have scripts detect proactively if they'd need to call
us for support before the system starts behaving poorly.
Is there a way to parse the output of "vacuum" to tell me
if my fsm settings aren't big enough to keep up, and or
indicate a need to vacuum more frequently?
Or am I better off looking at something else? Like perhaps
log_min_duration_statement and tell them to call us if
we see statements getting slow for any reason?
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: Does anyone have a script to monitor if FSM settings are sufficient?
@ 2005-01-30 06:53 Uwe C. Schroeder <uwe@oss4u.com>
parent: Ron Mayer <rm_pg@cheapcomplexdevices.com>
0 siblings, 0 replies; 2+ messages in thread
From: Uwe C. Schroeder @ 2005-01-30 06:53 UTC (permalink / raw)
To: Ron Mayer <rm_pg@cheapcomplexdevices.com>; pgsql-admin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
What I'm doing in a case like that is have the system send a copy of the
vacuum etc. messages to my email account. So I check in on those values once
in a while and if I think I need to become active I actually call the
customer and tell him it's time to do some maintenance.
Most customers appreciate the cost free service of monitoring the thing for
them. Well, you'd certainly have to disclose up front that you'll be getting
system information emails sent.
UC
On Saturday 29 January 2005 05:50 pm, Ron Mayer wrote:
> I may be implementing a database at a customer's site that would
> ideally run administration free for a year or so -- or at least
> be able to have scripts detect proactively if they'd need to call
> us for support before the system starts behaving poorly.
>
>
> Is there a way to parse the output of "vacuum" to tell me
> if my fsm settings aren't big enough to keep up, and or
> indicate a need to vacuum more frequently?
>
> Or am I better off looking at something else? Like perhaps
> log_min_duration_statement and tell them to call us if
> we see statements getting slow for any reason?
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
- --
Open Source Solutions 4U, LLC 2570 Fleetwood Drive
Phone: +1 650 872 2425 San Bruno, CA 94066
Cell: +1 650 302 2405 United States
Fax: +1 650 872 2417
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
iD8DBQFB/IR6jqGXBvRToM4RAu7bAKCEICnKCy13ptyxHhjQlZePArVwpACgzGfX
rm5jWNtKkSnxF/FWGlZyrQU=
=Yj52
-----END PGP SIGNATURE-----
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2005-01-30 06:53 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-01-30 01:50 Does anyone have a script to monitor if FSM settings are sufficient? Ron Mayer <rm_pg@cheapcomplexdevices.com>
2005-01-30 06:53 ` Uwe C. Schroeder <uwe@oss4u.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox