There are many differences.On Wed, Aug 17, 2011 at 9:38 PM, Sim Zacks <sim@compulab.co.il> wrote:The point was not whether I have a bug in an external application, the point is that I need an external application which creates more overhead and another point of failure in the application stack.1) Not sure how an external python script is different from a PL/Python sproc except that the former exists external to transaction control.
Its not a question of whether I can or cannot build redundancy, it is a question of whether I have to build an entire system in order to call a database function from another database function. The only reason this is complicated is because it needs to be in its own session. That simple issue shouldn't force me to build: a) a daemon application, b) include redundancy to ensure that it is running, c) not be included in my database backup/restore.2) there is absolutely no reason you can't build redundancy into this system.
Any overhead that is not necessary should not be added in. It is the minor level of frustration that something didn't work when I migrated servers until the "Oh Yeah" kicked in. Then looking through all my notes to find the compilation instructions for my daemon because we moved from a 32 bit server to a 64 bit. Then trying to figure out the syntax for the init script, because we moved from Gentoo to Debian and it is slightly different. It isn't a lot of overhead but it is completely unneccessary in our situation.3) The overhead really shouldn't be bad, and if your parts are well-modularized, and carefully designed overhead really should be minimal.
Best Wishes, Chris Travers
Sim