Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders

From: Andres Freund <andres(at)anarazel(dot)de>
To: Mark Dilger <hornschnorter(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders
Date: 2017-04-24 22:46:36
Message-ID: 20170424224636.624gmi3saomceb7o@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 2017-04-24 15:41:25 -0700, Mark Dilger wrote:
> The recent fix in 546c13e11b29a5408b9d6a6e3cca301380b47f7f has local variable overwriteOK
> assigned but not used in twophase.c RecoverPreparedTransactions(void). I'm not sure if that's
> future-proofing or an oversight. It seems to be used in other functions. Just FYI.

That's just a temporary workaround while the problem's being analyzed.

- Andres

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2017-04-24 23:04:37 pgsql: doc: update release doc markup instructions
Previous Message Mark Dilger 2017-04-24 22:41:25 Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-04-24 22:59:57 Re: snapbuild woes
Previous Message Mark Dilger 2017-04-24 22:41:25 Re: [COMMITTERS] pgsql: Replication lag tracking for walsenders