Re: Query about 'initdb' error

"=?gb18030?B?0e7S3bTm?=" <1057206466(at)qq(dot)com> writes:
> &nbsp; &nbsp; When I do 'make' and 'make install', there is no warning or error infomation appeared. Compilation step seems to have no problem. Also, I use gdb to backtrace initdb, the result is as below:

> performing post-bootstrap initialization ... Segmentation fault (core dumped)
> Program received signal SIGPIPE, Broken pipe.

> I am not able to fully recognize the insight of backtrace, but it's
> strange that it receives 'signal SIGPIPE, Broken pipe'.&nbsp; &nbsp;
> Looking forward to your reply. Yours sincerely.

At this phase, initdb is just shoving SQL commands down a pipe to a
"standalone backend" that's doing the real work. Evidently your
backend dumped core, and you need to be looking at that dump not
initdb itself. Depending on how your machine is set up, you might
need to use initdb's --noclean option to keep it from throwing away
the incomplete data directory, as the backend might have dropped core
in there.

regards, tom lane