Re: Unnecessary delay in streaming replication due to replay lag

Soumyadeep Chakraborty <soumyadeep2007@gmail.com>

From: Soumyadeep Chakraborty <soumyadeep2007@gmail.com>

To: Daniel Gustafsson <daniel@yesql.se>

Cc: Michael Paquier <michael@paquier.xyz>, pgsql-hackers <pgsql-hackers@postgresql.org>, "lchch1990@sina.cn" <lchch1990@sina.cn>, 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-19T08:35: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

Attachments

v4-0001-Introduce-feature-to-start-WAL-receiver-eagerly.patch (text/x-patch) patch v4-0001

Hi Daniel,

Thanks for checking in on this patch.
Attached rebased version.

Regards,
Soumyadeep (VMware)