| From: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
|---|---|
| To: | 'Robert Haas' <robertmhaas(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Statement-level rollback |
| Date: | 2017-03-07 00:33:18 |
| Message-ID: | 0A3221C70F24FB45833433255569204D1F6AC0A2@G01JPEXMBYT05 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Robert Haas
> >> Can you provide some references on how other systems provide this feature?
> >
> > Oracle doesn't.
>
> Really?
Sorry, my sentence was misleading.
I meant by "Oracle/MySQL doesn't" that they do not provide a configuration parameter or START TRANSACTION mode to choose between statement rollback and transaction rollback. They just rolls back the failed statement. I wish Postgres could behave the same way.
Regards
Takayuki Tsunakawa
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-03-07 00:40:01 | Re: dump a comment of a TSDictionary |
| Previous Message | Andres Freund | 2017-03-07 00:04:19 | Re: Performance degradation in TPC-H Q18 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | legrand legrand | 2017-03-07 20:49:29 | Re: Statement-level rollback |
| Previous Message | Robert Haas | 2017-03-06 18:24:00 | Re: Statement-level rollback |