Re: pgsql: Workaround for RecoverPreparedTransactions()

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-committers <pgsql-committers(at)postgresql(dot)org>
Subject: Re: pgsql: Workaround for RecoverPreparedTransactions()
Date: 2017-04-26 15:07:57
Message-ID: CANP8+j+pZgzJCA+CAFjeGrVBqX_Rdcv03zxHa9vos4NrU8NHcQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

On 26 April 2017 at 15:47, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 4/23/17 17:14, Simon Riggs wrote:
>> Workaround for RecoverPreparedTransactions()
>>
>> Force overwriteOK = true while we investigate deeper fix
>
> This is causing a compiler warning. What is the time line on
> reverting/amending this?

I was just working on it actually. Soon. Today.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Peter Eisentraut 2017-04-26 16:10:07 pgsql: Fix query that gets remote relation info
Previous Message Fujii Masao 2017-04-26 15:03:38 pgsql: Fix typo in comment.