No, I'm not worried about them failing. My code isn't transactional...
I'm just worried about getting whole bunch of warnings about reference
leaks.
On Tue, 2007-10-09 at 09:59 -0400, Alvaro Herrera wrote:
> The only code that knows how to cleanup completely after transaction
> failure is the subtransaction code. If you need to do something that
> may cause a transaction abort, then you must use subtransactions.
>
> (You could of course write "your own layer" but it would duplicate
> subtransaction start/abort so there wouldn't be any point.)
>
> It's expensive, yes, but there are good reasons for that. If you are
> worried about that, I'm sure there are optimizations possible.
>
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org/
