On Mon, Jun 5, 2017 at 7:24 AM, Noah Misch <n...@leadboat.com> wrote:
> [Action required within three days. This is a generic notification.]
> The above-described topic is currently a PostgreSQL 10 open item. Simon,
> since you committed the patch believed to have created it, you own this open
> item. If some other commit is more relevant or if this does not belong as a
> v10 open item, please let us know. Otherwise, please observe the policy on
> open item ownership and send a status update within three calendar days of
> this message. Include a date for your subsequent status update. Testers may
> discover new open items at any time, and I want to plan to get them all fixed
> well in advance of shipping v10. Consequently, I will appreciate your efforts
> toward speedy resolution. Thanks.
I have just provided a patch that takes care of solving this issue and
cleans up the lock handling for all the 2PC redo code paths.
Sent via pgsql-hackers mailing list (firstname.lastname@example.org)
To make changes to your subscription: