| Type: | string |
| Context: | postmaster |
| Restart: | true |
| Since: | 12 |
This parameter specifies that recovery should end as soon as a consistent state is reached, i.e., as early as possible. When restoring from an online backup, this means the point where taking the backup ended.
Technically, this is a string parameter, but 'immediate' is currently the only allowed value.
On StackOverflow
- CRITICAL: system ID mismatch, node belongs to a different cluster: 6859654378827691778 != 6859654951670505099
- Java Hibernate insert hypertable in timescaledb is very slow
- Why does "explain analyzing" this query fnish fast (showing a parallel plan), while running the actual query without "explain analyze" doesn't?
- Very slow index creation after turning all PostgreSQL settings
- PostgreSQL 13 sometimes works but sometimes huge execution time
On pgsql-hackers
- Re: Throttling WAL inserts when the standby falls behind more than the configured replica_lag_in_bytes
- Re: [Patch] ALTER SYSTEM READ ONLY
- Re: pg_settings.pending_restart not set when line removed
- Re: how to distinguish between using the server as a standby or for executing a targeted recovery in PG 11?
- Re: [Ext:] Re: Stream Replication not working