| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Henry Combrinck" <henry(at)zen(dot)co(dot)za> |
| Cc: | pgsql-bugs(at)postgresql(dot)org, Joe Conway <mail(at)joeconway(dot)com> |
| Subject: | Re: BUG #4203: perform dblink() in begin/exception returns wrong SQLSTATE code |
| Date: | 2008-05-27 15:56:43 |
| Message-ID: | 28639.1211903803@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
"Henry Combrinck" <henry(at)zen(dot)co(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomasz Rybak | 2008-05-27 19:14:23 | BUG #4204: COPY to table with FK has memory leak |
| Previous Message | Henry Combrinck | 2008-05-27 15:13:26 | BUG #4203: perform dblink() in begin/exception returns wrong SQLSTATE code |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-05-27 16:08:07 | Re: Doc patch: type modifiers |
| Previous Message | Jeff Davis | 2008-05-27 15:22:22 | Doc patch: type modifiers |