Re: Unnecessary delay in streaming replication due to replay lag

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Asim Praveen <pasim@vmware.com>

Cc: PostgreSQL mailing lists <pgsql-hackers@postgresql.org>, "Hao Wu (Pivotal)" <hawu@pivotal.io>

Date: 2020-08-09T08:41:15Z

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 Sun, Aug 09, 2020 at 05:54:32AM +0000, Asim Praveen wrote:
> I would like to revive this thready by submitting a rebased patch to
> start streaming replication without waiting for startup process to
> finish replaying all WAL.  The start LSN for streaming is determined
> to be the LSN that points to the beginning of the most recently
> flushed WAL segment.
> 
> The patch passes tests under src/test/recovery and top level “make check”.

I have not really looked at the proposed patch, but it would be good
to have some documentation.
--
Michael