Re: Speedup twophase transactions
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Stas Kelvich <s.kelvich@postgrespro.ru>
Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>, Jesper Pedersen <jesper.pedersen@redhat.com>
Date: 2016-04-12T22:04:18Z
Lists: pgsql-hackers
On Wed, Apr 13, 2016 at 1:53 AM, Stas Kelvich <s.kelvich@postgrespro.ru> wrote: >> On 12 Apr 2016, at 15:47, Michael Paquier <michael.paquier@gmail.com> wrote: >> >> It looks to be the case... The PREPARE phase replayed after the >> standby is restarted in recovery creates a series of exclusive locks >> on the table created and those are not taken on HEAD. Once those are >> replayed the LOCK_STANDBY record is conflicting with it. In the case >> of the failure, the COMMIT PREPARED record cannot be fetched from >> master via the WAL stream so the relation never becomes visible. > > Yep, it is. It is okay for prepared xact hold a locks for created/changed tables, > but code in standby_redo() was written in assumption that there are no prepared > xacts at the time of recovery. I’ll look closer at checkpointer code and will send > updated patch. > > And thanks again. That's too late for 9.6 unfortunately, don't forget to add that in the next CF! -- Michael
Commits
-
Speedup 2PC recovery by skipping two phase state files in normal path
- 728bd991c3c4 10.0 landed
-
Add tests for two-phase commit
- 30820982b295 10.0 landed
-
Improve grammar of message about two-phase state files.
- 38c363adf497 10.0 landed
-
Speedup 2PC by skipping two phase state files in normal path
- 978b2f65aa12 9.6.0 cited