Re: BUG #16678: The ecpg connect/test5 test sometimes fails on Windows

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: exclusion(at)gmail(dot)com
Cc: tgl(at)sss(dot)pgh(dot)pa(dot)us, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16678: The ecpg connect/test5 test sometimes fails on Windows
Date: 2020-10-26 01:12:18
Message-ID: 20201026.101218.590594677882784230.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

At Sun, 25 Oct 2020 08:00:00 +0300, Alexander Lakhin <exclusion(at)gmail(dot)com> wrote in
> And regarding the src/test/recovery test failure with a 10 ms delay
> added... I've increased a log level and get probably the same behaviour
> as described in
> https://www.postgresql.org/message-id/flat/OFCA523F90.7499E22F-ON4325828E.005573C4-4325828E.0055B412%40iba.by
> The primary node can't finish smart shutdown and logs of the primary and
> the standby are filling with the following messages:
...
>  
> Though the patch proposed by Kyotaro Horiguchi doesn't help. It this
> looks like an issue that should be fixed, I can investigate it further.

Yeah, that patch just rejects to start from a wrong backup. If a
specific legit operation makes such a backup, it should be fixed.

regareds.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Amit Langote 2020-10-26 03:11:23 Re: BUG #16644: null value for defaults in OLD variable for trigger
Previous Message Tom Lane 2020-10-25 20:53:35 Re: BUG #16644: null value for defaults in OLD variable for trigger