| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Ravi Krishna <srkrishna1(at)aol(dot)com> |
| Cc: | Vijaykumar Jain <vjain(at)opentable(dot)com>, bhargavpostgres(at)gmail(dot)com, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Slot issues |
| Date: | 2018-10-14 21:55:56 |
| Message-ID: | 20181014215556.dpdadv5zn7cdkvpx@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi,
On 2018-10-14 17:52:30 -0400, Ravi Krishna wrote:
> The best part in Db2 HADR is that when the standby is catching up with the master after a long time, it will
> start from the last LSN and fetch it from the primary WAL directory (active logs ). If not found, it will look for it
> in the archived logs and start applying from there until the current
> point.
Uh, it works precisely the same in postgres.
> No rep slot business.
You're not forced to use slots. Their purpose is to allow to force the
primary to keep necessary resources around. Which also allows to get rid
of the archive in some setups.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ravi Krishna | 2018-10-14 22:15:52 | Re: Slot issues |
| Previous Message | Andres Freund | 2018-10-14 21:54:36 | Re: Slot issues |