On Monday, September 7, 2026 2:37 PM Amit Kapila <[email protected]> wrote: > On Fri, Sep 4, 2026 at 3:27 PM Zhijie Hou (Fujitsu) <[email protected]> > wrote: > I have made minor changes in the comments to make them clear. See > attached. > > > > > > > Both 4 and 5 are documented but will it be better to provide this > > > information explicitly, say via Logging when the conflcit_slot is > > > not getting advanced due to any of these reasons? > > > > We can do that. It seems to me we could make this improvement for PG20 > > at this stage. For PG19, I think we can improve the documentation to > > make it a bit clearer instead. Amit and I discussed this off-list, and > > See 0002 for the patch Amit shared to improve the doc. > > Thanks for sharing the doc updates. Can you please fold those in 0001 and > share a combined patch?
Thanks for the changes. I've merged them, here is the updated patch. I confirmed that the patch applies cleanly on PG19 as well. Best Regards, Zhijie Hou
v4-0001-Re-initialize-conflict-slot-xmin-when-a-database-.patch
Description: v4-0001-Re-initialize-conflict-slot-xmin-when-a-database-.patch
