Query about 'initdb' error - Mailing list pgsql-hackers

From 杨逸存
Subject Query about 'initdb' error
Date
Msg-id tencent_B53298C08807961EFDB5ED6411660F9EFE07@qq.com
Whole thread Raw
Responses Re: Query about 'initdb' error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Dear hacker:
    I am a student from Nanjing University. I have some troubles about command 'initdb'. After I modify sth about system catalog, I use initdb to init the database. But it caused this problem: 
    'performing post-bootstrap initialization ... Segmentation fault (core dumped)'
    'child process exited with exit code 139'
    
    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.
0x00007ffff7475224 in __GI___libc_write (fd=4, buf=0x555555838910, nbytes=71)
    at ../sysdeps/unix/sysv/linux/write.c:27
27 ../sysdeps/unix/sysv/linux/write.c: No such file or directory.
(gdb) bt
#0  0x00007ffff7475224 in __GI___libc_write (fd=4, buf=0x555555838910, 
    nbytes=71) at ../sysdeps/unix/sysv/linux/write.c:27
#1  0x00007ffff73f028d in _IO_new_file_write (f=0x555555828040, 
    data=0x555555838910, n=71) at fileops.c:1203
#2  0x00007ffff73f2021 in new_do_write (to_do=71, 
    data=0x555555838910 " * string literal (including a function body!) or a multiline comment.\n\n\n\nguage';\nge';\n;\n;\nrministic, collencoding, collcollate, collctype)VALUES (pg_nextoid('pg_catalog.pg_collation', 'oid', 'pg_cata"..., 
    fp=0x555555828040) at fileops.c:457
#3  _IO_new_do_write (fp=0x555555828040, 
    data=0x555555838910 " * string literal (including a function body!) or a multiline comment.\n\n\n\nguage';\nge';\n;\n;\nrministic, collencoding, collcollate, collctype)VALUES (pg_nextoid('pg_catalog.pg_collation', 'oid', 'pg_cata"..., 
    to_do=71) at fileops.c:433
#4  0x00007ffff73ef858 in _IO_new_file_sync (fp=0x555555828040)
    at fileops.c:813
#5  0x00007ffff73e395d in __GI__IO_fflush (fp=0x555555828040) at iofflush.c:40
#6  0x000055555555d5ec in setup_dictionary (cmdfd=0x555555828040)
    at initdb.c:1675
#7  0x000055555555f838 in initialize_data_directory () at initdb.c:2909
#8  0x0000555555560234 in main (argc=3, argv=0x7fffffffded8) at initdb.c:3228
    I am not able to fully recognize the insight of backtrace, but it's strange that it receives 'signal SIGPIPE, Broken pipe'.
    Looking forward to your reply. Yours sincerely.

pgsql-hackers by date:

Previous
From: "Drouvot, Bertrand"
Date:
Subject: Re: Minimal logical decoding on standbys
Next
From: Magnus Hagander
Date:
Subject: Re: SSL SNI