The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/warm-standby.html Description:
Somewhere here: https://www.postgresql.org/docs/current/warm-standby.html I would expect a few lines about the possibility of delayed replication/delayed standby. After going through all this site I finally ended up googling and found this: https://about.gitlab.com/blog/delayed-replication-for-disaster-recovery-with-postgresql/ So, yes PostgreSQL can do delayed replication. But it is hidden here: https://www.postgresql.org/docs/current/runtime-config-replication.html#GUC-RECOVERY-MIN-APPLY-DELAY What about adding something like: 26.2.10. Delayed Replication When streaming replication is used a standby tries to keep up as fast as possible. But sometime it is desirable for a standby to lag artificially. The most common use case is to not apply Oops-Queries or to not provide the most recent data to a specific user group (freemium business model). This can be achieved with the the configuration: recovery_min_apply_delay = '4h'
