Hello,
At Fri, 26 Jun 2026 09:51:16 +0900, Fujii Masao <[email protected]> wrote
in
> On Fri, Jun 26, 2026 at 2:19 AM Bharath Rupireddy
> <[email protected]> wrote:
> > The use there is referring to the whole set of transaction IDs and how
> > one can visualize the use of them - so "XID space" in that context
> > seems fine to me.
> >
> > But the wraparound warnings read better when they say how many more
> > transaction IDs are left:
> >
> > + errdetail("Approximately %.2f%% of MultiXactIds remain before
> > wraparound.",
> > + errdetail("Approximately %.2f%% of transaction IDs remain before
> > wraparound.",
>
> Okay, I've updated the patches as suggested. The updated patches are attached.
I'm not sure I'm following this correctly, but the explanation above
sounded to me as if the warning should report the number of IDs
remaining before wraparound, e.g. "Approximately N MultiXactIds remain
before wraparound", so I'm a bit confused by the proposed wording.
> + errdetail("Approximately %.2f%% of MultiXactIds remain before wraparound.",
The attached patch adopts that wording. However, I'm not sure how to
interpret it. The value is still expressed as a percentage, but it is
no longer clear what that percentage is relative to.
Whichever approach we choose, I think the wording should be explicit.
If the value is reported as a percentage, then something like "x.xx%
of MultiXactId space remains" seems clearer to me. If it is reported
as a count, then "N MultiXactIds remain" would make more sense.
Regards,
--
Kyotaro Horiguchi
NTT Open Source Software Center
