| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Matt Miller <mattm(at)epx(dot)com> |
| Cc: | pgsql-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: PL/pgSQL: EXCEPTION NOSAVEPOINT |
| Date: | 2005-08-03 20:25:30 |
| Message-ID: | 3738.1123100730@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-patches |
Matt Miller <mattm(at)epx(dot)com> writes:
> 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. You do not have the
option to continue processing after elog(ERROR); the (sub)transaction
rollback is necessary to clean up inconsistent state.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matt Miller | 2005-08-03 20:32:30 | Re: PL/pgSQL: EXCEPTION NOSAVEPOINT |
| Previous Message | Matt Miller | 2005-08-03 19:58:13 | PL/pgSQL: EXCEPTION NOSAVEPOINT |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-08-03 20:28:21 | Re: openbsd, plpython, missing threading symbols |
| Previous Message | Matt Miller | 2005-08-03 19:58:13 | PL/pgSQL: EXCEPTION NOSAVEPOINT |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Matt Miller | 2005-08-03 20:32:30 | Re: PL/pgSQL: EXCEPTION NOSAVEPOINT |
| Previous Message | Matt Miller | 2005-08-03 19:58:13 | PL/pgSQL: EXCEPTION NOSAVEPOINT |