| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | amit(dot)kapila16(at)gmail(dot)com, 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-10-03 08:15:45 |
| Message-ID: | YzqaMYVHe/lPRnNI@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Sep 16, 2022 at 10:55:53AM +0900, Kyotaro Horiguchi wrote:
> 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.
You could hardcode it so as it does not blow up the whole view, say
20~30. Anyway, I agree with the concern raised upthread about the
amount of extra data this would add to the output, so having at least
the number of subxids would be better than the existing state of
things telling only if the list of overflowed. So let's stick to
that.
Here is another idea for the list of subxids: show the full list of
subxids only when using --xid. We could always introduce an extra
switch, but that does not seem worth the extra workload here.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2022-10-03 08:49:23 | Re: Improve description of XLOG_RUNNING_XACTS |
| Previous Message | Masahiko Sawada | 2022-10-03 08:01:16 | Re: Small miscellaneous fixes |