<p><font size="2">> In general I don't think it even makes sense to think of making<br /> > executor rollback
non-transactional.<br/><br /> Agreed.<br /><br /> I would not want to rollback some statements and not others within
a<br/> transaction. I would like a complete rollback to happen, but only when<br /> the exception propogates out of
theexception block unhandled, not when<br /> the exception is first thrown. Maybe if I could get into the TRY<br />
sectionof the PG_CATCH()/PG_TRY() construct without an intervening<br /> elog(ERROR) then I'd have a chance ...<br
/><br/> > Seems like your choices are<br /> > ...<br /> > implementing a separate expression evaluator<br />
>...<br /> > make the restriction "read-only database access"<br /> > ...<br /><br /> Thanks for all these
ideas. I'm just getting to know the PG code tree,<br /> and I appreciate the guidance.</font>