| From: | Matt Miller <mattm(at)epx(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL: EXCEPTION NOSAVEPOINT |
| Date: | 2005-08-03 20:32:30 |
| Message-ID: | 1123101150.3385.51.camel@dbamm01-linux |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-patches |
On Wed, 2005-08-03 at 16:25 -0400, Tom Lane wrote:
> > The idea is to allow a PL/pgSQL exception to not automatically
> > rollback the work done by the current block.
>
> This fundamentally breaks the entire backend.
Yeah, but besides that, can you quick commit this to HEAD so I don't
have to keep track of it locally?
Just kidding.
> You do not have the
> option to continue processing after elog(ERROR); the (sub)transaction
> rollback is necessary to clean up inconsistent state.
Okay, I'll look at this more closely. Can you give me an example of
what can go wrong?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-08-03 20:33:29 | Re: oids and pg_class_oid_index constraint violations |
| Previous Message | Tom Lane | 2005-08-03 20:25:30 | Re: PL/pgSQL: EXCEPTION NOSAVEPOINT |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-08-03 20:48:06 | Re: PL/pgSQL: EXCEPTION NOSAVEPOINT |
| Previous Message | Andrew Dunstan | 2005-08-03 20:28:21 | Re: openbsd, plpython, missing threading symbols |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-08-03 20:48:06 | Re: PL/pgSQL: EXCEPTION NOSAVEPOINT |
| Previous Message | Tom Lane | 2005-08-03 20:25:30 | Re: PL/pgSQL: EXCEPTION NOSAVEPOINT |