| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | RKN Sai Krishna <rknsaiforpostgres(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Query regarding replication slots |
| Date: | 2022-01-11 11:37:47 |
| Message-ID: | 20220111113747.7mk4stfbxo4zobqc@jrouhaud |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jan 11, 2022 at 04:48:59PM +0530, RKN Sai Krishna wrote:
> Hi All,
>
> I have a very basic question related to replication slots. Why should
> the master/primary server maintain the replication slot info like lsn
> corresponding to each standby server etc. Instead, why can't each
> standby server send the lsn that it needs, and master/primary server
> maintain the minimum lsn across all of the standby servers so that the
> information could be used for cleanup/removal of WAL segments?
Because the information is needed even if the standby servers are not
available, and if you only have a global xmin then you can't do much when
removing one of the slots.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Julien Rouhaud | 2022-01-11 11:47:00 | Re: ICU for global collation |
| Previous Message | Daniel Verite | 2022-01-11 11:36:46 | Re: ICU for global collation |