Preamble: I use the word action below in reference to, for example, an SMTP session or the addition of user; not to an SQL transaction.
On Wed, 02 Jun 2004 15:18:03 +0200 Ilja Booij <[EMAIL PROTECTED]> wrote: > We can even let it fail with a FATAL in the event that we're > trying to set the wrong flag, as it basically is a programming > error, and we should probably shutdown if it happens. > That's debatable. While it does indicate a programming error, that shouldn't take down the server. It should make sure the database is returned to a clean state and that the current action fails with a significant error. Given that it is a programming error, realistically it will only be triggered by some bizarre bug, caused by something like being handed a message which ends with\r\r\n\rr\/\n'\r\n\r, or the digits of the remote user's IP address adding up to 42. It should certainly scream in all the relevant logs, but I don't think taking the server down is appropiate. Having said that, having a hook to force a failure would be useful in testing and some non-critical deployments. -fr. -- Feargal Reilly, Codeshifter, Chrysalink Systems. ICQ: 109837009 | YIM: ectoraige PGP Key ID: 0xE721BBE6 (expires 06-Aug-2004) Visit http://ie.bsd.net/ - BSDs presence in Ireland
pgpbbeRrKk9gY.pgp
Description: PGP signature
