Query about 'initdb' error

From: 杨逸存 <1057206466(at)qq(dot)com>
To: pgsql-hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Query about 'initdb' error
Date: 2021-03-18 08:35:48
Message-ID: tencent_B53298C08807961EFDB5ED6411660F9EFE07@qq.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Dear hacker:
&nbsp; &nbsp; 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:&nbsp;
&nbsp; &nbsp; 'performing post-bootstrap initialization ... Segmentation fault (core dumped)'
&nbsp; &nbsp; 'child process exited with exit code 139'

&nbsp; &nbsp;&nbsp;
&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.0x00007ffff7475224 in __GI___libc_write (fd=4, buf=0x555555838910, nbytes=71)&nbsp; &nbsp; at ../sysdeps/unix/sysv/linux/write.c:2727 ../sysdeps/unix/sysv/linux/write.c: No such file or directory.(gdb) bt#0&nbsp; 0x00007ffff7475224 in __GI___libc_write (fd=4, buf=0x555555838910,&nbsp;&nbsp; &nbsp; nbytes=71) at ../sysdeps/unix/sysv/linux/write.c:27#1&nbsp; 0x00007ffff73f028d in _IO_new_file_write (f=0x555555828040,&nbsp;&nbsp; &nbsp; data=0x555555838910, n=71) at fileops.c:1203#2&nbsp; 0x00007ffff73f2021 in new_do_write (to_do=71,&nbsp;&nbsp; &nbsp; 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"...,&nbsp;&nbsp; &nbsp; fp=0x555555828040) at fileops.c:457#3&nbsp; _IO_new_do_write (fp=0x555555828040,&nbsp;&nbsp; &nbsp; 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"...,&nbsp;&nbsp; &nbsp; to_do=71) at fileops.c:433#4&nbsp; 0x00007ffff73ef858 in _IO_new_file_sync (fp=0x555555828040)&nbsp; &nbsp; at fileops.c:813#5&nbsp; 0x00007ffff73e395d in __GI__IO_fflush (fp=0x555555828040) at iofflush.c:40#6&nbsp; 0x000055555555d5ec in setup_dictionary (cmdfd=0x555555828040)&nbsp; &nbsp; at initdb.c:1675#7&nbsp; 0x000055555555f838 in initialize_data_directory () at initdb.c:2909#8&nbsp; 0x0000555555560234 in main (argc=3, argv=0x7fffffffded8) at initdb.c:3228&nbsp; &nbsp; 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.

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2021-03-18 08:47:20 Re: shared-memory based stats collector
Previous Message Drouvot, Bertrand 2021-03-18 08:33:45 Re: Minimal logical decoding on standbys