Re: [BUG] FailedAssertion in SnapBuildPurgeOlderTxn

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Maxim Orlov <orlovmg(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: [BUG] FailedAssertion in SnapBuildPurgeOlderTxn
Date: 2022-11-22 03:04:23
Message-ID: CAA4eK1JRp1WxS-c50hCNaE_HG53CG+MyYFvLLfiTWLRdEC0Dcg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 22, 2022 at 2:22 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
>
> On 2022-11-21 15:47:12 +0300, Maxim Orlov wrote:
> > After some investigation, I think, the problem is in the snapbuild.c
> > (commit 272248a0c1b1, see [0]). We do allocate InitialRunningXacts
> > array in the context of builder->context, but for the time when we call
> > SnapBuildPurgeOlderTxn this context may be already free'd. Thus,
> > InitialRunningXacts array become array of 2139062143 (i.e. 0x7F7F7F7F)
> > values. This is not caused buildfarm to fail due to that code:
>
> Amit, that does indeed seem to be a problem...
>

I'll look into it.

--
With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Julien Rouhaud 2022-11-22 03:06:52 Re: Proposal: Allow user with pg_monitor role to call pg_stat_reset* functions
Previous Message Hayato Kuroda (Fujitsu) 2022-11-22 03:03:52 RE: wake up logical workers after ALTER SUBSCRIPTION