From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | thunder1(at)126(dot)com |
Cc: | robertmhaas(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: [BUG] standby node can not provide service even it replays all log files |
Date: | 2019-10-23 04:18:27 |
Message-ID: | 20191023.131827.2210460300407362091.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At Wed, 23 Oct 2019 12:51:19 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> Hello.
>
> At Tue, 22 Oct 2019 20:42:21 +0800 (CST), Thunder <thunder1(at)126(dot)com> wrote in
> > Update the patch.
> >
> > 1. The STANDBY_SNAPSHOT_PENDING state is set when we replay the first XLOG_RUNNING_XACTS and the sub transaction ids are overflow.
> > 2. When we log XLOG_RUNNING_XACTS in master node, can we assume that all xact IDS < oldestRunningXid are considered finished?
>
> Unfortunately we can't. Standby needs to know that the *standby's*
> oldest active xid exceeds the pendig xmin, not master's. And it is
> already processed in ProcArrayApplyRecoveryInfo. We cannot assume that
> the oldest xids are not same on the both side in a replication pair.
Could we send a full xid list after new standby comes in? Or can
START_REPLICATION return it?
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | vignesh C | 2019-10-23 04:42:32 | Re: Ordering of header file inclusion |
Previous Message | Michael Paquier | 2019-10-23 03:51:33 | Re: [PATCH] Do not use StdRdOptions in Access Methods |