On Wed, Apr 16, 2025 at 1:00 PM Alexander Lakhin <exclus...@gmail.com> wrote: > 16.04.2025 06:05, Richard Guo wrote: > On Wed, Apr 16, 2025 at 11:54 AM Richard Guo <guofengli...@gmail.com> wrote: > I noticed this recoveryCheck test failure on flaviventris after > pushing commit 3b35f9a4c (Fix an incorrect check in get_memoize_path). > ... > I'm not convinced this failure is related to 3b35f9a4c; it seems > unlikely that just changing how Memoize paths are created would cause > it. > > Does anyone have any insights into what might be going on?
> Forgot to include the link to the failure. Here it is: > > https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=flaviventris&dt=2025-04-16%2001%3A58%3A42 > Judging by: > ### Restarting node "standby" > # Running: pg_ctl --wait --pgdata > /home/bf/bf-build/flaviventris/HEAD/pgsql.build/testrun/recovery/035_standby_logical_decoding/data/t_035_standby_logical_decoding_standby_data/pgdata > --log > /home/bf/bf-build/flaviventris/HEAD/pgsql.build/testrun/recovery/035_standby_logical_decoding/log/035_standby_logical_decoding_standby.log > restart > waiting for server to shut > down........................................................................................................................................................................................................................................................................................................................................................................... > failed > pg_ctl: server does not shut down > > I think it's a known issue: > https://wiki.postgresql.org/wiki/Known_Buildfarm_Test_Failures#001_rep_changes.pl_fails_due_to_publisher_stuck_on_shutdown > and is not related to the Memoize paths. Got it. Thanks for the information. Thanks Richard
