Re: pg_receivewal starting position

Kyotaro Horiguchi <horikyota.ntt@gmail.com>

From: Kyotaro Horiguchi <horikyota.ntt@gmail.com>

To: ronan.dunklau@aiven.io

Cc: bharath.rupireddyforpostgres@gmail.com, michael@paquier.xyz, pgsql-hackers@lists.postgresql.org, sawada.mshk@gmail.com

Date: 2021-10-27T02:20:08Z

Lists: pgsql-hackers

At Wed, 27 Oct 2021 11:17:28 +0900 (JST), Kyotaro Horiguchi <horikyota.ntt@gmail.com> wrote in 
> Each pg_receivewal run stalls for about 10 or more seconds before
> finishing, which is not great from the standpoint of recently
> increasing test run time.
> 
> Maybe we want to advance LSN a bit, after taking $nextlsn then pass
> "-s 1" to pg_receivewal.

Hmm. Sorry, my fingers slipped.  We don't need '-s 1' for this purpose.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center

Commits

Add TAP test for pg_receivewal with timeline switch
- 0f9b9938a036 15.0 landed
Speed up TAP tests of pg_receivewal
- d680992af540 15.0 landed
Allow pg_receivewal to stream from a slot's restart LSN
- f61e1dd2cee6 15.0 landed
Add replication command READ_REPLICATION_SLOT
- b4ada4e19fd7 15.0 landed
doc: Describe calculation method of streaming start for pg_receivewal
- 438d467a5241 10.19 landed
- e6c5f1b45265 11.14 landed
- fb1aa489e481 12.9 landed
- 7c949f1b3aab 13.5 landed
- affec9f6a2de 14.1 landed
- 1e9475694b0a 15.0 landed
Add PostgresNode::command_fails_like()
- de1d4fef71cb 15.0 landed