| From: | Bèrto ëd Sèra <berto(dot)d(dot)sera(at)gmail(dot)com> |
|---|---|
| To: | Kasia Tuszynska <ktuszynska(at)esri(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: transaction error handling |
| Date: | 2011-12-01 07:18:10 |
| Message-ID: | CAKwGa_-LqpPHt-U20eJ2_tz4JWt3ET80d1Z5Ww8t3xTs9yM4FA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-bugs |
Hi
On 30 November 2011 22:30, Kasia Tuszynska <ktuszynska(at)esri(dot)com> wrote:
> With Postgres that is not the case, if the 50th sql statement in a long
> transaction incurs an error, the whole transaction is rolled back for you
> automatically, you the developer have no say in that unless you bracket
> each statement with a savepoint creation and destruction, just to be able
> to capture the potential error that may arise on that 50th sql statement.
>
Thanks, now I finally got what you meant.
Bèrto
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hellmuth Vargas | 2011-12-01 19:21:20 | problem with restore: collision id`s lob |
| Previous Message | M. D. | 2011-12-01 00:05:48 | Re: Read Only Role |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Davis | 2011-12-01 07:21:41 | Re: possible bug seen with -DCLOBBER_CACHE_ALWAYS and changing GUCs |
| Previous Message | Suneel Kumar M | 2011-12-01 04:19:29 | Postgre Cross compilation for coldfire processor. |