From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: pgsql-docs@lists.postgresql.org
Subject: Re: The description for pg_replication_slots.restart_lsn
Date: Wed, 24 Jun 2020 21:00:16 -0400
Message-ID: <20200625010016.GA22779@alvherre.pgsql> (raw)
In-Reply-To: <6497f1e9-3148-c5da-7e49-b2fddad9a42f@oss.nttdata.com>
On 2020-Jun-17, Fujii Masao wrote:
> 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.
We just added the invalidated_at LSN to replication slots; while working
on the tests for that today, I was thinking that it might be useful to
display that LSN in pg_replication_slots. What do you think of the idea
of publishing the invalidated_at LSN in pg_replication_slot.restart_lsn
when the slot is invalid?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-docs@postgresql.org
Cc: alvherre@2ndquadrant.com, masao.fujii@oss.nttdata.com, pgsql-docs@lists.postgresql.org
Subject: Re: The description for pg_replication_slots.restart_lsn
In-Reply-To: <20200625010016.GA22779@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox