| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Jakub Wartak <jakub(dot)wartak(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Subject: | Re: Syncrep and improving latency due to WAL throttling |
| Date: | 2023-01-27 08:20:46 |
| Message-ID: | 20230127082046.ydzyufv4xrpkp6t3@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-Jan-27, Bharath Rupireddy wrote:
> Looking at the patch, the feature, in its current shape, focuses on
> improving replication lag (by throttling WAL on the primary) only when
> synchronous replication is enabled. Why is that? Why can't we design
> it for replication in general (async, sync, and logical replication)?
>
> Keeping replication lag under check enables one to provide a better
> RPO guarantee
Hmm, but you can already do that by tuning walwriter, no?
--
Álvaro Herrera
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2023-01-27 08:51:59 | Re: New strategies for freezing, advancing relfrozenxid early |
| Previous Message | Takamichi Osumi (Fujitsu) | 2023-01-27 08:09:24 | RE: Time delayed LR (WAS Re: logical replication restrictions) |