| From: | Scott Marlowe <scott(dot)marlowe(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-11-29 20:43:55 |
| Message-ID: | CAOR=d=2Wv23iA_i740TLvmapwAxNf3N08xDH-yAmS0H31YhP7w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-bugs |
On Tue, Nov 29, 2011 at 10:57 AM, Kasia Tuszynska <ktuszynska(at)esri(dot)com> wrote:
> Postgres:
> Begin transaction
> Insert - no error
> Insert - error raised
> Transaction loss = no implicit rollback to the single error free insert.
>
> Is this a correct interpretation of the Postgres transaction error handling?
> If so, are there any changes being considered, or perhaps already implemented?
You can insert a savepoint explicitly if you wish, but without setting
one, then the whole transaction will be rolled back.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Walter Hurry | 2011-11-29 20:49:35 | Re: transaction error handling |
| Previous Message | Kasia Tuszynska | 2011-11-29 20:34:44 | Re: transaction error handling |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Walter Hurry | 2011-11-29 20:49:35 | Re: transaction error handling |
| Previous Message | Kasia Tuszynska | 2011-11-29 20:34:44 | Re: transaction error handling |