| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Shubhang Joshi <shubhangjoshi2405(at)gmail(dot)com>, OMPRAKASH SAHU <sahuop2121(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: WAL replay is too slow on secondary server |
| Date: | 2025-10-30 12:15:03 |
| Message-ID: | ce7a0632877f187246a96bde9c41e590c8986703.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Thu, 2025-10-30 at 17:08 +0530, Shubhang Joshi wrote:
> On Thu, 30 Oct, 2025, 10:07 am OMPRAKASH SAHU, <sahuop2121(at)gmail(dot)com> wrote:
> > We have a postgresql cluster setup using patroni.
> > The DB is being used for heavy transactional application, now the problem is that on replica server WAL replay is too slow.
> > We have increased the IOPS to 6k and Throughput to 600 on nvme EBS volume of wal directory and 10k &800 on data directory.
> >
> > but the WAL is being accumulated on the replica as usual and applying wal is having no improvement.
>
> Please check the network speed — we faced a similar issue earlier, and it turned out to be related to network performance.
> Kindly verify the network latency with your network team as well.
If WAL is piling up on the standby, how can network speed be the problem?
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2025-10-30 13:38:50 | Re: Replication Question / Issue - PRIMARY with SYNC and ASYNC Replication |
| Previous Message | Shubhang Joshi | 2025-10-30 11:38:06 | Re: WAL replay is too slow on secondary server |