Re: BUG #19028: INITDB fails post-bootstrap initialization with FATAL " " is not a valid binary digit at character 1

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: KAZAR Ayoub <ma_kazar(at)esi(dot)dz>
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19028: INITDB fails post-bootstrap initialization with FATAL " " is not a valid binary digit at character 1
Date: 2025-08-22 02:16:40
Message-ID: CA+hUKGKyjaYumC9wxCRGnBySJpVBURcpF1f48BGgbk+YUjo+GA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Aug 21, 2025 at 5:03 PM KAZAR Ayoub <ma_kazar(at)esi(dot)dz> wrote:
> This was fixed after doing a clean compilation of master which i forgot about only after reporting it, this bug is not valid anymore while i still find it interesting to understand the reason why it was happening.

I vaguely recall problems when lexer or parser code had been generated
by different binaries, when I'd changed the PATH or upgraded some
packages or something like that. (Older branches had a related
footgun built in, see 721856ff, but you said this is master.) The
symptom I recall was a psql that would crash in the slash lexer so may
be completely unrelated... just mentioning it since you said a clean
build did the trick.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Xuneng Zhou 2025-08-22 03:25:47 Re: BUG #19006: Assert(BufferIsPinned) in BufferGetBlockNumber() is triggered for forwarded buffer
Previous Message Michael Paquier 2025-08-21 21:36:56 Re: "unexpected duplicate for tablespace" problem in logical replication