From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, hlinnaka <hlinnaka(at)iki(dot)fi>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Race condition in recovery? |
Date: | 2021-05-23 08:49:18 |
Message-ID: | CAFiTN-vXOT4eP0fzY5MEck0gTebTFCa52bbefJQwHOpus+TEMA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, May 22, 2021 at 8:33 PM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> > For my original case, both standby1 and standby2 are connected to the
> > primary. Now, standby1 is promoted and standby2 is shut down. And,
> > before restarting, all the local WAL of the standby2 is removed so
> > that it can follow the new primary. The primary info and restore
> > command for standby2 are changed as per the new primary(standby1).
>
> One thing I don't understand is why the final WAL segment from the
> original primary didn't end up in the archive in this scenario. If it
> had, then we would not have seen the issue in that case.
I used different archive folders for primary and new
primary(standby1). I have modified your test.sh slightly (modified
test2.sh attached) so that I can demonstrate my scenario where I was
seeing the issue and this is getting fixed after putting the fix we
discussed[1]
[1]
-
expectedTLEs = readTimeLineHistory(receiveTLI);
+
expectedTLEs = readTimeLineHistory(recoveryTargetTLI);
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
Attachment | Content-Type | Size |
---|---|---|
test2.sh | application/x-shellscript | 1.7 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Nitin Jadhav | 2021-05-23 09:49:07 | Re: Multi-Column List Partitioning |
Previous Message | Michael Paquier | 2021-05-23 08:38:31 | Re: Subscription tests fail under CLOBBER_CACHE_ALWAYS |