| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | nathandbossart(at)gmail(dot)com |
| Cc: | zhjwpku(at)gmail(dot)com, xu(dot)xw2008(at)163(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17903: There is a bug in the KeepLogSeg() |
| Date: | 2023-04-25 04:14:52 |
| Message-ID: | 20230425.131452.517547289278432754.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
At Mon, 24 Apr 2023 12:14:52 -0700, Nathan Bossart <nathandbossart(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2023-04-25 13:00:02 | BUG #17908: plpython_to_hstore() crashes with a non-dict argument |
| Previous Message | Kyotaro Horiguchi | 2023-04-25 03:33:32 | Re: BUG #17731: Server doesn't start after abnormal shutdown while creating unlogged tables |