Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records - Mailing list pgsql-hackers

From Kyotaro Horiguchi
Subject Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
Date
Msg-id 20221011.154824.2222289551494538331.horikyota.ntt@gmail.com
Whole thread Raw
List pgsql-hackers
> On Wed, 5 Oct 2022 at 16:30, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > One other point to discuss: should we consider back-patching?  I've
> > got mixed feelings about that myself.  I don't think that cases where
> > this helps significantly are at all mainstream, so I'm kind of leaning
> > to "patch HEAD only".

At Mon, 10 Oct 2022 13:24:34 +0100, Simon Riggs <simon.riggs@enterprisedb.com> wrote in 
> It looks fine to eventually backpatch, since StandbyReleaseLockTree()
> was optimized to only be called when the transaction had actually done
> some AccessExclusiveLocks.
> 
> So the performance loss is minor and isolated to the users of such
> locks, so I see no problems with it.

At Wed, 5 Oct 2022 12:00:55 -0700, Nathan Bossart <nathandbossart@gmail.com> wrote in 
> +1.  It can always be back-patched in the future if there are additional
> reports.

The third +1 from me.

regards.

-- 
Kyotaro Horiguchi
NTT Open Source Software Center



pgsql-hackers by date:

Previous
From: Peter Smith
Date:
Subject: Re: create subscription - improved warning message
Next
From: Amit Kapila
Date:
Subject: Re: Add common function ReplicationOriginName.