Message-ID: <e4ddf83b-b399-aea4-498d-eb8e35e055e9@dunslane.net>
Date: Thu, 30 Dec 2021 15:35:45 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.2.0
Subject: Re: Why is src/test/modules/committs/t/002_standby.pl flaky?
Content-Language: en-US
To: Thomas Munro <thomas.munro@gmail.com>,
 pgsql-hackers <pgsql-hackers@postgresql.org>
References: 
 <CA+hUKG+OeoETZQ=Qw5Ub5h3tmwQhBmDA=nuNO3KG=zWfUypFAw@mail.gmail.com>
From: Andrew Dunstan <andrew@dunslane.net>
In-Reply-To: 
 <CA+hUKG+OeoETZQ=Qw5Ub5h3tmwQhBmDA=nuNO3KG=zWfUypFAw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/e4ddf83b-b399-aea4-498d-eb8e35e055e9%40dunslane.net>
Precedence: bulk


On 12/30/21 15:01, Thomas Munro wrote:
> Hi,
>
> There's a wait for replay that is open coded (instead of using the
> wait_for_catchup() routine), and sometimes the second of two such
> waits at line 51 (in master) times out after 3 minutes with "standby
> never caught up".  It's happening on three particular Windows boxes,
> but once also happened on the AIX box "tern".
>
>     branch     |  animal   | count
> ---------------+-----------+-------
>  HEAD          | drongo    |     1
>  HEAD          | fairywren |     8
>  REL_10_STABLE | drongo    |     3
>  REL_10_STABLE | fairywren |    10
>  REL_10_STABLE | jacana    |     3
>  REL_11_STABLE | drongo    |     1
>  REL_11_STABLE | fairywren |     4
>  REL_11_STABLE | jacana    |     3
>  REL_12_STABLE | drongo    |     2
>  REL_12_STABLE | fairywren |     5
>  REL_12_STABLE | jacana    |     1
>  REL_12_STABLE | tern      |     1
>  REL_13_STABLE | fairywren |     3
>  REL_14_STABLE | drongo    |     2
>  REL_14_STABLE | fairywren |     6
>
>  


FYI, drongo and fairywren are run on the same AWS/EC2 Windows Server
2019 instance. Nothing else runs on it.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com