Re: Parallelize WAL Sender and WAL receiver

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 




> On Sep 4, 2024, at 9:03 PM, Karthik Yellapragada <karthik.yellapragada@xxxxxxxxx> wrote:
> 
> Hello all,
> 
> I frequently face the problem of wals generated faster than the wals transferred and applied.
> 
> Is there a way to speed up the process? So I don’t accumulate a lot of WALs at the primary?
> 
> Regards,
> Karthik.

What do you mean by parallelized WAL sender? Do you have many replicas connecting to the primary? Have you tried cascading replication?

What’s the network between the systems? Is a WAN with high latency? Can the replica pull from the WAL file from an archive?  For a high latency networks like New York to London; I would terminate the WAL receiver via a script if replication exceeded an acceptable delay to ensure SLA  where met.  It is faster to pull the WAL files from the local archive which where already replicated to London than streaming replication over a high latency WAN.  After It catches up, it will reconnect to streaming replication.  







[Index of Archives]     [Postgresql Home]     [Postgresql General]     [Postgresql Performance]     [Postgresql PHP]     [Postgresql Jobs]     [PHP Users]     [PHP Databases]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Databases]     [Yosemite Forum]

  Powered by Linux