No core file generated after PostgresNode->start

From: Andy Fan <zhihui(dot)fan1213(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: No core file generated after PostgresNode->start
Date: 2020-05-11 01:48:34
Message-ID: CAKU4AWon1H1wkeRNqjj+dACYq45BrCKU+py2Tx4m=k8ys2-4Cg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jonathan S. Katz 2020-05-11 02:08:46 2020-05-14 Press Release Draft
Previous Message Kyotaro Horiguchi 2020-05-11 01:16:19 A comment fix