Sorry to revive this post, but I have the same problem:
I set a streaming replication slave with this steps:
1) create a physical replication slot in master
2) pg_basebackup -S slot (...)
3) create a recovery.conf with primary_conninfo, primary_slot_name and
recovery_min_apply_delay = '4d'
4) star
On Sun, May 13, 2018 at 09:42:42AM +0200, Hannes Erven wrote:
> But when new WAL is needed, the standby will fetch /all/ WAL present on the
> master.
Fetching as much WAL as possible when recovery happens is wanted by
design, so as it recovers as much as possible. And that's documented.
> I'd sa
Michael,
Am 2018-05-13 um 08:23 schrieb Michael Paquier:
On Sun, May 13, 2018 at 01:39:48AM +0200, Hannes Erven wrote:
what is Postgresql's strategy when to fetch WAL from the master while in
streaming replication, and could it be tweaked?
Fetching WAL from a primary (or another standby) can
On Sun, May 13, 2018 at 01:39:48AM +0200, Hannes Erven wrote:
> what is Postgresql's strategy when to fetch WAL from the master while in
> streaming replication, and could it be tweaked?
>
> I'm using a physical streaming replication slave to have a database lagging
> behind about one month behind
Hi,
what is Postgresql's strategy when to fetch WAL from the master while in
streaming replication, and could it be tweaked?
I'm using a physical streaming replication slave to have a database
lagging behind about one month behind the primary, by setting
"recovery_target_time" to the desire
