| From: | Nikhil Sontakke <nikhils(at)2ndquadrant(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Stas Kelvich <s(dot)kelvich(at)postgrespro(dot)ru>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>, Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: Speedup twophase transactions |
| Date: | 2017-01-27 11:01:38 |
| Message-ID: | CAMGcDxdE0gs2i5doxZhF4Ko0jRfXEfvdnSix5tbXMr1xGqqoaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 27 January 2017 at 15:37, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On 27 January 2017 at 09:59, Nikhil Sontakke <nikhils(at)2ndquadrant(dot)com> wrote:
>>>> But, I put the recovery process and the checkpointer process of the
>>>> standby under gdb with breakpoints on these functions, but both did
>>>> not hit CreateRestartPoint() as well as CheckPointGuts() when I issued
>>>> a promote :-|
>>>
>>> No end-of-recovery checkpoints happen at promotion since 9.3. You can
>>> still use fallback_promote as promote file to trigger the pre-9.2 (9.2
>>> included) behavior.
>>
>> Ok, so that means, we also need to fsync out these 2PC XIDs at promote
>> time as well for their durability.
>
> Why?
The xact_redo code will add prepared transactions to the
KnownPreparedList in memory. Earlier it used to create the on-disk 2PC
file.
At standby promote, the surviving (yet uncommitted) prepared
transactions from KnownPreparedList need to be persisted, right?
Regards,
Nikhils
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2017-01-27 11:04:06 | Re: Push down more full joins in postgres_fdw |
| Previous Message | Simon Riggs | 2017-01-27 10:07:46 | Re: Speedup twophase transactions |