Re: BUG #17903: There is a bug in the KeepLogSeg()
От | Nathan Bossart |
---|---|
Тема | Re: BUG #17903: There is a bug in the KeepLogSeg() |
Дата | |
Msg-id | 20230421214347.GA1441786@nathanxps13 обсуждение исходный текст |
Ответ на | Re: BUG #17903: There is a bug in the KeepLogSeg() (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
Ответы |
Re: BUG #17903: There is a bug in the KeepLogSeg()
|
Список | pgsql-bugs |
On Fri, Apr 21, 2023 at 10:42:31AM +0900, Kyotaro Horiguchi wrote: > From what I understand, the XLogSegNo calculations are designed > without considering the actual value range. Basically, it assumes that > (XLogSegNo + <any positive int>) can overflow. If we take the actual > value range into account, we can make that change. > > The choice lies on whether we assume the actual value range or not. Yeah, after staring at this some more, I think your proposed fix is the way to go. Alternatively, we could adjust the conditional for the max_slot_wal_keep_size block to if (keep != InvalidXLogRecPtr && keep < recptr) but AFAICT that yields the exact same behavior. -- Nathan Bossart Amazon Web Services: https://aws.amazon.com
В списке pgsql-bugs по дате отправления: