| From: | Alex Vinogradovs <AVinogradovs(at)Clearpathnet(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: PG_TRY(), PG_CATCH().... |
| Date: | 2007-10-09 17:41:06 |
| Message-ID: | 1191951666.34056.12.camel@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2007-10-09 18:09:04 | Re: DB upgrade |
| Previous Message | Scott Marlowe | 2007-10-09 17:12:53 | Re: Solutions for listening on multiple ports? |