| From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | Jeevan Ladhe <jeevan(dot)ladhe(at)enterprisedb(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: warning in twophase.c |
| Date: | 2017-04-25 07:21:53 |
| Message-ID: | fc1f88a8-0b19-3367-47bb-dd2b41fa7511@lab.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2017/04/25 16:16, Jeevan Ladhe wrote:
> I have also been seeing this warning lately, I had tried to check git log,
> and
> seems like following commit 546c13e11b29 by Simon has introduced it.
>
> But per the commit log, this seems to be a temporary arrangement:
>
> commit 546c13e11b29a5408b9d6a6e3cca301380b47f7f
> Author: Simon Riggs <simon(at)2ndQuadrant(dot)com>
> Date: Sun Apr 23 22:12:01 2017 +0100
>
> Workaround for RecoverPreparedTransactions()
>
> Force overwriteOK = true while we investigate deeper fix
>
> Proposed by Tom Lane as temporary measure, accepted by me
>
> With latest update on following thread, it seems like Simon has proposed a
> fix that gets rid of flag overwriteOK:
>
> http://www.postgresql-archive.org/StandbyRecoverPreparedTransactions-recovers-subtrans-links-incorrectly-td5957751.html#a5957853
I see, thanks.
Regards,
Amit
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kyotaro HORIGUCHI | 2017-04-25 08:01:03 | Re: statement_timeout is not working as expected with postgres_fdw |
| Previous Message | Jeevan Ladhe | 2017-04-25 07:16:45 | Re: warning in twophase.c |