Re: BUG #17903: There is a bug in the KeepLogSeg() - Mailing list pgsql-bugs

From Kyotaro Horiguchi
Subject Re: BUG #17903: There is a bug in the KeepLogSeg()
Date
Msg-id 20230425.131452.517547289278432754.horikyota.ntt@gmail.com
Whole thread Raw
In response to Re: BUG #17903: There is a bug in the KeepLogSeg()  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: BUG #17903: There is a bug in the KeepLogSeg()
List pgsql-bugs
At Mon, 24 Apr 2023 12:14:52 -0700, Nathan Bossart <nathandbossart@gmail.com> wrote in 
> Here is a new version of the patch.  It is fundamentally the same as v2,
> but I've adjusted the comment and commit message a bit.  Barring
> objections, I am planning to commit this (and back-patch to v13) in the
> near future.

> When determining the oldest segment that must be kept for
> replication slots, KeepLogSeg() might calculate a segment number
> ahead of the one for the LSN given to the function.  This causes

Maybe the KeepLogSeg() is a mistake of
XLogGetReplicationSlotMinimumLSN()?

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-bugs by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: Re: BUG #17731: Server doesn't start after abnormal shutdown while creating unlogged tables
Next
From: PG Bug reporting form
Date:
Subject: BUG #17908: plpython_to_hstore() crashes with a non-dict argument