Re: Improve description of XLOG_RUNNING_XACTS

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, bharath(dot)rupireddyforpostgres(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-11-01 11:03:41
Message-ID: CAA4eK1+5NdbYJNU_9hgGA1m8ef4+L5izYq8WwLNK_=Ed+_Su5Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 1, 2022 at 12:53 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Mon, Oct 17, 2022 at 02:53:57PM +0900, Michael Paquier wrote:
> > No objections from here if you want to go ahead with v3 and print the
> > full set of subxids on top of the information about these
> > overflowing.
>
> While browsing the CF entries, this was still listed. Amit, any
> updates?
>

I am planning to take care of this entry sometime this week.

--
With Regards,
Amit Kapila.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andy Fan 2022-11-01 11:08:52 Re: Prefetch the next tuple's memory during seqscans
Previous Message Michael Paquier 2022-11-01 10:59:00 Re: Commit fest 2022-11