Re: Reporting WAL replay progress during pre-consistency standby reovery

On Mon, 9 Nov 2026 at 10:11, Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com> wrote:
>
> > v1 applies cleanly to current master and builds without warnings.
> >
> > I think this is worth having and have a few comments:
>
> Thanks for supporting the proposal, reviewing the patch, and catching
> these issues. I appreciate the detailed analysis and testing.
>
> I have attached v2 with both changes. I restored the unconditional
> disable_startup_progress_timeout() call in EnableStandbyMode() and
> removed the log_startup_progress_interval == 0 check from
> disable_startup_progress_timeout().
>
> I also tested reloading the interval from one second to zero during
> pre-consistency replay and confirmed that the timer stops firing after
> consistency.
>
> Please review the v2 patch and let me know if you have any other comments.
>
> Best Regards,
> Nitin Jadhav
> Microsoft

Hi!
During recovery, if you try to connect to the database via psql, you
will get an error message: "the database system is not yet accepting
connection"/"Consistent recovery state has not been yet reached." etc.
What if we report the current replay LSN here?

--
Best regards,
Kirill Reshke