Hi All, I posted about this last year [1] -- sharing our experience hitting WAL archival gaps in production and asking for last_archived_wal to be surfaced on the standby via keep-alive messages.
Glad to see Andrey's patch reviving this. If the full shared mode lands, great. But even if that's too much for now, just exposing last_archived_wal on the standby -- in pg_stat_wal_receiver or anywhere queryable -- would unblock everyone solving this problem externally. [1] https://www.postgresql.org/message-id/flat/CAO7WNRTBrPn0WU9GTimoK-0FHRynaUHa34%3DAp5puCzEipNymFg%40mail.gmail.com Thanks, Harinath
