Dear Alexander, Fujii-san, > 038_walsnd_shutdown_timeout_subscriber.log doesn't really contain the > expected warning: > 2026-05-29 21:11:58.777 CEST [2273817][logical replication apply > worker][124/2:0] LOG: logical replication apply worker for subscription > "test_sub" has started > 2026-05-29 21:12:03.232 CEST [2271870][client backend][4/6:0] LOG: > statement: BEGIN; > 2026-05-29 21:12:03.232 CEST [2271870][client backend][4/6:0] LOG: > statement: LOCK TABLE test_tab IN EXCLUSIVE MODE; ...
To confirm; IIUC the warning should be contained on the publisher log, not the subscriber side. And below log appeared on the publisher; ``` 2026-05-29 21:12:03.426 CEST [2275591][walsender][26/1:0] FATAL: canceling authentication due to timeout 2026-05-29 21:12:03.432 CEST [2273580][checkpointer][:0] LOG: shutting down ``` Is there a possibility that walsender was shut down during the authentication, especially in-between BackendInitialize() and end of PerformAuthentication()? > I think this can be explained by the fact that walrcv->ready_to_display > is set before WalReceiverMain's loop reached. I've reproduced this test > failure with: Verified it could reproduce the failure, but there were no "canceling authentication due to timeout" in the publisher log on my env. Best regards, Hayato Kuroda FUJITSU LIMITED
