![]() Program terminated with signal SIGABRT, Aborted. LOG: database system is ready to accept connections LOG: invalid record length at 0/21C9FE8: wanted 24, got 0 LOG: database system was not properly shut down automatic recovery in progress LOG: database system was interrupted last known up at 06:37:34 CET LOG: all server processes terminated reinitializing HINT: In a moment you should be able to reconnect to the database and repeat your command. WARNING: terminating connection because of crash of another server processÄETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. LOG: terminating any other active server processes LOG: server process (PID 49666) was terminated by signal 6: Aborted I have tried to find out what commands that are causeing this problem, but have not been able to find it, but I will get some help on Friday to see if we can find out more and make a simple SQL that fails. It seems to work on Postgis 2.5 but it seems to fail on any Postgis 3 version. This happens on with Postgres 12 and Postgres 13 for Os I use CentOS Linux release 8 on all the severs. It seems like no data are lost here because the server does recovery at startup. The pre-data input is little bit more than 200.000 lines with more than 6000 CREATE statements, if I test with the first 100 lines it does not crash. There are no error in the restore_sl_rest_ofdata_pre_data.log ![]() Pg_restore -section=pre-data -format=d -d sl data/sl/schema_sl_rest_ofd/ 2> log/sl/restore_sl_rest_ofdata_pre_data.log ![]() Postgres crashes right after this command. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |