RE: initdb -c "track_commit_timestamp=on" crashes in case of debug build

From: "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com>
To: 'Peter Eisentraut' <peter(at)eisentraut(dot)org>
Cc: "'pgsql-hackers(at)lists(dot)postgresql(dot)org'" <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: RE: initdb -c "track_commit_timestamp=on" crashes in case of debug build
Date: 2025-01-07 01:58:45
Message-ID: OSCPR01MB149661A6C656319A6EFCF85D2F5112@OSCPR01MB14966.jpnprd01.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear Peter,

> Yes, this was previously reported [0] but nothing was done about it. We
> just need to find some place to "do nothing" in bootstrap mode to avoid
> the crash. Your patch seems ok to me for that.

Thanks for giving the old discussion. I couldn't find it. According to the post [1],
there are no similar failures for boolean GUCs.

From this perspective, we do not have to do some fundamental ways to fix this bug,
i.e., my patch is enough.

[1]: https://www.postgresql.org/message-id/0307b599-9528-643d-934c-a7e76d376e94%40enterprisedb.com

Best regards,
Hayato Kuroda
FUJITSU LIMITED

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiro Ikeda 2025-01-07 02:29:12 Re: Doc: fix the rewrite condition when executing ALTER TABLE ADD COLUMN
Previous Message Peter Smith 2025-01-07 01:52:12 Re: Skip collecting decoded changes of already-aborted transactions