Re: Fix early elog(FATAL)

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Noah Misch <noah(at)leadboat(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Fix early elog(FATAL)
Date: 2024-12-14 04:16:39
Message-ID: Z10Gp-ryW44JGnYo@nathan
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2024-12-14 05:08:57 Re: Proposal for Updating CRC32C with AVX-512 Algorithm.
Previous Message Nathan Bossart 2024-12-14 04:14:43 Re: Fix early elog(FATAL)