No core file generated after PostgresNode->start - Mailing list pgsql-hackers

From Andy Fan
Subject No core file generated after PostgresNode->start
Date
Msg-id CAKU4AWon1H1wkeRNqjj+dACYq45BrCKU+py2Tx4m=k8ys2-4Cg@mail.gmail.com
Whole thread Raw
Responses Re: No core file generated after PostgresNode->start
List pgsql-hackers
Hi:

When I run make -C subscription check,  then I see the following logs
in ./tmp_check/log/013_partition_publisher.log 

2020-05-11 09:37:40.778 CST [69541] sub_viaroot WARNING:  terminating 
connection because of crash of another server process

2020-05-11 09:37:40.778 CST [69541] sub_viaroot DETAIL:  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.

However there is no core file generated. In my other cases(like start pg
manually with bin/postgres xxx) can  generate core file successfully at 
the same machine.  What might be the problem for PostgresNode case? 

I tried this modification, but it doesn't help.

--- a/src/test/perl/PostgresNode.pm
+++ b/src/test/perl/PostgresNode.pm
@@ -766,7 +766,7 @@ sub start

                # Note: We set the cluster_name here, not in postgresql.conf (in
                # sub init) so that it does not get copied to standbys.
-               $ret = TestLib::system_log('pg_ctl', '-D', $self->data_dir, '-l',
+               $ret = TestLib::system_log('pg_ctl', "-c", '-D', $self->data_dir, '-l',
                        $self->logfile, '-o', "--cluster-name=$name", 'start');
        }

Best Regards
Andy Fan

pgsql-hackers by date:

Previous
From: Kyotaro Horiguchi
Date:
Subject: A comment fix
Next
From: "Jonathan S. Katz"
Date:
Subject: 2020-05-14 Press Release Draft