From: Nathan Bossart <nathandbossart@gmail.com>
To: Noah Misch <noah@leadboat.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Fix early elog(FATAL)
Date: Fri, 13 Dec 2024 22:16:39 -0600
Message-ID: <Z10Gp-ryW44JGnYo@nathan> (raw)
In-Reply-To: <Z10GM5BBojDI3u14@nathan>
References: <20241208034614.45.nmisch@google.com>
<Z1i-K95hTcggVOgn@nathan>
<20241212033414.e0.nmisch@google.com>
<Z1sKJBE6-Lo08PEt@nathan>
<20241214031505.05.nmisch@google.com>
<Z10GM5BBojDI3u14@nathan>
On Fri, Dec 13, 2024 at 10:14:43PM -0600, Nathan Bossart wrote:
> On Fri, Dec 13, 2024 at 07:15:05PM -0800, Noah Misch wrote:
>> I don't feel strongly either way. I did write it the option-1 way originally.
>> Then I started thinking about changes at a distance causing the other
>> InitProcessGlobals() tasks to palloc or elog. We could do option-1 in master
>> and keep the back branches in their current state.
>
> I don't feel strongly either way, either. I don't think it's important
> enough to diverge from the back-branches.
Also, thank you for fixing this.
--
nathan
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-hackers@postgresql.org
Cc: nathandbossart@gmail.com, noah@leadboat.com
Subject: Re: Fix early elog(FATAL)
In-Reply-To: <Z10Gp-ryW44JGnYo@nathan>
* 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