Guillaume Smet <guillaume.smet@gmail.com> writes:
> A customer of us recently wanted to separate user errors from system
> errors as different teams are working on these 2 types of errors and
> while they might want to ignore user errors (bad-written SQL queries
> and so on), they want to be sure system errors are analyzed carefully.
> A good way to differentiate the 2 types of errors is to use the SQL state.
This might or might not be worth doing, but it seems pretty nearly
entirely useless for the claimed purpose. What is your division between
"user errors" and "system errors", and how will the SQLSTATE help you
make that?
regards, tom lane