| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com> |
| Subject: | Re: Statement-level rollback |
| Date: | 2018-12-08 04:24:29 |
| Message-ID: | CA+TgmobUtQi53-xC3=-thtKWaSiUyp5tye05WBtHB=PjoMNALA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Dec 7, 2018 at 7:25 PM Alexander Korotkov
<a(dot)korotkov(at)postgrespro(dot)ru> wrote:
> The first thing, which comes to the mind is undo log. When you have
> undo log, then on new subtransaction you basically memorize the
> current undo log position. If subtransaction rollbacks, you have to
> just play back undo log until reach memorized position. This might be
> an option for zheap. But actually, I didn't inspect zheap code to
> understand how far we're from this.
Yeah, zheap works this way.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2018-12-08 04:29:16 | Re: Statement-level rollback |
| Previous Message | Michael Paquier | 2018-12-08 03:54:52 | Re: [HACKERS] Bug when dumping "empty" operator classes |