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

From Thomas Munro
Subject Re: BUG #19028: INITDB fails post-bootstrap initialization with FATAL " " is not a valid binary digit at character 1
Date
Msg-id CA+hUKGKyjaYumC9wxCRGnBySJpVBURcpF1f48BGgbk+YUjo+GA@mail.gmail.com
Whole thread Raw
In response to Re: BUG #19028: INITDB fails post-bootstrap initialization with FATAL " " is not a valid binary digit at character 1  (KAZAR Ayoub <ma_kazar@esi.dz>)
List pgsql-bugs
On Thu, Aug 21, 2025 at 5:03 PM KAZAR Ayoub <ma_kazar@esi.dz> wrote:
> This was fixed after doing a clean compilation of master which i forgot about only after reporting it, this bug is
notvalid 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.



pgsql-bugs by date:

Previous
From: Michael Paquier
Date:
Subject: Re: "unexpected duplicate for tablespace" problem in logical replication
Next
From: Xuneng Zhou
Date:
Subject: Re: BUG #19006: Assert(BufferIsPinned) in BufferGetBlockNumber() is triggered for forwarded buffer