From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: The description for pg_replication_slots.restart_lsn |
Date: | 2020-06-25 00:42:47 |
Message-ID: | d6517043-606c-a953-bc66-bca101c5a604@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On 2020/06/17 23:47, Fujii Masao wrote:
> Hi,
>
> The document explains that restart_lsn column in pg_replication_slots view is:
>
> The address (LSN) of oldest WAL which still might be required by
> the consumer of this slot and thus won't be automatically removed
> during checkpoints.
>
> But the latter part is not true in v13 thanks to max_slot_wal_keep_size.
> I think that we need to update it as follows. Thought?
>
> The address (LSN) of oldest WAL which still might be required by
> the consumer of this slot and thus won't be automatically removed
> during checkpoints unless this LSN gets behind more than
> max_slot_wal_keep_size from the current LSN.
>
> Patch attached.
Barring any objection, I will commit this patch.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2020-06-25 01:00:16 | Re: The description for pg_replication_slots.restart_lsn |
Previous Message | Bruce Momjian | 2020-06-24 23:38:37 | Re: Default setting for enable_hashagg_disk |