Re: BUG #18945: Standby synchronization problem

From: Dilip Kumar <dilipbalaut(at)gmail(dot)com>
To: lucasmarola(at)hotmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18945: Standby synchronization problem
Date: 2025-06-02 13:12:08
Message-ID: CAFiTN-u0kuSwypDDChK4Po+4hAtm8HO94EoNCtDwPvBGw7R3Tg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Mon, Jun 2, 2025 at 5:56 PM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference: 18945
> Logged by: lucas marola
> Email address: lucasmarola(at)hotmail(dot)com
> PostgreSQL version: 16.8
> Operating system: Red Hat Enterprise Linux release 9.5 (Plow)
> Description:
>
> Sometimes, the WAL application on the standby environment takes a long time
> to complete. However, after restarting the application process, it returns
> to normal.

it's difficult to pinpoint the exact problem with the information
provided. However, a common scenario involves read-only queries on a
standby database conflicting with the WAL apply process. And as a
result of restarting the application it will terminate all the backend
so you are not facing issues of conflict any more. You can check the
value of 'max_standby_streaming_delay' as this will control how long
the WAL apply process should wait in case of a conflict with the
snapshot of the local queries. If you have steps to reproduce/or more
details on the exact scenario, then that would be helpful.

--
Regards,
Dilip Kumar
Google

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Matheus Alcantara 2025-06-02 14:05:12 Re: BUG #18920: LOAD '$libdir/plugins' no longer works in 18beta1
Previous Message PG Bug reporting form 2025-06-02 12:18:58 BUG #18945: Standby synchronization problem