| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Statement-level rollback |
| Date: | 2017-02-28 13:17:17 |
| Message-ID: | 1915.1488287837@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-jdbc |
"Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> writes:
> As I stated here and at the PGConf.ASIA developer meeting last year, I'd
> like to propose statement-level rollback feature.
I do not really see how this would ever get past the compatibility
problems that forced us to give up on server-side autocommit years ago.
If you want to provide a client-side facility for this, perhaps that could
fly.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2017-02-28 13:19:12 | Avoiding bloat in CIC |
| Previous Message | Tom Lane | 2017-02-28 13:05:16 | Re: avoid bloat from CREATE INDEX CONCURRENTLY |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tsunakawa, Takayuki | 2017-03-01 08:00:49 | Re: Statement-level rollback |
| Previous Message | Tsunakawa, Takayuki | 2017-02-28 07:39:45 | Statement-level rollback |