Re: exception handling in plpgsql - Mailing list pgsql-hackers

From Korry
Subject Re: exception handling in plpgsql
Date
Msg-id 1104625808.7784.4.camel@sakai
Whole thread Raw
In response to Re: exception handling in plpgsql  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sat, 2005-01-01 at 14:10 -0500, Tom Lane wrote: <blockquote type="CITE"><pre>
<font color="#000000">Korry <<a href="mailto:korry@starband.net">korry@starband.net</a>> writes:</font>
<font color="#000000">> It seems you can’t trap every condition listed in errocodes-</font>
<font color="#000000">> appendix.html; in particular, you can’t trap SUCCESSFUL_COMPLETION, any</font>
<font color="#000000">> of the conditions listed in the WARNING category, or any of the</font>
<font color="#000000">> conditions listed in the NO DATA category.  (At least through 8.0 rc1 -</font>
<font color="#000000">> I haven't checked in later versions).</font>

<font color="#000000">Those aren't errors.</font>
</pre></blockquote><br /> Right.  Just trying to clarify the issue for the person that asked the question.  <br /><br
/>The pl/pgSQL documentation (37.7.5) says:<br /><br /> > The <tt>condition</tt> names can be any of those shown in
<ahref="file:///usr/local/pg800b5/doc/postgresql/html/errcodes-appendix.html">Appendix A</a>.<br /><br /> As you say,
notall of the conditions listed in Appendix A are error conditions.  Perhaps 37.7.5 should be changed to clarify? 
Withoutlooking at plerrcodes.h, you can't find a definitive list.<br /><br /><br />         -- Korry<br /><br /> 

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: 'COPY ... FROM' inserts to btree, blocks on buffer
Next
From: Bruce Momjian
Date:
Subject: Re: [PATCHES] Bgwriter behavior