Re: Unnecessary delay in streaming replication due to replay lag

Daniel Gustafsson <daniel@yesql.se>

From: Daniel Gustafsson <daniel@yesql.se>

To: Soumyadeep Chakraborty <soumyadeep2007@gmail.com>

Cc: Michael Paquier <michael@paquier.xyz>, pgsql-hackers <pgsql-hackers@postgresql.org>, "lchch1990@sina.cn" <lchch1990@sina.cn>, Asim Praveen <pasim@vmware.com>, Masahiko Sawada <masahiko.sawada@2ndquadrant.com>, "Hao Wu (Pivotal)" <hawu@pivotal.io>, "ahsan.hadi" <ahsan.hadi@highgo.ca>, Anastasia Lubennikova <a.lubennikova@postgrespro.ru>, Ashwin Agrawal <ashwinstar@gmail.com>

Date: 2021-11-15T09:59:04Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Generate GUC tables from .dat file
- 63599896545c 19 (unreleased) cited
Skip WAL recycling and preallocation during archive recovery.
- cc2c7d65fc27 15.0 cited
Fix scenario where streaming standby gets stuck at a continuation record.
- 066871980183 11.0 cited

> On 10 Nov 2021, at 00:41, Soumyadeep Chakraborty <soumyadeep2007@gmail.com> wrote:

> Thanks for the detailed review! Attached is a rebased patch that addresses
> most of the feedback.

This patch no longer applies after e997a0c64 and associated follow-up commits,
please submit a rebased version.

--
Daniel Gustafsson		https://vmware.com/