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: Simon Riggs <simon@2ndquadrant.com>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>, Jesper Pedersen <jesper.pedersen@redhat.com>, Robert Haas <robertmhaas@gmail.com>
Date: 2016-09-27T00:30:02Z
Lists: pgsql-hackers
On Thu, Sep 22, 2016 at 12:30 AM, Stas Kelvich <s.kelvich@postgrespro.ru> wrote:
> I’m not giving up yet, i’ll write them) I still have in mind several other patches to 2pc handling in
> postgres during this release cycle — logical decoding and partitioned hash instead of
> TwoPhaseState list.
>
> My bet that relative speed of that patches will depend on used filesystem. Like it was with the
> first patch in that mail thread it is totally possible sometimes to hit filesystem limits on file
> creation speed. Otherwise both approaches should be more or less equal, i suppose.

OK. I am marking this patch as returned with feedback then. Looking
forward to seeing the next investigations.. At least this review has
taught us one thing or two.
-- 
Michael


Commits

  1. Speedup 2PC recovery by skipping two phase state files in normal path

  2. Add tests for two-phase commit

  3. Improve grammar of message about two-phase state files.

  4. Speedup 2PC by skipping two phase state files in normal path