From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Why is src/test/modules/committs/t/002_standby.pl flaky? |
Date: | 2021-12-30 20:35:45 |
Message-ID: | e4ddf83b-b399-aea4-498d-eb8e35e055e9@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2021-12-30 22:16:34 | Re: Column Filtering in Logical Replication |
Previous Message | Melanie Plageman | 2021-12-30 20:30:50 | Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?) |