On 1/26/22 18:45, Andrew Dunstan wrote:
> On 1/26/22 16:17, Robert Haas wrote
>> 3. fairywren failed the last run in module-commit_tsCheck. It's unhappy
>> because:
>>
> Intermittent failures give a false positive against the latest set of
> commits. These failures started happening regularly ab
On Wed, Jan 26, 2022 at 04:17:19PM -0500, Robert Haas wrote:
> 1. snapper failed 4 out of the last 5 runs in recoveryCheck. The
> latest run as of this writing shows this:
>
> [19:09:50] t/026_overwrite_contrecord.pl ok43136 ms
> # poll_query_until timed out executing this query:
> #
Kyotaro Horiguchi writes:
> I'm not sure why walsender of the standby continued running not knowing the
> primary has been once dead for such a long time.
Isn't this precisely the problem that made us revert the "graceful
disconnection" patch [1]? Munro seems to have a theory about
why that bro
At Wed, 26 Jan 2022 18:45:53 -0500, Andrew Dunstan wrote
in
> It's very unlikely any of this is your fault. In any case, intermittent
> failures are very hard to nail down.
The primary starts at 2022-01-26 16:30:06.613 the accepted a connectin
from the standby at 2022-01-26 16:30:09.911.
P: 20
On 1/26/22 16:17, Robert Haas wrote
> 3. fairywren failed the last run in module-commit_tsCheck. It's unhappy
> because:
>
> [16:30:02] t/002_standby.pl ok13354 ms ( 0.06 usr 0.00 sys +
> 1.11 cusr 3.20 csys = 4.37 CPU)
> # poll_query_until timed out executing this query:
> # SELECT
