you've posted the tutorial "error then die" use which is not useful in a production environment.
If you're referring to apache error template, that's not error handling and should be a last resort. There could multiple sources of failure and you want to customize the error page you show the user according to the source (registered user / administrator / anonymous visitor etc.) as well as the cleanup process.
Part of the cleanup is preserving environment data (such as POST data) and logging it silently. Having the webserver redirect automatically on error is the same as redirecting manually so there is no difference. In either case, you mostly wouldn't the user to be able to refresh and cause the same error again.
I still think you guys are wrong...
Since all of us devil's advocates are thinking the same, and seeing as we are all experienced developers, you'll have to be a little more detailed in your reasoning to convince us..