On 2020/06/30 14:56, Fujii Masao wrote:
On 2020/06/25 14:48, Fujii Masao wrote:
On 2020/06/25 10:00, Alvaro Herrera wrote:
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
On 2020/06/25 14:48, Fujii Masao wrote:
On 2020/06/25 10:00, Alvaro Herrera wrote:
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
On 2020/06/25 10:00, Alvaro Herrera wrote:
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 r
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 t
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.
Bu
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
