"Arguile" wrote:
> PostgreSQL doesn't support nested transactions nor can it distinguish
> between errors. Any error in the transaction block causes an automatic
> rollback. It's definitely convenient to be able to gracefully recover, but
> don't expect this anytime soon in Pg.
>
> (I learned this after losing ten minutes of hand typing to a typo ;).
>
>
> Tom Lane wrote on pgadmin-hackers:
>
> TL> No, the real problem is that we have only one mechanism for recovering
> TL> to a valid state after an error, and that is transaction abort.
> TL>
> TL> Distinguishing statement abort from transaction abort will require
> TL> a huge amount of work --- every transaction-or-longer-lifetime data
> TL> structure in the backend will need to be looked at, for example, to see
> TL> how it can be rolled back to the proper state after a statement abort.
> TL> It'll probably get done someday, but don't hold your breath ...
Thanks. Thats really not what I wanted to hear, but it helps ;)
Joern
--
Joern Reder -- Software Development, dimedis GmbH, 50672 Koeln
http://www.dimedis.de/ http://spirit.dimedis.de/
supporting: http://www.zyn.de/ http://www.netcologne.de/~nc-joernre/
CPAN: http://www.perl.com/CPAN/modules/by-module/CIPP/JRED/
