| From: | Rod Taylor <pg(at)rbt(dot)ca> |
|---|---|
| To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, pgsql-hackers(at)postgresql(dot)org, Peter Brant <Peter(dot)Brant(at)wicourts(dot)gov> |
| Subject: | Re: fsutil ideas |
| Date: | 2006-02-24 15:34:13 |
| Message-ID: | 1140795253.5092.122.camel@home |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > This seems an area where providing consistent cross- platform
> behavior
> > might be difficult. Do we actually need this functionality inside the
>
> > DBMS in the first place?
>
> It sounds like we should probably just shelve the idea of sharing this
> code. It is very useful to us, since it allows a single database
> connection to monitor the health of the database and detect impending
> failure. Having our monitoring software need to know the operating
> system of each database, with security to log into the OS of each
> machine, would be far worse from a security standpoint, more fragile,
> and more work than adding these functions to the database. But no
Why don't you have a process on the machine update a set of values in
the database that you then read from remote?
You don't need to know the free diskspace in real time. A 2 minute old
value is probably just as good.
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2006-02-24 15:35:01 | Re: fsutil ideas |
| Previous Message | Kevin Grittner | 2006-02-24 15:24:15 | Re: fsutil ideas |