| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Statement-level rollback |
| Date: | 2017-03-01 15:25:06 |
| Message-ID: | 8048e93a-90d0-b444-48b2-aa8833d7d697@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
On 2/28/17 02:39, Tsunakawa, Takayuki wrote:
> I'd like to propose statement-level rollback feature. To repeat myself, this is requested for users to migrate from other DBMSs to PostgreSQL. They expect that a failure of one SQL statement should not abort the entire transaction and their apps (client programs and stored procedures) can continue the transaction with a different SQL statement.
Can you provide some references on how other systems provide this feature?
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2017-03-01 15:35:38 | Re: Possible spelling fixes |
| Previous Message | Peter Eisentraut | 2017-03-01 15:24:10 | Re: Statement-level rollback |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2017-03-01 16:05:19 | Re: Statement-level rollback |
| Previous Message | Peter Eisentraut | 2017-03-01 15:24:10 | Re: Statement-level rollback |