Re: BUG #4203: perform dblink() in begin/exception returns wrong SQLSTATE code - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4203: perform dblink() in begin/exception returns wrong SQLSTATE code
Date
Msg-id 28639.1211903803@sss.pgh.pa.us
Whole thread Raw
In response to BUG #4203: perform dblink() in begin/exception returns wrong SQLSTATE code  ("Henry Combrinck" <henry@zen.co.za>)
Responses Re: BUG #4203: perform dblink() in begin/exception returns wrong SQLSTATE code  (Joe Conway <mail@joeconway.com>)
List pgsql-bugs
"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

pgsql-bugs by date:

Previous
From: "Henry Combrinck"
Date:
Subject: BUG #4203: perform dblink() in begin/exception returns wrong SQLSTATE code
Next
From: "Tomasz Rybak"
Date:
Subject: BUG #4204: COPY to table with FK has memory leak