|
|
|
|
|
|
by oa335
1330 days ago
|
|
|
If the listener is offline, the Postgres will see that a subscriber is behind and mark more of internal data as needing to be retained - this will keep certain maintenance tasks from being run (i.e. VACUUM). If VACUUM is not run for long enough, it will cause a catastrophic failure in your DB. The application can catch up when restarted, if it retains the last WAL position. When it restarts, can asks Postgres to start replaying from that point. |
|
|