| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Speedup twophase transactions |
| Date: | 2016-01-09 18:27:13 |
| Message-ID: | CANP8+j+6bz4LzFX0uqjYMzNm3MVU1eBx+L7no2eT5c7i0GhB2Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9 January 2016 at 12:26, Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru> wrote:
> I’ve updated patch and wrote description of thighs that happens
> with 2PC state data in the beginning of the file. I think now this patch
> is well documented,
> but if somebody points me to places that probably requires more detailed
> description I’m ready
> to extend that.
>
Your comments say
"In case of crash replay will move data from xlog to files, if
that hasn't happened before."
but I don't see that in code. Can you show me where that happens?
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2016-01-09 18:27:47 | Re: pgsql: Avoid pin scan for replay of XLOG_BTREE_VACUUM |
| Previous Message | Andres Freund | 2016-01-09 18:08:47 | Re: pgsql: Avoid pin scan for replay of XLOG_BTREE_VACUUM |