"Henry Combrinck" <henry@zen.co.za> writes:
> Description: perform dblink() in begin/exception returns wrong
> SQLSTATE code
> The code returned is always 42601 (syntax_error) irrespective of the actual
> error (eg, unique_violation).
Yeah, the dblink code should probably try a bit harder to propagate the
original error fields. I'm inclined to think that it should propagate
sqlstate/message/detail/hint verbatim, and indicate the fact that this
happened on a dblink connection as CONTEXT, rather than structuring the
ereport the way it does now. Joe, what do you think?
regards, tom lane