From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
---|---|
To: | amit(dot)kapila16(at)gmail(dot)com |
Cc: | sawada(dot)mshk(at)gmail(dot)com, ashutosh(dot)bapat(at)enterprisedb(dot)com, ashutosh(dot)bapat(dot)oss(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Re: Improve description of XLOG_RUNNING_XACTS |
Date: | 2022-09-16 01:55:53 |
Message-ID: | 20220916.105553.548342984445657886.horikyota.ntt@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At Thu, 15 Sep 2022 17:39:17 +0530, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote in
> I see your point but I am still worried due to the concern raised by
> Horiguchi-San earlier in this thread that the total number could be as
> large as TOTAL_MAX_CACHED_SUBXIDS. I think if we want to include
> information only on the number of subxacts then that is clearly an
> improvement without any disadvantage.
>
> Does anyone else have an opinion on this matter?
The doesn't seem to work for Sawada-san's case, but I'm fine with
that:p
Putting an arbitrary upper-bound on the number of subxids to print
might work? I'm not sure how we can determine the upper-bound, though.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2022-09-16 02:22:46 | Re: pg_basebackup's --gzip switch misbehaves |
Previous Message | Andres Freund | 2022-09-16 01:54:38 | warning about missing format string annotations |