| From: | PG Doc comments form <noreply(at)postgresql(dot)org> |
|---|---|
| To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Cc: | oli(dot)sennhauser(at)fromdual(dot)com |
| Subject: | Delayed replication missing in documentation |
| Date: | 2026-07-31 08:51:15 |
| Message-ID: | 178548787563.1228.7091256507204447634@wrigleys.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
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'
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2026-07-31 09:08:31 | References/Links missing |
| Previous Message | David G. Johnston | 2026-07-30 12:45:58 | Re: Shadowing type names because I am not smart |