From: Nathan Bossart <nathandbossart@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: dgrowleyml@gmail.com
Cc: kuzmin.db4@gmail.com
Cc: pgsql-hackers@lists.postgresql.org
Subject: Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
Date: Wed, 5 Oct 2022 12:00:55 -0700
Message-ID: <20221005190055.GC201192@nathanxps13> (raw)
In-Reply-To: <2414481.1664983822@sss.pgh.pa.us>
References: <2138765.1664924048@sss.pgh.pa.us>
<2208668.1664927591@sss.pgh.pa.us>
<20221005001531.GC779730@nathanxps13>
<20221005.104103.1560341327554683899.horikyota.ntt@gmail.com>
<2414481.1664983822@sss.pgh.pa.us>
On Wed, Oct 05, 2022 at 11:30:22AM -0400, Tom Lane 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".
+1. It can always be back-patched in the future if there are additional
reports.
--
Nathan Bossart
Amazon Web Services: https://aws.amazon.com
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: nathandbossart@gmail.com, tgl@sss.pgh.pa.us, horikyota.ntt@gmail.com, dgrowleyml@gmail.com, kuzmin.db4@gmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Startup process on a hot standby crashes with an error "invalid memory alloc request size 1073741824" while replaying "Standby/LOCK" records
In-Reply-To: <20221005190055.GC201192@nathanxps13>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox