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],
On 06.01.25 14:14, Hayato Kuroda (Fujitsu) wrote:
While working on another thread I found $subject. I've tested only on master,
but I doubt this could happen even on PG16 and 17. You can reproduce by:
```
$ initdb -D data -c "track_commit_timestamp=on"
...
child process was terminated by signal 6
Hi hackers,
While working on another thread I found $subject. I've tested only on master,
but I doubt this could happen even on PG16 and 17. You can reproduce by:
```
$ initdb -D data -c "track_commit_timestamp=on"
...
child process was terminated by signal 6: Aborted
initdb: removing data directo
