Horton

Re: Speedup twophase transactions

Nikhil Sontakke <nikhils@2ndquadrant.com>

View thread View on postgr.es
From: Nikhil Sontakke <nikhils@2ndquadrant.com>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Stas Kelvich <s.kelvich@postgrespro.ru>, Michael Paquier <michael.paquier@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>, Jesper Pedersen <jesper.pedersen@redhat.com>
Date: 2017-02-01T08:29:25Z
Lists: pgsql-hackers

Attachments

>> Shouldn’t the singular part of the message above be:
>> "%u two-phase state file was written for a long-running prepared transaction"
>>
>> But, then, English is not my native language, so I might be off here :-)
>
> If there's one file per long-running prepared transaction, which I
> think is true, then I agree with you.

PFA, small patch to fix this, then.

Regards,
Nikhils
-- 
 Nikhil Sontakke                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

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