On Tue, 2010-01-12 at 17:41 -0500, Greg Smith wrote: > Bruce Momjian wrote: > > Right, so what is the risk of shipping without any fancy monitoring? > > > > You can monitor the code right now by watching the output shown in the > ps display and by trolling the database logs. If I had to I could build > a whole monitoring system out of those components, it would just be very > fragile. I'd rather see one or two very basic bits of internals exposed > beyond those to reduce that effort.
Considering that is pretty much the best we can do with log shipping, I would have to agree. We should either provide real monitoring facilities (not necessarily tools, but at least queries or an api) for the feature or the feature isn't ready to go in. > I think it's a stretch to say that > request represents a design change; a couple of UDFs to expose some > internals is all I think it would take to dramatically drop the amount > of process/log scraping required here to support a SR system. Bingo. Joshua D. Drake -- PostgreSQL.org Major Contributor Command Prompt, Inc: http://www.commandprompt.com/ - 503.667.4564 Consulting, Training, Support, Custom Development, Engineering Respect is earned, not gained through arbitrary and repetitive use or Mr. or Sir. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
